A reauthorization path must preserve workflow continuity without exposing another tenant’s connection state.
The partner needs customers moved before workflows stop, while authorization controls must remain intact.
Who you’d be doing this for
“My support queue is full of customers asking why a workflow they used yesterday is disconnected.”
Arunee Rattanakorn · Platform Engineering Manager
Owns the embedded automation experience at a managed software partner facing the credential cutoff.
What is at stake
Google-connected embedded workflows are disconnecting as customers reach the reauthorization cutoff. You have to weigh partner continuity against a migration that never blurs tenant authorization boundaries.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- workflow continuity vs tenant isolation
- partner urgency vs shared-service stability
- guided reauthorization vs minimal data exposure
- cutoff speed vs migration verification
Why Zapier
Powered by Zapier API depends on managed partners keeping embedded workflows connected inside their own products.
Written with these in mind
Not your kind of problem? 3 more at Zapier, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.