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.

implemented in latest release [image] May 21, 2026 / Manage users visibility, Send web request action in automations Changelog Manage users visibility By default, every user in your workspace can see every other user (only Guests can’t see each other). This i…

Do you mean that you want to be able to access the http call functionality via a dedicated GUI rather than via a script?

Yes, sort of like a form. I’ve included a screenshot from make to meet the character minimum for a response. [image]

[image] ear Feedback needed: scripts in automations that shouldn't be scripts Call a webhook/URL +1 for easier http call/webhook emit UI.

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 cre…

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 t…

@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?

Cool! 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. Set POST header. Env variables would be great for auth header, since currently we ha…

[image] Illusory: 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 , my previo…

[image] carson: +1 for easier http call/webhook emit UI. I find a UI 2 to 3X easier than a script depending on the context: UI builders make it easier to create things for non-technical clients or team members to take ownership of. reduce the time cost of deploying an integration assuming t…

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 s…

[DONE] Webhook Action in Automations

Ideas & Features

carson August 30, 2024, 8:10pm 4

+1 for easier http call/webhook emit UI.

👂 Feedback needed: scripts in automations that shouldn't be scripts

Topic		Replies	Views
Emit Webhook as an Action Get Help	1	306	August 23, 2023
Webhook Trigger for Rules Ideas & Features automations	6	547	February 28, 2026
Ability to work with external requests and map fields Integrations	1	241	July 11, 2023
Can you use fibery to trigger scripts API & Programming	4	503	August 31, 2023
🧐 Your opinion needed. Automations in Fibery (limitations and opportunities) News & Announcements	76	1365	May 21, 2026

[DONE] Webhook Action in Automations

Related topics