Skip to main content

Components

Components are the building blocks of a workflow. Each component handles a specific task — fetching data, filtering records, transforming output, or sending notifications. Connect them on the canvas to build a complete automated process.

To add a component, click the + button in the workflow builder and select from the list.

Available components​

Start a workflow​

  • Trigger: defines how and when the workflow starts. Every workflow has one. See that page for the available ways to start a workflow.

Get data​

  • REST API: calls a web service and returns its answer.
  • M3 API: reads from or writes to Infor M3.
  • M3 Fetch: reads data from Infor M3, also used by lookup workflows.
  • Data Lake: runs an SQL query on large amounts of data in the Infor Data Lake.
  • File Loader: loads the most recently edited file from a SharePoint or OneDrive folder.
  • Lookup Workflows: fetches values from another workflow to pre-fill inputs.

Shape data​

  • Transform: reshapes JSON data with JSONata expressions.
  • Code: runs your own JavaScript.
  • Converter: converts data between JSON, CSV and XML.
  • M3 Filter and Generic Filter: in VXL Live workflows, keep only the rows that match a condition. In other workflows, filter with JSONata in a Transform step.

Deliver​

  • Email: sends an email, optionally with a file attached.
  • SMS: sends a short text message.
  • Excel: maps workflow data to and from spreadsheet columns.

Store​

  • Table Updater: writes data from any step into an existing Vince Platform table.
  • Table: stores output from an M3 API step in a table, and creates the table on the first run.

VXL Live​

note

M3 API, M3 Fetch, M3 Filter, Generic Filter, Excel, Table and Lookup Workflows are VXL Live components. You build them in the workflow editor, and they are used from VXL Live. Their pages are in the VXL Live section. See VXL Live Components for the list.

Which component do I need?​

  • I need to call a web service: REST API.
  • I need data from Infor M3 right now, or want to change M3: M3 API.
  • I need a lot of M3 data for a report: Data Lake.
  • I need to change the shape of the data: Transform.
  • I need to convert CSV or XML to JSON, or back: Converter.
  • I want to send a report by email: Email.
  • I want a text message when something happens: SMS.
  • I want to keep results for later or for an app: Table Updater, or Table for M3 API output.
  • I want the workflow to run on a schedule or when another system calls it: Trigger.

For how the components fit together, see Workflow Architecture 101.

Component order matters​

Data flows sequentially from one component to the next. Each component receives the output of the previous step, so the order in which you connect components determines what data is available at each stage.

note

Every workflow must begin with a Trigger component. You cannot add other components before configuring the trigger.

Last updated on