Capture real-time events
Use generated webhook URLs to start workflows from external systems.
Webhooks
Turn external events into real-time workflows
Receive webhook events from external services, process payloads immediately, and trigger workflows without polling or manual checks.
Core Capabilities
What this feature helps your team do
Transform incoming payloads
Parse data, validate fields, branch logic, and send results to connected apps.
Return workflow results
Support synchronous API-style flows when callers need an immediate response.
Real-time connectivity
Stop waiting for systems to be checked manually
Webhooks let external products tell puq.ai when something happens, so workflows can respond as soon as the event arrives.
- Unique webhook endpoints
- Async and sync processing patterns
- Payload mapping
- Lifecycle-friendly integration setup
How It Works
A practical path from setup to production
Create a webhook trigger
Generate a URL for the workflow.
Register the URL
Add it to the external system that sends events.
Process the payload
Use the incoming data in actions, conditions, and AI steps.
Return or continue
Respond immediately or let the workflow continue asynchronously.
Common Use Cases
Where teams use Webhooks
Payment event handling
GitHub issue automation
Form submission workflows
Internal API workflows
Webhooks questions
Clear answers about how this capability fits into real workflow automation.
A webhook trigger starts a workflow when another system sends an HTTP request to a generated endpoint.
Yes. Incoming payload fields can be mapped into actions, conditions, code, and AI steps.
Yes. Webhook workflows can support API-like patterns where a response is returned after processing.
Webhooks are event-driven, so workflows can start immediately without repeatedly checking another system for changes.
Automate Every Job