Workflow

Overview

The Workflow Node allows developers to attach an existing workflow as a subworkflow, enabling modularity, reusability, and simplified workflow management.

By using subworkflows, developers can: ✅ Avoid Duplication – Use the same workflow across multiple parent workflows. ✅ Simplify Complex Workflows – Break down large workflows into manageable steps. ✅ Improve Maintainability – Make debugging and updates easier by isolating logic into reusable subflows.

Configurations

Field	Description
Workflow	Select an existing workflow that will be attached and executed as a subworkflow.
Input	Define the input data to be passed to the subworkflow. This should match the expected input format of the selected subworkflow.

How the Workflow Node Works

1️⃣ The parent workflow calls the selected subworkflow. 2️⃣ The input data is passed to the subworkflow for execution. 3️⃣ The subworkflow runs independently, processing its steps. 4️⃣ Once completed, the subworkflow returns the output to the parent workflow.

Example Use-Cases

Use-Case 1: Processing Invoices in a Finance Workflow

A finance automation workflow requires invoice processing as a separate, reusable step.

Configuration:

Field	Value
Workflow	Process Invoice
Input	{ "invoiceId": "12345", "amount": "1000" }

Execution Process:

1. The Process Invoice subworkflow is triggered with the input data.

2. It validates the invoice, checks compliance, and logs the transaction.

3. Once processed, it returns the final status to the parent workflow.

🔹 Why Use a Subworkflow? ✔ Keeps the parent workflow clean and focused. ✔ Allows multiple workflows to reuse the invoice processing logic. ✔ Easy to update invoice handling without modifying multiple workflows.

---

Use-Case 2: Loan Origination System

A loan application workflow needs to verify applicant details through a separate KYC (Know Your Customer) process.

Configuration:

Field	Value
Workflow	Verify KYC
Input	{ "customerId": "A9876" }

Execution Process:

1. The Verify KYC subworkflow retrieves customer details.

2. It performs ID verification and credit checks.

3. The subworkflow returns an approval status to the parent workflow.

🔹 Why Use a Subworkflow? ✔ Standardizes KYC processing across multiple workflows. ✔ Allows quick updates to KYC rules without affecting multiple workflows. ✔ Improves workflow organization by isolating verification logic.

---

Use-Case 3: Data Enrichment Pipeline

A data processing workflow needs to clean and enrich incoming customer records before storage.

Configuration:

Field	Value
Workflow	Data Cleansing
Input	{ "recordId": "C10293" }

Execution Process:

1. The Data Cleansing subworkflow standardizes formats, removes duplicates, and enriches records.

2. It validates email addresses, phone numbers, and other key fields.

3. The subworkflow returns the cleaned record to the parent workflow for further processing.

🔹 Why Use a Subworkflow? ✔ Reduces repetitive data validation logic across workflows. ✔ Allows independent testing and debugging of the data cleansing process. ✔ Keeps the parent workflow lightweight and focused on orchestration.

---

Key Takeaways for Developers

✅ Promotes Reusability – Subworkflows allow reusing standard logic instead of duplicating it in multiple workflows.

✅ Improves Readability & Debugging – Complex logic is encapsulated in a subworkflow, making parent workflows easier to maintain.

✅ Facilitates Scalable Architecture – Updates to a subworkflow automatically reflect across all workflows using it.

✅ Supports Modular Execution – Subworkflows run independently, ensuring better organization and execution control.

By leveraging the Workflow Node, developers can design scalable, modular, and maintainable workflows, ensuring that business processes remain adaptable and easy to manage. 🚀