Sub-workflow - error "Referenced node doesn't exist"

[Cheun_Apan]

Hello everyone,

I’m asking for your help.

I’m trying to connect two workflows. The first is a form. After submitting it, I want to launch other workflows.

I’m attaching a screenshot of my main workflow (the form) as well as the start of a secondary workflow.

When running, I get the error:

Referenced node doesn’t exist
Error details: Other info
ExpressionError: Referenced node doesn’t exist at createExpressionError (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-workflow@file+packages+workflow/node_modules/n8n-workflow/src/workflow-data-proxy.ts:775:11) at Proxy.$ (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-workflow@file+packages+workflow/node_modules/n8n-workflow/src/workflow-data-proxy.ts:1056:12) at Proxy.eval (eval at getFunction (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@[email protected]/node_modules/@n8n/tournament/src/FunctionEvaluator.ts:13:16), :6:42) at FunctionEvaluator.evaluate (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@[email protected]/node_modules/@n8n/tournament/src/FunctionEvaluator.ts:20:13) at Tournament.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@[email protected]/node_modules/@n8n/tournament/src/index.ts:45:25) at evaluateExpression (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-workflow@file+packages+workflow/node_modules/n8n-workflow/src/expression-evaluator-proxy.ts:20:9) at Expression.renderExpression (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-workflow@file+packages+workflow/node_modules/n8n-workflow/src/expression.ts:332:29) at Expression.resolveSimpleParameterValue (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-workflow@file+packages+workflow/node_modules/n8n-workflow/src/expression.ts:311:28) at Expression.getParameterValue (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-workflow@file+packages+workflow/node_modules/n8n-workflow/src/expression.ts:522:16) at ExecuteContext.getNodeParameter (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core@[email protected]_@[email protected]_46e522f8a77ed5eccc0991bfcca21502/node_modules/n8n-core/src/execution-engine/node-execution-context/node-execution-context.ts:367:37)

Thank you in advance for your help.

Information on your n8n setup

• **n8n version: I have a self-hosted n8n on a VPS, version n8n 1.104.1 (Self-Hosted).
• **Database (default: SQLite): default
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[jabbson]

If you look at the execution logs for each workflow - did the second one even started? Which node errored out? Can you attach the workflows here for us to take a look?

[Cheun_Apan]

Good evening,

Thank you for your reply, and I apologize for the delay in mine. I’m on vacation and turned off my computer for a few days.

Here are my two workflows.

• Workflow 1 : Formation_PSCF_Inscription
• Workflow 2 : Formations_Inscription

After rereading the documentation, the sub-workflow runs fine, but there is no data.

My “Formation_PSCF_Inscription” workflow is my registration form. I built it this way because I have a complex registration process.

The second workflow is intended to register the items in my baserows database.

Thank you for your help.

Sincerely,

[jabbson]

Hey @Cheun_Apan hope all is good, no worries, I am glad you had time to relax and hopefully had some good time.

I understand you recovered from the problem where you have been referencing the node which doesn’t exist. Now, the new issue appears to be around returning data from the subflow to the main flow.

Base on what you mentioned above, “the second workflow is intended to register the items in my baserows database”, meaning insert data. The issue is that even though the sub-workflow runs fine", “there is no data” returned.

What data is expected to be returned? I ran this for my database (thank you for pinning some data) and it appears that the data was inserted (I only used submittedAt and formMode though). Could you explain what do you see when the flow runs and what do you expect instead?

[Cheun_Apan]

Thank you for your quick response.

Actually, the “Formation_PSCF_Inscription” workflow is my main workflow, and the goal is for it to send its data to the “Formations_Inscription” workflow.

I want it to send all the information present at the end of the “Formation_PSCF_Inscription” workflow (all the information received step by step).

Good evening.Thank you for your quick response.

Actually, the “Formation_PSCF_Inscription” workflow is my main workflow, and the goal is for it to send its data to the “Formations_Inscription” workflow.

I want it to send all the information present at the end of the “Formation_PSCF_Inscription” workflow (all the information received step by step).

Good evening.

[jabbson]

So what doesn’t happen? What doesn’t work for you? Could you illustrate it with screenshots and maybe an explanation in the following form:

• I do X
• I expect Y to happen
• Instead Z happens

[Cheun_Apan]

Hello,

First of all, I apologize for my late reply; I’m working nights right now, and I’m a bit behind the times.

The problem with this is that, after completing all the different forms (which are steps for me), none of the information is being sent to the second workflow.

But after these few days of reflection, I think it’s important to start from the basics and the initial objective.

We are a training organization. I want to implement several things to automate our process.

This workflow is designed to be the first step, namely the registration form.
Once a training course is subscribed, I want the data from the form to be added to our database, which is under baserow. Then, using the information in the database, I want to be able to prepare and send, using automation, training documents (contract, registration certificate, invitation, attendance list, diploma, etc.) and accounting documents (quotes, invoices, etc.). I also want to be able to send and track the completion of some additional questionnaires.
Currently, I work manually with spreadsheets and manual mail merges.

I’ve started a database on baserow. I created my tables there:

• Contract → with general information for the contract
• Clients → including our clients’ administrative and legal information
• Learners → including our learners’ administrative information (knowing that a client can also be a learner)
• Dogs → because we train in the field of companion animals and our clients can bring their pets
• Trainings → listing all of our training information
• Sessions → listing our various training sessions
• Trainers → listing the organization’s trainers
• Locations → listing the training facilities (because we travel for our training, we do not have a location)
• OPCO (Professional Association for the Protection of Animals) → listing the public organizations that can fund our training.

My first objective is therefore to create a form allowing me to collect the information I need:

• desired training
• sessions the client wishes to attend from among the sessions related to the chosen training
• client type (individual, professional, association)
• administrative and legal information about the client, depending on their type (they vary depending on whether they are an individual or a professional)
• administrative information about the participating learner(s) (in the case of professionals, several can attend at the same time, and this must be covered by a single contract)
• the client’s choice to apply for financing, depending on their type
• the preferred payment method (eventually, a portion with a link to the payment platforms)

Subsequently, once this information has been collected, I will need to create other workflows for the following steps, particularly document customization.

In light of this information, is my workflow relevant, or should I think differently?

I thank you warmly for your help.

With all my sympathy,

Alexander

[Cheun_Apan]

Thank you all for your help, I will do something else. So, I am closing the topic.