Skip to main content

Overview

Webhooks allow external systems to react to Forge events in real-time. Trigger CI/CD pipelines, send notifications, update project management tools, or run custom automation.
Real-time integration: Get notified instantly when tasks complete, attempts fail, or processes finish.

Available Events

Task Events

Attempt Events

Process Events


Creating Webhooks

Via API

Via SDK


Webhook Payload

Structure

Signature Verification

Verify webhook authenticity:

Use Cases

Deploy on Task Completion

CI/CD Integration

Notification System

Project Management Integration


Event Listeners

In-Process Listeners

For running logic in the same process as Forge:

Event Filtering


Retry Logic

Automatic Retries

Forge automatically retries failed webhook deliveries:

Manual Retry


Webhook Management

List Webhooks

Update Webhook

Delete Webhook

Test Webhook


Webhook Endpoints

Express Example

Next.js API Route


Best Practices

Always Verify Signatures

Prevents unauthorized webhooks

Respond Quickly

Respond within 5 seconds

Handle Duplicates

Events may be delivered multiple times

Log Everything

Essential for debugging

Troubleshooting

Checklist:
  • Is webhook URL publicly accessible?
  • Is firewall allowing incoming requests?
  • Is webhook active? (active: true)
  • Check Forge logs: forge logs --filter webhooks
Causes:
  • Wrong secret
  • Payload modified (middleware parsing)
  • Incorrect signature algorithm
Solution:
Check:
Common issues:
  • Timeout (endpoint too slow)
  • 500 errors (server crash)
  • SSL certificate errors

Next Steps

Custom Executors

Trigger custom executors via webhooks

Workflows

Complete automation workflows

API Reference

Webhook API documentation