How to do a human-in-the-loop workflow without a human-in-the-loop node

Describe the problem/error/question

I put in a feature request to add a RocketChat man-in-the-loop node, so far not much interest.

How can I create workflow that does the same thing to use in the meantime?

I have a developer background, just new to n8n.

Looking for some general guidance, maybe: “here’s a video/url that shows you”, or just use such and such node along with such and such node … need to implement this api which rocketchat is missing and that’s why we don’t have a man-in-the-middle would be nice (if true, would be good to know before i put too much time into it).

Information on your n8n setup

  • n8n version: latest kubernetes helm chart deployment
  • Database (default: SQLite): postgres via cloudnative-pg operator
  • n8n EXECUTIONS_PROCESS setting (default: own, main): ?
  • Running n8n via (Docker, npm, n8n cloud, desktop app): kubernetes
  • Operating system: workernodes are running redhat9

I’ve found this link:

https://medium.com/@jovial_brass_otter_147/introduction-to-developing-an-n8n-trigger-node-1a286bbd0abd

maybe that’s what i need, reading …

I’ve learned its possible to configure a webhook via RocketChat Administration→Integrations→Outgoing .

This looks like the easier solution if you have admin access to a rocketchat server.

Due to my current security, this isn’t an option for me, so I may need to implement a websocket trigger using the technique documented in the previous posting.

If anyone knows of an existing implementation of a websocket trigger, I’d prefer to use an existing solution.

I keep finding articles that say the existing RocketChat node lets you trigger based off a message etc… like everything is there, but yet I can only find one method to send to a ‘channel/user’.

Hi @lknite

You can implement your own human in the loop logic by using the Wait node with the “On Webhook Call” option, this is the method I prefer.

There is also a community node called gotoHuman:

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.