Right now, webhooks send a default payload as an array of items: [{item1 object},{item2 object},...] This is creating a problem with most popular automation tools, like n8n, make.com and zappier The customers have to create custom steps, like increasing the number of records for a webhook, checking logs, etc, so we need to make it easier for customers to use webhooks. First thing to do is to try a different payload, where all results are under a format like this: { 'results': [{item1 object},{item2 object},...]} This way, the automation tools won't see it as multiple records, but as one. Now, in order to not break the previous implementations of webhooks, we need an UI change. When you use a webhook node in canvas, it needs to have a dropwdown of payload. By default it will be 'Standard', but we should have other choices like: 'N8N', 'Make.com', 'Zappier', 'Other Automation tools' All, apart from standard, will send the new format of the payload. The idea to have all the choices is to, in the future, separate the payloads in case we have to go more custom. When we fire the webhook, we need to check the payload type.
0 votes
Vote to help us prioritize this feature
Sign in to join the discussion
Sign in