Human in the Loop – Send and Wait for Response with Multiple Approval Options

I’m working on an n8n flow that includes a"Send and Wait for Response"step, but I’d like to implement an approval system similar to Power Automate Approvals.

In Power Automate, users can approve requests not only via email but also through Teams, the Power Automate app, and other interfaces. I’d like to offer similar flexibility in n8n, where users can approve or decline requests from different sources, not just via email.

I’m open to developing a custom solution for this, but I need to ensure that I correctly handle the approval and decline links. I noticed that n8n constructs these links as follows:

https://myaccount.app.n8n.cloud/webhook-waiting/[ID Integer]/[ID Guid]?approved=[false/true]

Would it be a valid approach to store these URLs and allow users to trigger them from a custom application or another platform? If so:

  1. Should I manually construct these URLs in my application, or is there a way to dynamically reference them within n8n?
  2. Are there best practices for handling these links securely?

Hey @Joseph_Caruana
In n8n all these tools have Send and wait for response option too:

The approval url seems to be a combination of the workflow execution id and node ID Guid.

I know you can reference the execution id from withing the workflow like this:
{{ $execution.id }}
or {{$exection.resumeUrl}} which returns the whole url until the execution id

I don’t know of any dynamic way to get the ‘wait for response’ node Guid though.
You can manually get it by copying the node and pasting the json in a text editor and it doesn’t change unless you delete the node so you might be able to set it as env variable or a config node or something but it is static configuration :expressionless:

1 Like

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