AssetBolt
AssetBolt
Docs
  • Docs
  • Changelog
  • Feature requests
  • Support portal

Connecting an integration

Every integration AssetBolt supports, which are beta, and the two ways to connect one.

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.

  • 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

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

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, 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 three 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.

A Microsoft tenant admin must approve consent for these connections.

Credentials

Everything else asks you to paste credentials:

  • Kandji — 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.

Multiple connections

Some providers support more than one connection — several Kandji 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.

PrevAutomations
NextConnecting an AI assistant (MCP)
Was this helpful?
    • Automations
    • Connecting an integration
    • Connecting an AI assistant (MCP)
    • Notification preferences
    • API keys
    • Printing asset labels
    • Language and appearance settings
    • Organization preferences
    • Exporting your data
    • Webhooks
    • Managing your account and password