Support outgoing webhooks

Grist should allow the user (and integrators) to trigger other services on common events such as record updates.

Without webhooks, users (and integrators) need to resort to polling, which is less than ideal for everyone concerned. Our Zapier integration currently uses polling, but if we had webhooks it could be upgraded to ‘instant’ triggers, meaning faster workflows for users and less server load for us.

Update: there is some unofficial support for webhooks, for those willing to use the Grist API to configure them. For hosted Grist, Webhook URLs are allowed for the following domains:

• zapier.com
• pabbly.com
• webhook.site
• meta-api.io
• pipedream.com, pipedream.net
• deta.sh
• netlify.com

If you need a different domain, please request it. If self-hosting, be sure to add the domain you care about to a comma-separated ALLOWED_WEBHOOK_DOMAINS environment variable (e.g. zapier.com,pabbly.com,webhook.site).

[HermesRatgers]

@paulfitz Added it and it works, I also added this thread to Pabbly so they can add the webhook aswell. Btw the integration can be managed by you aswell, simply request this by email them your pabbly emailadres and request editor permission. https://pabbly.hellonext.co/b/Update-Existing-Application/p/webhook-triggers-for-getgrist

[paulfitz]

@simplynail do you mean a UI for creating webhooks? No, there’s no ETA for that, sorry. We do want to get it done when we have capacity, I know that isn’t very helpful for you.