Fantastic news!
Is the webhook instant or is there also that 1-2-5-minute delay?
In my test (triggering a button column with a webhook) it was instant!
Ha ha - yes, the polarity is often a point of confusion. This is why I tend to describe webhooks with an added predicate; inbound and outbound. Coda has enabled inbound webhooks - i.e., a webhook listener. Outbound webhooks are achieved through packs - either custom or pre-made (Like Makeās).
Depending on a few factors (e.g. how many other API requests your doc is processing), there may be a delay from when the endpoint receives the POST request and when the automation is run.
Yes, that predicate makes a lot of sense and helps with the confusion. Thank you
This is massive! Very excited to explore the possibilities here. Was hoping for webhook functionality in Packs, but this lets you execute Pack formulas with a hook so should take care of the use cases I was imagining.
I have a feature request related to this:
Please allow passing the API token as a query param in the webhook URL
(e.g. https://coda.io/apis/v1/docs/xxxxxxxxxx/hooks/automation/grid-auto-yyyyyyyyyy?key=MY_API_TOKEN
)
Reason: many (if not most) 3rd party tools that can trigger webhooks only let you set up the URL but not any custom headers. So thereās currently no way to e.g. integrate a Telegram Bot with Coda because thereās no way I can instruct Telegram to pass an Authentication: Bearer <token>
header in its webhook trigger.
I understand this is potentially a security issue (exposing the token through URL) but if the token is generated specifically for a hook and is restricted to it, this shouldnāt be much of a problem.
Alternatively allow accepting anonymous triggers with no auth tokens and let us manually filter through requests in the āIFā step.
Hi, @Paul_Danyliuk! Thanks for the feature request. Weāre aware of the limitations of this current model. We went with this approach because it was the easiest way to leverage our existing API infrastructure to make v1 of this feature work.
In the meantime, if you require unauthenticated webhook endpoints, we recommend using Zapier webhooks as an intermediary between your service and the Coda webhook. I know itās not ideal, so weāll still keep your feature request in mind.
For my use case, it turns out that cross-doc actions is what I need. Info here: How to Use Cross-Doc Actions | Coda Help Center
Iām trying to move rows from a table in one doc to a table in another doc. I didnāt figure out that cross-doc actions were the solution until I reached out to support, so leaving this for others in the same boat.