trigger-registry

Yes, you can create reactive triggers that execute skills or routines in response to external webhooks and integration events. This applies to automation scenarios such as GitHub push notifications, Stripe payment reactions, and Linear issue workflows with selectable filters.

You can create a webhook trigger by defining the trigger type as webhook, setting the source to stripe, applying event filters, and selecting an action type such as a skill, prompt, or routine script to execute when the payment event fires.

You can test webhook triggers using a dedicated trigger test endpoint provided by the dashboard backend API. This allows you to verify trigger behavior and event filtering reliability before processing live external events.

The trigger system supports secure webhook endpoints with HMAC validation to ensure incoming integration events are authentic. It also supports secret regeneration for maintaining webhook security over time.

When a Linear issue trigger fires, you can execute a Claude skill, a free-form prompt, or an existing routine script. The action type is selectable when defining the trigger for your event-driven automation workflow.

You can manage triggers using CRUD operations and toggle their enabled or disabled states via the dashboard backend API. This allows you to pause event-driven automation without deleting the trigger configuration.