Child Flows for Reusable Logic

Why Child Flows?

Child flows let you:

• Reuse common logic across multiple flows
• Reduce duplication and maintenance burden
• Create cleaner, more readable flow designs
• Test components independently

Creating a Child Flow

Step 1: Create the Flow

Create a new flow with the trigger "Manually trigger a flow". This becomes your child flow.

Step 2: Define Inputs

In the trigger, click "Add an input" to define what data the child flow needs:

• Text, Number, Yes/No for simple values
• File for attachments
• Email, Date for formatted inputs

Step 3: Add a Response Action

Add "Respond to a PowerApp or flow" to return data to the parent:

Response outputs:
- processedData (Text)
- success (Yes/No)
- errorMessage (Text)

Calling the Child Flow

In your parent flow, add the "Run a Child Flow" action and select your child flow.

Example: Email Notification Child Flow

Trigger inputs:
- recipientEmail (Text)
- subject (Text)
- templateName (Text)
- dynamicData (Text - JSON)

Actions:
1. Get email template from SharePoint
2. Parse dynamicData JSON
3. Replace template placeholders
4. Send email
5. Log to audit list
6. Respond with success/failure

Best Practices

• Keep child flows focused on a single responsibility
• Always include error handling and return status
• Document inputs and outputs clearly
• Version your child flows (v1, v2) for breaking changes

Child flows can't run longer than 30 days and count against your flow run limits - plan accordingly.