Human approval or input via Email. Email node in ActionFlows. Inputs, outputs, and how to use it.
Overview
Human approval or input via Email.
Requirements
Credential Required
This node likely requires an integration credential. Add the related API key/secret from Integrations before execution.
Inputs
Standard Inputs
Approval Typeselect · optional
The type of approval action the human can take
- Required
- No
- Multiple
- No
- Default
approve- Options
- approveeditreject
BCCtext · optional
Hidden recipients to copy on the email
- Required
- No
- Multiple
- No
Bodytextarea · required
Email body content (supports HTML)
- Required
- Yes
- Multiple
- No
CCtext · optional
Additional recipients to copy on the email
- Required
- No
- Multiple
- No
Datajson · optional
The data that needs human review or approval
- Required
- No
- Multiple
- No
From Addresstext · required
The email address that will appear as the sender
- Required
- Yes
- Multiple
- No
Prompt for Humantext · required
The prompt or question to present to the human reviewer
- Required
- Yes
- Multiple
- No
Subjecttext · required
Subject line for the email
- Required
- Yes
- Multiple
- No
Timeout (minutes)number · optional
Maximum time to wait for human approval (in minutes)
- Required
- No
- Multiple
- No
- Default
60- Constraints
- min: 1 · max: 1440 · step: 1 (minutes)
Recipient Emailtext · required
Email address where the message will be sent
- Required
- Yes
- Multiple
- No
Outputs
Approval Statustext
Status of the approval (approved, rejected, timeout)
Approval Timenumber
Time taken for approval in seconds
Approved Datajson
Data after human approval or modification
Human Responsetext
Any additional response or comment from the human
Message IDtext
Unique identifier of the sent email
Successboolean
Success state of the email sending operation