# Infor ION Data Flow, Calling an API in a Workflow, and Task Dropdowns

> Source: https://netray.co/erp-help/infor-ion-dataflow-api-in-workflow-dropdown-task
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

A data flow moves documents or data from a source to a target, with mapping in between. Inside an ION workflow you call an API through a service step that uses ION API credentials, and a task dropdown gets its options either from a fixed list defined on the form or from values your workflow loaded earlier. Details depend on your ION version.

## Kind

how-to

## System

infor-os

## Erp

Infor ION (Infor OS)

## Module

ION Data Flows / ION Workflow

## Query

infor ion dataflow

## Alternate Queries

- infor ion api within a workflow
- dropdown in infor ion task
- ion workflow task form dropdown values

## Applies To

Infor OS ION (Connect, Workflow, ION API), cloud and on-premise. Step and form control names vary by version.

## Steps

### How to wire a data flow, an API call and a dropdown

**Items:**

- Build the data flow first: define source and target connection points, add the mapping and test with a sample document.
- Create the service account and authorized app for ION API access, and download the .ionapi credential file for the caller.
- In the workflow designer add a step that calls the API (service or script-style activity in your version), set method, URL and body.
- Map the response to workflow variables so later steps can use the returned values.
- On the user task form, add a dropdown field and choose its option source: a static list or a variable holding a list.
- If options come from an API, call the API before the task, build a list variable of value and label pairs, and bind the dropdown to it.
- Handle failures: add a branch for non-success responses that notifies an administrator rather than failing silently.
- Test the full path in a non-production tenant, including permissions of the user opening the task.

## Sections

### Data flow basics

**Body:**

A data flow connects a source to a target and carries the documents in between, often with a mapping. Monitor the flow to see each document's state, and use resubmit for failed ones after fixing the cause.

Keep flows small and named for their business purpose. One flow per document type and direction is easier to support than a catch-all.

### Calling an ION API from a workflow

**Body:**

ION API is the gateway to Infor application APIs. A workflow call needs an access token from the service account or authorized app, then a request to the API path with the proper headers.

Parse the JSON response into variables. Treat any non-2xx status as an error branch, and log the response body so you can diagnose it later.

**Code:**

- GET https://<ion-api-host>/<tenant>/<application>/<service>/<resource>
Authorization: Bearer <access token>
Accept: application/json

### Dropdown values in a task

**Body:**

For stable choices such as approve, reject and send back, define a static list on the form. For values that change, such as a list of warehouses, load them from the source system in an earlier step and bind the dropdown to that list.

If the dropdown shows empty, the usual cause is that the list variable is not populated before the task starts, or its structure does not match the value and label the control expects.

## Pitfalls

- Calling the API with an expired token and not handling the 401.
- Binding a dropdown to a variable that is empty at task creation.
- Hard-coding environment URLs, which breaks when promoting from test to production.
- Making the workflow depend on a slow API without a timeout path.
- Giving the service account broader ION API scopes than the workflow needs.

## Ai Angle

An assistant can draft the API request for a workflow step from the endpoint's documentation, check the response structure against the dropdown binding, and explain failures from the monitor. Running it on a local model keeps tokens and tenant details inside your network. Netray builds this for sites with on-prem Infor systems.

## Faq

### How do I call an ION API inside a workflow?

**Answer:** Use a service-style step that sends an authenticated request to the ION API gateway, using a service account credential, then map the JSON response to workflow variables for later steps.

### Why is my dropdown in an ION task empty?

**Answer:** Usually the list variable is not populated before the task is created or its fields do not match what the control expects. Populate and verify it in a prior step.

### What is an ION data flow?

**Answer:** A configured route that moves documents or data from one connection point to another with optional mapping, visible and resubmittable in the ION monitor.

### Where do I get the credentials to call ION API?

**Answer:** From an authorized app and service account created in Infor OS, which provides the .ionapi file used to obtain tokens. Treat it as a secret.

## Search terms

infor ion dataflow, infor ion api within a workflow, dropdown in infor ion task, ion workflow api call, ion api service account, ion data flow monitor, infor os workflow form, ionapi file

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json