There are common approaches to share data between workflows without heavy code:
Execute Workflow (Sub-workflow) Node:
If you have a parent workflow that needs to call another (child) workflow, you can use the âExecute Workflowâ node. This lets you pass data as input to the child workflow and then receive a response.
Example:
External Data Storage Solutions:
Alternatively, you could store shared data in an external data store such as a Google Sheet, database, or even via webhooks. This method is useful if the workflows run independently and not in a parent/child relationship.
Data Stores or Google Sheets: Store the variable in an external location and then have your workflows read and write to that location.
Webhooks: One workflow could update a value through a webhook call that the other workflow listens to.
Assuming your 2 workflows run independently of each other (i.e. one of them doesnât call the other one), and the values you need to share are small/simple, there is a static worfklow data feature you could use.
The challenge is that the âglobalâ data kept by $getWorkflowStaticData is scoped to a single workflow, so you would need to create a 3rd âcommonâ workflow to wrap a set of âstatic dataâ in order to make the same data values available to both of your other workflows. That 3rd/common workflow would also handle updating the value. Your other 2 workflows would use the Execute Sub-Workflow node to access the common one.