How to Continue Workflow After a Return Node
In BuildShip, the
Return node is typically used to terminate the workflow and send a response back to the client. If you need to continue the workflow after sending a response, you can use the Parallel Execution node to run multiple flows concurrently.
Here's a step-by-step guide on how you can achieve this:
1. Parallel Execution Node: Add a Parallel Execution node to your workflow. This node will allow you to run multiple branches in parallel.
2. Branch 1 - Return Node: In the first branch, add your Return node to send the response back to the client.
3. Branch 2 - Airtable Node: In the second branch, add your Airtable nodes to check if the user exists and update or create the user accordingly.
4. Continue Workflow: After the Airtable nodes, you can add more nodes to continue your backend tasks.
This way, the workflow will not terminate after the Return node, and the Airtable path will be executed in parallel.
For more details on how to use the Parallel Execution node, you can refer to the BuildShip documentation: Branch Node and Switch Node.
If you need further assistance, please submit your query via the in-app support button.Branch (If Else) – BuildShip
A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.
2 Replies
Please disregard this question. I was able to make it work 😄
BuildShip AI Support - Crafting Solution, (Avg response time: ~2 minutes 🙂)
Sorry, there was an error processing your request. Please try again in ~1 minute