Webhook Event duplication (old thread)
Hi team!
I'm working on extending TwentyCRM with a Zapier-like automation tool called N8n (N8n.io). I'm seeing some odd behavior with how TwentyCRM is sending Webhooks.
I have a custom data model called "Automations" that is effectively an extention of the standard Companies model for things such as client onboarding, system email send status, etc.
I'm on v0.23.2, and I have a Webhook filtered to Automations, UPDATE events to be sent. But I'm receiving ~4 duplicate webhook payloads on a single field's value change.
I've incorperated some consistancy/idempotency into my worflow to set concurrency=1 and a GET to ensure we're using TwentyCRM's latest value and not the value in the Webhook payload. This has solved the duplication issue on my end, but it is 4x the workflow execution load at the moment to filter out these events.
Does anyone know what the cause could be of why so many events are being thrown?
Do record view's or GET's via API cause these events to be thrown?
Thanks!
7 Replies
What's funny for me is a fact that integration with n8n is one of the most requested features https://github.com/twentyhq/twenty/discussions/3828
GitHub
N8N and Windmill integrations · twentyhq twenty · Discussion #3828
Zapier is fine, but not great for an open source tool. Have you considered other integration brokers/platforms ?
It's super easy to make your own integration for TwentyCRM in N8n, I think it took me all of an hour or two after understanding TwentyCRM's REST API
Could you write down steps how did you integrate Twenty with n8n? I'll maybe try to reproduce it later but with https://webhook.site
Webhook.site - Test, transform and automate Web requests and emails
Instantly generate a free, unique URL and email address to test, inspect, and automate (with a visual workflow editor and scripts) incoming HTTP requests and emails
It's really easy, there isn't really anything to document as odd as that is to say:
- use the HTTP Request Node
- use the interactive dev docs - https://twenty.com/developers/rest-api/core#
- auth with
Authorization: Bearer <token> using header auth
Then just start chaining them together like this:
If you've got specific questions about any of the Core APIs or anything, feel free to open a new help thread and we can continue there, hoping to keep this thread centered around possible causes of the Webhook event duplication
Wait, you can add webhooks directly with Settings
I'm blind
@Skyfox675 I'm trying to check webhooks on webhook.site, added correct URL in settings but created few objects and no webhook was received
Can you open a new help thread for troubleshooting getting your webhooks wokring?