Human Approval (Email)

Pause workflow and email a human for approval before continuing

Node Type

Human in the Loop

Category

Human in the Loop

Icon

Mail

Overview

The Human Approval (Email) node is a Human in the Loop node that pauses your workflow and sends an email to a human for approval before continuing. This is essential for workflows that require human oversight, decision-making, or validation at critical steps.

Key Features

  • Workflow Pause: Automatically pauses execution until approval is received
  • Email Notification: Sends approval request with context to designated recipient
  • Approval Link: Includes one-click approval link in email
  • Context Sharing: Passes workflow data to approver for informed decisions
  • Resume on Approval: Workflow continues automatically after approval
  • Audit Trail: Tracks approval status and decision-maker
⚠️
Important: This node will pause your workflow execution until a human approves the request. The workflow will not continue until the approval link in the email is clicked.

Prerequisites

Email Service

Requires email service for sending approval requests

Email service configured and accessible
Valid sender email address
Email delivery permissions and credentials

Approval Process

Understanding of approval workflow requirements

Clear approval criteria and decision points
Designated approvers with email access
Understanding of workflow pause and resume behavior

Use Cases

Content Approval

Send generated content to a manager for review before publishing to social media or sending to customers.

Risk Management

Require human approval for high-value transactions, sensitive data processing, or compliance-critical operations.

Customer Communication

Get approval before sending important emails to customers, especially for sensitive or high-value communications.

Quality Control

Have humans review AI-generated content, data analysis results, or automated decisions before they're finalized.

Node Configuration

Required Fields

Recipient Email

Type:text
Required:Yes
Value Type:string

The email address of the person who will receive the approval request. They will receive an email with context and an approval link.

Subject

Type:text
Required:Yes
Value Type:string

The subject line of the approval email. Should clearly indicate what needs approval.

Message

Type:text
Required:Yes
Value Type:string

The message body of the approval email. Include context, details, and any relevant information for the approver.

Optional Fields

Context Data

Type:JSON
Required:No
Value Type:object

Additional data to include in the approval email. This can contain workflow variables, generated content, or any information the approver needs.

Examples & Use Cases

Content Publishing Approval

Get approval before publishing AI-generated content

{
  "recipientEmail": "[email protected]",
  "subject": "Approval Required: Blog Post Draft",
  "message": "Please review the AI-generated blog post below before publishing.",
  "contextData": {
    "title": "{{blogPost.title}}",
    "content": "{{blogPost.content}}",
    "targetDate": "{{publishDate}}"
  }
}

Sends blog post draft to editor for approval before publishing.

Transaction Approval Workflow

Require approval for high-value transactions

Workflow Structure

💳 Transaction Trigger → ✅ Human Approval → 💸 Process Payment → 📧 Confirmation
{
  "recipientEmail": "[email protected]",
  "subject": "High-Value Transaction Approval Required",
  "message": "Amount: ${{transaction.amount}}. Approve to proceed with payment.",
  "contextData": {
    "amount": "{{transaction.amount}}",
    "vendor": "{{transaction.vendor}}",
    "invoiceId": "{{transaction.id}}"
  }
}

Best Practices

Do's

  • Include clear context and relevant data in the message
  • Use descriptive subject lines that indicate urgency
  • Add workflow variables to show what needs approval
  • Set appropriate timeout policies for approvals
  • Log approval decisions for audit trails
  • Test approval emails before production use

Don'ts

  • Don't use for time-critical workflows without fallbacks
  • Avoid vague messages without context
  • Don't forget to handle rejection scenarios
  • Avoid sending approvals to wrong email addresses
  • Don't include sensitive data in plain text emails
  • Avoid creating bottlenecks with too many approval steps
💡
Pro Tip: Use template variables in your message to show the approver exactly what they're approving. Include key details like amounts, content previews, or affected users directly in the email body.

Troubleshooting

Common Issues

Email Not Received

Symptoms: Approver doesn't receive the approval email

Solution: Check spam folders and verify the recipient email address is correct. Ensure your email service is properly configured and has sending permissions.

Workflow Stuck

Symptoms: Workflow remains paused indefinitely

Solution: This is expected behavior - the workflow waits for approval. Implement timeout logic or send reminder emails. Check that the approval link in the email is working.

Approval Link Broken

Symptoms: Clicking approval link doesn't work

Solution: Verify your workflow service URL is accessible and properly configured. Check that the approval token hasn't expired.

Wrong Person Approved

Symptoms: Approval came from unexpected email

Solution: Anyone with access to the approval link can click it. Consider implementing additional verification or using role-based approval systems.

Related Resources