The use case: how Delivery Hero deploys n8n
Delivery Hero uses a single n8n workflow to handle employee account recovery requests. The employee's manager approves the request, and automated API calls to Okta, Jira and Google systems then restore access.
More reported results
Figures published in n8n’s case study. They are not independently measured by usedby.
the average time locked out dropped from 35 to 20 mins
TIME TO DEPLOYMENT 5 hours
In the customer’s words
We have seen drastic efficiency improvements since we started using n8n. It’s incredibly powerful, but also simple to useOther AI tools used by Delivery Hero
Other public relationships recorded on usedby.
Explore Delivery Hero’s AI stackn8n users in Logistics & Supply Chain
Companies in the same sector, with public evidence.
See all n8n customersGo straight to the source
Based on n8n’s published case study. We check the public evidence; the results are reported by the vendor.
n8n.io- Last checked
- Oct 7, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 200 hours per monthChecked
Printed word for word on the page, near the name of Delivery Hero.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Delivery Hero.
- Delivery Hero uses n8nChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
With account recovery requests being handled automatically by n8n and managers doing the approval, the average time locked out dropped from 35 to 20 mins. This meant that employees were locked out for a total of 200 hours per month less.





