Overview

Overview

Action Types are special workflow elements that enhance your test workflows beyond standard test script execution. They allow you to control workflow logic, manage timing, send notifications, and handle data operations.

🎯 What Are Action Types?

Action Types are like utility functions for workflows. They complement test scripts by providing timing control, retry logic, notifications, and data management capabilities.

---

What Are Action Types?

Action Types are reusable actions you can add to your workflows to:

• Control execution flow - Wait, Retry, Stop

• Send notifications - Email alerts and communications

• Manage data - Fetch and store test data

• Document workflows - Add comments and notes

Think of them as steps that complement your test scripts to create sophisticated, resilient workflows.

---

Available Actions

Action	Purpose	Learn More
Wait	Pause execution for specified duration	Detailed Guide
Retry	Automatically retry failed steps	Detailed Guide
Stop	Conditionally halt workflow execution	Detailed Guide
Send Email	Send email notifications	Detailed Guide
Data Hub	Access centralized test data	Detailed Guide
Comment	Add documentation to workflows	Detailed Guide

---

Quick Start

Adding an Action to Your Workflow

1. Open your workflow in the editor

2. Click "Add Action" button on the canvas

3. Select action type from the menu

4. Configure the action with required parameters

5. Connect to other nodes as needed

6. Save your workflow

Example: Adding Retry Logic

[API Call]
    ↓
[Retry Action: 3 attempts]
    ↓
[Next Step]

---

Common Use Cases

Reliable API Testing

Combine Retry with Wait to handle intermittent failures:

[API Request] → [Retry: 5 attempts] → [Verify Response]

Data-Driven Testing

Use Data Hub to fetch test data:

[Data Hub: Get Users] → [Login Test] → [Profile Update]

Multi-Step Workflows

Use Wait for synchronization:

[Create Order] → [Wait: 30 seconds] → [Verify Email]

Conditional Execution

Use Stop for conditional logic:

[Login Test] → [Stop if Failed] → [Remaining Tests]

---

Best Practices

✅ Do

Recommended Practices

• ✅ Use Retry for transient failures - Handle temporary network issues gracefully

• ✅ Add Wait between dependent steps - Allow systems time to process

• ✅ Document complex sections - Use comments for clarity

• ✅ Test action configurations - Verify behavior before scheduling

• ✅ Monitor action performance - Track reliability and execution times

• ✅ Use appropriate timeouts - Match your system's response times

• ✅ Combine actions strategically - Retry + Wait + Stop for robustness

❌ Don

💡 Tips

---

Combining Actions: Real-World Example

Workflow: Resilient Payment Processing

[Data Hub: Fetch Payment Data]
         ↓
[API: Create Order]
         ↓
[Retry: 3 attempts]
         ↓
[Wait: 2 seconds]
         ↓
[Web: Verify Payment Success]
         ↓
    ┌────┴────┐
Success    Failure
    ↓          ↓
[Log Result][Send Email Alert]

💬 Comment: "Payment workflow with retry logic and notifications"

---

Detailed Guides

Select an action type to learn more:

• Wait - Add delays and synchronization

• Retry - Handle failures automatically

• Stop - Conditional workflow termination

• Send Email - Send notifications

• Data Hub - Access test data

• Comment - Document workflows

---

Related Topics

• Execution Flow - Understand workflow execution

• Error Handling - Comprehensive error strategies

• Workflow Patterns - Common patterns using actions

• Conditional Execution - Advanced branching logic

• Features Overview - All available features

---

Next Steps

Start by learning about the most commonly used actions:

1. Learn about Wait - Master timing and synchronization

2. Learn about Retry - Build resilient workflows

3. Learn about Stop - Implement conditional logic

4. Explore all actions - Master the complete toolkit