Get Started with UKG Compose in UKG Pro

Build your first workflow in UKG Compose with a step-by-step tutorial using a scheduled trigger, logic, and actions.

Get Started with UKG Compose in UKG Pro

Note: Compose is only available for Beta testing. See Welcome to UKG Compose > Beta Disclosure for more information.

This page walks through a first workflow in UKG Compose using a simple pattern that is easy to test: a scheduled trigger, followed by a small amount of logic, followed by a notification-style action.

This is the recommended first workflow because it is easier to validate than a business event that depends on a specific HCM or WFM transaction. It also maps well to both Pro-only and Pro Suite customers.

Before you begin

Before building your first workflow, confirm the following:

  • You can access Compose from UKG Pro
  • Your user has the required HCM security rights for Compose access
  • Your tenant is on the latest supported UKG AuthN version
  • If you plan to use HCM Webhooks Trigger later, your tenant has the required UKG Webhooks prerequisite configured

Step 1: Open Compose from UKG Pro

In UKG Pro, navigate to Compose:

  • In Classic view, Compose appears under Configurations
  • In MX view, Compose appears within Application Setup

When you open Compose from UKG Pro, the product opens without requiring a separate login because the experience uses the existing UKG Pro session.

Step 2: Create a new workflow

From the Compose landing page, select Create Workflow.

You can also open the editor from the Workflows page by choosing: Workflows > Add new > Workflow. This opens the Workflow Editor, which uses n8n’s drag-and-drop workflow design experience.

Step 3: Add a Scheduled Trigger

In the editor:

  1. Select Add first step.
  2. Choose a Schedule Trigger node.
  3. Configure a simple schedule for testing, such as every hour or once per day at a known time.

For a first workflow, use a schedule that is easy to test and reason about.

Understanding the node selection panel

When you select Add first step or click the + button on an existing node, the node selection panel appears on the right side of the editor. This panel provides a catalog of available nodes organized by category:

  • Trigger nodes - Start workflows from schedules, webhooks, forms, or UKG Pro events
  • Action nodes - Perform work such as notifications, API calls, or data updates
  • Logic nodes - Control flow with IF, Switch, and data transformation
  • UKG-specific nodes - Custom nodes for UKG integrations (triggers, notifications, approvals, queries)

You can search for nodes by name or browse by category. The panel includes both standard n8n nodes and custom UKG nodes designed for UKG-specific workflow scenarios.

Step 4: Add logic with IF or Switch

After the scheduled trigger:

  1. Add an IF or Switch node.
  2. Configure a simple condition for testing.

Examples:

  • Route one path when today is a weekday
  • Route one path when a test value equals true
  • Branch based on a static variable or simple expression

The goal here is not business complexity. It is to help a first-time builder understand how Compose workflows branch and how data moves between nodes.

Step 5: Add an action

After the logic node, add one action on each branch.

For the first public version of this page, use a placeholder for supported UKG nodes, such as:

  • UKG Notification
  • Form response
  • another approved UKG action node

Step 6: Test the workflow

Before turning the workflow on:

  1. Open each node and confirm it is configured correctly.
  2. Resolve any node validation issues.
  3. Use Execute Step where appropriate.
  4. Select Execute Workflow to manually test the workflow in the editor.

For a first workflow, manually executing the flow is the fastest way to validate that the trigger, branch logic, and action configuration are working as expected.

Step 7: Activate the workflow

After a successful test, use the Inactive / Active toggle to activate the workflow Once activated, the workflow is ready to run based on its configured trigger.

Step 8: Review executions

Open the Executions tab to review past runs and answer questions like:

  • Did the workflow start when expected?
  • Which path did the IF or Switch node take?
  • Did the action node complete successfully?
  • Was any data missing or malformed?

What to build next

After completing your first workflow, common next steps include:

Related pages