ActionKit Triggers API provides our complete library of pre-built triggers in simple endpoints to discover, configure, and subscribe to events on behalf of your users. You can use the Triggers API to:Documentation Index
Fetch the complete documentation index at: https://docs.useparagon.com/llms.txt
Use this file to discover all available pages before exploring further.
- Add triggers to your workflow builder product from our catalog of 130+ integrations
- Kick off your AI agents / agentic workflows from events occurring in your users’ connected integrations
- Subscribe your webhook to integration events on behalf of your users (for example, Slack: Message Received or Google Calendar: New Event)
Triggers API is currently in beta.The core API is stable and ready for production use, but the monitoring tools and UI in ActionKit Logs is subject to change. If you have feedback or questions, please reach out to our support team.
Getting Started
To get started with the Triggers API, you will need a Connected User with at least 1 account connected in a supported integration. You can then continue to start by configuring a webhook URL (below).Configure a Webhook URL
In the Paragon dashboard, open Settings and add your Webhook URL under the ActionKit tab. This URL will receive events on behalf of all of your users.You can also save your generated Signing Secret to verify that incoming payloads to this webhook are coming from Paragon.
Activate a Trigger
Go to the Connected Users page and select the user you connected an integration with. In the Triggers section, turn on any kind of trigger that you want to listen for.You will see a code example for the equivalent API call you can use to subscribe a user to this trigger.
Trigger an Event
Trigger the event type you activated in the account you connected for your user.You can see the result delivered to your webhook (within a few seconds) or in ActionKit Logs.
API Usage
Base URLFor on-premise instances
For on-premise instances
.authenticate with the Paragon SDK. See examples in Installing the SDK.
Using Multi-Account Authorization
Using Multi-Account Authorization