How Workday customers, customer contracts, invoices, payments and projects can reach HubSpot, and how won HubSpot deals can start Workday customer contracts, using Workday's web services, REST APIs and Report-as-a-Service.
Workday Financial Management runs contracts, billing, receivables and the books, most often for services businesses. HubSpot runs the customer relationship and the sales pipeline. The integration lets each system do its job and puts the contract and billing facts sales needs on the HubSpot record.
Documentation and credentials come only through the vendor, under a license, partner agreement or customer login.
Gated API. Detailed API documentation is published to Workday customers in Workday Community. The client's Workday administrator creates the integration system user and grants each operation.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
Workday exposes customers, contracts, invoices and payments through its web services and reports, so HubSpot can see the full contract-to-cash picture while Workday stays the system of record for finance.
Campaign Creators assessment
Workday offers SOAP web services grouped by functional area (Revenue Management and Financial Management cover customers, contracts, invoices and payments), REST APIs, and Report-as-a-Service, which turns any custom report into a web service that returns JSON, CSV or XML. HubSpot does not publish its own Workday app, so this is a custom build on those interfaces. Two things set the pace: access is set up inside the client's tenant (an integration system user, a security group and permissions for each operation and report), and Workday's detailed API documentation is available to customers through Workday Community, so CC confirms operations and fields with the client's Workday team. The design centers on customer contracts and billing schedules rather than product orders.
Ratings are CC judgments from Workday's public documentation. Operations, report fields, security and limits are confirmed in the client's tenant during discovery.
With Report-as-a-Service, the client's Workday team builds a custom report and enables it as a web service. HubSpot then receives exactly the figures finance already reports, such as open balance and billed revenue.
Revenue flows through customer contracts with typed lines (Subscription, Fixed Fee Project, Project Time and Expense, Usage Based and others) and billing schedules. How a HubSpot deal becomes a contract is the core design decision.
Workday assigns no default security groups to web service operations. The client's administrator creates the integration system user and grants each operation and report before any build.
Seven Workday surfaces matter to HubSpot. Four carry the integration, two support it, and one is a scope decision the client makes early.
The customer profile holds contacts, addresses, contracts, invoices, payments and write-offs. Customers can be grouped, placed in hierarchies and used as worktags.
The sales agreement: lines, dates, payment terms and milestones. Workday calculates billing and revenue recognition from it.
Invoices created from billing schedules, projects or directly, with company, customer, currency, due date and lines with sales items and worktags.
Payments, deposits and write-offs recorded on the customer profile. They give HubSpot the open balance and payment history for each account.
For clients that bill from Workday projects, project status and billing progress give account teams the delivery view.
Custom reports exposed as web services, read over REST or SOAP. Report prompts are passed as URL parameters.
Every contract and invoice belongs to a company and carries worktags such as cost center, region, project, sales item and revenue category. The client decides which ones HubSpot needs.
HubSpot never calls Workday directly. A CC-built integration layer reads Workday web services and reports, matches records to HubSpot, writes in batches, and sends won deals back as draft customer contracts for finance to complete.
HubSpot owns prospects, contacts, deals and quotes. Workday owns customers once created, contracts after submission, billing, receivables and revenue.
Won deals arrive in Workday as draft contracts. Finance sets billing and revenue schedules and approves them through the Customer Contract Event.
Each HubSpot deal creates at most one Workday contract. The contract reference is stored on the deal, and any failure goes to a queue a person can replay.
Each phase ends on a gate the client signs off before the next begins. Customers and reporting go live first, then contract write-back.
Confirm how the client sells (subscriptions, fixed-fee projects, time and expense), which companies are in scope, and which system owns each record type. Decide how new Workday customers are created.
The client's Workday administrator creates the integration system user and security group, grants each web service operation and report, and registers an API client if REST is used.
Agree the custom reports Workday will expose through RaaS, how customers match HubSpot companies, and which worktags each contract needs.
Create the properties, product library settings, invoice pipeline, association labels and property groups in a HubSpot sandbox.
Build customer and sales item sync, then invoice and payment reads, then contract write-back. Test against the Workday sandbox tenant, never production.
Load customers, sales items and an agreed history of contracts, invoices and payments, then compute rollups once.
Run contract write-back alongside the current handoff for two weeks, then switch on.
Workday's field-level documentation is available to customers, so most source fields are described rather than quoted. Exact element names come from the client's web service version and report definitions during discovery.
| Workday field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Customers | ||||
| Customer ID | wd_customer_id | Company | WD → HS | Primary match key. Confirm the reference ID type in discovery. |
| Customer name | name | Company | ↔ Both | Workday name wins once the customer exists in Workday. |
| Addresses (primary and shipping) | address, city, zip, country | Company | WD → HS | Primary address on the company. |
| Customer category | wd_customer_category | Company | WD → HS | One per customer. |
| Customer groups | wd_customer_groups | Company | WD → HS | A customer can belong to several groups. |
| Parent customer (hierarchy) | Parent company association | Company | WD → HS | Mirrors the Workday customer hierarchy. |
| Bill-to contacts | email, firstname, lastname | Contact | ↔ Both | Contacts match on email. HubSpot keeps the contacts it creates. |
| Sales items | ||||
| Sales item | hs_sku, name | Product | WD → HS | Workday sales item ID as SKU. Unique. |
| Revenue category | wd_revenue_category | Product | WD → HS | For reporting and contract lines. |
| Default price | price | Product | WD → HS | Where the client sets one. Confirm in discovery. |
| Deals → customer contracts | ||||
| Customer | wd_customer_id (company) | Deal | HS → WD | Taken from the associated company. |
| Company | wd_company | Deal | HS → WD | Default per pipeline, overridable by the rep. |
| Contract type | wd_contract_type | Deal | HS → WD | From the client's contract types. |
| Contract lines (sales item, line type, amount) | hs_sku, quantity, amount | Line item | HS → WD | One contract line per HubSpot line item. Line type set per product. |
| Contract start and end dates | wd_contract_start, wd_contract_end | Deal | HS → WD | Drives billing and renewal dates. |
| Worktags (cost center, region, project) | Deal properties | Deal | HS → WD | Required worktags default from the pipeline. |
| Customer PO number | wd_customer_po | Deal | HS → WD | Captured in HubSpot. |
| Customer contract reference | wd_contract_id | Deal | WD → HS | Written back after Workday accepts the draft. |
| Contract status | wd_contract_status | Deal | WD → HS | Draft, in approval or approved, as Workday reports it. |
| Invoices & payments | ||||
| Invoice number, invoice date, due date | Invoice record | Invoice | WD → HS | Read-only copy of the Workday invoice. |
| Invoice amount and currency | Invoice amount | Invoice | WD → HS | In the invoice currency. |
| Invoice status | wd_invoice_status | Invoice | WD → HS | Status as Workday reports it. |
| Contract on invoice line | Deal association | Invoice | WD → HS | Links each invoice to the deal that started the contract. |
| Payments received | wd_last_payment_date | Company | WD → HS | From a RaaS report or payment web service. |
| Open balance | wd_open_ar | Company | WD → HS | From a RaaS report, so it matches finance. |
| Billed revenue | wd_billed_ytd | Company | WD → HS | Sum of invoice amounts in the fiscal year. |
| Projects | ||||
| Project | wd_project_id | Deal | WD → HS | For contracts billed from Workday projects. |
| Project status | wd_project_status | Deal | WD → HS | Delivery view for the account team. |
Workday access is set up inside the client's tenant. Values Workday does not publish are marked for confirmation.
| Topic | Workday | HubSpot |
|---|---|---|
| Access model | An integration system user (ISU) and an integration security group, with permission for each web service operation and report. Workday assigns no default security groups to operations. Set up by the client's Workday administrator. | Self-serve in the client portal. Custom objects need an Enterprise hub; invoices are a standard object. |
| Interfaces | Workday Web Services (SOAP, versioned, grouped by functional area such as Revenue Management and Financial Management), Workday REST APIs, and Report-as-a-Service over REST or SOAP. | REST APIs: CRM objects, associations, products, line items, invoices, webhooks. |
| Authentication | ISU credentials for web services and RaaS. OAuth 2.0 through an API client registered in the tenant for REST. Confirm the client's standard in discovery. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Documentation | Workday publishes a SOAP API reference. Operation-level guides and the REST API directory are available to customers through Workday Community; CC works from the client's access. | Public developer documentation. |
| Change detection | RaaS reports with a last-updated prompt, and web service Get operations with request criteria. Confirm the approach per object. | Webhooks on deal stage change trigger contract write-back. |
| Rate limits | Not published. Confirm with Workday. | Per-10-second burst and daily limits by subscription tier. |
| Environments | Write-back is built and tested in the client's Workday sandbox tenant first. | HubSpot sandbox for build and test. |
Severity reflects impact on the SOW, not technical difficulty alone.
Each contract line type bills and recognizes revenue differently. Agree which HubSpot products map to which line types, and what finance completes in Workday, before mapping starts.
Every operation and report needs explicit permission for the integration user. Make tenant setup a client-owned dependency in the SOW, with the Workday administrator named.
A contract needs a Workday customer. The client decides whether the integration creates basic customers or routes a request through the Customer Request business process.
Field-level API detail sits behind Workday Community. Budget a short discovery spike with the client's Workday team to confirm operations, versions and report fields.
Contracts and invoices need the company and the worktags the client's setup requires. Missing worktags stop a draft from saving, so defaults are set per pipeline.
Approved contracts cannot be amended through web services. Upsells start a new HubSpot deal, and finance amends the contract in Workday; HubSpot reads the result.
Reps stop re-keying agreements. Finance receives a draft contract with the customer, lines, dates and worktags already filled in.
Contract end dates create HubSpot renewal deals ahead of time, so account managers start the conversation early.
Open balance, overdue invoices and last payment sit on the company record, so sales and service see the whole relationship before they call.
Overdue invoices create tasks for the account owner, so the customer hears from someone they know.
Project status and billed-to-date show on the deal, so account teams see delivery progress without a Workday login.
Pipeline and billed revenue meet in HubSpot dashboards, split by company and the worktags finance uses.
HubSpot runs the pipeline up to the signed deal. Workday runs contracts, billing and receivables from there. The integration hands over at close and reports back at every step after.
All custom properties use the wd_ prefix in a Workday property group. Rollups are calculated in the integration layer or come from Workday reports, so every report agrees.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| wd_customer_id | Workday Customer ID | Company | Single-line text | Customer reference ID; unique |
| wd_customer_category | Workday Customer Category | Company | Dropdown | Customer category |
| wd_open_ar | Open Receivables | Company | Number (currency) | Open balance from a RaaS report |
| wd_billed_ytd | Billed This Fiscal Year | Company | Number (currency) | Sum of invoice amounts in the fiscal year |
| wd_last_payment_date | Last Payment Received | Company | Date picker | Latest customer payment date |
| wd_revenue_category | Workday Revenue Category | Product | Dropdown | Sales item revenue category |
| wd_company | Workday Company | Deal | Dropdown | Default per pipeline |
| wd_contract_type | Workday Contract Type | Deal | Dropdown | Client's contract types |
| wd_contract_id | Workday Customer Contract | Deal | Single-line text | Contract reference returned on create |
| wd_contract_status | Workday Contract Status | Deal | Dropdown | Draft, in approval, approved |
| wd_contract_end | Contract End Date | Deal | Date picker | Drives renewal deals |
| wd_invoice_status | Workday Invoice Status | Invoice | Dropdown | Invoice status |
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 operation-level API guides are available to customers, so each item marked for confirmation is verified in the client's tenant during discovery.
Yes, through a custom build. HubSpot does not publish its own Workday app, so Campaign Creators builds on Workday's SOAP web services (Revenue Management and Financial Management), its REST APIs and Report-as-a-Service, which turns a custom Workday report into a web service. Access is set up in the client's tenant through an integration system user.
Workday customers, contacts and sales items sync to HubSpot companies, contacts and products. Customer contract status, invoices, payments, open receivables and billed revenue are written to HubSpot, and project status can show on the deal for clients that bill from Workday projects. Won HubSpot deals go back to Workday as draft customer contracts.
Each record has one owner. HubSpot owns prospects, contacts, deals and quotes. Workday owns customers once created, contracts after submission, billing, receivables and revenue. Won deals arrive in Workday as draft contracts, and finance completes and approves them there.
Seven phases, each closed by a client sign-off: contracts and ownership, tenant access (an integration system user, security group and permission for each operation and report), reports and mapping, HubSpot data model, build and test in the Workday sandbox tenant, backfill, and a two-week parallel run before contract write-back is switched on.
Timeline and cost depend on the contract line types, companies, worktags and reports in scope, and on whether contract write-back and project data are included. Campaign Creators confirms these in discovery with the client's Workday team and provides a fixed scope before the build starts.