> ## 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.

# Triggers API

> Subscribe to events from your users' integrations, using our catalog of pre-built triggers or Custom Webhooks.

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:

* 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)

<Info>
  **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](/actionkit/actionkit-logs) is subject to change. If you have feedback or questions, please reach out to our [support team](mailto:support@useparagon.com).
</Info>

## 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).

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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](/actionkit/actionkit-logs).
  </Step>
</Steps>

## API Usage

**Base URL**

```
https://actionkit.useparagon.com/projects/[Project ID]
```

<Accordion title="For on-premise instances">
  ```
  https://worker-actionkit.[On-Prem Base URL]/projects/[Project ID]
  ```
</Accordion>

**Authentication**

To authenticate to Triggers API, present a Bearer token with the Paragon User Token (a JWT):

```js theme={null}
Authorization: Bearer [Paragon User Token]
```

This is the same token that you used to call `.authenticate` with the Paragon SDK. See examples in [Installing the SDK](/getting-started/installing-the-connect-sdk).

<Accordion title="Using Multi-Account Authorization">
  [Multi Account Authorization](/apis/api-reference/multi-account-authorization#getting-started) is a set of SDK options that enables you to connect multiple accounts of the same integration type for a [Connected User](/billing/connected-users).

  You can use Multi-Account Authorization with Triggers API by specifying a credential with a header of `X-Paragon-Credential`.

  ```http REST API theme={null}
  POST https://actionkit.useparagon.com/projects/<Project ID>/triggers

  Authorization: Bearer <Paragon User Token>
  X-Paragon-Credential: <Credential ID>
  ```
</Accordion>