Sending webhooks as an action, configurable via the UI

Feature Requests
1

Context

I want to create an N8N automation which will fire whenever a webhook automation is triggered.

This may seem like a very esoteric use case, but is in fact not so inconceivable!

In my case, I want to implement an automation that:

  • Triggers when a home assistant plugin turns active.
  • Runs a prompt through a large language model
  • Sends a templated email notification which seems to be a little challenging to do nicely in the built-in automations.

The Workaround

Currently the lack of a webhook action has to be worked around by manually adding rest commands into configuration.yaml.

Once done, they are exposed as RESTful commands that can be called as actions in automations, like this:

image
image701×600 26.2 KB

However, this approach is significantly more limited than the functionality on the other side, that of triggering webhooks.

It would be nice to be able to do all these common actions via the UI:

  • Change webhook URL
  • Change REST command type
  • Rename webhook (etc)

Webhooks are supported natively on the other side of the automation chain as trigger events:

image
image701×328 13.2 KB

So to enable users to make full use of this popular and powerful home automation stack (N8N + HA) it would be nice to have full native support for both trigger and sending webhooks

2

Hello danielrosehill,

This appears to be a Frontend Related Feature Request as it is asking for changes to Frontend Menus, Dashboards, or Sections.

These Feature Requests are handled in a different system, and will not be seen by the right people if posted in the HA forums.

Please add your Feature Request into GitHub here:
home-assistant/frontend Other Feature Requests · Discussions · GitHub .

See more info about Feature Requests HERE

3

To me it sounds like the backend functionality needs to be created first and then the frontend needs to be updated.

I’ve been looking for this functionality as well and can’t believe this is not there yet.

@danielrosehill maybe this can be used as a workaround :