# How Delivery hero uses n8n

**200 hours per month**: “employees were locked out for a total of 200 hours per month less”

As published on [n8n.io](https://n8n.io/case-studies/delivery-hero/). Captured by usedby on 2026-10-07.

- Company: [Delivery hero](https://www.usedby.ai/companies/delivery-hero.md)
- Tool: [n8n](https://www.usedby.ai/tools/n8n.md)
- Industry: [Logistics & Supply Chain](https://www.usedby.ai/companies/industry/logistics-supply-chain.md)
- Teams: IT service delivery

## What the story says

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.

Summary written by usedby from the source page, in English. The figures are those of n8n and Delivery hero, not ours.

> 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.

- **35 to 20 mins**: “the average time locked out dropped from 35 to 20 mins”
- **5 hours**: “TIME TO DEPLOYMENT 5 hours”

> We have seen drastic efficiency improvements since we started using n8n. It’s incredibly powerful, but also simple to use
>
> Dennis Zahrt, Director of Global IT Service Delivery

## What usedby checked

We compared the story with its live page on 2026-10-07.

- Checked: the figure 200 hours per month is printed word for word on the page, near the name of Delivery hero.
- Checked: the passage quoted above is copied word for word from the page, near the name of Delivery hero.
- Checked: each number in our summary is printed on the page.
- Checked: Delivery hero uses n8n. Confirmed line. Latest check across sources: 2026-10-07.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/delivery-hero-n8n · How we check: https://www.usedby.ai/methodology