.png)
Workhuman Integration Guide
Workhuman can be integrated with enterprise systems through tenant-specific APIs, conditional callbacks, and scheduled data exchanges that must be confirmed for each customer environment.
Workhuman integration options at a glance
Workhuman integration availability depends on the customer’s product edition, tenant configuration, contract, and Workhuman approval. A public, generally available REST API, GraphQL API, SOAP service, webhook framework, bulk API, and file specification were not confirmed in the supplied research. Workhuman may provide tenant-specific or partner-enabled APIs, scheduled exports, or selected outbound callbacks. Martini can consume confirmed Workhuman endpoints, receive supported notifications, process scheduled files, map employee and recognition data, apply eligibility and idempotency rules, and deliver results to HR, finance, collaboration, or analytics systems. Credentials and other confirmed authentication materials can be stored securely in Martini.
| Integration point | Supported by Workhuman? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Not confirmed | Workhuman may provide tenant-specific or partner-enabled APIs for Employees, Recognition, Rewards, Nominations, Programs, or Redemptions. Public endpoint coverage and availability were not verified. | Martini can consume a confirmed Workhuman REST API, map payloads, apply validation and business rules, and orchestrate downstream updates. |
| GraphQL APIs | Not confirmed | No official Workhuman GraphQL API documentation was confirmed. | Martini can consume GraphQL services when a documented Workhuman endpoint is made available, but no Workhuman GraphQL capability should be assumed. |
| SOAP APIs | Not confirmed | No official Workhuman SOAP documentation was confirmed. | Martini can consume documented SOAP services if Workhuman provides one for the required tenant or product, but this is not a confirmed Workhuman mechanism. |
| Webhooks / outbound callbacks | Not confirmed | Public documentation confirming Workhuman webhooks or callbacks was not found. Notifications may be limited to selected events or customers. | Martini can receive and validate confirmed Workhuman callbacks, trigger workflows, deduplicate events, and route them to downstream systems. |
| Bulk / asynchronous APIs | Not confirmed | Scheduled extracts or batch interfaces may be available, but public official documentation was not verified. | Martini can process confirmed batch responses or asynchronous completion flows using scheduled or event-driven workflows. |
| File / attachment APIs | Not confirmed | Administrative or data-export processes may exist, but a public specification for Workhuman file import, export, or attachment APIs was not confirmed. | Martini can process confirmed CSV, Excel, JSON, or other files and map them into downstream systems or Workhuman import structures. |
| Authentication | Not confirmed | Workhuman-specific authentication, scopes, roles, and service-account requirements require confirmation. OAuth 2.0, API keys, certificates, and other methods must not be assumed. | Martini can store confirmed credentials and secrets in secure configuration and use the authentication method documented for the Workhuman tenant. |
| Database / analytics access | Not confirmed | No customer-facing SQL interface or direct Workhuman database access was confirmed. Direct database connectivity should not be assumed. | Martini can persist integration state in an appropriate customer-controlled data store, but should not connect directly to Workhuman databases without explicit authorization. |
How Workhuman exposes data and business events
Workhuman REST APIs
A public, generally available Workhuman REST reference was not confirmed. Workhuman may expose tenant-specific or partner-enabled APIs for employee, recognition, reward, or related objects, subject to product and contract requirements.
Martini implementation pattern
Martini implementation pattern: once Workhuman confirms the base URL, resources, authentication, pagination, and permissions, a Martini workflow calls the required endpoints, validates responses, maps objects to a canonical model, applies business rules, and writes to downstream systems. The workflow records identifiers and processing outcomes for reconciliation.
Implementation sequence
Workhuman Webhooks or callbacks
Public documentation confirming Workhuman webhooks or outbound callbacks was not found. If enabled for a tenant, notification coverage may be limited to selected recognition, reward, employee, or redemption events.
Martini implementation pattern
Martini implementation pattern: expose or configure the receiving endpoint required by the confirmed Workhuman callback design, validate the event token or signature if documented, and trigger a workflow that retrieves the full object when the notification contains only an identifier. Martini then deduplicates and routes the event.
Implementation sequence
Scheduled Workhuman exports
Workhuman may provide scheduled extracts or tenant-specific file-based exchanges, but a public official file specification was not confirmed. This option should be designed only after Workhuman confirms format, cadence, and delivery method.
Martini implementation pattern
Martini implementation pattern: schedule a workflow to retrieve or receive the confirmed export, parse the agreed file or payload format, validate rows, map Employees or activity objects, and write accepted data to target systems. Rejected rows and source file identifiers are retained for reconciliation.
Implementation sequence
Common Workhuman integration patterns
Pattern 1: Synchronize employees from an HR system
When to use this pattern
Use this pattern when Workhuman needs employee, manager, organizational, or employment-status data from an HR platform. The exact Workhuman provisioning API or import mechanism must be confirmed before implementation.
Integration direction
Example Mapping
| Workhuman Field | Canonical Field | Target Field |
|---|---|---|
| workerId | employee.externalId | Workhuman Employee identifier |
| workEmail | employee.email | Workhuman Employee email |
| managerId | employee.managerExternalId | Workhuman Employee manager |
| employmentStatus | employee.status | Workhuman Employee status |
Martini implementation pattern
A scheduled Martini workflow retrieves changed employees, validates required identifiers and manager relationships, normalizes organizational values, and submits create or update operations through the confirmed Workhuman interface. Stable identifiers prevent duplicates; transient failures are retried and rejected rows are retained for review.
Martini capabilities used
- workflows
- API consumption
- scheduling
- data mapping
- business rules
- error handling
Pattern 2: Reconcile rewards and redemptions
When to use this pattern
Use this conditional pattern when Workhuman exposes Rewards or Redemptions and finance, payroll, or benefits systems require a controlled transaction feed.
Integration direction
Example Mapping
| Workhuman Field | Canonical Field | Target Field |
|---|---|---|
| employeeId | employee.externalId | Employee identifier |
| rewardId | incentive.transactionId | External transaction ID |
| amount | incentive.amount | Approved amount |
| redemptionStatus | incentive.status | Posting status |
Martini implementation pattern
Martini retrieves records incrementally when a modified timestamp or cursor is available, maps employee and transaction identifiers, checks program and approval rules, and sends approved transactions to the target system. An idempotency key and persisted processing status prevent duplicate financial posting; temporary failures can be retried safely.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- idempotency
- error handling
Pattern 3: Route recognition notifications
When to use this pattern
Use this pattern only when Workhuman enables outbound callbacks or another supported event mechanism for the required recognition or reward events.
Integration direction
Example Mapping
| Workhuman Field | Canonical Field | Target Field |
|---|---|---|
| recognitionId | recognition.id | Notification correlation ID |
| recipientEmployee | recognition.recipient | Message recipient |
| recognitionType | recognition.category | Message category |
| recognitionUrl | recognition.link | Message link |
Martini implementation pattern
Martini receives the confirmed notification, validates its security material, checks for duplicate delivery, and retrieves the current recognition object when necessary. It applies privacy, channel, and employee-status rules before sending a formatted message to the collaboration platform, while retaining failed deliveries for retry.
Martini capabilities used
- workflows
- webhook consumption
- data mapping
- business rules
- error handling
Pattern 4: Consolidate recognition activity for reporting
When to use this pattern
Use this pattern when Workhuman provides an API or scheduled export for Recognition and the organization needs reporting across departments, regions, or employee populations.
Integration direction
Example Mapping
| Workhuman Field | Canonical Field | Target Field |
|---|---|---|
| recognitionId | recognition.externalId | Recognition event key |
| giverEmployeeId | recognition.giverId | Giver employee key |
| recipientEmployeeId | recognition.recipientId | Recipient employee key |
| createdAt | recognition.createdAt | Event timestamp |
Martini implementation pattern
A scheduled Martini workflow retrieves or receives activity, converts the confirmed Workhuman format into a reporting model, enriches it with employee or organizational data where permitted, and loads the warehouse. The workflow uses checkpoints, duplicate detection, validation, and a rejected-record path to support repeatable reconciliation.
Martini capabilities used
- workflows
- scheduling
- API or file consumption
- data mapping
- data transformation
- error handling
Applications commonly integrated with Workhuman
Workhuman commonly sits alongside HR, identity, collaboration, and financial systems. The integration method and supported direction must be verified with Workhuman for the customer’s tenant, product edition, and permissions.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Workday | Synchronize worker profiles, employment status, organizational hierarchy, and manager relationships used for recognition eligibility. | Workday → Martini → Workhuman | Use a scheduled Martini workflow to retrieve approved worker changes, validate identifiers and status values, map the data to the Workhuman employee model, and retry or quarantine rejected changes. Any Workhuman API or import mechanism must be confirmed. |
| SAP SuccessFactors | Keep employee and organizational data aligned with the population eligible for Workhuman programs. | SAP SuccessFactors → Martini → Workhuman | Retrieve incremental employee changes when supported, transform department, location, manager, and employment-status fields, apply eligibility rules, and submit the result through the Workhuman interface made available to the customer. |
| Oracle HCM Cloud | Provision employee and organizational attributes used to administer recognition programs. | Oracle HCM Cloud → Martini → Workhuman | Orchestrate a scheduled synchronization, validate required employee fields, use stable identifiers for upserts, and persist processing outcomes for reconciliation. Workhuman API or file support remains subject to confirmation. |
| ADP Workforce Now | Synchronize workforce status and attributes and potentially support downstream reward-related reporting. | ADP Workforce Now → Martini → Workhuman | Retrieve approved workforce changes, map them into a canonical employee structure, apply deactivation and duplicate-prevention rules, and deliver them through a confirmed Workhuman API or export/import process. |
| UKG Pro | Transfer employee, manager, location, and organizational data used to administer recognition programs. | UKG Pro → Martini → Workhuman | Schedule extraction from UKG Pro, normalize organizational values, validate manager relationships, and process Workhuman updates with retry and exception handling when a supported Workhuman interface is available. |
| Microsoft Entra ID | Support identity lifecycle, authentication, and access management for Workhuman users where Workhuman enables compatible identity integration. | Microsoft Entra ID → Martini → Workhuman | Use Martini to orchestrate approved identity or provisioning exchanges, protect credentials and tokens, and apply group or status rules. Workhuman protocol and provisioning support must be verified. |
| Microsoft Teams | Surface recognition notifications or links to recognition activity in collaboration workflows if Workhuman exposes suitable events or exports. | Workhuman → Martini → Microsoft Teams | Receive a confirmed Workhuman callback or retrieve recognition activity on a schedule, validate and deduplicate the event, then format and send a controlled Teams notification through its supported interface. |
| Slack | Deliver recognition notifications or employee-experience updates to collaboration channels if Workhuman event support is enabled. | Workhuman → Martini → Slack | Use a conditional event or scheduled workflow to retrieve eligible recognition activity, apply privacy and routing rules, and publish a formatted Slack message while recording delivery status. |
How to build a Workhuman integration in Martini
Objective
Establish which Workhuman integration mechanism is available for the tenant, product, and contract before designing the workflow.
Instructions in Martini
- Confirm API, callback, export, or import availability with Workhuman
- Request base URLs, resource coverage, sandbox access, permissions, rate limits, and data-retention requirements
- Confirm authentication, scopes, service accounts, certificates, or other required credentials
Objective
Configure confirmed Workhuman credentials without embedding secrets in workflow definitions or logs.
Instructions in Martini
- Store confirmed credentials in Martini secrets or environment configuration
- Configure the authentication method documented by Workhuman
- Restrict access according to least-privilege roles and tenant permissions
Objective
Select a trigger that matches the confirmed Workhuman capability and synchronization requirement.
Instructions in Martini
- Use a scheduled workflow for confirmed APIs or exports
- Use a callback or webhook trigger only when Workhuman enables the required events
- Define the initial load, incremental window, and checkpoint strategy
Objective
Receive or retrieve Workhuman data using the documented interface and preserve enough context for reconciliation.
Instructions in Martini
- Call confirmed endpoints or retrieve the agreed export
- Handle pagination, cursors, modified-date filters, and time zones as documented
- Persist source identifiers, timestamps, and processing checkpoints
Objective
Convert Workhuman payloads into a canonical model and reject incomplete or unsafe data before downstream writes.
Instructions in Martini
- Map Employees, Recognition, Rewards, Nominations, Programs, or Redemptions to target fields
- Validate required identifiers, statuses, dates, and organizational values
- Apply privacy filtering and avoid logging sensitive employee payloads unnecessarily
Objective
Enforce Workhuman-specific eligibility, approval, status, budget, privacy, and duplicate-prevention rules explicitly.
Instructions in Martini
- Check employee status and program eligibility
- Apply approval, geographic, legal, currency, or budget rules where relevant
- Use stable identifiers and idempotency keys for create or update operations
Common Workhuman data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Employees | Synchronize employee identity, status, department, location, manager, and eligibility information. | Workday, SAP SuccessFactors, Oracle HCM Cloud, ADP Workforce Now, UKG Pro, identity platforms | Martini validates stable identifiers and required fields, maps organizational attributes, applies activation or deactivation rules, and processes confirmed API or file interfaces. |
| Recognition | Exchange peer or manager recognition activity for reporting, notifications, or employee-experience workflows. | Data warehouses, Microsoft Teams, Slack, reporting services | Martini can retrieve or receive confirmed recognition data, apply privacy and routing rules, deduplicate events, and deliver normalized records downstream. |
| Rewards | Reconcile awards, points, or other recognition-related incentives with approved financial or employee-benefit processes. | Finance applications, payroll systems, data warehouses | Martini maps employee and transaction identifiers, applies approval and eligibility rules, and records processing status when the object is exposed. |
| Nominations | Process employee nominations or recognition submissions that may require review or approval. | Workflow systems, reporting platforms, employee-experience applications | Martini can validate nomination status and required fields, route approved items, and isolate rejected or incomplete data if a supported interface exists. |
| Programs | Represent configured recognition or reward programs, including eligibility, budget, and rule context. | HR systems, reporting platforms, governance stores | Martini can use confirmed program attributes to drive routing and business rules, while avoiding assumptions about resource names or field availability. |
| Redemptions | Track employee use of awarded points or rewards where exposed by the relevant Workhuman product and integration method. | Finance, payroll, employee-benefit, and analytics systems | Martini can reconcile stable transaction identifiers, prevent duplicate posting, and retain errors for controlled replay when Redemptions are available. |
Authentication and security considerations
Confirm the Workhuman access model
Workhuman-specific authentication, scopes, roles, and service-account requirements were not confirmed. Verify whether the tenant uses OAuth 2.0, API keys, certificates, SSO-related provisioning, or another method before implementation.
Protect employee data
- Store confirmed credentials in Martini secrets or secured environment configuration.
- Apply least-privilege permissions and restrict workflow access.
- Minimize collection and avoid unnecessary logging of employee or recognition payloads.
- Confirm tenant, TLS, source-IP, retention, and privacy requirements with Workhuman.
Operational considerations for Workhuman integrations
Plan for an unconfirmed interface
Confirm API or export availability, resource coverage, pagination, rate limits, incremental filters, time zones, sandbox access, and versioning before production design.
Make synchronization repeatable
- Use stable employee and transaction identifiers for idempotency.
- Persist checkpoints and processing status.
- Retry only transient failures and isolate validation or permission errors.
- Verify callback delivery guarantees, ordering, signature validation, and duplicate behavior if events are enabled.
- Test field additions, enum changes, deactivations, schema changes, and downstream outages.
Why use Martini instead of scripts or point-to-point integrations?
Coordinate conditional integration methods
Workhuman access may vary by tenant, product, contract, and partner status. Martini provides a maintainable workflow layer that can consume a confirmed API, process an approved export, or receive an enabled callback without coupling business rules directly to one script.
Separate transport from business logic
Martini centralizes mapping, validation, eligibility decisions, idempotency, retries, monitoring, and downstream delivery. It can also expose a controlled API for internal applications while preserving reusable integration assets and environment-specific security configuration.
Frequently asked questions
Workhuman integration depends on the customer’s tenant and product configuration. Possible mechanisms include tenant-specific or partner-enabled APIs, selected outbound callbacks, and scheduled exports or imports, but the availability of each mechanism must be confirmed with Workhuman. Martini can orchestrate the exchange, transform employee and recognition data, apply business rules, and deliver results to HR, finance, collaboration, or analytics systems.
Yes, conditionally. Martini can integrate with Workhuman using the native API, callback, file, or other supported interface that Workhuman makes available to the customer. A public, generally available Workhuman API and broad webhook framework were not confirmed in the supplied research, so access and object coverage should be verified before implementation.
No dedicated Workhuman connector is required. Martini can use Workhuman’s confirmed native APIs, callbacks, files, authentication methods, or other supported endpoints and orchestrate the integration through workflows, mappings, validations, and error handling.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Workhuman. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Workhuman, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.
Start by confirming whether the Workhuman tenant provides a REST API, scheduled export or import, or selected callback capability. GraphQL and SOAP support were not confirmed, and direct database access should not be assumed. Martini can consume the confirmed interface and expose a controlled API or workflow around it.
Only if Workhuman enables outbound callbacks or webhooks for the required tenant and events. Public documentation confirming broad webhook support was not found. If callbacks are available, Martini can validate notifications, deduplicate them, retrieve full objects when necessary, and route events to downstream systems.
Synchronization can be scheduled or event-driven depending on the interface Workhuman provides. Martini can retrieve or receive Employees, Recognition, Rewards, Nominations, Programs, or Redemptions, map them to a canonical model, apply eligibility and status rules, and use stable identifiers, checkpoints, and reconciliation records to prevent duplicates.
Martini maps Workhuman payloads into target application models, validates required fields, and applies explicit privacy, eligibility, approval, and idempotency rules. Workflows can distinguish authentication, validation, rate-limit, duplicate, temporary-service, and downstream failures, retry transient errors, and retain rejected records for controlled reconciliation.
Related Martini documentation
Workflows
Plan your Workhuman integration
Confirm the Workhuman tenant capabilities and let Martini orchestrate secure data synchronization, transformation, business rules, and downstream delivery.