Hey,
so I have two workflows. One Login Workflow, that I want to use for multiple Sub-Workflows.
When I execute the Execute Workflow Node, I give it all Data from my form node to take in the next workflow. When I try to place a new form page in the other workflow, it says “Form Trigger node must be set before this node”.
My first problem: I want to trigger this workflow from the login workflow, so i use the Execute Workflow Trigger and cannot use a form trigger.
Secondly, if I would use another form trigger in the second worklow, I cannot be sure if the user is logged in, because it has its own URL and anyone could enter that in their browser and skip the login workflow/form completly.
Is there any way I can archive starting a form in one workflow and continuing it in another one?
I used a code node with the following contents before the execute workflow:
“return $(‘On form submission’).all();” → This is giving all the Data in the next workflow, the error persists anyways.
Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.
```
<your workflow>
```
That implies to any JSON output you would like to share with us.
Make sure that you have removed any sensitive information from your workflow and include dummy or pinned data with it!
I do not think you can separate Webhook and Respond to webhook into different workflows. However, you can return the data from the sub-workflow back to the parent and use that data in Respond to webhook in the parent workflow. In fact, the data from the last node executed in the sub-workflow gets available in the parent workflow.
Same use case here - authenticating a user (without using basic auth) before allowing access to a workflow. I’ve tried to use a workflow with Form nodes within it to trigger a sub-workflow but that demands the sub-workflow has a “manual start” trigger. This stops that workflow having an “on form submission” trigger. This means the form pages in the sub-workflow then complain about not having an “on form submission” trigger.
It’s chicken and egg.
If there was a way to hand around workflows when a form is present in both, that would be very useful.