Multiple n8n Form Redirects - How to Retrive/Pass Form Data to Compile a 'Final' Form?

Describe the problem/error/question

Hello, I have a program comprised of multiple conditional workflows. The initial workflow is an n8n form, which will redirect to one of several second workflows each containing an additional n8n form. The is necessary because the specific redirect is conditional depending on the result of the initial n8n form.

This works fine, but at the end I wish to compile the results of both the initial n8n form and the conditional second n8n form. What is the simplest and safest way of doing this? Ideally I would send the initial form data along with the redirect but this doesn’t appear to be an option.

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Hey @Jonathan_Sherman,

I don’t have a pretty solution for this right now but we will likely be releasing multi step n8n forms next week or the week after depending on internal reviews (feat(n8n Form Page Node): New node by michael-radency · Pull Request #10390 · n8n-io/n8n · GitHub) I would maybe wait for that assuming your currently project isn’t urgent as it will make life a lot easier.

Another option could be to save the output to a database / baserow / airtable / seatable and fetch it when you need it at the end.

Nice timing, good to hear. Another idea might be to use Execute Workflow with Wait node’s form submission, though I’m not completely sure it’ll work. Anyways, good to hear a solution is on the way.

1 Like

Hi @Jon, is this release still on target for the near term? Many thanks

@Jon been over a month now… this is getting a little painful.

Best bet is to use the wait node, then you can collect all data in a single flow.

Did a quick setup already with the wait node recently. It works okay, but assuming this node is still in the pipeline, I will just have to rewrite the workflows to replace it (I presume).

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