Update request approvers in Zip after a re-org
Automatically update Zip request approvers after a re-org from a Slack request with Stepwork. Reassign approval chain steps to match the approved org structure.
- Use case
- Data hygiene & cleanupProcurement
- Best for
- Procurement Manager, Finance Operations Manager
- Applications used
Zip
Slack
- Business outcome
- Time savings
The problem
The manager moved on. Their approvals did not.
After a re-org or a role change, Zip approval chains still name the old managers. Requests route to people who changed teams or left, and sit in queues nobody is watching.
Requesters chase approvals in Slack, procurement digs through each chain to find the dead end, and purchases stall for days over a routing problem.
The outcome
Approval chains match the live org chart
Stepwork updates the approval chain assignments in Zip to match the approved org change. The run records who asked, which change it came from, and every chain step it updated.
- The request names the approved org change and the new approvers.
- A name that matches no Zip user stops the run.
- The Slack reply lists each chain step that changed.
The process
From approved re-org to updated approval chains
Procurement posts the approved org change in Slack. Stepwork updates the approvers in Zip, in the same order every time.
- Step 1
Request it in Slack
A procurement manager posts the approved org change: who is leaving each approval role and who takes it over. That message starts the flow, and Stepwork records who asked and when.
- Step 2
Find the affected chains
Stepwork signs in to Zip and finds every approval chain step assigned to each outgoing approver. If a name in the request matches no Zip user, the run stops.
- Step 3
Reassign the approvers
Stepwork replaces each outgoing approver with the new one named in the request, the same edits procurement makes by hand in the workflow settings.
- Step 4
Confirm and reply in Slack
Stepwork checks each updated chain against the request, then posts the list of changes back in Slack.
Why Stepwork
Routing follows today’s org chart
A deterministic agent runs the approver update path you recorded in Zip. It applies the org change your team approved; it does not decide who approves what.
Similar use cases
Similar use cases
- Create a Zip intake request from SlackCreates the purchase request in Zip with vendor, amount, category, and business justification from the requester's details.
Create a requisition in Coupa from an approved requestCreates the requisition in Coupa with supplier, line items, cost center, and justification from the approved intake.- Update a supplier record in Coupa from an approved changeApplies approved supplier record changes — banking, contacts, payment terms — with the change reason documented.
FAQ