---
title: "Request a feature - Workflow Webhooks"
description: "Suggest an improvement to Workflow Webhooks. Describe the outcome you want and how you handle it today."
canonical: "https://crm-tool.k8s-gcp-dev.eu.codecreationlabs.cloud/h/flow-webhooks/help/request-a-feature"
---

# Request a feature

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

**Form: Contact**

## 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](https://crm-tool.k8s-gcp-dev.eu.codecreationlabs.cloud/h/flow-webhooks/introduction.md) has the details.

## Found a bug instead?

If something is broken rather than missing, use [Report a bug](https://crm-tool.k8s-gcp-dev.eu.codecreationlabs.cloud/h/flow-webhooks/help/report-a-bug.md) - bugs are
triaged ahead of feature requests.