Using multiple webhooks in one published story
You can utilize multiple webhooks within a single published story to facilitate your workflows. You can have two webhooks leading into the beginning of a story if your use case requires it. When doing so, ensure that the data format and the tools involved remain consistent across these inputs.
Note that a send to story action's entry point must be a webhook action itself and is restricted to only one entry point.
Copying a webhook action
To copy a webhook action, ensure that the secret and path are identical to the original version, and then delete the old webhook action.
You can also recreate a deleted webhook by setting up a new webhook with the original secret and path.
Adding CORS to a webhook action
Add CORS (Cross Origin Resource Sharing) to a webhook action by selecting ‘+ Option’ in the properties panel and choosing "Enable CORS".
Sending the webhook request body as a response
When a request is made to a webhook action, the default response is "Ok". To change the response to send the request body instead, follow these steps:
First, add the response option to the webhook action.
Then, add a value pill referencing the body of the webhook action using the syntax:
Rate limits for Tines webhooks
Individual webhook paths are restricted to 1,000 requests per minute.
The overall webhook rate limit per tenant is 2,500 requests per minute. If a tenant reaches this limit, webhooks will stop receiving events tenant-wide.