# Integrations (/integrations)
Integrations connect your workflows to services such as Gmail, Slack, GitHub, and HubSpot. Connect with OAuth or use a supported API token or service account, then select the saved credential in a block. Sim stores credentials securely and refreshes OAuth tokens when the provider supports it.
You can connect **multiple accounts per service** — for example, two separate Gmail accounts for different workflows.
## The Integrations page [#the-integrations-page]
Click **Integrations** in the workspace sidebar. The page shows your **Connected** accounts, a **Featured** list, and a search box covering every available service.
The page's second tab, **Skills**, holds your workspace's [agent skills](/agents/skills).
Open a service to see what it offers:
* **Skills** — ready-made capabilities you add with one click, like *upsert-contact* for HubSpot.
* **Templates** — starter workflows built around the service.
* **+ Add to Sim** — connects your account.
## Connecting with OAuth [#connecting-with-oauth]
1. Open the service's page and click **Add to Sim**. If a menu appears, choose **Connect with OAuth**.
2. Enter a **Display name** to identify this connection (e.g. "Work Gmail" or "Sales HubSpot"), and optionally a **Description**.
3. Review the **Permissions requested** — these are the scopes Sim will ask the provider for.
4. Click **Connect** and complete the provider's sign-in and approval flow.
When the provider redirects you back, the connection appears under **Connected**.
For API tokens and service accounts, select the corresponding option from **Add to Sim** and follow the setup guide under that service. These connections have different fields and rotation requirements.
## Using integrations in workflows [#using-integrations-in-workflows]
Blocks that require authentication (e.g. Gmail, Slack, HubSpot) display an account selector. Select the connected account you want that block to use.
You can also connect another account directly from the block by selecting **Connect another \[service] account** at the bottom of the dropdown.
If a block requires an integration and none is selected, the workflow will fail at that step.
## Using a credential ID [#using-a-credential-id]
Each connection has a unique credential ID you can use to reference it dynamically. This is useful when you have multiple accounts for the same service and want to switch between them programmatically — for example, routing different workflow runs to different Gmail accounts based on a variable.
To copy a credential ID, open the connection from the **Connected** list and use the copy control next to its name.
In any block that requires an integration, click **Switch to manual ID** next to the account selector to switch from the dropdown to a text field.
Paste or reference the credential ID in that field. You can use a `{{SECRET}}` reference or a block output variable to make it dynamic.
## Managing a connection [#managing-a-connection]
Open a connection from the **Connected** list to manage it:
* Edit the **Display name** and **Description**.
* Manage **Members** — invite teammates and assign them an **Admin** or **Member** role. Admins can edit, reconnect, disconnect, and manage access; Members can use the connection in workflows. When you connect an account, you are its Admin.
* **Reconnect** — re-authorize if the connection expired or you need updated permissions.
* **Disconnect** — remove the connection entirely.
If you disconnect an integration that is used in a workflow, that workflow will fail at any block referencing it. Update blocks before disconnecting.
## Token renewal and connection failures [#token-renewal-and-connection-failures]
Sim attempts OAuth token renewal when a provider supports it and the connection has a usable refresh token. A revoked or expired refresh token can make a block fail even when the saved connection still appears in **Integrations**. A credential Admin can open it and select **Reconnect** to authorize again.
OAuth tokens are encrypted before storage. The account selector and credential ID reference the saved connection; they do not expose its token. API tokens and service-account secrets have provider-specific rotation rules documented in their setup guides.