# Webhook and Automations **URL:** \ **Category:** Misc\ **Created:** [September 5, 2023, 10:37am UTC](https://community.fibery.io/t/webhook-and-automations/5080 "2023-09-05T10:37:04Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![dukevannori](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@dukevannori](https://community.fibery.io/u/dukevannori)\ **Post date:** [September 5, 2023, 10:37am UTC](https://community.fibery.io/t/webhook-and-automations/5080/1 "2023-09-05T10:37:04Z")
HI, i am starting to use n8n and fibery in combination to make some automation stuff happening on google contacts and others now I run into this problem: i have an automation on my contact type. so when i change a name it start the automation to clean up this name. that results in two updates on the contact-type… ergo two webhooks are fired. in n8n i get that webhook result and because it fires double, also the automation in n8n runs twice … any way of having a webhook “threshold” ? or another solution would be to have a webhook triggered not automatically on every change but actually just when i hit a “sync” button on a contact entity. … that would be even better actually - as it would not trigger on every little change that is happening on a contact any idea? 🙂 ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 5, 2023, 11:05am UTC](https://community.fibery.io/t/webhook-and-automations/5080/2 "2023-09-05T11:05:21Z")
> [@dukevannori](#): > > when i change a name it start the automation to clean up this name. that results in two updates on the contact-type Not sure what you mean. Are you saying that when you rename a contact, the webhook fires twice? Is this because of some automation in Fibery? ---
**Author:** ![dukevannori](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@dukevannori](https://community.fibery.io/u/dukevannori)\ **Post date:** [September 5, 2023, 11:48am UTC](https://community.fibery.io/t/webhook-and-automations/5080/3 "2023-09-05T11:48:16Z")
exactly. i have an automation, that puts Lastname, Firstname (namefield) into separate first and last name fields. and this is triggered from an update and so the webhook fires twice - once from the manual edit, once from the automation edit. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 5, 2023, 12:07pm UTC](https://community.fibery.io/t/webhook-and-automations/5080/4 "2023-09-05T12:07:49Z")
I think it’s unlikely that we would implement webhook ‘batching’ or a ‘sync’ button. I think the expectation is that the recipient of the webhook firing should filter out changes that aren’t relevant. BTW why is this actually a problem?: > [@dukevannori](#): > > in n8n i get that webhook result and because it fires double, also the automation in n8n runs twice … ---
**Author:** ![dukevannori](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@dukevannori](https://community.fibery.io/u/dukevannori)\ **Post date:** [September 5, 2023, 1:46pm UTC](https://community.fibery.io/t/webhook-and-automations/5080/5 "2023-09-05T13:46:57Z")
but it should be possible to write a script that sends data from that entity as json to a webservice like zapier/n8n? ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 5, 2023, 1:56pm UTC](https://community.fibery.io/t/webhook-and-automations/5080/6 "2023-09-05T13:56:13Z")
For a service like Zapier, you wouldn’t need to write a script to send data - the Fibery integration with Zapier supports ‘watching’ for changes. Then, if you specifically need JSON, you can use a Zapier module to format the data received as you need it. I’m not too familiar with n8n, so I don’t know what’s possible, but since you have the changes in Fibery triggering in n8n, I don’t quite understand why there needs to be a ‘push’ from the Fibery side… ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 5, 2023, 1:57pm UTC](https://community.fibery.io/t/webhook-and-automations/5080/7 "2023-09-05T13:57:07Z")
It is possible to make http calls from within a Fibery script if that helps: [. | Fibery](https://the.fibery.io/@public/User_Guide/Guide/Scripts-54/anchor=Http-service-functions--af3e5bbc-3359-4268-8b0e-1023398c0d7e) ---
**Author:** ![dukevannori](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@dukevannori](https://community.fibery.io/u/dukevannori)\ **Post date:** [October 5, 2023, 11:23pm UTC](https://community.fibery.io/t/webhook-and-automations/5080/8 "2023-10-05T23:23:29Z")
following up on this: is it possible to trigger a webhook-event with a script=button? this way n8n could listen to a webhook, but not on every change and every entity in that DB, but only those i actually want to “push”. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [October 6, 2023, 4:42pm UTC](https://community.fibery.io/t/webhook-and-automations/5080/9 "2023-10-06T16:42:07Z")
> [@dukevannori](#): > > is it possible to trigger a webhook-event with a script=button? Well, if the button causes a change, then that change would trigger the webhook, but I presume you mean that you want the button to trigger a webhook, but changes from other activities in the db should not. In that case, then the answer is no. To be honest, it’s not obvious to me why you would want to use webhooks in this situation - can’t you just make a call to the relevant service from within a script in the button automation. This is how I would imagine you would ‘push’ data from Fibery. ---
**Author:** ![dukevannori](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@dukevannori](https://community.fibery.io/u/dukevannori)\ **Post date:** [October 7, 2023, 8:34pm UTC](https://community.fibery.io/t/webhook-and-automations/5080/10 "2023-10-07T20:34:05Z")
ill check that option … thanks ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [May 15, 2025, 2:12pm UTC](https://community.fibery.io/t/webhook-and-automations/5080/11 "2025-05-15T14:12:24Z")
I agree that this is the solution here. But, I still think it would be helpful to have trigger conditions for webhooks here in Fibery. Example: You’d like to trigger an action in another system when the state changes in Fibery. This is a case where I’d prefer a webhook because I’d have multiple different external actions based on what the state is. Yes, my external listener can do some filtering, but Fibery webhooks don’t include metadata on what field changed, the old value and the new one. Today’s version of Fibery webhooks trigger for every change indiscriminately an it would be more efficient to restrict the triggers than to aggressively filter with no change log. ---
**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\ **Post date:** [August 28, 2025, 7:06pm UTC](https://community.fibery.io/t/webhook-and-automations/5080/12 "2025-08-28T19:06:13Z")
Totally. This would be very very helpful. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [May 14, 2026, 3:36pm UTC](https://community.fibery.io/t/webhook-and-automations/5080/13 "2026-05-14T15:36:06Z")
Related > [@Webhook Action in Automations](https://community.fibery.io/t/webhook-action-in-automations/7485): > > I hope this becomes an automation/button action. It would increase the usability/flexibility of Fibery for low-code users if there was a UI that builds an API call similar to Zapier and Make.