Connected accounts

Connected accounts authorize FastHook to subscribe to provider events and execute Actions. They belong to the selected FastHook team and can be reused by compatible Sources and Workflow Steps.

Manage them under Settings → Connected accounts or create one from a Trigger or Action dialog.

Connection types

OAuth 2.0

FastHook redirects you to the provider for consent and stores the resulting provider account. Google Workspace, Slack, Stripe, Shopify, HubSpot, Linear, Notion, Dropbox, Microsoft, Airtable, Trello, and other providers use OAuth where supported.

App installation

GitHub uses an app installation. Repository access is determined by the repositories granted to that installation, not only by the Source configuration.

API credentials

Some providers require customer credentials. Examples include a Twilio Account SID and Auth Token, a Telegram bot token, or PayPal REST app credentials. Secret values are stored encrypted and are not returned by the API.

Provider-specific bot or webhook modes

Discord Actions can use a customer webhook, a customer-owned bot, or the hosted FastHook bot. The available fields and capabilities change with the selected authentication mode.

Reuse an account

Choose an existing account when multiple Sources or Actions should operate in the same provider workspace. Reuse reduces duplicate consent flows, but it also creates a shared dependency: revoking that account can affect every linked resource.

Use separate accounts when environments, customers, workspaces, or permission boundaries must remain isolated.

Scopes and permissions

Trigger and Action definitions declare the provider scopes or permissions they require. FastHook may request additional scopes when a new operation needs them.

Provider authorization does not guarantee access to every resource. A connected user can still lack access to a private channel, repository, drive, spreadsheet, project, or record selected later.

See Authentication, scopes, and permissions for the complete lifecycle, least-privilege, reconnect, rotation, and troubleshooting procedure.

Reconnect

Reconnect when a token expired, consent was withdrawn, required scopes changed, or the provider reports an authorization error.

After reconnecting:

1. Confirm the account status is healthy.
2. Reopen affected Sources and verify their selected resources.
3. Reopen affected Actions and confirm remote resource pickers load.
4. Produce a controlled trigger event.
5. Inspect the new Workflow run in Audit.

Revoke or disconnect

Before revoking an account, identify the Sources and Actions that reference it. Pause affected Workflows when losing access would create repeated failures.

Revocation removes FastHook's ability to use that account, but provider-side app installations, webhooks, or tokens may also require cleanup in the provider console. Follow the provider's own security process when credentials may be compromised.

Credential rotation

Rotate API credentials at the provider, update or reconnect the FastHook account, then test one controlled Action. Never paste secrets into Workflow text mappings, descriptions, fixtures, or documentation screenshots.

Troubleshooting

• Account not listed: confirm the selected FastHook team and provider match the Trigger or Action.
• Permission denied: compare required Action permissions with the connected provider identity and selected resource.
• Remote picker is empty: verify provider access and reconnect if scopes changed.
• Source stopped producing events: inspect provider subscription or notification-channel status as well as the account.
• Action worked before but now fails: check token status, resource deletion, role changes, provider rate limits, and the exact account ID shown in Audit.

Browse Integrations for supported apps or return to Triggers and Actions.