Webhooks

Webhooks allow external services to trigger workflow execution by sending HTTP requests. TradingGoose supports two approaches for webhook-based triggers.

Configuration

How It Works

1. Add Generic Webhook Block — Drag the Generic Webhook block to start your workflow
2. Get Webhook URL — Copy the automatically generated unique endpoint
3. External Integration — Configure your external service to send POST requests to this URL
4. Workflow Execution — Every request to the webhook URL triggers the workflow

Features

• Flexible Payload — Accepts any JSON payload structure
• Automatic Parsing — Webhook data is automatically parsed and available to subsequent blocks
• Authentication — Optional bearer token or custom header authentication
• Rate Limiting — Built-in protection against abuse

Trigger Mode for Service Blocks

Alternatively, you can use specific service blocks (like Slack, GitHub, etc.) in "trigger mode" to create more specialized webhook endpoints.

Use Generic Webhook when:

• Integrating with custom applications or services
• You need maximum flexibility in payload structure
• Working with services that don't have dedicated blocks

Use Trigger Mode when:

• Working with supported services (Slack, GitHub, etc.)
• You want service-specific event filtering
• You need automatic webhook registration