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

# Zapier

*This article covers Zapier connections created after February 2026. To check your version, look at the Domain ID under your domain. If it shows `zapier_ics`, use the steps below. If it shows `zapier.com`, use the legacy connector instructions. This integration has no read-only mode, so provisioning is mandatory.*

## After this article

You'll be able to connect Zapier to Lumos to sync and provision users and groups.

## Capabilities

| Functionality | Type | Sync | Provision | Description |
| - | - | - | - | - |
| Users | Account | Yes | Yes | User account records |
| Groups | Permission | Yes | Yes | Access control groups |

| Deprovisioning Action | Type | Description |
| - | - | - |
| Deactivate | User | Deactivates the user in Zapier, marking them as Suspended |
| Delete | User | Changes the user's status to Inactive |

**User status mapping.** `active` maps to Active. `inactive` and a deleted user (no longer returned by Zapier) both map to Deprovisioned. Deactivating a user prevents them from logging into Zapier. Deactivating or deleting doesn't reclaim a license.

## Required plan and roles

* **Zapier plan:** you need the Zapier **Enterprise** plan.
* **Zapier role:** the connecting user must be at least an **Admin**.
* **Authentication:** the integration uses a Zapier SCIM bearer token.

## Read-only access vs provisioning

**Is read-only possible?** No. This integration has no read-only mode, provisioning is mandatory. The SCIM bearer token used to connect inherently supports full user and group provisioning.

**What full provisioning requires.** The Zapier Enterprise plan, an Admin enabling SCIM User Provisioning in Admin Center and generating the SCIM Bearer Token, and verifying each user's domain in Admin Center before provisioning them. Follow the steps below.

**Watch out for.** These steps apply only to Zapier connections created after February 2026 (Domain ID `zapier_ics`). Legacy `zapier.com` connections use different instructions. Provisioning a user whose domain isn't verified fails, verify it first. Deactivating or deleting a user doesn't reclaim a Zapier license.

## Instructions

**Phase 1: Generate a SCIM bearer token in Zapier**

1. Log in to `zapier.com` as an account admin.
2. Go to **Settings → Admin Center**.
3. Click **SCIM User Provisioning**, then **Enable Provisioning**.
4. Copy the **SCIM Bearer Token**.
5. Before provisioning users, verify your domains. Go to **Admin Center → Domain management**, click **Add domain**, and follow the steps to verify each domain.

**Phase 2: Connect in Lumos**

1. Find the Zapier card in your Lumos integrations. Reconnect an existing card or add a new one.
2. Paste the **SCIM Bearer Token**.
3. Enter an **Account Name**, any unique value that helps you identify this Zapier account (for example your company or workspace name).
4. Click **Connect**.

## API Endpoints Used

<Note>
  The API endpoints this integration uses are available to logged-in Lumos customers. [Log in](/login) to view them.
</Note>

## Troubleshooting

**Provisioning fails for a user's domain.** You must verify the user's domain before provisioning. Go to **Admin Center → Domain management** in Zapier, add the domain, and finish the verification steps.

**Can't connect the integration.** Confirm you're on the Zapier Enterprise plan, that you're logged in as an Admin, and that the SCIM bearer token is current. Regenerate the token from **Admin Center → SCIM User Provisioning** if needed.