Skip to main content

​
Prerequisites

  • A Trigger.dev account with active projects and tasks
  • Access to your Trigger.dev project settings to configure webhooks

​
Step-by-Step Setup

​
1. Navigate to Integrations

In your Corelayer dashboard, go to the Integrations page.

​
2. Add Trigger.dev Integration

Click the Add Integration button and select Trigger.dev from the list of available integrations.

​
3. Copy the Webhook URL

Corelayer will provide a webhook URL. Copy this URL for use in the next step.

​
4. Enter Your Tasks URL

Provide the URL of your Trigger.dev tasks page (e.g., https://cloud.trigger.dev/orgs/<org>/projects/<project>/env/<environment>/tasks). Corelayer uses this to extract your organization, project, and environment details.

​
5. Configure the Webhook in Trigger.dev

In your Trigger.dev project:
  1. Go to your project settings
  2. Add a new webhook with the URL provided by Corelayer
  3. Copy the webhook signing secret generated by Trigger.dev

​
6. Enter the Webhook Secret

Paste the webhook signing secret into the Corelayer setup form and click Save.

​
7. Add Trigger.dev to Your Service Maps

When configuring your Corelayer Service Maps, select Trigger.dev as a relevant integration for your services.

​
What Corelayer Can Do With Trigger.dev

Once connected, Corelayer will:
  • Receive real-time webhook events when jobs fail or encounter errors
  • Pull job execution context for debugging
  • Correlate job failures with other integrations for root-cause analysis
  • Summarize errors and suggest remediation steps

​
Managing Your Integration

​
Disconnecting

To disconnect your Trigger.dev integration:
  1. Navigate to Settings > Integrations
  2. Find your Trigger.dev integration and click Uninstall
  3. Confirm the uninstallation
  4. Remove the webhook from your Trigger.dev project settings

​
Troubleshooting

​
Integration Not Working?

  • Verify the webhook URL is correctly configured in Trigger.dev
  • Ensure the webhook signing secret matches between Trigger.dev and Corelayer
  • Check that your Trigger.dev tasks URL is in the correct format
  • Confirm that your Trigger.dev environment is active and running jobs
Need help? Contact support for assistance with your Trigger.dev integration.