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

# Connect Zapier with SCIM API Token – StackOne Hub

> Link a Zapier account in the StackOne Hub using SCIM API Token. End-user guide to authorize the integration and start using Zapier actions.

> [!WARNING]
>
> SCIM user provisioning is available only to Zapier Enterprise accounts with Workspaces, and you must first [verify at least one domain](https://help.zapier.com/hc/en-us/articles/34976125153677) in **Domain management**. Verification can take up to 72 hours. If your Enterprise account does not have Workspaces, contact your Zapier account manager. Zapier gives this token no scopes or read-only version: it is the same token an identity provider uses, so it can also create, update and deactivate members, although StackOne only reads with it. Turning on user provisioning changes the account: members can no longer be removed from Zapier's Members page (remove them through your identity provider or the SCIM API) and members cannot change their own details.

## Get the SCIM API token

The SCIM API token is created when you enable user provisioning, and it reads the members and groups of the whole Zapier organization.

**1. Sign in to Zapier**

Sign in to your [Zapier account](https://zapier.com/app/login) as the **Owner** or a **Super admin** of your organization.

<ul>
  <li>**Super admin** is the smallest role that can set up SCIM, because SCIM is set up at the organization level. A workspace **Admin** or **Member** cannot.</li>
  <li>Open the [user provisioning settings](https://zapier.com/app/settings/company/user-provisioning), or go to **Settings** and select **User Provisioning** in the left sidebar menu.</li>
</ul>

**2. Enable user provisioning**

Click **Enable**. Zapier generates a new authentication token.

<ul>
  <li>If user provisioning is already enabled and you do not have the token, regenerate it on the same page. Zapier marks the previous token as unavailable, so paste the new token into your identity provider too, or its provisioning stops.</li>
</ul>

**3. Copy the token**

Copy the authentication token and store it securely for use later.

<ul>
  <li>Zapier names no expiry for this token.</li>
  <li>Paste it into the **SCIM API Token** field in StackOne Hub.</li>
</ul>

## Revoke the token

To stop StackOne from reading your members, regenerate the token.

<ul>
  <li>Open the [user provisioning settings](https://zapier.com/app/settings/company/user-provisioning).</li>
  <li>Regenerate the token. Zapier marks the previous token as unavailable, so the StackOne connection stops working.</li>
  <li>Paste the new token into your identity provider as well, if you use one, or the provisioning there stops working.</li>
</ul>

## Linking the Account from the Hub

**1. Navigate to the Hub**

Use one of the three [Linking Account Methods](https://docs.stackone.com/connect/managing-connectors/linking-accounts.md) to access the Hub.

**2. Fill out the fields**

Fill out the following fields using details from your provider:

<ul>
  <li>**SCIM API Token**</li>
</ul>

**3. Connect**

<ul>
  <li>Click **Connect**</li>
  <li>If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider's authorization flow.</li>
  <li>Once authorization is successful, you will see a confirmation popup</li>
</ul>

If the account linking is successful, you will see the newly linked account on your [Accounts](https://app.stackone.com/accounts) page.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.