@Dash right now a new hire in Workday goes to a Google Sheet, then Zapier, then it starts the onboarding checklist. It breaks about once a month. Could we get rid of the Zapier step?
Live in Slack or Microsoft Teams
Onboard from Workday without a Zapier chain
The old path was Workday to a spreadsheet to Zapier to the checklist, and it broke whenever a field name changed. Dash reads the new hire record directly and starts the onboarding run itself, so there is no middle layer to maintain or debug.
Get started for free Chat with Dash, the AI teammate that works inside Slack and Microsoft Teams.
Yes, and the sheet too. I can read the Workday record and start the onboarding run directly.
Today · Workday → Google Sheet → Zapier → checklist · 3 hops, 2 places to break
Instead · Workday → run started · 1 hop
Instead · Workday → run started · 1 hop
I looked at why it breaks. The last four failures were all the same cause: a field renamed in Workday, which the sheet accepted silently and Zapier then mapped to nothing. Nobody found out until a new hire had no checklist on day one.
Reading the record directly means a renamed field is a visible error at the point it happens, not a silent empty row two systems later.
🤯 4
What happens to the Zaps if we do this?
Three Zaps become redundant. I would leave them switched on and paused rather than deleted while you run both paths for a fortnight and compare, because the failure mode you want to avoid is discovering a hidden dependency after the old path is gone.
One of the three also writes to a recruiting spreadsheet that nobody mentioned. That is a real dependency and it is not part of onboarding. Do not switch that one off with the others.
I will not disable anything. When you are ready, approve it and we do it one Zap at a time.
Teams @Dash right now a new hire in Workday goes to a Google Sheet, then Zapier, then it starts the onboarding checklist. It breaks about once a month. Could we get rid of the Zapier step?
Yes, and the sheet too. I can read the Workday record and start the onboarding run directly.
Today · Workday → Google Sheet → Zapier → checklist · 3 hops, 2 places to break
Instead · Workday → run started · 1 hop
Instead · Workday → run started · 1 hop
I looked at why it breaks. The last four failures were all the same cause: a field renamed in Workday, which the sheet accepted silently and Zapier then mapped to nothing. Nobody found out until a new hire had no checklist on day one.
Reading the record directly means a renamed field is a visible error at the point it happens, not a silent empty row two systems later.
🤯 4
What happens to the Zaps if we do this?
Three Zaps become redundant. I would leave them switched on and paused rather than deleted while you run both paths for a fortnight and compare, because the failure mode you want to avoid is discovering a hidden dependency after the old path is gone.
One of the three also writes to a recruiting spreadsheet that nobody mentioned. That is a real dependency and it is not part of onboarding. Do not switch that one off with the others.
I will not disable anything. When you are ready, approve it and we do it one Zap at a time.