Webhook is not triggered when a row is created

Technical Help
, ,
1

Hello,
I am using this baserow for my NGO : https://bdd.alternatiba.eu/
And I have configured a webhook, that is supposed to be triggered on row creation, but it appears that the triggering function doesn’t work.

The webhook seems to work fine : I can test it and I got the response I want.

Is there a problem with a the triggering function ? Am I supposed to update something ?

Thanks,

Nicolas

2

Hi @nicolastroadec,

the webhook should work. Can you provide additional information about your problem?

  • Steps to reproduce
  • Baserow version

Please can you also try using a public webhook test site like https://webhook.site/ for your webhook URL and see if you are receiving the calls?

3

Hi @petrs, I’m experiencing the same issue. I was able to successfully send a webhook test to my n8n webhook and to webhook.site, but it isn’t triggered by row creation or row update events. I’m in version 1.29.3

4

Hello everyone, hope you’re doing very well! I am experiencing what appears to be this exact same issue with my self-hosted Baserow instance, where webhooks configured to trigger on row creation are not activating as expected. Here’s a detailed account of the problem and the troubleshooting steps I’ve undertaken:

Issue Description:

• Webhook Configuration:

• Initially set to “Send me everything.”

• Later adjusted to trigger specifically on “Rows are created” events.

• Observed Behavior:

• The “Trigger test webhook” function successfully sends data to the receiving endpoint.

• However, creating a new row does not activate the webhook, and the call logs remain empty.

Troubleshooting Steps Undertaken:

  1. Verified Webhook Settings:

• Changed the configuration from “Send me everything” to explicitly select “Rows are created” events.

• Specified the primary field to monitor.

• Saved the configuration; logs confirmed the changes.

  1. Reviewed Logs:

• Backend logs display POST/PATCH requests to the relevant table when rows are created.

• No corresponding entries appear in the webhook call logs for these actions.

  1. Checked Service Status:

• Confirmed that the Celery worker is active and processing tasks.

  1. Enabled Debug Logging:

• Set the BASEROW_BACKEND_LOG_LEVEL environment variable to DEBUG in the Docker Compose file to obtain detailed logs.

• Despite this, the logs did not provide additional insights into the webhook issue.

Environment Details:

• Baserow Version: Latest as of December 12, 2024 (1.29.3).

• Deployment: Self-hosted using Docker Compose.

• Docker Compose Configuration:

services:
  baserow:
    container_name: cloud.mydomain.com
    image: baserow/baserow:latest
    environment:
      BASEROW_PUBLIC_URL: 'https://cloud.mydomain.com'
      BASEROW_BACKEND_LOG_LEVEL: DEBUG
    ports:
      - "8081:80"
    volumes:
      - baserow_data:/baserow/data

volumes:
  baserow_data:
    external: true

Additional Information:

• Testing with Webhook.site: I have been using Webhook.site to test the webhook functionality. The test webhook successfully sends data to the endpoint, which can be monitored at this link.

• Potential Bug: Given the steps taken and the persistence of the issue, this may be a bug in the current Baserow version.

Steps to Reproduce:

  1. Configure a webhook to trigger on “Rows are created” events.

  2. Create a new row in the specified table.

  3. Observe that the webhook does not trigger, and no entries appear in the call logs.

5

Hey all,

I don’t think the trigger/webhook is fundamentally broken after doing some test on our production instance so we need to investigate this more.

Specifically could anyone having these problems share the URLs and payloads that you use (you can do so privately via DM)? Or can you check whether your URL or data contain NUL characters? I see some Sentry reports regarding webhook and NUL characters so that might be the problem here.