Connecting an integration

Integrations pull assets into AssetBolt automatically and push events out.

Integrations require a Pro plan or higher. On Core, the integrations page shows an upgrade prompt.

What's available

MDM and endpoint management

Pulls devices in from the tool that already manages them.

• Iru (formerly Kandji)

• Jamf Pro

• Microsoft Intune

• Apple Business Manager — beta

• Apple School Manager — beta

Identity and directory

Syncs people from your directory.

• Microsoft Entra ID

• Okta

• Google Workspace

These three can also feed directory groups into AssetBolt teams: an admin picks a group on the connection, links it to a new or existing team, and membership stays in sync from there. See People, teams, and locations for how group-synced teams behave.

Cloud and data discovery

Discovers digital assets — databases, buckets, warehouses — in your cloud accounts. All four are beta.

• AWS — beta

• Google Cloud — beta

• Azure — beta

• Snowflake — beta

Ticketing

• Linear

• Jira — beta

Communication

• Slack — beta

• Microsoft Teams — beta

Webhooks

Webhooks are built in rather than connected. See Settings → Integrations → Webhooks.

Two ways to connect

One-click OAuth

Google Workspace, Microsoft Entra ID, Intune, Azure, Slack, Microsoft Teams, and Linear connect by clicking Connect and approving AssetBolt on the provider's consent screen. Nothing to copy or paste.

Intune, Entra ID, and Google Workspace also offer an advanced path if you'd rather use your own app registration or service account.

Microsoft consent and app names

AssetBolt uses Microsoft Entra apps for four connections. You will see these names on the Microsoft consent screen:

• AssetBolt Directory and MDM for Microsoft Entra ID and Microsoft Intune. This is one shared app. Admin consent granted once covers both connections.

• AssetBolt Cloud Discovery for Azure cloud discovery.

• AssetBolt for Microsoft Teams for Microsoft Teams notifications. This is a separate app because it uses delegated permissions and a per-user consent flow, not the tenant-wide permissions the other Microsoft connections use.

A Microsoft tenant admin must approve consent for the Directory and MDM and Cloud Discovery connections. Microsoft Teams can be connected by any team member unless the tenant has turned off user consent, in which case an admin grants it once for the whole tenant.

Google consent and app name

AssetBolt uses a single Google OAuth client for Google sign in and the Google Workspace directory integration. On the consent screen, the app appears as AssetBolt Web Client. The Workspace directory connection requests read-only Admin SDK Directory scopes. A Google Workspace super admin must approve consent for this connection.

Credentials

Everything else asks you to paste credentials:

• Iru — subdomain and API token.

• Jamf Pro — server URL, client ID, client secret (from API Roles & Clients).

• Okta — org URL and API token.

• Apple Business Manager and Apple School Manager — key ID, client ID, and a private key.

• AWS, Google Cloud, Snowflake, Jira — provider-specific credentials.

AssetBolt tests the connection when you save it.

Microsoft Teams also accepts an incoming webhook URL as a fallback: paste a URL from a Teams channel's Workflows menu instead of connecting with OAuth. A webhook posts to that one channel and needs no admin consent, but it can't list channels for you to pick from.

Multiple connections

Some providers support more than one connection — several Iru tenants, for instance. Each appears as its own row.

A note on beta

Beta integrations work, but they're newer and less proven than the rest. Expect rougher edges, and tell us what you find.

Zendesk appears in the integrations list marked Coming soon. It isn't built yet and can't be connected.