Workflow Trigger: Inbound Webhook in Sparkforge

What it does

The Inbound Webhook trigger starts a Sparkforge workflow when an external system POSTs, GETs, or PUTs data to a unique webhook URL. Use it for form submissions, payment events, third-party app updates — anything that can fire an HTTP request.

Trigger name: Inbound Webhook

What it captures: Incoming POST/GET/PUT requests to the URL Sparkforge generates for the trigger. Payload data can be mapped to workflow fields.

How to configure

1. Open or create a workflow. Add Inbound Webhook as the trigger.
2. Copy the webhook URL. Sparkforge generates a unique URL for this trigger.
3. Configure the external app. Point its webhook or HTTP action at the Sparkforge URL. Send the payload as JSON.
4. Test the integration. Send a test request from the external app to confirm Sparkforge receives the data.
5. Map the payload. Pick which incoming fields populate which workflow variables or contact fields.
6. Save the trigger. Click Save Trigger to lock it in.

Example: Stripe payment confirmation

Wire Stripe events into Sparkforge so successful payments trigger downstream automations.

1. Create a workflow in Sparkforge with the Inbound Webhook trigger and grab the URL.
2. In Stripe, add a webhook for the payment_intent.succeeded event pointed at the Sparkforge URL.
3. Stripe POSTs a JSON payload, e.g.:

   {
     "customer_id": "CUST_001",
     "amount": 100,
     "currency": "USD",
     "status": "successful"
   }

4. In the Sparkforge workflow, map customer_id to the contact lookup, then chain actions: update lead status to Paid, send a confirmation email, fire follow-up automations.