Datasource: Webhook
Use Webhook for direct push-based ingestion from external systems.
A webhook datasource exposes an endpoint that receives inbound requests and emits payloads into workflow execution.
Best Use Cases
- Third-party callback integrations
- Fast event triggering from SaaS systems
- Low-latency API-to-workflow handoff
Configuration Fields
| Field | Required | Type | Default | Purpose |
|---|---|---|---|---|
| No manual fields | - | - | - | Only datasource name is required. Webhook ID and token are generated automatically. |
How to Configure Correctly
- Select Webhook datasource type.
- Enter a datasource name and save.
- Copy the generated webhook URL.
- Configure external system callback target.
- Send a test payload and validate workflow trigger.
Endpoint Format
POST https://solutionengine.io/webhook/{id}?token={token}
Security Guidance
- Validate source authenticity in workflow logic
- Use secret headers/signatures from caller systems
- Restrict exposed webhook endpoints through network controls when possible
- Avoid predictable endpoint names for sensitive integrations
Webhook endpoints should not be treated as trusted input. Always validate payload structure and sender identity.
Common Problems
- No events: wrong endpoint mapping or caller misconfiguration
- Invalid payload: caller sends incompatible body shape
- Duplicate events: caller retries without idempotency handling
Related Pages
- Continue with Datasource - HTTP GET for polling-based alternatives.
- Continue with Workflows for request validation and idempotency patterns.