In the new Webhook Logging add a column with the source or location of the webhook (name of Automation, etc.)
We know. Totally wiffed that use case. We were thinking about troubleshooting a webhook as you build it... but then when it went live, we saw all these orphans... duh.
We're on it.
Please sign in to leave a comment.
Hi! We wanted to let you know we have made the updates to webhook activity logs that you requested here.
Now you'll see additional data for the webhook's rule object and type. And you'll be able to see the name of the source it comes from. For instance, if a webhook was triggered by a form fill on a page, the page name will be displayed. And you'll see the specific webhook's ID whenever it's from a source that isn't the API.
Learn more about webhook activity logs here.
Thanks for the update. That is helpful. I'm not a webhook expert but as I look at the log, if I were troubleshooting a webhook, the missing piece for me is the data sent (not just the destination URL). Is there another way I can find data that was sent to match the Response Data?
Click on the log item to open it and see both the sent payload and the response.
Ah, ok, I hadn't tried clicking on the Response Data to open the log item. Thanks! This will make troubleshooting fun... almost.