Triggers

Markdown

When events occur in apps, like a new Slack message, a GitHub commit, or an incoming email, triggers send event data to your application as structured payloads.

Triggers flow: Connected apps send events to Devcaster, which delivers them to your webhook endpoint via HTTP POST
How triggers deliver events from apps to your application

There are two delivery types:

  • Webhook triggers: Apps like GitHub and Slack push events to Devcaster in real time. When an event fires, Devcaster forwards the payload to your webhook endpoint.
  • Polling triggers: For apps that don't support outgoing webhooks (e.g., Gmail), Devcaster polls for new data every minute. Expect small delays between the event and delivery.

Working with triggers

  1. Configure your webhook endpoint so Devcaster knows where to deliver events
  2. Discover available trigger types for a toolkit (e.g., GITHUB_COMMIT_EVENT)
  3. Create an active trigger scoped to a user's connected account
  4. Receive events: Devcaster sends payloads to your endpoint
  5. Manage: enable, disable, or delete triggers as needed

Next steps