Skip to main content

Building No Code Flows

EmpowerID's No Code Flows feature enables organizations to automate recurring processes without requiring coding expertise. The platform includes a collection of predefined No Code Flows, each designed to address common organizational scenarios. If your organization requires a specific flow that is not included in the predefined set, you can create custom No Code Flows to meet your unique needs.

📄️ Create Flow Definitions

To create a No Code Flow in your organization, it's important to understand the specific business process that needs to be automated. This could be anything from the process of an employee leaving (known as "off-boarding") to another organizational procedure. Defining this process is the first step. Once that's complete, you'll need to create a Flow Definition – essentially a blueprint that outlines the exact sequence of actions required for the specified scenario. In this article, we'll walk you through the process of creating a Flow Definition step-by-step.

📄️ Create Flow Items

After creating a Flow Definition that represents the business process you want to automate with a No Code Flow, the next step is to create Flow Items for each action you want to occur within that flow. Using off-boarding as an example, actions could include disabling accounts, removing individuals from organizational groups, archiving emails, revoking access to company resources, and terminating their EmpowerID Person object within a specified timeframe. In this article, we will create a Flow Item that disables a user’s EmpowerID Person account and add the Flow Item to the Flow Definition created earlier.

📄️ Send Email Flow Item

The Email Flow Item within No Code Flows offers an automated solution for sending emails, seamlessly integrating email communication into various processes without manual intervention. Its purpose is to facilitate customized notifications based on specific conditions within workflows. For instance, in the scenario of an employee leaving a particular location, the regional administrator should receive a notification, whereas in other cases, the global administrator should be notified. This send email flow item allows users to tailor email notifications to suit unique requirements by configuring the flow item to match specific conditions.