Agiled Docs

OAuth integrations redirect you to the provider so you can authorize Agiled without copying API secrets into the workspace.

Use OAuth when the provider supports it. It is usually safer than manually copying long-lived API credentials.

OAuth access is still tied to the provider account that approved it. If that account loses access, leaves the company, or changes password/security policy, the integration may need to be reauthorized.

Connect an OAuth App

Open Settings > Apps or the feature-specific connection page.
Choose the provider.
Select the OAuth connection action.
Sign in to the provider account.
Review the permissions requested by Agiled.
Approve the connection.
Return to Agiled and confirm the connection success message.

Pick the Right Provider Account

Before approving OAuth, check the provider account shown in the provider window. For Google and Microsoft, browser sessions often default to the last personal or work account used. Switch accounts before approving if the wrong email appears.

Use shared or service-owned provider accounts when the integration should survive employee turnover, as long as that matches the provider's security policy.

For finance, calendar, mailbox, and project integrations, record the provider workspace or tenant that was approved. This prevents future admins from guessing which external account Agiled is using.

OAuth Providers in Agiled

OAuth is used by providers such as Google Calendar, Outlook Calendar, Zoom, Microsoft Teams, QuickBooks, Xero, Asana, HubSpot, Mailchimp, and several project management apps.

Choose the provider account carefully. Connecting the wrong Google, Microsoft, or CRM account can import the wrong data or write events to the wrong calendar.

If OAuth Fails

Return to the Agiled connection page and read the error message. Common causes include expired provider sessions, missing provider permissions, a blocked popup, using the wrong provider account, or returning to a different workspace than the one that started the connection.

Try again from the same Agiled workspace and browser tab that started the flow. If an admin approval is required by the provider, complete that approval before retrying.

If the redirect returns to the wrong workspace, stop and switch to the intended Agiled organization before reconnecting. OAuth connections should be created from the workspace that will own the data.

After Connecting

Run a small test sync or feature-specific check. For example, test one booking page after connecting a calendar or import a small sample after connecting a CRM.

Check the connected-account label inside Agiled after the redirect completes. Record who connected it, what provider workspace it points to, and what feature depends on it.

Reauthorization Checklist

Reconnect or reauthorize when:

provider permissions changed
the connected account was disabled or removed
calendar, CRM, or finance records stop syncing
the provider reports expired consent
an admin changes app access policies

After reconnecting, repeat the smallest useful test and review recent app runs.

Disconnecting OAuth

Disconnect the app in Agiled when the provider should stop syncing. If access must be fully removed, also revoke Agiled from the provider's connected-apps or security settings.

OAuth Connection Checklist

Before relying on a connected app:

confirm the provider account and tenant
review requested scopes
run one small feature-specific test
record who owns reauthorization
confirm the integration appears connected in Agiled
check provider-side connected app settings when full revocation is needed

OAuth App Connections