Course Content
Flows – Expert
0/8
The Sleep Node – AI Agent
00:00
The Run Flow Action – AI Agent
00:00
The Table Node – AI Agent
00:00
Filtering a table – AI Agent
00:00
Setting Up an Event Trigger – AI Agent
00:00
Filtering Records for a Trigger – AI Agent
00:00
Using Values from the Trigger – AI Agent
00:00
Course Exercise: Creating a Monday Account Automatically based on Salesforce – AI agent
00:00
Flows – Expert

Lesson Guide: Building Modular Automation with the Run Flow Action

In this lesson, you will learn how to build decoupled, highly scalable architectures using the Run Flow Action Node in Noca Flow. As your business logic expands, managing massive single-canvas workflows can become overwhelming. By dividing your automations into small, reusable sub-flows, you can trigger specialized standalone processes from inside a main “parent” workflow.

We will walk through how to execute a specialized sub-flow designed to process Salesforce Closed Won opportunities directly from a primary execution track.

Step 1: Prep and Publish Your Sub-Flow

Before a parent workflow can call a secondary process, the target sub-flow must be standalone, saved, and successfully published.

  1. Create or open your dedicated child workflow (for example, our preset Closed Opportunities flow).

  2. Configure this sub-flow’s nodes to complete a specific task (e.g., a Salesforce Object Read Node matching Stage $=$ Closed Won).

  3. Click the Publish button in the top menu to lock in an official deployment version.

Step 2: Insert the Run Flow Action into Your Parent Canvas

Now, let’s step out into your primary parent workflow where the core automation logic is initiated.

  1. Open your main workflow canvas (e.g., our Run Flow blueprint starting with a Manual Trigger).

  2. Click the + icon on the path where you want the external process to execute.

  3. In the node picker search box, type Run Flow and click Insert to place the node onto your canvas.

Step 3: Map Your Sub-Flow Parameters

With the node selected, use the properties panel on the right side of the screen to lock in the configuration path.

  1. Select a Flow: Click the dropdown menu and select the child flow you want to launch (e.g., Closed Opportunities).

  2. Select Action: Set the execution command type to Run to invoke the sequence.

  3. Select a Version: Choose whether to target the current working Draft or pin the execution to a specific deployed Live checkpoint. To guarantee production stability, select your published Live version tag.

Step 4: Continue the Parent Workflow Path

The Run Flow action operates sequentially. Once called, execution control temporarily hands off to your sub-flow, completes all internal paths, and then safely hands control right back to your main flow to finish out the canvas.

  1. Click the + icon immediately following your Run Flow action node.

  2. Add a final downstream tracking task, such as a Salesforce Create Object Node, to log a system notification entry confirming that the combined child/parent process completed successfully.

  3. Click Save and Run to test your modular stack live!

Key Takeaways

  • Canvas Reusability: If you have a task that needs to run across multiple different areas of your business (like data logging, internal email alerts, or sanitization rules), turn it into a standalone sub-flow so you can easily reference it anywhere via a Run Flow node.

  • Version Pining: Locking your Run Flow action to a Live deployment version ensures your main production systems continue running flawlessly, even if you are actively editing or testing a draft variation inside the child sub-flow canvas.

Incredible work! You are now fully equipped to build advanced, modular automation patterns across Noca Flow. Want to dive deeper into ecosystem scaling? Head over to our community masterclasses to see what other administrators are launching!

Previous
Next