How to disconnect an integration in Tapmy
To disconnect an integration in Tapmy, pause anything that depends on it, disconnect it in Tapmy, then revoke Tapmy in the provider's authorized apps. A disconnect may not cancel posts, meetings or subscriptions already created.
On this page
Use this when you are removing a connected provider because of security, a change of owner, a move to another tool, or a workflow you no longer want.
What should I check before I disconnect?
List the connected account, the permissions it has, the resources selected, active schedules, queued posts, bookings, webhooks and synced data. Pick a quiet time. Write down the current working setup and who can roll it back, along with the store, provider account, time and time zone.
How do I disconnect an integration step by step?
There are usually two controls: the connection in Tapmy and the authorized-app access at the provider. Handle both. Removing one side can leave a token, queue or provider-created item still active.
- Note why you are disconnecting.
- Pause or review scheduled content, booking intake, sync jobs and automations that rely on it, and tell affected people.
- Export only the data you may keep and need. Save object IDs, last-success times and settings, but do not copy tokens.
- Read Tapmy's disconnect warning and write down what it says about imported data, public pages, availability and queued actions.
- Use Tapmy's disconnect action for the exact provider account. Do not delete the whole store as a shortcut.
- Open the provider's security or authorized-apps page and check whether Tapmy still has access. Revoke it if you need a full removal.
- Try a safe action that should now be blocked, and check that public bookings, links and store content behave as expected.
- Watch for delayed actions, then record the final state, retained data, owner, date and when you would reconnect.
How do I know it worked?
Tapmy no longer acts through the provider, the provider no longer authorizes Tapmy if you revoked it, queued work is sorted out, and your public pages fail safely or use a backup. Run one test with made-up data and check both Tapmy and the provider. An "authorized" label alone does not prove anything works.
What if actions continue or something breaks?
- Actions continue after disconnecting. Check queues, cached tokens, provider sessions, webhooks and any other store or account using the same connection.
- A public booking page or content breaks. Put your backup in place, or reconnect only after confirming identity, permissions and duplicate risk.
- Data vanishes. Stop changing things, save logs and IDs, read the retention warning and contact Support. Do not reconnect blindly.
Behavior varies by provider: data retention, queued-action cancellation, token revocation and reconnection history can differ. A Tapmy disconnect may not delete provider-created items or revoke provider access automatically.
Make one reversible change at a time. Never share passwords, codes, API keys, tokens, DNS credentials, private calendar links, customer records or unpublished posts.
What should I do next?
Once stable, remove old public references, update the workflow owner, and set up a replacement if you need one.
If your test still fails, contact Tapmy Support with the store, provider, affected item or public host, time and time zone, exact error, expected result and screenshots. Rotate any exposed credentials at the provider before you write in.