Triggers

Triggers are webhooks that notify external services. Use triggers to rebuild static sites, invalidate caches, or sync data with other systems.

How Triggers Work

Triggers are manually fired to make HTTP requests to configured URLs. You can fire triggers from the admin UI, API, or MCP.

Trigger Configuration

Each trigger has the following settings:

Trigger Limits

• Each domain can have up to 5 triggers
• Trigger execution has a 15 second timeout
• Failed triggers are logged but don't affect other operations

Trigger Logs

Every trigger execution is logged with:

• Status - SUCCESS or FAILED
• Response code - HTTP status code (200, 404, 500, etc.)
• Duration - How long the request took in milliseconds
• Error message - If the trigger failed, why

View trigger logs in the Triggers page of your domain admin.

Firing Triggers

You can fire triggers from:

1. Sidebar - Click the play button next to Triggers in the sidebar, then select which trigger to run
2. Triggers page - Click the play button next to any trigger in the list
3. API - POST /api/public/{domain}/triggers/{triggerId}/fire
4. MCP - Use the fire_trigger tool

Best Practices

1. Use HTTPS - All trigger URLs must use HTTPS for security
2. Handle failures gracefully - Your webhook endpoint should respond quickly
3. Idempotency - Design your webhook handler to handle duplicate requests
4. Monitoring - Check trigger logs regularly to catch failures

Example Use Cases

Static Site Rebuilds

Configure a trigger to call your static site builder (Vercel, Netlify, etc.):

URL: https://api.vercel.com/v1/integrations/deploy/prj_xxx/xxx
Method: POST

Cache Invalidation

Notify your CDN to purge cached content:

URL: https://api.cloudflare.com/client/v4/zones/xxx/purge_cache
Method: POST

Data Sync

Send updates to a search index or external database:

URL: https://your-app.com/api/content-updated
Method: POST