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

# Using Tokens with Zapier

> Step-by-step guide to configuring Opigno Enterprise access tokens in your Zapier integration

## Overview

After creating an access token in your Opigno Enterprise instance, you need to configure it in Zapier to establish the connection between the two platforms. This guide walks you through the complete configuration process.

<Info>
  Make sure you have your Client ID and Client Secret ready before starting. These credentials are provided when you create an access token in Opigno Enterprise.
</Info>

## Prerequisites

Before configuring Zapier, ensure you have:

<Check>
  * An active Opigno Enterprise instance
  * Administrator access to create access tokens
  * A valid access token with Client ID and Secret
  * A Zapier account (free or paid)
</Check>

<Warning>
  If you haven't created an access token yet, follow the [Access Token Management](/zapier-integration/token-generation) guide first.
</Warning>

## Configuring Zapier Authentication

<Steps>
  <Step title="Access Zapier Integration Settings">
    1. Log into your Zapier account
    2. Navigate to **My Apps** in the left sidebar
    3. Search for "Opigno Enterprise" or locate it in your apps list
    4. Click **Add Connection** or **Connect Account**
  </Step>

  <Step title="Enter Opigno Instance Details">
    You'll be prompted to provide your Opigno Enterprise connection details.

    ### Base URL

    <ParamField body="base_url" type="string" required>
      Enter the complete URL of your Opigno Enterprise backoffice instance.

      **Format examples:**

      * `https://yourcompany.opigno.cloud`
      * `https://learn.yourcompany.com`
      * `https://training.example.com`

      <Info>
        Use the exact URL you access to log into the Opigno backoffice. Do not include trailing slashes or additional path segments.
      </Info>
    </ParamField>

    ### Client ID

    <ParamField body="client_id" type="string" required>
      Paste the Client ID that was generated when you created the access token.

      **Where to find:**

      1. Go to your Opigno backoffice
      2. Navigate to **Configuration** → **Authentication** → **Manage access tokens**
      3. Locate your token in the list
      4. Copy the Client ID value

      <Tip>
        Keep your access token creation confirmation or the tokens list open in another tab for easy reference.
      </Tip>
    </ParamField>

    ### Client Secret

    <ParamField body="client_secret" type="string" required>
      Paste the Client Secret that was shown during token creation.

      <Warning>
        **Important Security Notes:**

        * The Client Secret is only displayed once during token creation
        * If you didn't save it, you'll need to create a new token
        * Never share this value or commit it to version control
        * Treat it with the same security as a password
      </Warning>

      **If you lost the secret:**

      1. Revoke the old token in Opigno
      2. Create a new access token
      3. Immediately copy and save the new credentials
      4. Return to Zapier with the new values
    </ParamField>
  </Step>

  <Step title="Test the Connection">
    After entering all three fields:

    1. Click **Yes, Continue** or **Test** (depending on Zapier's interface)
    2. Zapier will attempt to authenticate with your Opigno instance
    3. Wait for the connection test to complete

    <Check>
      **Success indicators:**

      * Green checkmark or "Connected" status
      * Your connection appears in the list of authenticated accounts
      * You can proceed to build Zaps using this connection
    </Check>

    <Warning>
      **If the test fails**, see the Troubleshooting section below before creating a new token.
    </Warning>
  </Step>

  <Step title="Save and Name Your Connection">
    Once the test succeeds:

    1. Give your connection a descriptive name (e.g., "Opigno Production - Sales Team")
    2. Click **Save** or **Continue**
    3. The connection is now available for use in your Zaps

    <Tip>
      Use descriptive names if you manage multiple Opigno instances or learning areas. This helps identify which connection to use when building Zaps.
    </Tip>
  </Step>
</Steps>

## Verifying Your Connection

After successful configuration, verify that your connection works properly:

<Steps>
  <Step title="Create a Test Zap">
    1. Click **Create Zap** in Zapier
    2. Choose an Opigno Enterprise trigger or action
    3. Select your newly created connection
  </Step>

  <Step title="Test the Trigger or Action">
    1. Choose a test trigger (e.g., "New User Registered to Training")
    2. Click **Test trigger**
    3. Verify that Zapier can retrieve data from your Opigno instance

    <Check>
      If test data appears, your connection is working correctly and you can proceed with building your automation workflows.
    </Check>
  </Step>
</Steps>

## Connection Scope and Limitations

Understanding what your token connection can access:

### Permission Inheritance

Zapier connections inherit all permissions from the user who creates the access token. This means the token acts with the same level of access as the user who created it.

**Currently in Opigno Enterprise:**

* Only administrator users can create access tokens
* Administrators have unrestricted access across all hierarchy levels
* This ensures tokens have full access to data within their assigned backoffice

**What this means for your integration:**

When an administrator creates a token, the Zapier connection can:

* Access all users within the assigned backoffice, regardless of hierarchy level
* Retrieve data from any hierarchy level in that backoffice
* Register users to trainings at any level
* View training progress and scores across all levels
* Access live session data throughout the backoffice

This setup is effective because:

* Administrators have no hierarchy restrictions
* Zapier workflows can operate across all levels within the backoffice
* You avoid permission-related errors in automated workflows
* Integration logic remains simple without hierarchy permission checks

<Info>
  Administrator-created tokens provide complete access within their assigned learning area. This eliminates permission limitations that could prevent automation workflows from functioning correctly.
</Info>

### Data Access

Your connection can access:

* Registration and completion events
* Training statistics and scores
* Live session data

### Limitations

Your connection cannot:

* Access data from other learning areas
* Modify system-wide settings
* Access administrative functions
* Retrieve data outside the token's scope

## Managing Multiple Connections

If you work with multiple Opigno instances or learning areas:

### Naming Convention

Use clear, descriptive names for each connection:

**Recommended format:**

```
[Environment] - [Learning Area/Purpose]
```

**Examples:**

* `Production - Sales Team`
* `Staging - Marketing Department`
* `Dev - Testing Environment`

### Switching Between Connections

When building a Zap:

1. Select the appropriate trigger or action
2. Choose which connection to use from the dropdown
3. Verify you've selected the correct connection for your use case

### Connection Management

* Regularly audit your active connections
* Remove connections for revoked or expired tokens
* Update connection names to reflect current usage
* Document which Zaps use which connections

## Next Steps

Now that your Zapier connection is configured:

<CardGroup cols={2}>
  <Card title="Zapier Triggers" icon="bolt" href="/zapier-integration/components/triggers">
    Explore available triggers to start workflows based on Opigno events.
  </Card>

  <Card title="Access Token Management" icon="key" href="/zapier-integration/token-generation">
    Return to the token management guide for creating or revoking tokens.
  </Card>
</CardGroup>