About building Flows

The triggering event and the resulting actions in your use case are linked through connectors, functions, and mapped input and output values.

  • Connector - Which applications are involved in your Flow? Connectors enable you to interact with them without manually configuring APIs.
  • Function - Functions allow you to interact with, change, or control the data in your Flow. Typically, a Function card is placed between Action cards.
  • Connection - A connection is your unique level of access to the connected app (for example, admin or end user).
  • Input - Input fields determine how an action or function card proceeds. For example, the input field on Search for User action card might be Email address.
  • Output - Output fields contain the results that are generated by the event, action, or function card. For example, a User Unassigned from Application event card might produce output values like Date and Time, Message, Event ID, Event Type, and Event Time.
  • Mapping - The movement of data between cards is referred to as mapping. To map data between cards, drag and drop the output field of one card to the input field of another card. Be sure that the format of the fields match (text, number, true/false, date & time, object, or list).
  • Screenshot of User ID mapped between cards

Optional elements

  • Notes - Notes explain the Flow or set reminders. You can add them between events, actions, or functions without affecting the run-time process.
  • Templates - A template is a copy of a Flow created by Okta that fulfills a use case with minimal configuration.