Major

UKG AI: Native features, API integration, and Major workflows

Understand UKG Bryte AI, six verified Pro WFM API operations, and how Major connects workforce evidence across systems with review queues and approvals.

Ritvij GautamUpdated
Major x UKG logo lockup

UKG AI includes Bryte AI features for workforce insights, reporting, and hiring assistance. This guide explains those native capabilities, UKG Pro WFM API integration, and how Major adds cross-system apps, agent judgment, and approval workflows for HR operations and plant supervisors.

What UKG does for workforce teams

UKG provides human capital management and workforce management software. Its Pro WFM API exposes the schedules, punches, timecards, accruals, and employee groups that workforce teams use to run hourly operations.

Shift supervisors compare expected coverage with who arrived. Payroll teams investigate incomplete time records before closing a pay period. HR operations teams reconcile leave information with employee records held elsewhere. These jobs share a dependency: the employee, date range, and business location must match before a discrepancy means anything.

UKG Pro HCM and UKG Pro WFM have different API surfaces and authentication requirements. The authentication overview makes that distinction explicit. This guide focuses its endpoint examples on Pro WFM, not UKG Ready or a universal UKG API.

Major adds the deterministic app layer around that work. An app holds matching rules, case history, and supervisor review queues. An agent evaluates ambiguous exceptions. A workflow schedules collection and routes approvals. Major is the enterprise platform where agents build the software they run on, so repeatable reconciliation becomes reusable software rather than a fresh reasoning task every shift.

UKG AI: what Bryte already provides

UKG's Bryte AI marketplace listing describes three useful capabilities by name:

  • Job Genius & Interview Guide: creates job descriptions from a role's title, functions, and skills, and helps hiring managers prepare interview questions.
  • Frontline Insights: helps employees understand their work schedules and manage availability, shifts, and location preferences.
  • Conversational Reporting: lets managers ask for analysis and reports through a conversational interface.

These are sensible starting points when the work stays inside UKG. Confirm availability for your product, tenant, and agreement rather than assuming every Bryte feature exists in every UKG deployment. A marketplace description is not evidence that a corresponding public API is available.

Major adds value when the question crosses systems. A staffing recommendation may need production demand from Plex, current UKG attendance, and a supervisor's pending decision. A leave discrepancy may need an approved request from BambooHR alongside a UKG accrual balance.

The agent makes the judgment about the discrepancy and drafts the explanation. The Major app preserves evidence and review state, while the workflow controls notifications and approval. That extends UKG's native features without pretending they are absent or treating conversational reporting as a complete cross-system operating process.

How UKG connects to Major

UKG has no native or Pipedream connector in the catalog: it connects as a custom API connector, with base URL and auth configured once by IT. Do not treat UKG's presence in the research catalog as proof of a ready-made native connection.

For Pro WFM, the quick start defines the tenant-specific API root as https://<hostname>/api. The endpoint paths below are relative to that root. IT verifies the tenant hostname, enabled authentication flow, and permissions before exposing operations to an app or agent.

Credentials stay centrally stored in Major's connector vault, never in prompts or application code. IT scopes the connection to the employee populations and operations needed for the process. Major's SSO, RBAC, and audit logs cover the apps, agents, and workflows using it.

Start with read access. A staffing monitor needs schedules and attendance evidence, not permission to approve payroll or change punches. Configure any later write capability separately and put an approval step before consequential changes.

Major orchestrates UKG; it never replaces it. UKG remains the source of workforce records, and the Major app becomes the control surface for cross-system exceptions and approvals.

UKG API guide for governed integrations

Authentication and permissions

The UKG Authentication guide documents authorization-code, user-context, and client-credentials flows. Client credentials suit system-to-system integrations and are associated with a Function Access Profile. Its client-credentials example returns the scope access:wfm and uses the audience https://wfm.ukg.net/api. That scope is not a substitute for the tenant's access profile.

The legacy WFM security guide documents a different token flow. Match your tenant's configuration rather than mixing examples. The quick start shows the Authorization and appkey headers. Pro HCM Core instead uses Basic authentication with a web service account and customer API key, according to the cross-product overview.

Pagination, limits, and testing

Employee groups uses index, default 0, and count, default 100. Follow each operation's documented pagination rather than inventing a common cursor. Gate entry punches also defines index and count in its request object and limits a request to 500 employees.

The limits guide documents HTTP 429 for throttling and HTTP 413 for service limits. A universal requests-per-minute allowance and rate-limit response headers are not documented publicly on the reviewed pages. Inspect response metadata without assuming a specific header exists.

The authentication guide distinguishes nonproduction credentials from production credentials. The webhooks guide provides a WFM nonproduction webhook environment and a Test Endpoint action. Use those facilities with an authorized nonproduction tenant, not an assumed anonymous sandbox.

Events and delivery

TimecardPunchChangeEvent fires when a timecard punch is created, updated, or deleted. Its event time differs from the actual punch time. It is an event schema, not a REST command to retrieve punches.

The webhooks user guide supports an optional HMAC secret of at least 24 characters. Configure it and follow UKG's verification instructions, including replacing the referenced signature library's prefix with webhook. The reviewed guide does not specify a retry timetable. It warns that events can arrive out of order and recommends secondary polling where missed events are unacceptable.

POST /v1/commons/devicegatepunches/multi_read

Retrieves gate entry punches for selected employees, with the documented UDM monitoring access control point.

  • App: displays arrival evidence next to each staffing case.
  • Agent: assesses whether missing arrival evidence warrants escalation, without equating gate entry with paid working time.
  • Workflow: batches employee populations within the documented 500-employee request limit before a shift.

POST /v1/timekeeping/punches/apply_read

Returns employee punches in real time, using the request schema documented for this operation.

  • App: records the punch evidence used in an exception review.
  • Agent: interprets a possible missed clock-out against the schedule and surrounding context.
  • Workflow: refreshes punch evidence after an event or on a scheduled reconciliation pass.

GET /v1/timekeeping/timecard

Returns a manager timecard using an employee identifier and a date range or symbolic period.

  • App: presents the relevant pay-period record in a restricted review view.
  • Agent: explains whether the reported exception is consistent with the current timecard.
  • Workflow: re-reads the record before sending a proposed correction for approval.

GET /v1/scheduling/employee_schedule

Returns an employee schedule according to the supplied parameters.

  • App: stores a dated schedule snapshot alongside the case.
  • Agent: compares expected coverage with attendance evidence and external production demand.
  • Workflow: collects the upcoming shift window and refreshes it before escalation.

GET /v1/scheduling/timeoff/accruals

Returns an accrual balance for a manager-context request.

  • App: displays the balance and effective context beside an external leave request.
  • Agent: distinguishes a likely timing difference from a discrepancy requiring HR review.
  • Workflow: retrieves the balance before a payroll cutoff and again after an authorized correction.

GET /v2/commons/employee_groups

Lists employee groups, or finds one by name, with pagination and the employee-group access control point.

  • App: maintains the group reference list used by exception filters.
  • Agent: uses group context to explain which operational team should review a case.
  • Workflow: refreshes all pages and records completion before dependent reconciliation begins.

UKG automation use cases on Major

Plex and UKG shift coverage review

Compare production demand with scheduled and observed attendance before a shift starts. Use the schedule and gate entry operations above, and keep gate activity separate from proof of a payable shift.

  • App: holds line requirements, employee mappings, and coverage cases.
  • Agent: prioritizes plausible coverage gaps using production context.
  • Workflow: collects both systems, routes recommendations to the supervisor, and records the response.

Workday and UKG headcount reconciliation

A transfer or termination can make a roster stale. Use the employee schedule operation to check the relevant UKG window against authorized worker changes from Workday. A punch event alone cannot establish a hire, transfer, or termination.

  • App: tracks cross-system employee mappings and unresolved differences.
  • Agent: evaluates whether a mismatch indicates stale scheduling or an identity problem.
  • Workflow: runs on a schedule or an authorized worker-change trigger and requests HR review.

BambooHR and UKG PTO investigation

Use the accrual operation and manager timecard read to investigate approved leave that does not appear consistent with UKG records. Compare units and effective dates before declaring a balance error.

  • App: preserves leave-request references, balance snapshots, and review status.
  • Agent: explains whether timing, policy, or missing information might explain the difference.
  • Workflow: prepares a pre-payroll queue and routes corrections to an authorized operator.

UKG punch exceptions with Slack notifications

Use the real-time punch and manager timecard reads after a verified punch event, with polling as a backstop.

  • App: holds one case per employee, shift, and exception type.
  • Agent: drafts a short explanation and identifies missing evidence.
  • Workflow: sends a minimal Slack notification linking to the restricted case, never a channel dump of payroll records.

These are proposed implementation patterns grounded in the UKG integration surfaces. They are not claims of published customer deployments or completed step-by-step guides. For adjacent system planning, see Plex production workflow automation, BambooHR AI and HR operations, and Workday apps, agents, and workflows. These related hubs describe the other systems, not UKG tutorials.

How to build the UKG review architecture on Major

UKG and Plex data flow through a Major workflow, agent judgment, and supervisor review app

UKG remains the workforce record; Major holds cross-system review state.

Build the app as the durable center of the process. Its managed database holds employee mappings, source timestamps, exception cases, approval records, and delivery attempts. Views give supervisors a queue rather than a stream of disconnected alerts.

  1. Configure the UKG custom API connector and the authorized production-data connection once.
  2. Have the workflow collect bounded date windows, validate response shapes, and save source references.
  3. Run deterministic matching and arithmetic in the app before asking for judgment.
  4. Give the agent only the evidence necessary to assess the unresolved case.
  5. Route its recommendation through a workflow decision and, when required, human approval.
  6. Save the outcome and refresh the source records before closing the case.

The diagram's workflow node represents orchestration, not an app making a staffing decision. The agent judges ambiguity, and the app holds state. As matching logic becomes understood, the agent can build reusable app logic for that repeatable work. Reason once. Run forever.

For example: a pre-shift staffing review with numbers

For example, consider an illustrative plant reviewing 200 employee-shift records each day. Suppose opening the schedule, checking arrival evidence, and recording a result takes two minutes per record. The manual baseline is 200 × 2 minutes = 400 minutes, or 6 hours and 40 minutes per day.

A proposed Major workflow collects those records and runs deterministic employee matching. Assume, for planning only, that 180 records match cleanly and 20 need investigation. If a reviewer spends three minutes on each evidence-backed case, review takes 20 × 3 = 60 minutes. Add 20 minutes for a reconciliation check and the modeled total is 80 minutes.

The difference is 400 minus 80 = 320 minutes, or 5 hours and 20 minutes of handling time. These numbers are assumptions, not a customer result, a benchmark, or a promise about connector performance.

The agent might judge that one missing arrival is urgent because that role covers a constrained production line. The supervisor still approves reassignment. Measure actual false alerts, stale records, and review time in a pilot before using the model for staffing or budget decisions.

Governance, approvals, and failure handling

UKG punch evidence leads to either an informational alert or human approval in a Major review queue

Informational alerts can follow policy; time and pay changes require approval.

Define an action policy before enabling the agent. It may summarize evidence, classify an exception, and draft a message. It must never independently invent a punch, approve a timecard, alter pay, or change a leave balance. Keep employment decisions with authorized people.

Use separate permissions for restricted HR evidence and general supervisor notifications. Record the approving person in Major even when the UKG connection uses system credentials. An approval should identify the exact employee, period, proposed action, and evidence version.

For HTTP 429, use bounded exponential backoff with jitter and any server-provided timing guidance, without assuming an undocumented header. For HTTP 413, reduce the request population or time window instead of retrying the same oversized request. Both status meanings come from UKG's limits guide.

Verify webhook authenticity before processing, deduplicate deliveries, and re-read current records because delivery order is not guaranteed. UKG recommends polling as a backstop for integrations that cannot tolerate missed changes.

Persist checkpoints and failed cases so a restart does not duplicate notifications. Mark incomplete data explicitly. A source outage must create a visible collection failure, not a conclusion that everyone is absent. Audit source reads, agent recommendations, approvals, and final outcomes with sensitive payloads redacted from general logs.

UKG AI Apps, Agents and Workflow Automations

Step-by-step UKG builds will appear here as they are published.

Frequently asked questions

What is UKG AI?

UKG AI includes Bryte AI capabilities such as Job Genius & Interview Guide, Frontline Insights, and Conversational Reporting. Product availability varies. Major extends the operating process around UKG with cross-system apps, agent judgment, durable review state, and approval workflows.

Does Major have a native UKG connector?

No. UKG connects to Major through a custom API connector with the tenant base URL and authentication configured once by IT. Credentials stay in the connector vault, and access is scoped to the process.

Can I use the same authentication for UKG Pro HCM and WFM?

Do not assume so. UKG documents different authentication models across products. Pro HCM Core uses Basic authentication with a web service account and customer API key. WFM supports OAuth-based flows whose configuration depends on the tenant.

Can a UKG AI agent fix missed punches automatically?

An agent on Major can investigate evidence and propose a correction. Time and pay changes should require an authorized person's approval. The app retains the evidence and review history, and the workflow routes the decision before any consequential action.

Does UKG support punch webhooks and a test environment?

UKG documents TimecardPunchChangeEvent for punch creation, updates, and deletion. Its webhooks guide includes a Test Endpoint action and a WFM nonproduction environment. Configure HMAC verification and use polling to reconcile changes that events may miss.

What are the UKG API rate limits?

The reviewed WFM limits guide documents HTTP 429 for throttling and HTTP 413 for service limits, but no universal requests-per-minute allowance or rate-limit response headers. Individual operations specify limits, including a 500-employee maximum for gate entry punch requests.

Sources

Start building on Major

Build a UKG staffing or timekeeping review app with scoped API access, evidence-backed agent recommendations, and supervisor approvals.

About the author

Ritvij Gautam is Head of Growth at Major.

Last reviewed November 20, 2026 by Ritvij Gautam.

Frequently asked questions

What is UKG AI?
UKG AI includes Bryte AI capabilities such as Job Genius & Interview Guide, Frontline Insights, and Conversational Reporting. Product availability varies. Major extends the operating process around UKG with cross-system apps, agent judgment, durable review state, and approval workflows.
Does Major have a native UKG connector?
No. UKG connects to Major through a custom API connector with the tenant base URL and authentication configured once by IT. Credentials stay in the connector vault, and access is scoped to the process.
Can I use the same authentication for UKG Pro HCM and WFM?
Do not assume so. UKG documents different authentication models across products. Pro HCM Core uses Basic authentication with a web service account and customer API key. WFM supports OAuth-based flows whose configuration depends on the tenant.
Can a UKG AI agent fix missed punches automatically?
An agent on Major can investigate evidence and propose a correction. Time and pay changes should require an authorized person's approval. The app retains the evidence and review history, and the workflow routes the decision before any consequential action.
Does UKG support punch webhooks and a test environment?
UKG documents TimecardPunchChangeEvent for punch creation, updates, and deletion. Its webhooks guide includes a Test Endpoint action and a WFM nonproduction environment. Configure HMAC verification and use polling to reconcile changes that events may miss.
What are the UKG API rate limits?
The reviewed WFM limits guide documents HTTP 429 for throttling and HTTP 413 for service limits, but no universal requests-per-minute allowance or rate-limit response headers. Individual operations specify limits, including a 500-employee maximum for gate entry punch requests.