Workflow WebhooksWorkflow Webhooks

Request a feature

Tell us what would make Workflow Webhooks better. The more specific the goal, the better.

Request a feature - Workflow Webhooks

Tell us what would make Workflow Webhooks better. The more specific the goal, the better.

Drop a file here, or click to choose

What helps most

  • Describe the outcome, not the feature. "I need to route a call to a different Flow based on a field in the payload" tells us more than "add a router".
  • Say how you handle it today. A workaround shows us the shape of the gap.
  • Tell us the volume. Something that runs 10,000 times a month is a different problem from something you do once a week.

Already possible?

A few things people ask for that already exist:

  • More than four fields - tick Security -> Allow Custom Request Body to pass the whole payload through, on top of the four mapped fields.
  • A different auth header name - the static-token header is configurable per webhook in Advanced Settings; it just defaults to X-Api-Key.
  • Calling an external system from Flow - that is the Flow action this app ships, the reverse direction of the trigger.
  • Re-running a call that failed - open the invocation in History and replay it.

If one of those covers you, Introduction to Workflow Webhooks has the details.

Found a bug instead?

If something is broken rather than missing, use Report a bug - bugs are triaged ahead of feature requests.