How to Use the Inbound Webhook Workflow Trigger

The Inbound Webhook trigger turns any Sparkforge workflow into a public endpoint. When an external system fires an HTTP request at the trigger URL, Sparkforge captures the payload and runs the workflow with that data available in every downstream action.

What an Inbound Webhook Does

Each workflow that uses this trigger gets a unique URL. External systems hit that URL with a POST, GET, or PUT request and a JSON body. Sparkforge parses the body, exposes its fields to the workflow, and runs the steps you have built.

Use Cases

• eCommerce orders: when a new order is placed, send the customer name, email, phone, and order total to Sparkforge so the contact and tags are created automatically.
• Support tickets: when a ticket is filed in your helpdesk, sync the subject, priority, and customer ID into Sparkforge to drive a follow-up sequence.
• Form fills on third-party sites: capture leads from sites you do not host and start a Sparkforge nurture sequence.
• Custom internal tools: if your team has a tool that does not have a native Sparkforge integration, point its webhook output at the inbound URL.

Premium Action Notes

Inbound Webhook is part of Sparkforge Premium Triggers & Actions. Premium executions are billed at $0.01 each. Each new sub-account gets 100 free executions, and rebilling can be enabled per sub-account or globally through the SaaS configurator.

Set Up the Trigger

1. Open Automations > Workflows and create or edit a workflow.
2. Click Add Trigger and choose Inbound Webhook.
3. Sparkforge generates a unique URL — copy it.
4. Click Test Workflow. Sparkforge waits for an incoming request.
5. From the external system, fire a sample request at the URL with realistic data. Use POST with a JSON body for most cases.
6. Sparkforge displays the parsed payload. Click Save to lock the field map.

Use the Captured Fields in Actions

Once the trigger is mapped, every field in the payload is available as a merge field. For example, a payload with customer.email exposes {{inbound_webhook.customer.email}}.

Communication Actions

Drop merge fields directly into email, SMS, and WhatsApp action bodies — for example, Hi {{inbound_webhook.customer.first_name}}, your order #{{inbound_webhook.order.id}} is confirmed.

If/Else Actions

Branch on any payload value. Route high-value orders to a sales notification, route low-value ones to a standard receipt, or split by region using a country code field.

Things to Watch

• Each test request consumes a premium execution. Use a dedicated sandbox sub-account for early testing.
• Sparkforge expects a JSON body. If your sender uses form-encoded data, switch the request to JSON or convert it upstream.
• Field names in the payload must stay consistent. If the sender renames a field, the merge field stops resolving.