Actions
An Action performs a specific task (e.g., Create, Update, Retrieve, Delete) within a workflow.
Implementation Lifecycle
Overview: Configure metadata and assign the required authentication method.
Input Builder: Define user-facing fields (e.g.,
Email,Message).API Configuration: Define the request (Method, Endpoint, Headers, Body) using JavaScript to execute the task.
Sample Data: Provide the expected JSON response structure to enable downstream field mapping.
Input Data Access
Use the following pattern to reference user inputs in your API code:
context.inputData.<fieldKey>
Example: context.inputData.email
Technical Solution
Challenge | Solution |
Field Mapping | Always define Sample Data so users can map outputs to future steps. |
Dynamic Inputs | Use the Input Builder to keep forms minimal and relevant. |
Execution Logic | Use JavaScript in the API Configuration to handle complex transformations. |
💡 Best Practice: Ensure your Sample Data accurately reflects your API's production response. If the schema is incorrect, users will be unable to map data, rendering the action unusable in automated workflows.
