Webhooks FAQs

Get answers to frequently asked questions about Webhooks.

What are common errors encountered with the Webhooks connector?

Common errors with the Webhooks connector include:

• Webhook address is already used

  • This error occurs when the event name used in your webhook address is already being used in another recipe. Each event name must be unique across all your webhook recipes to avoid overlap and confusion. To resolve this error, change the event name in your webhook to something unique that isn’t being used in another recipe.

• Error generating schema for response

  • This error appears when there's a mismatch between the Content-Type specified in the webhook header and the actual payload data type. For example, the header indicates JSON data, but the payload is in XML format. This mismatch typically occurs with legacy or custom applications that don't follow standard HTTP practices, resulting in a Content-Type that doesn't match the actual payload format. To correct this error, check with the application owner to ensure the webhook API sends data in the correct format. If adjusting the source isn’t possible, you can manually configure the payload schema in Workato by selecting Save and skip and then defining the schema yourself.

What should I do if the application sending the webhook does not follow standard HTTP practices?

If the sending application's Content-Type doesn’t match the payload format, and it cannot be corrected at the source, you should manually configure the payload schema in Workato to match the actual data format being received.

Can the same webhook address be used in multiple recipes?

No. Each webhook address must be unique within your Workato account to prevent different recipes from inadvertently triggering each other.

What are rate limits for webhooks?

Our webhook gateway has the following rate limits:

• Steady rate: 20 events per second, equivalent to 72,000 events per hour.
• Burst allowance: 1,000 events that can be processed beyond the steady rate in a burst.

Leaky bucket rate limiting

The webhook gateway uses a leaky bucket approach with the following process:

• If you receive more than 20 events in a second, the excess events consume your burst allowance.

• If you receive fewer than 20 events in a second, the remaining capacity refills your burst allowance, but only if the burst allowance is less than 1,000 events.

If you exceed both the steady rate (20 events per second) and the burst allowance (1,000 events), the webhook gateway returns a 429 Too Many Requests response for additional events until the rate falls within the limit.

How do I generate a unique webhook address?

To generate a unique webhook address:

1

Select the Webhooks connector from the list of Apps.

2

Click Guided setup to open the setup wizard.

3

Enter a unique event name for the webhook.

4

Complete the remaining steps in the setup wizard.