Flows, mappings and schedules
Design a flow, map fields between systems, preview the result, publish a version and schedule it.
Updated 07/10/2026
On this page
Integrations and flows
An integration belongs to a project and groups related flows, for example "Order to cash" with one flow for orders and another for invoices. Each flow has a trigger (manual or schedule), a target environment and numbered versions.
Start from scratch with Connect → New integration, or install a ready-made pattern from Connect → Templates. Templates create the integration, its flow and placeholder steps for you to point at your own connections.
Steps
| Step type | Purpose |
|---|---|
manual_trigger, schedule_trigger | Starts the flow |
source | Reads records with a connection's read operation, such as orders.list |
map | Maps source fields to destination fields |
transform | Applies an expression to records |
filter | Drops records that do not match a condition |
validate | Checks records before they are written |
destination | Writes records with a connection's write operation, such as invoices.create |
Each step can set a timeout (1–300 seconds, default 30), a retry policy and an error policy. Edges join steps and can carry a condition and a priority.
Mappings
A map step translates each source record into the destination operation's input. Nexra loads both schemas from the operations bound to the flow, so you pick fields rather than typing paths.
| Mapping type | Result |
|---|---|
direct | Copies a source field, for example customer.email to Email |
constant | Writes a fixed value |
default | Uses the source value, or a fallback when it is empty |
transform | Applies an expression to the source value |
Use Preview to run the mapping against a sample record and see the exact payload the destination would receive. Nothing is written to the provider during a preview. Mark destination fields as required to stop incomplete records early.
Validate, compile and publish
Validate checks the flow graph and every binding:
- the connection is active and in the flow's environment;
- the operation is available;
- writes are enabled on the connection;
- the provider permissions were granted at the last health check;
- credentials are present;
- no write operation is used as a source.
Publish freezes the version. Published versions are immutable; to change a flow, create a new version from it.
Pause and Resume stop and restart a published flow without losing its history.
When compilation fails, the console lists each issue against the step it concerns.
Schedules
Add a schedule to a flow with a five-field cron expression and a time zone (default UTC), for example */15 * * * * for every 15 minutes. Schedules can be paused, resumed, edited or deleted. A scheduled run uses the flow's active published version and deployment.
Running a flow
Sandbox: run from the flow page at any time.
Production: needs an approved, active deployment (see Approvals and deployments).
Every run needs an idempotencyKey and a correlationId (8–160 characters of letters, digits, ., _, : or -). Repeating a run with the same key returns the original run instead of starting a new one.
Exporting an integration
On an integration, choose Review API / MCP export → Download service contract to download nexra-connect-service.json. It describes how to invoke and monitor the integration over MCP. See Export MCP and API configuration.