Skip to content

Testing Workflows

Always test your workflows before activating them! This ensures everything works as expected.

⚠️ Important: Never activate a workflow without testing it first. A broken workflow could send incorrect emails or fail silently.

Why Test?

Section titled “Why Test?”

Testing helps you:

  • Verify nodes are configured correctly
  • Check connections work as expected
  • See actual data flow
  • Catch errors before they affect real users

Testing Methods

Section titled “Testing Methods”

Method 1: Manual Test Run

Section titled “Method 1: Manual Test Run”

The safest way to test:

1

Click "Test" Button

Find the Test button in the workflow builder toolbar

2

Provide Test Data

If prompted, enter sample data for testing

3

Watch Execution

See each node execute in real-time

4

Review Results

Check if outcomes match expectations

▶️
Add Screenshot Here
Test Execution - Show workflow running with progress

Method 2: Use Manual Trigger

Section titled “Method 2: Use Manual Trigger”

Add a Manual Trigger node for testing:

  1. Create workflow with Manual Trigger
  2. Connect your actions
  3. Click “Run” to test
  4. Replace with real trigger when ready
💡 Pro Tip: Keep the Manual Trigger even after adding a real trigger. This lets you test anytime without waiting for real events.

What to Check

Section titled “What to Check”

✅ Configuration Checklist

Section titled “✅ Configuration Checklist”
  • All required fields filled
  • Email addresses correct
  • API keys valid
  • Trigger settings appropriate
  • Connections properly made

✅ Data Flow Checklist

Section titled “✅ Data Flow Checklist”
  • Variables resolve correctly
  • Data reaches all nodes
  • Transformations work as expected
  • Conditions evaluate properly

✅ Output Checklist

Section titled “✅ Output Checklist”
  • Emails sent to correct recipients
  • Messages formatted correctly
  • No sensitive data exposed
  • Timing is acceptable
✓
Add Screenshot Here
Test Results - Show success/failure indicators

Reading Execution Logs

Section titled “Reading Execution Logs”

The execution log shows what happened:

✓ Manual Trigger - Started
✓ Email Node - Email sent successfully
✓ Slack Node - Message posted
✓ Workflow Complete - Success
📋
Add Screenshot Here
Execution Log - Show detailed log view

Understanding Log Entries

Section titled “Understanding Log Entries”
  • ✓ Green - Node executed successfully
  • ⚠ Yellow - Warning (still worked)
  • ✗ Red - Error (node failed)
  • ⏸ Gray - Skipped (conditional branch)

Common Test Scenarios

Section titled “Common Test Scenarios”

Test 1: Basic Email

Section titled “Test 1: Basic Email”

Goal: Verify email sends correctly

  1. Use your own email as recipient
  2. Run test
  3. Check inbox (and spam folder)
  4. Verify subject and message are correct

Test 2: Conditional Logic

Section titled “Test 2: Conditional Logic”

Goal: Test both branches

  1. Run test with data that triggers “true” branch
  2. Verify correct action executes
  3. Run test with “false” data
  4. Verify other branch executes

Test Case 1

Priority = "high" → Slack ✓

Test Case 2

Priority = "low" → Email ✓

Test 3: Data Transformation

Section titled “Test 3: Data Transformation”

Goal: Verify data transforms correctly

  1. Provide sample input data
  2. Run transformation node
  3. Check output matches expected format
  4. Verify next nodes use transformed data

Test Data

Section titled “Test Data”

Use Realistic Test Data

Section titled “Use Realistic Test Data”
✅ Good Test Data:
- Real email addresses (yours) - Actual format samples - Edge cases (empty fields, special characters) - Various scenarios (high/low priority, etc.)
❌ Avoid:
- Customer email addresses - Production data - Sensitive information - Invalid formats

Debugging Failed Tests

Section titled “Debugging Failed Tests”

When a test fails:

1

Find the Error

Check execution log for red ✗ marks

2

Read Error Message

Click the failed node to see details

3

Fix the Issue

Update configuration or connections

4

Test Again

Run another test to verify fix

🔧
Add Screenshot Here
Error View - Show error message and details

Common Errors

Section titled “Common Errors”

”Email failed to send”

Section titled “”Email failed to send””
  • Check API key is valid
  • Verify “from” address is authorized
  • Ensure recipient email is correct

”Variable not found”

Section titled “”Variable not found””
  • Check variable name spelling
  • Verify data exists in previous nodes
  • Use correct syntax: {{data.field}}

”Trigger not firing”

Section titled “”Trigger not firing””
  • Check trigger configuration
  • Verify credentials (Google, etc.)
  • Ensure conditions are met

Testing Best Practices

Section titled “Testing Best Practices”
✅ Best Practices:
1. Test after each major change 2. Use your own contact info for testing 3. Test all conditional branches 4. Verify with different data scenarios 5. Check execution time is reasonable 6. Review all outputs before activating

When You’re Ready

Section titled “When You’re Ready”

After successful testing:

  1. Review execution logs one final time
  2. Verify all test emails/messages look correct
  3. Update any test-specific configurations
  4. Toggle workflow to “Active”
  5. Monitor first few real executions
🎯 Success!
Once your workflow passes all tests, you can confidently activate it knowing it will work correctly!

Next Steps

Section titled “Next Steps”