Zapier connection shows auth expired or disconnected
Your Zapier card in MapleGather shows “Reconnect needed” or your Zaps have stopped firing because the connection is no longer active.
What’s happening
Section titled “What’s happening”“Reconnect needed” (auth_expired): The OAuth token that authorizes MapleGather to communicate with Zapier has expired. Your Zaps will not fire until you re-authorize the connection. This happens automatically over time.
Milestone note: The
auth_expiredreconnect path applies once OAuth provider connections are live. At M1, the Zapier connection uses a scoped API key that does not expire on its own — if you see “Reconnect needed” at M1, contact support, as this would indicate an unexpected state.
Connection shows as disconnected or removed: The connection was explicitly disconnected using the Disconnect action, which is permanent. The credentials are wiped and the connection record is removed. You’ll need to connect from scratch.
How to fix it
Section titled “How to fix it”For “Reconnect needed”:
- Go to Admin & Security > Integrations > Zapier.
- On the connection card that shows “Reconnect needed,” select the reconnect link.
- Complete the OAuth consent flow in the browser tab that opens. You’ll come back to MapleGather when it is done.
- Confirm the card now shows “Active” with a recent “Last sync” timestamp.
For a disconnected connection:
- Go to Admin & Security > Integrations > Zapier.
- Follow the steps in Connect Zapier (no-code) to reconnect from scratch. A new scoped key is generated for the new connection.
- After reconnecting, reconfigure any Zaps in Zapier that were using the old connection.
If the Zapier consent screen says your role can’t grant a scope
Section titled “If the Zapier consent screen says your role can’t grant a scope”If the OAuth consent step shows a message like “This Zap wants payments:read, which your role can’t grant,” your admin role does not have permission to authorize that scope. You can:
- Ask an organization owner to connect from their account (which has the necessary permissions).
- Proceed without that scope — the Zap will work for the scopes you can grant, but features requiring the missing scope will not work.
If that didn’t work
Section titled “If that didn’t work”If the connection shows “Active” but Zaps are still not firing, check the Zap’s own run history in Zapier for error details. Zapier surfaces the API response (including any ValidationProblem errors) in its run log.
Contact support if the “Reconnect needed” state persists after reconnecting.