Send notifications from your Paragon project into your logging, analytics, and APM services.
Note: This feature is only available to Admin users. Learn more.
Event Destinations allow you to configure notifications for events that occur in your Paragon project.
For example, if you’d like to add another email to be notified by email when a workflow fails, you can add an Email Destination. If you prefer notifications via Slack, you can configure a Webhook Destination to a Slack incoming webhook.
You can find your project’s Event Destinations by navigating to the global Settings tab in the left sidebar and selecting Monitoring under your Project Settings.
From this Monitoring page, you can take any of the following actions for any Event Destination:
By default, your project will include an Email Destination for Workflow Failure events, using the email address of the user that created the project.
You can set up additional Email Destinations by following these steps:
From the Settings > Monitoring page, click the Add Destination button at the top right.
In the Type field, select Email.
In the To field, enter the desired email to be notified.
Optionally, send a test email with the Test Email button at the bottom left.
Click Save to create and enable the new destination.
Webhook Destinations are available for Paragon customers on paid plans. To learn more, contact our team at [email protected].
Webhook Destinations allow you to receive event notifications from your Paragon project via HTTP requests. Webhook Destinations will receive a POST request when the event occurs, with configurable request headers and body contents.
If you use Slack, Datadog, New Relic, or Sentry, you can configure a Webhook Destination by clicking “Select Template” under Request Payload and following the guide to configure below:
Send events as messages in Slack
Send events as logs in Datadog
Send events as logs in New Relic
Send events as issues in Sentry
You can set up a Webhook Destination by following these steps:
From the Settings > Monitoring page, click the Add Destination button at the top right.
In the Type field, select Webhook (HTTP Request).
In the URL field, enter the desired URL to receive the event payload.
Optionally, in the Request Payload field, you can change the format of the payload. By default, the webhook will receive the full event object ($.event
). Use {{
to specify a part of the event data to use in the request payload.
Optionally, additional request headers can be specified by expanding “Show more request options”.
Send a test request to your Webhook Destination by clicking Test Webhook button at the bottom left.
Click Save to create and enable the new destination.
Note: Your Webhook Destination may be automatically disabled if your webhook responds with too many non-2xx status codes for consecutive events.
The following events can be sent from your Paragon project:
Workflow Failure
An error occurs at any point in a workflow and causes the workflow to reach the Failed status.
Example webhook payload:
Credential Failure
An error occurs during the OAuth refresh process which cannot be retried. After this error, the user’s credential will be marked as invalid.
Use this event to notify your user to revisit the Connect Portal in your app and re-establish the connection to the affected integration.
Example webhook payload:
We are working on adding support for more events. Have a request for other events you’d like to send from your Paragon project? Let us know.