Agiled Docs

Disconnect an app when the provider account changes, the integration is no longer needed, or the workspace should stop importing or syncing provider data.

Disconnecting stops future access. It usually does not remove records that were already imported or created in Agiled.

Disconnect from Settings Apps

Open Settings > Apps.
Open the installed app.
Review the connected account and recent runs.
Select the uninstall or disconnect action.
Confirm the app is no longer listed as connected.

After disconnecting, review recent runs or logs if the app had active imports. This helps confirm no sync was halfway through when access was removed.

If the integration imported records, decide whether those records should remain, be archived, or be cleaned up separately. Disconnecting the app does not undo past imports.

Replacement Workflow

If you are replacing a provider, connect the replacement first when possible. Then test the affected workflow, update public pages or templates, and only then disconnect the old provider.

This is especially important for payment providers, calendars, email sending, and automation channels because public links or scheduled jobs may continue to depend on the old connection.

For customer-facing providers, prepare a rollback path. Keep the old provider available until the replacement has handled at least one safe payment, booking, email, sync, or notification test.

Disconnect a Mailbox

Open Settings > Mailboxes.
Find the connected mailbox.
Select Disconnect.
Confirm the mailbox row is removed or no longer active.

Before Disconnecting

Check whether the provider is used by:

Public payment links.
Calendar availability and appointment sync.
CRM email sending.
Automation or notification channels.
Import workflows that the team still relies on.

Also check workflow actions, public booking pages, checkout links, invoice payments, and team instructions that mention the provider.

Test the feature that used the integration. For example, send a test email after disconnecting a mailbox, open a booking page after disconnecting a calendar, or open a checkout link after disconnecting a payment provider.

If the provider stores tokens or app authorizations, revoke Agiled from the provider account too when the connection should be fully removed.

Tell affected users what changed. A disconnected app can make buttons, public pages, workflows, or sync results look broken if teammates do not know the provider was intentionally removed.

Provider Account Cleanup

Some providers keep app authorization active until you remove Agiled from their own security or connected-apps settings. When access must be fully revoked, open the provider account and remove the Agiled authorization there too.

Use the provider's audit log when available to confirm the last sync or API access time.

Disconnect Safely

Before confirming:

Identify the owner of the provider account.
Check active workflows, public pages, templates, and settings that use it.
Review the most recent sync or import run.
Communicate the change to users who rely on the provider.
Test the affected Agiled feature after disconnection.

If the provider is being replaced, connect and test the replacement before removing the old integration.

Troubleshooting After Disconnect

If a feature stops working after disconnection, check whether it still points to the old provider. Update event types, mailboxes, payment settings, workflow actions, templates, and public pages before reconnecting blindly.

Disconnect an App