Pause, disconnect or hand over a Zapier workflow
Pause Britixo automations, arrange connection revocation and transfer ownership without confusing Zap deletion with CRM data deletion.
Before you begin
List the Zaps and company connections involved. Agree who owns any pending work and whether the change is a temporary pause, a permanent disconnect or a staff handover.
CRM workspace → Tools → Britixo Automations (or Utilities in a classic layout)
Follow these steps
- Pause or turn off the relevant Zaps in Zapier before changing their connection.
- Review other Zaps that may use the same connection or subscribe to the same events.
- For permanent removal, follow the approved app’s disconnect process and ask support to confirm connector-side revocation where necessary.
- For handover, establish an approved replacement account and connection, then test the new workflow before retiring the old connection.
- Check the connector’s counts and the destination after the change. Preserve relevant run references for unfinished work.
Check the result
The old automation stops as intended, remaining Zaps use the right connection and any replacement workflow has been tested.
Rules, fields and operating limits
- Revoking a connector connection disables its associated subscriptions.
- Turning off a Zap, removing a subscription and revoking a connection are related but different operations.
- The current CRM overview has no client-facing revoke button; advanced revocation or investigation may require support.
If something does not look right
If events continue after a Zap is paused, check for another active Zap or subscription and ask support to verify connector-side authorisation. Do not assume that deleting one browser connection view stops every workflow.
Questions and answers
Does disconnecting delete existing leads?
No. Connection revocation does not delete CRM leads or records already created in another app.
Does pausing a Zap revoke its credentials?
Do not assume so. Pausing stops that Zap; permanent credential revocation is a separate connection-management operation.
Can one Zap be paused while others keep running?
Yes, subject to the way the Zaps share connections and subscriptions. Review the affected workflows before revoking a shared connection.
What happens to queued events after revocation?
The worker rechecks authorisation and can cancel deliveries that are no longer authorised. Agree how any unfinished business work will be handled.
Can I hand over my personal login?
Do not share a personal password or verification code. Arrange an approved staff/account handover and replacement connection.
Can I reconnect later?
You can repeat the approved consent flow if the workspace and account remain eligible. Reconnection does not promise recovery of historical missed events.
Useful next steps
Contact Britixo support. Include the workspace, action, run reference and time; keep credentials private.