# \[DONE\] Webhook Action in Automations **URL:** \ **Category:** Ideas & Features\ **Tags:** automations\ **Created:** [May 27, 2024, 1:31am UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485 "2024-05-27T01:31:48Z")\ **Posts on this page:** 20\ **Page:** 1
**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 27, 2024, 1:31am UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/1 "2024-05-27T01:31:48Z")
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. ---
**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 27, 2024, 5:27am UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/2 "2024-05-27T05:27:57Z")
Do you mean that you want to be able to access the http call functionality via a dedicated GUI rather than via a script? ---
**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 28, 2024, 8:36pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/3 "2024-05-28T20:36:09Z")
Yes, sort of like a form. I’ve included a screenshot from make to meet the character minimum for a response. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2a5fed84637f140168f35abbb695a95acd41792f.png) ---
**Author:** ![carson](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/carson/32/7503_2.png) [@carson](https://community.fibery.io/u/carson)\ **Post date:** [August 30, 2024, 8:10pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/4 "2024-08-30T20:10:15Z")
> [@ear Feedback needed: scripts in automations that shouldn't be scripts](https://community.fibery.io/t/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/25): > > Call a webhook/URL +1 for easier http call/webhook emit UI. ---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [August 31, 2024, 9:15pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/5 "2024-08-31T21:15:07Z")
100% to all of these mentioned. We do the same. I think POST to webook would be at the top of the list. We should be able to trigger a webhook and send some or ALL entity data to the webhook. This is a big missing piece to Fibery actions. We make due with scripts but it is annoying to have to create an entire script just use a button or rule action. ---
**Author:** ![carson](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/carson/32/7503_2.png) [@carson](https://community.fibery.io/u/carson)\ **Post date:** [August 23, 2023, 12:29am UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/6 "2023-08-23T00:29:53Z")
I’m looking to loop external softwares into actions taken within Fibery. For example, whenever an automation is triggered or a button pressed, I’d want to be able to emit a network call to a specific endpoint, and include query param and body data, pulled dynamically from the entity that triggered the automation (or table which owns the button). Is this possible, currently? It would let me use other services like Make or N8N for very complex automation workflows, based on events from within Fibery. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 2, 2024, 6:46am UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/7 "2024-10-02T06:46:32Z")
@helloitse @carson @Illusory We are considering this feature, but wonder it will be no easier to setup than with Scripts. Can you share your use cases how you use it now and how you would like to have it in Fibery? ---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [October 2, 2024, 12:58pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/8 "2024-10-02T12:58:09Z")
Cool! 1. Ability to trigger webhook from button or rule and send selected fields as body. Using Fibery UI would be easier than using scripts; in which you have to map fields to variables and formulate a httpPost. 2. Set POST header. Env variables would be great for auth header, since currently we have to expose auth values in script. 3. Automatically send Fibery UUID (so that the external client can know where it came from and potentially update it when it is complete) and provide Fibery URL in body as well. We use many POST scripts to control hardware, update external database or 3rd party apps and/or trigger further automations after posting to our API and running a workflow. Though we love coding, it would make building functions/actions in Fibery much easier and faster. If GET methods are being considered as well, then being able to call an external endpoint and retrieve data that can populate Fibery fields would be awesome as well. ---
**Author:** ![Illusory](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/illusory/32/10403_2.png) [@Illusory](https://community.fibery.io/u/Illusory)\ **Post date:** [October 3, 2024, 12:47pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/9 "2024-10-03T12:47:14Z")
> [@Illusory](#): > > 1. Ability to trigger webhook from button or rule and send selected fields as body. Using Fibery UI would be easier than using scripts; in which you have to map fields to variables and formulate a httpPost. **Update:** With the new [Automations in the Script AI Assistant](https://community.fibery.io/t/october-3-2024-quick-filters-on-relation-and-embedded-views-clean-email-body-automations-script-ai-assistant-and-more/7492), my previous point is somewhat diluted (at least for technical users who feel comfortable with scripting env). However, there may be an opportunity to encourage Free Plan users to upgrade to the Pro Plan by limiting Script AI Assistant usage on [Free Plans](https://community.fibery.io/t/fibery-free-plan-can-be-back-soon/6569). If Fibery’s UI supports webhook triggers, advanced users might use Scripts for webhook-related tasks where the UI falls short. In this case, providing access to the AI Script Assistant would simplify these advanced use cases and is another incentive to upgrade to paid plans. ---
**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:** [October 3, 2024, 4:31pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/10 "2024-10-03T16:31:45Z")
> [@carson](#): > > +1 for easier http call/webhook emit UI. I find a UI 2 to 3X easier than a script depending on the context: 1. UI builders make it easier to create things for non-technical clients or team members to take ownership of. 2. reduce the time cost of deploying an integration 3. assuming the UI can take field inputs using existing formula language, avoiding having to call each field into the script individually. 4. although in my screenshot, I’ve included the JSON payload as text, Make, Zapier, and Coda - via packs, have a dedicated UI to build the Headers, Query, and Body. This is a major value proposition when I want to work quickly and prototype. I often defer to the UI builders when establishing a connection or sending a test call. A note on the target audience: I do consider Fibery low-code not necessarily no-code. A UI builder for actions like external calls moves the needle closer to no-code. Current use case examples: - A webhook action at the end of an automation that creates an encoded Calendly URL to send this info back to HubSpot - Using an external API to turn address fields into Long and Lat for Fibery address fields type - Querying a simple API whose outputs don’t require reshaping/transformation like getting the postal code for an address ---
**Author:** ![Julius\_Forster](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/julius_forster/32/10848_2.png) [@Julius\_Forster](https://community.fibery.io/u/Julius_Forster)\ **Post date:** [October 15, 2024, 9:02pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/11 "2024-10-15T21:02:07Z")
Just joined Fibery yesterday, and I am super impressed on how much more it has to offer compared to ClickUp. I love the ability to execute JS, though for easy quick setup, having a simple webhook action where we can paste the URL together with variables (e.g. [UUID], [TaskName], etc.) that can be sent in the URL parameter would be awesome. That’s just one thing I’ve noticed as a new user. It’s obviously not a problem to set that up with JS, but it feels cleaner (and easier) to have a dedicated action. Thank you! ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 16, 2024, 6:12am UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/12 "2024-10-16T06:12:55Z")
> [@Julius\_Forster](#): > > That’s just one thing I’ve noticed as a new user. It’s obviously not a problem to set that up with JS, but it feels cleaner (and easier) to have a dedicated action. We have this feature in our backlog, but recently we added AI to scripts, so you can ask AI to write a webhook and in general it works good, so now we are not sure we will jump into this specific action. I linked your feedback to this feature. ---
**Author:** ![Renato\_Carvalho](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/renato_carvalho/32/11001_2.png) [@Renato\_Carvalho](https://community.fibery.io/u/Renato_Carvalho)\ **Post date:** [December 9, 2024, 11:04pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/13 "2024-12-09T23:04:21Z")
I think whaat Notion just did, is something that some of the people here were looking for. At least this is something I was looking for. An easy way to setup visually the event trigger, send the Webhook without script and even select easily what properties data I want so send without script. ![CleanShot 2024-12-09 at 19.56.33@2x](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/25c9b542986453a1f6a6007d78423b90dfaa7881.png) ---
**Author:** ![Edan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/edan/32/11187_2.png) [@Edan](https://community.fibery.io/u/Edan)\ **Post date:** [March 17, 2025, 2:40pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/14 "2025-03-17T14:40:45Z")
Adding my vote and bumping this in hopes that others help push it up in priority! 😊 ---
**Author:** ![cover](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cover/32/11891_2.png) [@cover](https://community.fibery.io/u/cover)\ **Post date:** [June 6, 2025, 5:22pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/15 "2025-06-06T17:22:09Z")
+1 vote and comment for topic promotion ---
**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:** [September 1, 2025, 8:05pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/16 "2025-09-01T20:05:22Z")
I don’t have access to scripts on my plan. But I’d highly appreciate being able to execute my n8n webhook from the Rules at least. Now playing with a workaround: Fibery to send an email with a special keyword, n8n to listen Gmail for the message with that keyword, then access Fibery API to make necessary updates. ---
**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:** [September 10, 2025, 3:53pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/17 "2025-09-10T15:53:01Z")
Absolutely. I think it makes sense that scripts are on a higher tier plan but would love webhooks to be available to all paid plans. Fibery is valuable to me as a tool I bring data into and live in. But manually having to take action in all the auxiliary platforms I use to support missing/out-of-scope functionality would put me in the ground 😅 ---
**Author:** ![ID.000](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/id.000/32/14109_2.png) [@ID.000](https://community.fibery.io/u/ID.000)\ **Post date:** [May 14, 2026, 3:06pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/18 "2026-05-14T15:06:53Z")
Hi Fibery team! 😀 We understand why Script Actions in Automation Rules are restricted to Admins: Rules keep running after being saved, even if the author later loses access, so scripts can be risky. But could you consider adding a safer alternative: Call Webhook / Send HTTP Request action for Automation Rules. This would allow Space Architects to trigger n8n, Make, Zapier, … without giving them full JavaScript execution inside Fibery. Ideally, it could support: - selected fields in the payload; - execution history / audit log; - workspace-level toggle controlled by Admins. For our team, this would solve a big bottleneck. We have trusted junior/middle automation builders with Architect access in specific Spaces. Right now, almost all useful automations require scripts bit with native Webhook it can be solved [api key have the same permisson level as user]. A controlled Webhook Action would be a great middle ground between basic automations and full Script Actions. 😀 ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [May 21, 2026, 2:02pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/19 "2026-05-21T14:02:19Z")
implemented in latest release > [@May 21, 2026 / Manage users visibility, Send web request action in automations](https://community.fibery.io/t/may-21-2026-manage-users-visibility-send-web-request-action-in-automations/10894): > > Manage users visibility By default, every user in your workspace can see every other user (only Guests can’t see each other). This is great…until you start collaborating closely with your clients and contractors and invite them as Members or Observers. Your customer base gets exposed, sensitive email addresses get leaked, and your GDPR compliance goes out of the window. Not anymore. Now you can prevent people outside of your org from seeing other users’ profiles: Change the default … ---
**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 21, 2026, 2:03pm UTC](https://community.fibery.io/t/done-webhook-action-in-automations/7485/20 "2026-05-21T14:03:35Z")