Skip to main content
Zapier is a workflow automation platform that connects apps to automate repetitive tasks. Connect your Zapier Enterprise account to Oleria to bring its users and groups into your identity and access graph.

​
What Oleria discovers

User accounts and profile attributes, and groups (Zapier calls them teams) with their members, synced from Zapier’s SCIM directory. Oleria uses this data for access reviews, refreshed on Oleria’s regular sync schedule.

​
Prerequisites

  • A Zapier Enterprise account with Workspaces. Zapier offers SCIM user provisioning only on Enterprise.
  • An account owner or admin in Zapier, to turn on user provisioning and get its SCIM token.
  • To let Oleria create users, verify their email domains under Domains in Zapier’s Settings.
  • Admin access on the Oleria platform to add a new integration.

​
Get your SCIM credentials from Zapier

1

Turn on user provisioning in Zapier

If your identity provider (for example, Okta or Microsoft Entra ID) already provisions Zapier, user provisioning is already enabled and your identity provider uses the existing token. Regenerating the token makes the previous one unavailable, which stops your identity provider’s provisioning. Give Oleria the same token your identity provider uses. If you no longer have it and regenerate it, update your identity provider with the new token too.
Sign in to Zapier as an account owner or admin, go to Settings, and select User Provisioning in the left sidebar (Zapier also calls it the Provision tab). Select Enable. Zapier generates a SCIM token.
2

Copy your Authentication Token

Copy the SCIM token Zapier generated. You’ll paste it into Oleria in the next section.

​
Connect Zapier to Oleria

1

Open the integration

Go to your Oleria workspace, select Integrations, then select the Zapier tile.
2

Complete the connection form

Fill in the connection form:
3

Save the integration

Select Connect to validate the credentials and save the integration.
If the connection fails with “Could not satisfy the request Accept header.”, contact us at support@oleria.com. A fix is rolling out.
Every Zapier connection uses the same base URL, so you can connect one Zapier account per Oleria workspace.

​
Verify the integration

Confirm the new instance appears on the Connected tab of your Oleria Integrations page with a status of Healthy. Oleria syncs users and groups from Zapier on its regular sync schedule once the initial sync completes.
If you regenerate the SCIM token in Zapier, the previous token stops working, so update the Authentication Token in Oleria by editing the integration, and in any identity provider that uses the same token.

​
Remediation actions

Oleria can also take these actions in Zapier when the SCIM token can update users and teams:
  • Enable or disable a user account
  • Add or remove a user from a team
  • Create a new user or team
Oleria doesn’t check the token’s permissions until an action runs. If an action fails, confirm the token can update users and teams in Zapier.

​
Known limitations

  • Zapier hides deactivated users from later SCIM requests, so a user deactivated (by Oleria or in Zapier) drops out of Oleria’s inventory after the next sync and can’t be selected for Enable. To re-enable a user Oleria disabled, an Oleria administrator can select Undo on that disable action in Action Center within 7 days. After that, re-enable the user in Zapier.
  • When a user is deactivated, Zapier immediately revokes their access, transfers their shared Zaps, app connections, and folders to the account owner, and pauses their unshared Zaps.
  • Zapier can’t deactivate the account owner. Transfer ownership in Zapier first if that user must lose access.

​
Contact us

For questions about this integration, contact us at support@oleria.com.