> ## Documentation Index
> Fetch the complete documentation index at: https://learn.workflow.dog/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Connect, select, reconnect, swap, and disconnect external accounts.

An **integration account** lets actions and triggers access an external
service, such as Google, Microsoft, Airtable, or OpenAI. Accounts are linked to
a project, then selected on the nodes and triggers that use them.

## Connect an account

The first connection starts inside the workflow editor, not on the project's
**Integrations** page.

<Steps>
  <Step title="Add or configure a connected action">
    Add an action that uses the service, or open a trigger that requires the
    service.
  </Step>

  <Step title="Open the account selector">
    Find **Third-party account** and choose **Connect new account**.
  </Step>

  <Step title="Authorize WorkflowDog">
    OAuth integrations open the provider's authorization page. API-key
    integrations open a credential dialog in WorkflowDog. Approve the permissions
    required by the current action or trigger.
  </Step>

  <Step title="Confirm the selection">
    After a successful connection, the new account is selected automatically.
    It also appears on the project's **Integrations** page.
  </Step>
</Steps>

<Note>
  The first account connected for a provider in a project becomes that
  provider's default account.
</Note>

## Select the right account

Each account selector lists accounts for the current provider and project. A
node can use an account only when it is healthy and has every permission the
node requires.

When an account input has never been set, WorkflowDog selects the healthy
default account if it has the required permissions. An explicit account
selection is preserved until it is cleared, disconnected, becomes unhealthy,
or no longer satisfies the node's permission requirements.

Use **Clear Selection** when a node should not inherit or retain the current
account.

## Manage connected accounts

Open **Integrations** from the project dashboard to see accounts grouped by
provider.

For each account, you can:

* **Set as Default** — Make it the automatic choice for unset account inputs
  from the same provider.
* **View Account Usage** — Find action nodes whose saved graph contains the
  account.
* **Swap Accounts** — Replace the account on selected action-node usages with
  another account from the same provider.
* **Disconnect** — Remove the account from the current project and clear its
  saved references.

Defaults are project-specific. Setting a Google account as the default in one
project does not make it the default in another.

## Swap action nodes to another account

Account swapping is useful before disconnecting an old employee account or
rotating a service account.

<Steps>
  <Step title="Connect the replacement">
    Connect the new account to the project and ensure it has the permissions
    required by the affected actions.
  </Step>

  <Step title="Open the old account's usage list">
    On **Integrations**, open the old account's menu. Under **Account Usage**,
    select the workflow and action-node locations to update.
  </Step>

  <Step title="Choose the replacement account">
    The replacement must belong to the same provider. Select it and choose **Swap
    Accounts**.
  </Step>

  <Step title="Review triggers separately">
    Open any trigger that uses the old account and select the replacement
    manually.
  </Step>
</Steps>

<Warning>
  **Account Usage** and **Swap Accounts** cover action nodes only. Trigger
  configurations are not listed or swapped by this tool.
</Warning>

## Approve missing permissions

Different nodes from the same provider can require different OAuth scopes. If
an existing account is missing a required permission, click it in the account
selector and complete authorization again.

WorkflowDog requests the new permissions together with the account's existing
permissions. Google reconnections show the consent screen again so Google can
issue refreshed credentials.

After reconnecting, review the node selection. An account that lacked required
permissions may have been cleared from the input before the reconnection.

## Reconnect an unhealthy account

An account marked **Needs Reconnecting** has credentials that WorkflowDog can
no longer use. Actions using it can produce node errors, and account-backed
triggers can stop receiving new events.

<Steps>
  <Step title="Reconnect from a node">
    Open an account selector and click the unhealthy account. OAuth providers
    take you through authorization again.
  </Step>

  <Step title="Check the Integrations page">
    Refresh the account list and confirm the warning is gone.
  </Step>

  <Step title="Verify affected triggers">
    Open each account-backed trigger and confirm its configuration. Reconnection
    starts background recovery for event subscriptions that need rebuilding.
  </Step>

  <Step title="Send a new event">
    Test with a new email, form response, or provider event. Do not assume an
    event missed during the outage will be replayed.
  </Step>
</Steps>

If reconnection continues to fail, revoke WorkflowDog from the provider's own
connected-app settings, then connect the account again.

## Disconnect an account

Disconnecting performs more than removing an account from the list:

* The project-to-account link is removed.
* Matching account selections in action-node graphs are changed to no
  selection.
* Matching account selections in trigger configurations are cleared.
* Trigger event sources are reconciled, including cleanup of external
  subscriptions that are no longer used.

<Warning>
  Disconnecting does not revoke WorkflowDog at the external provider. Use the
  provider's security or connected-app settings when you also need to revoke the
  authorization itself.
</Warning>

Swap action usages and reconfigure triggers before disconnecting when workflows
must continue without interruption.

## Troubleshooting

<AccordionGroup>
  <Accordion title="The account is connected but cannot be selected">
    The account is unhealthy or lacks a permission required by that node. Click
    the account to reconnect and approve the missing permissions, then refresh
    the selector.
  </Accordion>

  <Accordion title="The Integrations page is empty">
    Connect the first account from an action or trigger in the workflow editor.
    The Integrations page manages accounts after they have been linked to the
    project.
  </Accordion>

  <Accordion title="A trigger still uses the old account after a swap">
    Swapping is limited to action-node usages. Open the trigger configuration and
    choose the replacement account manually.
  </Accordion>

  <Accordion title="An account works in one project but is absent in another">
    Account links are project-specific. Connect the account from a workflow in
    the second project before trying to select it there.
  </Accordion>
</AccordionGroup>

Learn how account-backed event subscriptions behave in
[External triggers](/essentials/external-triggers).