Call Webhook / Send HTTP Request action for Automation Rules

Ideas & Features Automations
1

Hi Fibery team! :grinning_face:

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. :grinning_face:

2

A post was merged into an existing topic: Webhook Action in Automations