> ## 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.

# Zapier OAuth 2.0 connector profile – StackOne setup guide

> Set up the OAuth 2.0 connector profile for Zapier in StackOne. One-time admin setup required before your users can link Zapier accounts via Hub.

> [!WARNING]
>
> Client credentials and redirect URIs are only available after your integration is published as a public integration in Zapier's App Directory.

Select Actions to adjust the guideSome actions may require additional configuration in the provider to be accessible. Choose the actions you need and the guide will be updated.

Select all
Clear

ActionScope(s)

Loading actions...No actions match your search.

Dynamic Guide URL

Copy URL

Scopes Selected

<pre role="textbox" aria-readonly="true" tabIndex="0" />

Separator

Copy scopes

## Configure the redirect URI

Sign in to the [Zapier Developer Platform](https://developer.zapier.com/), open your integration and go to **Embed** > **Settings** > **Redirect URIs**. Add `https://api.stackone.com/connect/oauth2/zapier/callback`.

## Copy the client credentials

In **Embed** > **Settings** > **Credentials**, copy the **Client ID** and **Client Secret** into the **Client ID** and **Client Secret** fields of the StackOne connector profile. Regenerating the client secret invalidates the previous one.

## Choose OAuth scopes

Enter the space-separated scopes your integration needs in the **Scopes** field. Each action lists the scope it requires. Use `zap` to read only Zaps that use your integration, `zap:all` for all of the user's Zaps, or `zap:account:all` for every Zap shared in their account. The `promotions:read` and `promotions:write` scopes are only for Zapier partners that sponsor users through promotions.

**1. Available scopes**

Enables actions: Create Action Run, Create Authentication, Create Promotion Enrollment, Create Zap, Delete Authentication, Delete Zap, Disable Zap, Enable Zap, Get Action Run, Get Input Choices, Get Input Fields, Get Output Fields, Get Promotion Enrollment, Get User Profile, Get Zaps V1, List Authentications, List Zap Runs, List Zaps, Test Action Step, Update Zap

The scopes the connector actions use.

<ul>
  <li>
    profile
  </li>

  <li>
    zap
  </li>

  <li>
    zap:all
  </li>

  <li>
    zap:account:all
  </li>

  <li>
    zap:write
  </li>

  <li>
    zap:update
  </li>

  <li>
    zap:delete
  </li>

  <li>
    zap:pause
  </li>

  <li>
    zap:runs
  </li>

  <li>
    action:run
  </li>

  <li>
    authentication
  </li>

  <li>
    authentication:write
  </li>

  <li>
    connection:read
  </li>

  <li>
    connection:write
  </li>

  <li>
    connection:delete
  </li>

  <li>
    promotions:read
  </li>

  <li>
    promotions:write
  </li>
</ul>

## Creating the StackOne Connector Profile

To create the Connector Profile in StackOne for **Zapier**:

**1. Open the connector**

Log in to StackOne, open [Connectors](https://app.stackone.com/connectors), and select **Zapier**.

**2. Choose actions and events**

<ul>
  <li>Click **Add Profile**.</li>
  <li>If the connector offers more than one authentication method, set the **Auth Method** filter to **OAuth 2.0**.</li>
  <li>Select the actions, and any events, to enable for this Connector Profile.</li>
  <li>Click **Continue**.</li>
</ul>

**3. Set up authentication**

<ul>
  <li>Select **Authentication Type** as **OAuth 2.0**.</li>

  <li>
    Fill out the fields using details retrieved from your provider:

    <ul>
      <li>**Client ID**</li>
      <li>**Client Secret**</li>
      <li>**Scopes** (Optional)</li>
    </ul>
  </li>

  <li>Click **Create Profile**.</li>
</ul>

Congratulations! The new Connector Profile now shows up on the connector page. If you created it as a project member rather than an admin, it starts disabled until a project admin enables it. You can now continue to [Link Accounts](https://docs.stackone.com/connect/managing-connectors/linking-accounts.md) for **Zapier**.


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