How worker records in Workday HCM can run HubSpot's people side: giving new team members the right access on day one, keeping teams in step with the org chart, handing over records when someone moves or leaves, and, with consent, supporting talent and alumni marketing.
Workday HCM is where a company records who works there, in which team, under which manager and in which location. HubSpot is where those same people sell, market and serve customers. This integration is about the team, not the customers: it keeps HubSpot users, teams and record ownership in step with Workday.
Documentation and credentials come only through the vendor, under a license, partner agreement or customer login.
Gated API. Web service directories and the REST API reference are published to Workday customers in Workday Community. The client's Workday administrator sets up access in the tenant.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
Workday exposes worker and organization data through SOAP web services, a REST API and custom reports, so HubSpot access can follow the org chart from a team member's first day to their last.
Campaign Creators assessment
CC builds this on Workday's web services and on HubSpot's user provisioning API. A custom report the client's Workday admin builds (Report as a Service, or RaaS) exposes only the approved worker fields; the Human Resources and Staffing web services fill in organizations and changes. The integration creates HubSpot users with the right permission set and teams, moves them when they change role or territory, and hands over their records when they leave. Recruiting and alumni data can feed talent marketing, but only for people who opt in. Workday's detailed API documentation is available to customers through Workday Community, so CC confirms operations and fields against the client's tenant in discovery.
Ratings are CC judgments from Workday's public materials and HubSpot's developer documentation. Web service versions, report fields, security domains and limits are confirmed with the client's Workday admin during discovery.
Workday holds each worker's status, job profile, supervisory organization, manager and location, maintained by HR. HubSpot can trust it for access and team structure.
Compensation, national identifiers, benefits, performance and demographic fields never leave Workday. The custom report exposes only the approved fields, and the integration user cannot see the rest.
The client's HR, IT security and privacy owners approve the field list, the access rules and the offboarding steps before any build starts. Talent marketing needs its own consent review.
Seven parts of Workday matter to HubSpot. Four carry the core sync, two support optional programs that need consent, and one stays inside Workday.
Worker records, organizations, job profiles and locations, read through Workday's SOAP web services with response groups that limit what is returned.
A custom report the client's Workday admin builds and enables as a web service. It returns only the columns and workers the report defines, in JSON or XML.
Workday's REST API, called through an API client registered in the tenant. Used where it covers a resource the sync needs; coverage is confirmed against the client's tenant.
HubSpot's user provisioning API creates users with an email, name, permission set (role), primary team and additional teams, updates them, and removes them.
When someone moves territory or leaves, their contacts, companies, deals and tickets are reassigned by agreed rules before their HubSpot access ends.
Candidates who opt in to a talent community can become HubSpot contacts for employer-brand and job-alert emails. Off by default, and only with consent.
Compensation, benefits, national identifiers, performance reviews, leave and demographic data stay in Workday. The integration user has no access to these domains.
A CC integration layer pulls the approved worker report and organization data from Workday on a schedule, compares it with the HubSpot users and teams it manages, and applies the differences: new users, team and role changes, record handovers and removals. Optional talent and alumni contacts flow only with recorded consent.
Who works here, in which team and under which manager comes from Workday. HubSpot admins stop creating sales users by hand.
The integration reads only the approved report fields through a read-only integration user. Pay, benefits, IDs and performance data never leave Workday.
Records are reassigned before a user's access ends, so no customer is left without an owner and no deal goes dark.
Each phase ends on a gate the client signs off before the next begins. The roster runs in report-only mode first, so HubSpot admins see every change before the integration makes it.
Confirm which teams use HubSpot, how they map to Workday supervisory organizations and job profiles, and who owns HR, IT security and privacy decisions.
Agree the exact worker fields HubSpot may receive and document why each is needed. HR and privacy approve; anything not on the list stays in Workday.
The client's Workday admin creates the Integration System User, an integration security group with Get access to only the needed domains, the RaaS report and, if used, an API client.
Create permission sets and teams in HubSpot, the Team Member custom object, and the mapping tables: job profile to role, organization to team, and the handover rule for each team.
Build the scheduled intake, change detector, provisioning calls, record handover, audit log and failure alerts. Terminations run on a shorter schedule than other changes.
Run against production data for two weeks with writes switched off. The integration lists the users it would create, move and remove, and HubSpot admins check each one.
Switch on writes, starting with offboarding. Add talent community and alumni contacts only after their consent review.
Workday field names below describe worker data as Workday presents it. Exact element paths depend on the client's web service version and custom report, and are confirmed in discovery. HubSpot user fields follow HubSpot's user provisioning API.
| Workday field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Worker → HubSpot user | ||||
| Work email address | User | WD → HS | Match key. Required by HubSpot's provisioning API. | |
| Preferred name (legal name if blank) | firstName, lastName | User | WD → HS | |
| Employee ID | wd_employee_id | Team Member | WD → HS | Workday key. Unique. |
| Worker status, hire date | User created on the start date | User | WD → HS | Only for workers in agreed organizations or job profiles. |
| Job profile | roleId (permission set) | User | WD → HS | Mapping table. Roles exist in HubSpot first. |
| Supervisory organization | primaryTeamId | User | WD → HS | Mapping table: organization to HubSpot team. |
| Additional organizations or region | secondaryTeamIds | User | WD → HS | Replaced as a set on each update. |
| HubSpot user | wd_hubspot_user | Team Member | WD → HS | Links the roster record to the HubSpot user. |
| Organization & territory | ||||
| Business title | wd_business_title | Team Member | WD → HS | |
| Supervisory organization name | wd_supervisory_org | Team Member | WD → HS | For reporting by Workday organization. |
| Manager | wd_manager_email | Team Member | WD → HS | Used for handover rules and manager views. |
| Location | wd_location | Team Member | WD → HS | Feeds territory rules where territory follows location. |
| Cost center | wd_cost_center | Team Member | WD → HS | Optional. Confirm need in the privacy review. |
| Job or organization change | Handover task | Task | WD → HS | Sales operations reviews before records move, unless an automatic rule is agreed. |
| Offboarding | ||||
| Worker status, termination date | wd_worker_status | Team Member | WD → HS | Active or Terminated. Termination dates only, no reasons. |
| Termination | hubspot_owner_id on owned records | Contact, Company, Deal, Ticket | WD → HS | Reassigned to manager, successor or a queue by signed rule. |
| Termination | User removed | User | WD → HS | Provisioning API removes the user after handover; or queued for an admin to deactivate. |
| Termination | Open tasks reassigned | Task | WD → HS | Handling of active sequences confirmed in discovery. |
| HubSpot user ID | Workday worker identifier | User | HS → WD | Optional write-back where the client allows. Confirm the web service operation in discovery. |
| Talent & alumni contacts · opt-in only | ||||
| Candidate email (opted in) | Contact | WD → HS | Only candidates who joined the talent community. | |
| Candidate name | firstname, lastname | Contact | WD → HS | |
| Job family of interest | wd_job_family_interest | Contact | WD → HS | For job-alert segmentation. |
| Talent community consent | wd_talent_opt_in, subscription type | Contact | WD → HS | No consent, no sync. |
| Departing worker who joins the alumni program | wd_alumni_status | Contact | WD → HS | Personal email given at exit, with consent. |
Workday access is set up by the client's Workday security admin. Workday shares detailed API documentation with customers through Workday Community; values not published are marked for confirmation.
| Topic | Workday | HubSpot |
|---|---|---|
| Access model | Set up in the client's tenant by its Workday admin. Web service directories and the REST API reference are documented for customers in Workday Community; CC works from them with the client. | Self-serve in the client portal. Custom objects need an Enterprise hub. |
| Interfaces | SOAP web services (Human Resources, Staffing, Recruiting), the Workday REST API, and RaaS custom reports returned as JSON or XML. | User provisioning API (users, roles, teams), CRM APIs for records and owners, custom objects. |
| Authentication | An Integration System User (ISU) in an integration security group, with Get access to only the domains the sync needs. The REST API uses an OAuth 2.0 API client registered in the tenant. | Private app access token with the user provisioning scopes (crm.objects.users.write or settings.users.write) and CRM scopes. Paid seats need the billing write scope. |
| Rate limits | Not published. Confirm with Workday and the client's admin. | Per-10-second burst and daily limits by subscription tier. |
| Change detection | Scheduled report pulls filtered by effective or entry date; web service requests can be scoped by an as-of entry date and time. Terminations run more often than other changes. | Changes written through the provisioning and CRM APIs, each one logged. |
| Sensitive data | Pay, benefits, national IDs, performance, leave and demographics are excluded from the report and from the ISU's domains. | Field-level permissions by team; sensitive data properties available on Enterprise. |
| Environments | Build and test against a Workday sandbox tenant and a HubSpot sandbox. Confirm sandbox refresh timing with the client. | HubSpot sandbox for build and testing; production portal at launch. |
Severity reflects impact on the SOW, not technical difficulty alone.
HR and privacy approve every field before the build. In some countries, using employee data this way also needs a works council or data-protection review. Make this a client-owned dependency in the SOW.
A departed team member with HubSpot access is a security risk. Terminations run on a short schedule, failures alert IT, and HubSpot's API removes the user. If the client prefers to keep the profile, deactivation is queued for an admin, since the provisioning API documents removal, not deactivation.
Assigning a permission set with a paid seat needs the billing write scope and adds cost. The client decides whether the integration assigns seats or an admin approves each one.
Job profiles and organizations do not match HubSpot roles and teams one to one. Sales operations owns the mapping tables, and unmapped workers are flagged, not guessed.
Candidate data carries legal duties. Talent marketing is off by default, opt-in only, and application status and hiring decisions never reach HubSpot.
Workday's detailed API documentation sits behind customer access. Budget a short discovery spike with the client's admin to confirm web service versions, report fields and limits.
New sellers, marketers and service staff get the right HubSpot role and teams on their start date, without a ticket to the HubSpot admin.
When someone leaves, their records move to the right owner and their access ends, with a log for IT and sales operations.
HubSpot teams follow Workday organizations, so reports by team, forecasts and permissions stay accurate as people move.
A move between regions opens a handover task with the affected records listed, so nothing is reassigned by surprise.
Opted-in candidates receive job alerts and employer-brand emails from HubSpot, segmented by job family.
Former team members who opt in stay in touch through HubSpot, a source of referrals, rehires and future customers.
Every phase reuses the same worker report and mapping tables, so the integration can go live one change type at a time, starting with the one that reduces risk most.
All custom properties use the wd_ prefix in a Workday property group. Roster fields live on a Team Member custom object linked to the HubSpot user, so no HR data sits on customer records.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| wd_employee_id | Workday Employee ID | Team Member | Single-line text | Workday employee ID; unique |
| wd_hubspot_user | HubSpot User | Team Member | HubSpot user | Linked HubSpot user |
| wd_business_title | Business Title | Team Member | Single-line text | Workday business title |
| wd_supervisory_org | Supervisory Organization | Team Member | Dropdown | Workday organization name |
| wd_manager_email | Manager Email | Team Member | Single-line text | Manager's work email |
| wd_location | Location | Team Member | Dropdown | Workday location |
| wd_cost_center | Cost Center | Team Member | Dropdown | Optional; per privacy review |
| wd_worker_status | Worker Status | Team Member | Dropdown | Active or Terminated |
| wd_termination_date | Termination Date | Team Member | Date picker | Effective date only, no reason |
| wd_talent_opt_in | Talent Community Opt-In | Contact | Single checkbox | Recorded consent |
| wd_job_family_interest | Job Family of Interest | Contact | Multiple checkboxes | Candidate's stated interest |
| wd_alumni_status | Alumni Status | Contact | Dropdown | Opted-in former team member |
Choose the modules and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.
Based on public documentation. Workday's detailed API documentation is available to customers; items marked for confirmation are checked with the client's Workday admin during discovery.
Yes, through a custom build. Workday exposes worker and organization data through SOAP web services, a REST API and custom reports (Report as a Service), and Campaign Creators connects these to HubSpot's user provisioning API. The integration is about the team, not the customers: it keeps HubSpot users, teams and record ownership in step with Workday.
Approved worker fields flow from Workday to HubSpot: work email, preferred name, job profile (mapped to a HubSpot permission set), supervisory organization (mapped to a HubSpot team), manager, location and worker status. Roster details sit on a Team Member custom object, and opted-in talent community candidates and alumni can become HubSpot contacts. Compensation, benefits, national identifiers, performance and demographic data stay in Workday.
Workday is the source of truth for people: who works there, in which team, under which manager and in which location. HubSpot owns users' customer records, which are reassigned by agreed rules before a departing user's access ends. The only optional write-back is the HubSpot user ID to Workday, where the client allows it.
Seven phases, each closed by a client sign-off: discovery and stakeholders, field list and privacy review, Workday access (an Integration System User, a security group and the custom report), HubSpot model and mapping rules, build, a two-week report-only run, and launch. Offboarding is switched on first, and talent and alumni contacts are added only after their consent review.
Timeline and cost depend on the teams, worker fields and optional programs in scope (for example paid seat assignment, talent community and alumni contacts). Campaign Creators confirms these in discovery with the client's Workday admin and provides a fixed scope before the build starts.