How to Use the Custom Webhook Workflow Action in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Custom Webhook action sends real-time data from Sparkforge workflows to any URL. Configure the HTTP method, authorization, headers, query parameters, and request body inside the workflow builder.

The Custom Webhook action lets a Sparkforge workflow push data to any third-party service in real time. You pick the URL, HTTP method, authorization, headers, query parameters, and the body. No code, no server.

What the Custom Webhook action does

It connects a workflow step to an external API. When a contact reaches the step, Sparkforge fires the request you defined. Autocomplete on the body field surfaces every available variable from the contact record and any inbound webhook payloads earlier in the workflow.

Who uses it

Operators who need their CRM to talk to a tool Sparkforge doesn't natively integrate with — billing systems, custom dashboards, partner APIs, niche industry software. If you can hit it with HTTP, you can wire it into a workflow.

How to set up a Custom Webhook

Fill in the URL. Paste the endpoint the request should hit.
Pick the HTTP method. POST, GET, PUT, or DELETE.
Choose an authorization method. Multiple options are supported — pick the one your endpoint expects.
Add headers and query parameters. Headers carry credentials, content type, and cache control. Query parameters filter or shape what the endpoint returns.
Configure the request body. Map fields and custom values into whatever JSON structure the receiving API needs. The autocomplete picker exposes contact fields, custom values, and inbound webhook variables.

Troubleshooting

The action only succeeds if the receiving API returns a success response. Errors mark the step as Failed (and skipped) or trigger retry with exponential backoff.

If you're firing the webhook against a server with rate limits, watch your contact volume. The action runs the moment a contact hits the step, so a flood of contacts can flood your endpoint.

Frequently Asked Questions

What HTTP methods does the Custom Webhook action support?

POST, GET, PUT, and DELETE. Pick whichever the receiving endpoint expects.

What happens if my endpoint returns an error?

The workflow step is marked Failed and either skipped or retried with exponential backoff, depending on configuration. The error is recorded against the contact's workflow execution log.

Can I send authentication credentials in a Custom Webhook?

Yes. The action supports several authorization methods, and you can also pass credentials in custom headers if your endpoint expects them there.

Will the webhook fire faster than my receiving server can handle?

It can. The action runs the instant a contact reaches the step, so if you push a large batch of contacts into the workflow, the receiving server hits the requests in quick succession. Throttle by adding a Wait step before the webhook if needed.