Webhooks
Webhooks let external systems trigger your Canvas workflows. When a third-party service sends data to your webhook URL, Canvas starts the workflow with that data as the input.
Adding a Webhook Step
Drag the Webhook step from the Integrations category onto your canvas. This step acts as a trigger — it is the entry point for your workflow.
Configuration
When you add a Webhook step, Canvas generates a unique webhook URL. Configure it in the right panel:
- Webhook URL — Copy this URL and paste it into the external system that should trigger your workflow.
- Method — The HTTP method to accept (POST, GET, PUT, etc.). Most integrations use POST.
- Authentication — Optionally require a secret token in the request header for security.
- Payload mapping — Define how the incoming JSON data maps to variables that downstream steps can use.
How It Works
- An external system sends an HTTP request to your webhook URL.
- Canvas receives the request and parses the payload.
- The Webhook step outputs the parsed data as variables.
- Downstream steps use those variables to process the data.
Common Use Cases
- Form submissions — A website form sends data to Canvas, which creates a customer record and sends a confirmation email.
- Payment events — Stripe sends a webhook when a payment succeeds, triggering an invoice update workflow.
- CRM updates — An external CRM notifies Canvas when a deal closes, triggering an onboarding workflow.
Tips
- Always use authentication on production webhooks to prevent unauthorized triggers.
- Test webhooks by sending sample data with a tool like Postman or curl.
- The Webhook Manager component lets you view and manage all active webhooks across your canvases.
On this page