> ## Documentation Index
> Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Mapper

> Create or modify objects and arrays by mapping data.

Actions do the actual work in a workflow: API calls, transformations, notifications, flow control, and integrations. Use this action when your workflow needs to perform an operation, call an external service, or transform data for downstream nodes.

## When To Use

* Normalize event payloads from multiple trigger sources.
* Prepare a canonical object for downstream integrations.

## Configuration Checklist

1. Define target object/array schema.
2. Map source paths from trigger/action outputs to target fields.
3. Set defaults for optional fields.
4. Use mapped object in API calls or document generation.

## Inputs

* Required `node.data` metadata: `uiId`, `componentId`, and `operation` (for actions that define an operation).
* Action-specific configuration fields from the node editor.
* Upstream context values from triggers or previous nodes (for example `trigger.*` or prior action outputs).

## Outputs

* Adds action result data to the workflow context for downstream nodes.
* May produce external side effects (API updates, notifications, scripts, SSH commands, etc.).
* Can emit structured values consumed by conditions or subsequent actions.

## Failure Modes

* Missing required configuration or invalid parameter values.
* Missing/invalid context variable references from upstream nodes.
* External dependency failures (HTTP errors, auth failures, timeouts, rate limits).
* Payload validation/parsing errors during request or response handling.

## Best Practices

* Prefer small, composable actions over one large action with many responsibilities.