What Are Workflow Actions?
Workflow actions are the operational steps that perform tasks in your automation. Actions handle everything from sending API requests to processing data, with each action receiving input from previous steps and producing output for subsequent steps. Common action use cases:- Send HTTP requests to external APIs
- Transform and map data between different formats
- Add delays and timing controls
- Process arrays and lists with iterations
- Generate dynamic text and notifications
Universal Action Configuration
Error Handling: Continue on Error
Many actions share a common property for error handling:If set to
true, the workflow will not stop if this specific node fails. Instead, it will proceed down a special “error” path from the node, allowing you to build custom error-handling logic (e.g., sending a notification). If false, any failure will immediately stop the entire workflow run.Complete Actions Reference
Choose the right action type for your automation needs:Webhook Action: Send HTTP Requests to External APIs
The Webhook action sends HTTP requests to external services, making it the foundation for most API integrations. Use webhook actions to connect with third-party services, trigger external processes, or fetch data from remote systems.Configuration
The HTTP method. Options:
GET, POST, PUT, PATCH, DELETE.The URL to send the request to. You can use variables from previous steps, like
https://api.example.com/users/{{ node_1.user_id }}.For
POST, PUT, and PATCH requests, this is the JSON body of the request. Variables are supported.A list of HTTP headers to include, such as
Content-Type or Authorization. Values can be plain text or references to secrets in your Vault.For security, requests to private or internal IP addresses are blocked to prevent Server-Side Request Forgery (SSRF) attacks.
Altostrat API Action: Authenticated Platform Calls
The Altostrat API action makes authenticated calls to the Altostrat platform using your workflow’s linked authorization. This action simplifies platform integrations by automatically handling authentication headers and API versioning.Configuration
The HTTP method. Options:
GET, POST, PUT, PATCH, DELETE.The API endpoint path, starting with a
/. Example: /users?filter[status]=new.The JSON body for
POST, PUT, and PATCH requests. Variables are supported.Delay Action: Add Timing Controls to Workflows
The Delay action pauses workflow execution for a specified duration, allowing you to create timed sequences, rate-limit API calls, or wait for external processes to complete.Configuration
The amount of time to wait.
The unit of time. Options:
seconds, minutes, hours, days.There is a maximum delay of 15 minutes for a single delay step. For longer delays, you may need to chain multiple steps or use a different architectural approach.
Iterator Action: Process Arrays and Lists
The Iterator action processes arrays by running a sub-workflow for each item in the list. Essential for batch processing, bulk operations, and handling multiple records from API responses.Configuration
A reference to an array from a previous step. Example:
{{ node_1.data.users }}.A complete, self-contained workflow that will be executed for each item in the input array.
Sub-Workflow Context
Inside the iterator’s sub-workflow, a specialiterator variable is available with the following properties:
iterator.item: The current item being processed.iterator.index: The zero-based index of the current item.iterator.first:trueif this is the first item in the array.iterator.last:trueif this is the last item in the array.iterator.total: The total number of items in the array.
If any single iteration fails, the entire Iterator step (and the parent workflow) will fail. The results of each iteration are collected and made available as an array to the nodes following the Iterator.
Trigger Workflow Action: Create Modular Automations
The Trigger Workflow action calls other workflows, enabling modular automation design. Break complex processes into reusable components that can be called from multiple workflows.Configuration
The ID of the workflow you want to trigger.
A JSON object to send as the initial data to the target workflow. Variables are supported.
To prevent infinite loops, the system will detect and block circular dependencies (e.g., Workflow A calls Workflow B, which then calls Workflow A).
Data Mapper Action: Transform and Reshape Data
The Data Mapper action creates new JSON objects by mapping values from previous workflow steps. Essential for transforming data formats, creating API payloads, and restructuring information between different systems.For more advanced data manipulation using logic and filters, see our Liquid Templating documentation.
Configuration
A list of mappings.
- Key: The key in the new output object. You can use dot notation to create nested objects (e.g.,
user.profile.name). - Value: The value to assign. This can be a static value, a variable from a previous step, or even a mix of both.
JSON Parser Action: Convert Strings to Structured Data
The JSON Parser action converts JSON strings into structured objects that subsequent workflow steps can access. Use this action when receiving JSON data as text from APIs or external sources.Configuration
A reference to a string from a previous step that contains valid JSON. Example:
{{ node_1.body }}.The key under which the parsed data will be stored. Defaults to
data.Text Transform Action: Dynamic Text Generation with Liquid
The Text Transform action generates dynamic text using Liquid templating language. Create personalized messages, formatted reports, and complex text output with conditional logic and data from previous workflow steps.Learn more about Liquid syntax and capabilities in our Liquid Templating documentation.
Configuration
The Liquid template string. You can use variables from previous steps, which will be processed by the Liquid engine. Example:
Hello {{ node_1.user.name | upcase }}.The key where the rendered text will be stored. Defaults to
result.Date Transform Action: Date and Time Operations
The Date Transform action performs calculations and formatting on date and time values. Add or subtract time periods, format dates for different systems, or extract specific date components for workflow logic.Configuration
The starting date/time string (e.g., “2025-01-01T12:00:00Z”) or a variable.
The operation to perform. Options:
add, subtract, format, start_of, end_of.The value for the operation. For
add/subtract, this is the amount. For format, it’s the format string (e.g., Y-m-d). For start_of/end_of, it’s the unit (e.g., day, week).Required for
add and subtract. Options: days, weeks, months, years, hours, minutes, seconds.The key where the transformed date will be stored. Defaults to
result.Terminate Action: Controlled Workflow Completion
The Terminate action immediately stops workflow execution with a specified status. Use terminate actions to exit workflows early based on conditions while maintaining control over the final workflow state.Configuration
The final status to set for the workflow run. Options:
completed, failed.An optional message to record in the workflow run’s details, explaining why it was terminated.