Hosted version of Grist does not seem to be sending webhook response to pabbly connect

[anupamtandon]

Hello Team,
Is there problem with Grist - Pabbly connect?Hosted version of Grist does not seem to be sending webhook response to pabbly connect.

I believe existing connections seem to be working fine. Only new connections we are unable to make.
Please help.

Thank you!!
Anupam

[paulfitz]

Hi @anupamtandon, I'm not aware of a problem. Are there any specific error messages you are seeing that might narrow things down?

[anupamtandon]

This issue is specific to Pabbly connect (the integration service). So if we use pabbly connect to send the data (new record) from grist to our email marketing platform (such as acumba mail) , ideally grist should send webhook response to pabbly which then sends the grist's response to acumba mail. Here, for new connections, grist is not sending the webhook response to pabbly at all. So if grist is the first part of integration (trigger) then things are not working as expected. It is not issue with Grist functionality but issue in grist-pabbly communication.

[paulfitz]

@anupamtandon maybe you could provide a document id (if sensitive, I'd suggest you send it to support@getgrist.com) as a starting point into looking at this. There's nothing special in Grist to support Pabbly connect, other than their domain being on our allow-list for webhooks.

[anupamtandon]

@paulfitz thank you for your response. Sure, please find below the details of the test table that i created in Grist . I created a new test account and table in grist and tried to get webhook response in pabbly. But in pabbly no webhook response is coming. Has there been any recent changes in the GRIST API that needs to be updated in Pabbly's side?

UserID: [qspider10@gmail.com]
Password:

In GRIST, have created a table in the personal domain. I have named every thing there with name starting "Pabbly" .

Domain Name : Personal
Workspace Name : pabbly
Document Name : PabblyDocument
Table Name : PabblyTable

If a new record is added in PabblyTable, then I want to be able to capture the response in pabbly connect and then send it to accumbamail (another mail app). Howeve rfirst step itself is failing as Pabbly connect is unable to capture the webhook response. Pabbly Connect team says that possibly the Grist API documents have changed and there is nothing wrong at their end.

[paulfitz]

Hi @anupamtandon, thanks for the pointer to the document. Just so you are aware, this is a public repository, so to prevent abuse it would be a good idea to change the password on that account, even if there is nothing of value to you in it. Looking at https://docs.getgrist.com/api/docs/es467cPbaBL8/tables/_grist_Triggers/records I see a webhook listed that is subscribed to updates (changes in data) rather than adds (new records). I updated a record that was ready in the document, and saw in our logs an attempt made to deliver data to connect.pabbly.com, but if failed with an DocTriggers: Webhook responded with non-200 status message caused by a 404 error. This was the first attempt at message delivery I see for this document.

Can you double check that the document was configured to deliver webhooks on new records as opposed to updated records?

Sorry, I imagine this is frustrating, to be talking to Grist people and Pabbly people and to not be able to get a clear picture of what is happening to your webhooks.

[anupamtandon]

Hello @paulfitz , thank you very much for your kind suggestion. I had created the account only for testing purpose and once this issue is resolved, i will delete the account.

Coming to the issue, main problem is that the webhook response does not come for both scenarios (triggers): (i) New Records (ii) Updated Records. So something there seems to be broken. Also in my existing connections which i created 3 to 4 months ago, occasional errors have started popping up.