Webhooks Integration

The Webhooks integration with Asset Panda Pro enables real-time data delivery to external systems whenever specific events occur within Asset Panda. By automatically sending structured event data to configured endpoints, teams can trigger downstream workflows, keep third-party systems up to date, and build custom automations without polling or manual intervention. This integration is ideal for connecting Asset Panda with workflow tools, middleware platforms, and custom applications that require immediate updates.

Supported Events

Webhooks can be triggered for the following events in Asset Panda Pro:

  • Record created

  • Record updated

  • Record deleted

  • Form submitted

Each event sends a standardized JSON payload to the configured webhook endpoint

Prerequisites

  • Active Asset Panda Pro subscription

  • Administrator access to Asset Panda

  • One or more externally accessible webhook URLs that can accept HTTP POST requests

Webhook Configuration in Asset Panda

Webhooks are configured directly from the Agent page after enabling the integration from the Integration Store.

Add the Webhooks Integration

  1. Sign in to Asset Panda as an administrator.

  2. Navigate to Settings > Account Management.

  3. Open the Integration Store.

  4. Locate the Webhooks integration and click Add.

Configure a Webhook Agent

  1. Go to the Agents page.

  2. Create a new Agent or edit an existing one.

  3. Select a Trigger, such as:

    • When a record is created

    • When a record is updated

    • When a record is deleted

    • When a form is submitted

  4. Select Action as Subscribe to Webhook.

  5. Click Add URLs and enter one or more webhook endpoint URLs.

    • URLs must accept POST requests.

  6. Save the configuration and test the webook.

Webhook Payload Format

  • Webhook payloads are delivered in standard JSON format.

  • The payload includes structured event data relevant to the trigger type.

  • Payload structure is predefined by Asset Panda and cannot be customized.

Limitations

  • Webhook URLs must be publicly accessible and capable of receiving POST requests.

  • There is no retry mechanism. If a webhook request fails or the receiving system is unavailable, the payload will not be resent.

  • Payload customization is not supported; only the standard Asset Panda JSON payload is delivered.

  • Authentication, validation, and security (such as secret keys or token-based verification) must be implemented and enforced by the receiving system.


Last updated