Quick Answer
Pinnacle Series does not provide a prebuilt Workday connector, but organizations can build their own integration between Workday and Pinnacle Series using the Pinnacle Series APIs, single sign-on (SSO) and identity provider provisioning, at one of three levels: Level A (Reporting only), Level B (Reporting + content discovery) or Level C (Full orchestration).
What This Article Helps With
This article explains how an organization that runs Workday can plan and build its own integration between Workday and Pinnacle Series. It covers the three integration levels, the five implementation phases, the Workday attributes to map, how Pinnacle Series completions reach Workday, and the decisions to make before a scoping session. It is relevant to Workday administrators, IT and identity teams, L&D, HR, BI and compliance teams.
Building a Workday Integration with Pinnacle Series
Pinnacle Series does not include a Workday connector or a plug-and-play integration. An integration between Workday and Pinnacle Series is designed, built and maintained by your organization, or by an integration partner you choose, using these building blocks:
- Pinnacle Series APIs: the v3 Reporting API, the v2 API and the Legacy API (v1), with API credentials issued by Eagle Point Support.
- Single sign-on: SAML or OIDC from Workday to Pinnacle Series.
- User provisioning: through the native Pinnacle Series Microsoft Entra ID sync, when Workday provisions users into Entra ID, or through a scheduled flat file.
- Workday and middleware tools: such as the Workday REST API, Workday Studio, EIB and integration middleware.
The native integrations Pinnacle Series does include are Microsoft Entra ID sync and KnowledgeSmart. The Pinnacle Series team can support scoping of a Workday integration.
Workday and Pinnacle Series Integration Levels
The Workday integration levels are a progression: each level includes everything in the level before it.
- Level A: Reporting only. Pinnacle Series completions flow into the Workday learning record, so Workday reports and BI dashboards become complete. Employees still find and launch training as before. Level A needs the Foundation phase, Phase 2 and Phase 3.
- Level B: Reporting + content discovery. Level A, plus Pinnacle Series content is added as tiles or tasks in Workday Learning and launched with SSO, so employees do not sign in twice. Level B needs the Foundation phase and Phases 1, 2 and 3.
- Level C: Full orchestration. Level B, plus the integration uses Workday events such as new hire, role change, transfer or project assignment to create Pinnacle Series Assignments automatically. Level C is the most complex level and needs stable Level A and Level B integrations first. Level C needs the Foundation phase and Phases 1 to 4.
We recommend setting Level B as the initial delivery target and Level C as the long-term destination. Level C delivers the most value where people change roles, locations or projects often.
Workday Integration Implementation Phases
A Workday integration with Pinnacle Series is typically built in five phases. Phases 1 and 2 can run in parallel once the Foundation phase is confirmed, Phase 3 follows Phase 2, and Phase 4 comes last.
- Foundation: prerequisites (all levels). Users are provisioned from Workday to Pinnacle Series through an identity provider with no manual steps, the agreed Workday attributes drive the right Pinnacle Series Groups, leavers are deprovisioned automatically, and SSO (SAML or OIDC) works from Workday to Pinnacle Series. The Foundation phase also needs a provisioning path for people who are not in Workday, such as contractors and agency staff.
- Phase 1: content discovery (Levels B and C). Workday administrators add Pinnacle Series content, such as technical training Courses, skills assessments and CPD modules, as tiles or tasks in Workday Learning, and SSO signs learners in to Pinnacle Series when they launch it. Delivery and results stay in Pinnacle Series. Course descriptions and thumbnails for the tiles come from the Pinnacle Series Legacy API (v1), combined with the v3 Reporting API for other content data.
- Phase 2: completion writeback (all levels). The integration writes Pinnacle Series completions to Workday, so Workday becomes the single system of record for training completions.
- Phase 3: reporting layer (all levels). Pinnacle Series completions held in Workday reach existing data lakes and BI dashboards through the existing Workday pipeline, without rebuilding dashboards. Alternatively, a BI tool can connect directly to the Pinnacle Series v3 Reporting API.
- Phase 4: assignment orchestration (Level C). The integration uses Workday events to create Pinnacle Series Assignments automatically. Pinnacle Series Assignments can be created programmatically through the Pinnacle Series v2 API. Confirm how Workday workers and training map to Pinnacle Series users and content with the Pinnacle Series team before designing triggers.
How Pinnacle Series Completions Reach Workday
In Phase 2, the integration retrieves completion data from Pinnacle Series through the Pinnacle Series APIs and writes the data to Workday using the Workday REST API or a Workday Studio integration. The Pinnacle Series v3 Reporting API provides Course enrollment data and assessment assignment data, including completion progress and scores. Assessment scores and outcomes come from KnowledgeSmart, the assessment system integrated with Pinnacle Series.
The integration authenticates with a dedicated Pinnacle Series account that is excluded from SSO, using API credentials issued by Eagle Point Support. To retrieve completions for the whole organization, the account needs the Reporting Administrator permission; a Reporting Manager sees only the Groups they own or manage.
The completion fields typically written to Workday are listed below. Confirm the availability of each field against the Reporting API data dictionary during scoping.
- Worker ID: matches the completion to the Workday worker.
- Course or assessment ID: must map to a Workday learning content record.
- Completion date: the date the learner completed or passed.
- Score: the assessment score, where applicable.
- Pass or fail: the outcome status.
- CPD credit hours: where tracked; confirm that a matching Workday field exists before the build.
Integration middleware such as Boomi, MuleSoft or Azure Integration Services can carry the writeback. Without middleware, completion writeback is usually the largest build in a Workday integration project. Check data residency rules for any region where completion data passes through middleware.
Workday Attributes to Map to Pinnacle Series
Workday attributes flow to Pinnacle Series through an identity provider, such as Microsoft Entra ID, or through a scheduled flat file where identity provider provisioning is not yet in place. With a flat file, leavers can keep access to Pinnacle Series until the next file is processed. Send only the work-related attributes that Pinnacle Series needs:
- Required for all levels: Worker ID (Workday employee ID), first name, last name, work email, and employment status or termination. Work email is the sign-in identifier and SSO match, and must never be a personal address.
- Recommended for all levels: business line or division, region or country or location, job profile or job title, and cost center. These attributes drive Pinnacle Series Group membership, content visibility, role-based Learning Paths and reporting.
- Optional: worker type (employee or contractor) and manager.
- Level C only: hire date, which drives new-hire Assignment triggers.
Do not send home addresses, personal email addresses or phone numbers, dates of birth, or other personal data that Pinnacle Series does not use.
Workday Integration Scoping Decisions
Five decisions shape the scope of a Workday integration with Pinnacle Series. Reaching these decisions before the first scoping session moves the session from exploring to deciding:
- Which integration level is the target: Level A, Level B or Level C?
- Is provisioning from Workday through the identity provider reliable for all regions and worker types, or is a Foundation clean-up needed first?
- Is Workday the required system of record for training completions, including compliance, safety and CPD? If so, Phase 2 is mandatory.
- Is integration middleware available to carry completion writeback?
- Which Workday events should trigger training, and can those events be exposed through the Workday API or EIB?
Workday administrators and IT architecture are the two roles most needed in a scoping session.
Helpful Tips
- Identify populations that are not in Workday, such as contractors, agency staff and joint-venture staff, during the Foundation phase. Discovering these populations mid-project delays go-live.
- Phase 1 does not write completions to Workday. If managers need Pinnacle Series results in the same Workday view as other completions, include Phase 2 in the Phase 1 definition of done.
- For Phase 4, automate the highest-volume Workday event first, which is usually new hire, and expand from there.
- Pinnacle Series anonymizes some data automatically on a schedule. If you assess people who are not employees, such as job candidates, and need their results kept for a set period, agree the retention period with the Pinnacle Series team during scoping.
Common Questions
Does Pinnacle Series have a Workday connector?
No. Pinnacle Series does not provide a prebuilt Workday connector or a plug-and-play integration. Organizations build their own integration between Workday and Pinnacle Series using the Pinnacle Series APIs, SSO, the native Pinnacle Series Microsoft Entra ID sync and their own Workday tools and middleware.
Does integrating Workday with Pinnacle Series replace Workday Learning?
No. Existing Workday Learning content stays in place. Pinnacle Series content is added alongside Workday Learning content, and Pinnacle Series completions are written to the Workday learning record.
Which integration level should we start with?
We recommend targeting Level B (Reporting + content discovery) first, which gives employees one place to start their learning and gives Workday a complete completion record. Level C (Full orchestration) can be phased in once Level A and Level B are stable.
How are Workday workers matched to Pinnacle Series users?
The Workday Worker ID is the key for matching people, completions and Assignments across Workday and Pinnacle Series, and work email is the sign-in identifier and SSO match. How the Workday Worker ID is held in Pinnacle Series is agreed with the Pinnacle Series team during scoping.