Tediware
Sign In

Flows

Flows are the processing pipelines that move data between your systems and your trading partners. Each flow is a chain of nodes that fetch, transform, route, and deliver EDI documents or JSON data. Flows are built automatically from your partner configuration.

Directions

Every flow has a direction:

  • Inbound – EDI documents flow from your trading partner to your system. A typical inbound flow fetches files from a connection, converts EDI to JSON, extracts individual transaction sets, and delivers the results to your webhook.
  • Outbound – JSON data flows from your system to your trading partner as EDI. A typical outbound flow receives JSON via the partner API endpoint, maps it to the partner’s specification, generates EDI, and uploads the file to the partner’s connection.

Flow Status

Flows have two statuses:

  • Active – the flow is live and processing documents. Inbound flows fetch files automatically on their configured schedule. Outbound flows accept and process API submissions.
  • Pending – the flow is built but not yet processing. Inbound flows on a pending status do not fetch files on a schedule, but can still be triggered manually. Useful for testing before going live.

You can change a flow’s status from the flow detail page by clicking Edit.

The Flow Builder

The flow detail page displays a visual canvas showing every node in the flow and how they connect. Data flows left to right through the pipeline.

Each node on the canvas shows:

  • Its type (input, transformation, branch, or output)
  • The service it performs (e.g., SFTP Fetch, EDI to JSON, Webhook)
  • The resource it references (e.g., a connection name or mapping name)

Click a node to view or edit its configuration.

Node Types

Flows are composed of four kinds of nodes, each with specific services:

Input – entry points that bring data into the flow.

  • SFTP Fetch – polls an SFTP connection for files
  • AS2 Endpoint – receives files via AS2
  • Partner Endpoint – receives JSON submissions via the partner API

Transformation – process or convert data as it moves through the flow.

  • EDI to JSON – parses raw EDI into structured JSON
  • Transaction Set Extractor – splits a multi-transaction interchange into individual documents
  • Mapping – applies a JSONata transformation to reshape data
  • Implementation – validates and generates EDI from JSON using a partner’s specification
  • Pass-through – forwards data unchanged

Branch – routes data conditionally.

  • Transaction Set Branch – directs documents to different paths based on their X12 transaction set type (e.g., 810, 856)

Output – delivers processed data to external systems.

  • SFTP Upload – sends files to an SFTP connection
  • AS2 Upload – sends files via AS2
  • Webhook – delivers results to an HTTP endpoint

Processing

Inbound flows run on a schedule. The process frequency determines how often Tediware checks the connection for new files – options are every 5, 10, 30, or 60 minutes depending on your subscription tier. You can also click Process on the flow detail page to trigger an immediate run.

Outbound flows are triggered when you submit data to the partner API endpoint. There is no schedule – processing begins as soon as data is received.

Every processing run generates a trace GUID that links all results through the entire pipeline, useful for debugging and audit trails.

Inbound Flow Settings

Inbound flows have two additional settings, configurable from the Edit panel:

  • Process frequency – how often the flow checks for new files (5, 10, 30, or 60 minutes). Available options depend on your subscription tier.
  • Delete files – whether to remove files from the connection after they are successfully fetched and processed.

Building Flows from Partners

Flows are built from your partner configuration. On the partner detail page, you will see an inbound lane and an outbound lane. Each lane shows the current flow status or a Build button if no flow exists yet.

Build requirements:

  • Internal envelope assigned
  • External envelope assigned
  • Connection assigned
  • At least one transaction setting for that direction
  • For inbound: an inbound webhook configured

If any requirement is missing, the partner page shows what still needs to be configured.

Rebuilding: When you change a partner’s configuration after a flow has been built – for example, adding a new transaction setting or changing the connection – the partner page indicates the flow is out of date. Click Rebuild to apply the new configuration. Until rebuilt, the flow continues using its previous configuration.

When a flow is rebuilt, its status, frequency, delete files setting, and tags are preserved from the previous version.