AssetBolt
AssetBolt
Docs
  • Docs
  • Changelog
  • Feature requests
  • Support portal
    • 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

Webhooks

Webhooks send a real-time HTTP notification to a URL you control whenever something happens in AssetBolt. They're configured under Settings → Integrations → Webhooks, separately from the "Send a webhook" automation action.

Webhooks require a Pro plan or higher.

Creating a subscription

Each webhook subscription needs:

  • A destination URL - the HTTPS endpoint AssetBolt will POST to. Must resolve to a public address (AssetBolt blocks internal/private addresses) and can be up to 2048 characters.

  • At least one event - pick from the same event categories used by Automations (devices, accessories, consumables, licenses, people, integrations, cloud and data assets, maintenance, asset requests, warranties, audits, and so on). Duplicate selections are removed automatically, and unsupported event names are rejected.

  • An optional description - up to 500 characters, useful for telling subscriptions apart.

Your signing secret

When a subscription is created, AssetBolt generates a signing secret and shows it to you once, right after creation, in a copy dialog. Use it to verify that a delivery genuinely came from AssetBolt.

Copy the secret immediately. It is not stored anywhere you can retrieve it again. If you lose it, delete the subscription and create a new one to get a fresh secret.

Testing a webhook

Use the Test action on a subscription to send a sample delivery to your endpoint. Test deliveries are never retried, so a failed test just means your endpoint didn't respond successfully.

Delivery history

Each subscription's delivery history shows, per attempt:

  • The event type

  • The response status (or an error indicator if the request never got a response)

  • How long the request took

  • When it was sent

  • An error message, where relevant - hover over a truncated message to see the full text

Failed deliveries are retried automatically with increasing backoff, up to 5 attempts total. Deliveries stop retrying (and are marked failed) once a subscription is turned off or deleted, so you won't see attempts land after you've paused something.

Turning a subscription on or off

Toggle a subscription inactive to pause its deliveries without losing its configuration or history. Deleting a subscription removes it entirely; any deliveries still in flight for it are marked as failed rather than sent.

PrevExporting your data
NextManaging your account and password
Was this helpful?