GuidesConnect an app (Slack, GitHub, Zoom and others)
On this page0

Guide

Connect an app (Slack, GitHub, Zoom and others)

Link one of your company's apps to Zonitix so it can list who has an account there and, where the app allows it, create and remove accounts during onboarding and offboarding.

For: IT administratorPlan: All plans

Before you start

  • This is an IT task. It assumes you can sign in to the other app as an administrator and create an API key or token there. If you do not look after that app yourself, do this together with the person who does.
  • A Zonitix admin account that shows Access GovernanceIdentity Hooks in the menu.
  • Admin access to the app you are connecting, so you can create the key or token Zonitix signs in with. Each app calls it something different; step 2 lists them.
  • Your identity provider (Okta, Entra or Google) is connected the same way but has its own guide, Connect Okta, Entra or Google.
A connection is called a hook in the app. Words such as hook, token and SCIM are explained in Glossary: words used in these docs.

Add the app

  1. Step 1: Pick it from the marketplace

    Go to Access GovernanceIdentity Hooks and click “NEW INTEGRATION”. A window titled “Integration Marketplace” lists the apps by kind. Use “Search providers...” to find yours, then click its tile.

    A new card appears in the list as a “Draft”. Click “Configure” on it. The card’s more-actions menu (the three dots) has a “Setup guide” with the steps to follow inside the app itself.

  2. Step 2: Connect: paste what the app gave you

    Give the hook a “Hook Identity Name”, then fill in the fields for your app. Each field has a hint saying where to find the value.

    • Slack: “Bot user OAuth token”.
    • GitHub: “Organization” and “Personal access token”.
    • Zoom: “Account ID”, “Client ID” and “Client secret”.
    • Jira and Confluence: “Site”, “Admin email” and “API token”.
    • Zendesk: “Subdomain”, “Admin email” and “API token”.
    • ServiceNow: “Instance URL”, “Username” and “Password”.
    • Salesforce: “Consumer key”, “Consumer secret”, “Login URL” and “Profile ID”.
    • Notion: “Internal integration token”. Dropbox: “Access token”. BambooHR: “Subdomain” and “API key”.
    • 1Password: “SCIM bridge URL” and “Bearer token”.

    Secrets are stored encrypted. When you edit the hook later, a saved secret shows as STORED; leave it blank to keep it. Click “Next”.

  3. Step 3: Capabilities: decide what Zonitix may do

    Under “Permissions & Policies”, keep “Read Users” on so Zonitix can list who has an account. Turn on “Write Users” if you want onboarding and offboarding to create and switch off accounts in this app. With it off, those steps become tasks for IT to do by hand.

    Pick a “Synchronization Interval” and click “Next”.

  4. Step 4: Mapping and Validate

    Leave “Attribute Mapping” as it is and click “Save & validate”. Zonitix saves the hook and tests it against the real app. Fix anything that fails and click “Re-run checks”. When the checks pass, click “Finish”.

  5. Step 5: Done: run the first sync

    Click “DRY RUN” to see what a sync would bring in without changing anything, then “MANUAL SYNC”. To keep the list up to date by itself, turn on “AUTOMATED BACKGROUND SYNC”, then click “Done”.

An app that is not in the list

  1. Step 6: Use the generic connector

    Many apps can be managed through SCIM, a standard way for one system to create and switch off accounts in another. In the marketplace, pick “Generic SCIM 2.0”, or one of the ready-made SCIM tiles (Box, Adobe, Asana, Datadog, monday.com, Miro, HubSpot).

    You need two values from the app’s own provisioning settings: the “SCIM base URL” and a “Bearer token”. Add one hook for each app.

Three things the setup screens themselves point out. A Slack bot token can list users but cannot invite or deactivate them. A Figma personal access token cannot list your organisation’s members, so connect Figma through Generic SCIM 2.0 instead. A Dropbox token must come from a Business (Team) app, or the connection test passes and account changes are then refused. What each connector can read and change is in the Identity Hooks reference.

What you should see

The hook’s card shows Connected with a recent last-sync time. If write access is off, it also shows a Read-only tag.

In the persona builder, the app is now tagged Auto-ready instead of Needs a hook, when the hook is connected and “Write Users” is on.

If something goes wrong

A check fails on the Validate step
The message names what was refused. The usual causes are a mistyped address, a token that was revoked or copied incompletely, or a token created by someone without admin rights in the app. Correct it on the Connect step and click Re-run checks.
Onboarding or offboarding steps for this app land as IT tasks instead of happening automatically
The app refused the change, usually because Write Users is off or the token may only read. Turn on Write Users and give the token the write permissions named in the Setup guide.
The background sync switch is greyed out
It stays locked until validation passes. Open the hook, go to the Validate step and run the checks.
"No integrations found matching …"
The marketplace has no tile with that name. Clear the search and look under the app’s category, or use Generic SCIM 2.0 if the app supports SCIM.

Still stuck? See When something goes wrong, or Contact Zonitix support.

Where next

Previous
Connect Okta, Entra or Google
Next
Push users with SCIM