What Oleria discovers
User accounts and profile attributes synced from Zapier’s directory. Oleria uses this data for dormant account detection and access reviews, refreshed on Zapier’s standard sync schedule.Prerequisites
- Admin access in Zapier with permission to generate an API key.
- Admin access on the Oleria platform to add a new integration.
The exact location of these settings can change over time. If the steps below don’t match what you see, refer to Zapier’s own API documentation.
Get your SCIM credentials from Zapier
1
Generate an API key in Zapier
Sign in to Zapier as an admin, go to Team Settings → API, and generate an API key.
2
Copy your SCIM Base URL and Authentication token
Copy both values before you leave the page - you’ll paste them into Oleria in the next section:
- SCIM Base URL - the HTTPS API endpoint for your Zapier team.
- Authentication token - the API key you generated.
Copy the key now. Many applications display it only once. Store it securely and rotate it per your organization’s security policy.
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
Select Continue and fill in the connection form:
3
Save the integration
Select Connect to validate the credentials and save the integration.
Verify the integration
Confirm the new instance appears in your Oleria workspace under Connected Integrations with a status of Healthy. Oleria syncs users from Zapier on the standard SCIM provisioning schedule once the initial sync completes.If Zapier rotates your API key, update the Authentication token in Oleria by editing the integration.
Governance actions
Oleria can also invoke lifecycle actions in Zapier when the key you provide has write access:- Enable or disable a user account
- Create a new user
Many teams start with a read-only key for visibility, then grant write access once they’re ready to automate remediation in Zapier.