You can use webhooks to automate simple workflows or fire automated HTTP messages to third-party services, based on the same event triggers and constraints available for email notifications..
Who can create webhooks?
App admins and managers can create webhooks. Anyone who can create webhooks can also activate, deactivate, view, update, delete, and copy webhooks created by other users.
The owner of the webhook must meet all of the following conditions, or the webhook will not be sent:
- Owner has permission to the table.
- Owner is a registered user.
- Owner is not on the deny list.
What plans have access to webhooks and are charged for their use?
All billing plans except for Quickbase Essential have access to use webhooks. You are not charged for outgoing webhook messages. However, webhooks calling out to the Quickbase API will count against your API limit for the app receiving the message.
When you copy an app, all webhooks will be transferred but will be marked as inactive.
Can I transfer an app with webhooks to other users?
You can transfer an app with webhooks. If you transfer an app to a user who is an Admin, they will have full permissions on webhooks in the transferred app.
When you use a sandbox with an app, changes to webhooks are not supported; they won’t be tracked as changes in a sandbox and can’t be published as changes to the live app.
What happens if I share an app to the Exchange that is using webhooks?
When sharing an app to the Exchange your webhooks will be removed.
What limits do webhooks have?
- Table limit: You can create only ten webhooks per table.
- Size limit: The webhook message cannot be greater than 4MB. If this is exceeded the message will not be sent and the app manager will receive an alert as well as an email notification informing them that the message was not sent. To fix this, edit the webhook definition to reduce the message size.
- Payloads: If the size of the table record that trigger the webhook exceeds 1MB, the trigger event will be rejected from pipelines.
- Rate limit: For any app, a maximum of 50 webhook messages can be sent per second. If this rate is exceeded, subsequent message/s will not be sent and the app manager will receive an alert as well as an email notification informing them that the message/s was not sent. If you have multiple pipelines listening on events on the same app the limit will be shared between them. Limits are per app NOT per pipelines.
- Pipelines share webhooks. As a result:
- If you have multiple pipelines listening to the same table on mixed create/update events you should combine triggers.
- If you have multiple pipelines listening on events on the same app, the limit is shared.
- If the conditions on the trigger are the same webhook will be shared which means that having a more specific filters will result in more triggers.