{ "slug": "pega", "url": "https://apps.sectorgrowth.com/integrations/pega/", "name": "Pega", "vendor": "Pegasystems", "aliases": [ "Pegasystems", "Pega Platform", "Pega Sales Automation", "Pega Customer Service" ], "website": "https://www.pega.com/products/platform", "category": { "slug": "sales-and-marketing-platforms", "name": "Sales and marketing platforms", "url": "https://apps.sectorgrowth.com/categories/sales-and-marketing-platforms/" }, "summary": "Pega runs service cases and sales opportunities as workflows on Pega Platform. Joining it to HubSpot means working through its case APIs and flows.", "answer": "No. The HubSpot App Marketplace returns nothing for Pega or Pegasystems as of September 2026, and HubSpot publishes no Pega app. We recommend a custom API integration: the Pega case flow calls our service through a Connect REST rule, and the service writes HubSpot and opens Pega lead cases through the Pega API, at 70 to 150 build hours after 10 to 20 hours of discovery.", "nativeApp": { "status": "none", "verifiedAt": "2026-09-28" }, "api": { "style": "rest", "auth": "oauth2", "webhooks": "no", "changedSince": "partial", "sandbox": "yes", "docsUrl": "https://docs.pega.com/bundle/dx-api/page/platform/dx-api/dx-api-overview.html" }, "objects": [ { "source": "Organization", "hubspot": "company", "direction": "to_hubspot", "key": "Pega organization ID, held in a custom HubSpot property", "notes": "Pega Sales Automation models accounts as a separate object from the organization." }, { "source": "Contact", "hubspot": "contact", "direction": "two_way", "key": "Pega contact ID, with email for the first match" }, { "source": "Lead", "hubspot": "contact", "direction": "to_source", "key": "HubSpot contact id stored on the Pega lead case", "notes": "The case ID Pega returns is written back to the HubSpot contact." }, { "source": "Opportunity", "hubspot": "deal", "direction": "to_hubspot", "key": "Pega opportunity case ID" }, { "source": "Customer service case", "hubspot": "custom", "direction": "to_hubspot", "key": "Pega case ID", "notes": "A read-only copy for context, never worked in HubSpot." } ], "approaches": [ { "kind": "custom", "fit": "recommended", "why": "Pega can call an external endpoint from a step in a case flow through a Connect REST rule, so a keyed service can react to the case events that matter and read the full case through the Pega API, without paging data views on a timer." }, { "kind": "ipaas", "fit": "possible", "why": "A general automation platform can receive the same Connect REST call and create HubSpot records, which suits one case type at low volume; it has no reconciliation to fall back on when a call goes missing." }, { "kind": "native", "fit": "avoid", "why": "No app for Pega or Pegasystems is listed in the HubSpot App Marketplace, so there is nothing to install and nobody else maintaining a mapping." } ], "connectionMethods": [ "api", "ipaas" ], "effort": { "discoveryHours": [ 10, 20 ], "buildHours": [ 70, 150 ], "buildBand": "70 to 150 hours", "typicalElapsed": "4 to 8 weeks" }, "pattern": "webhook-queue", "faqs": [ { "q": "Is there a Pega or Pegasystems app in the HubSpot App Marketplace?", "a": "No. Searches of the HubSpot App Marketplace for pega and for pegasystems returned no apps at all in September 2026, and HubSpot publishes no Pega connector. The route is a custom API integration, with Pega calling out from its case flows and our service writing HubSpot and opening Pega lead cases through the Pega API." }, { "q": "How does an external service authenticate to Pega Platform?", "a": "Through an OAuth 2.0 client registration, a data instance in Pega that lets an external application call Pega REST services with an access token. Pega supports the authorization code, client credentials, password credentials, SAML bearer and JWT bearer grants, and we use client credentials for a server to server integration. Pega's Sales Automation API documentation also requires the calling operator to hold the PegaRULES:PegaAPI role." }, { "q": "Can Pega notify HubSpot when a case changes?", "a": "Not by subscription. Pega's documentation offers no webhook subscription for case changes, so the Pega team adds a Connect REST rule to the case flow, referenced from an Integrator shape at the step that should notify, and the case calls our endpoint when it reaches that step. Pega can also run REST connectors asynchronously through its integration agents, so a slow endpoint does not hold up the case." }, { "q": "What limits apply when reading Pega data pages through the API?", "a": "Requests to data pages sourced from a report definition time out after five seconds by default. A page returns 100 results unless you ask for more, and 5,000 at most; a larger result returns the first 5,000 with a message saying there are more. Data pages from built-on application layers are reachable only once their status is set to API." }, { "q": "Which Pega Sales Automation records can an integration create or update?", "a": "Pega's Sales Automation API documents get, create, update and search operations for contacts, accounts, organizations, opportunities and leads, all through the cases endpoint, with searches run against data pages such as the contact list. Dates must use the YYYYMMDDThhmmss.SS GMT format, and an update to an embedded list needs the pzIndexes parameter, or Pega adds a new entry instead." }, { "q": "Who does the Pega-side work in a Pega and HubSpot integration?", "a": "The client's Pega team or its Pega partner, because the changes live in the client's own application: Connect REST rules in the case flows, data pages set to API status, and the OAuth client registration. We write the event contract and the queries they implement, and their changes move through the client's release process from development to staging to production." }, { "q": "What does a Pega and HubSpot integration take in hours?", "a": "Plan on 10 to 20 hours of discovery and 70 to 150 hours of build on our side for organizations, contacts, leads, opportunities and a read-only case object, with a queue, keyed upserts and a nightly reconciliation. The Pega-side rules and data pages are separate time on the client's Pega backlog, and their release calendar sets the go-live date." } ], "sections": [ { "depth": 2, "text": "Why teams connect Pega to HubSpot", "anchor": "#why-teams-connect-pega-to-hubspot", "url": "https://apps.sectorgrowth.com/integrations/pega/#why-teams-connect-pega-to-hubspot" }, { "depth": 2, "text": "What syncs", "anchor": "#what-syncs", "url": "https://apps.sectorgrowth.com/integrations/pega/#what-syncs" }, { "depth": 2, "text": "Architecture", "anchor": "#architecture", "url": "https://apps.sectorgrowth.com/integrations/pega/#architecture" }, { "depth": 2, "text": "Three ways to connect", "anchor": "#three-ways-to-connect", "url": "https://apps.sectorgrowth.com/integrations/pega/#three-ways-to-connect" }, { "depth": 2, "text": "What breaks and how we prevent it", "anchor": "#what-breaks-and-how-we-prevent-it", "url": "https://apps.sectorgrowth.com/integrations/pega/#what-breaks-and-how-we-prevent-it" }, { "depth": 3, "text": "Notifications only where rules exist", "anchor": "#notifications-only-where-rules-exist", "url": "https://apps.sectorgrowth.com/integrations/pega/#notifications-only-where-rules-exist" }, { "depth": 3, "text": "Five-second timeouts on data pages", "anchor": "#five-second-timeouts-on-data-pages", "url": "https://apps.sectorgrowth.com/integrations/pega/#five-second-timeouts-on-data-pages" }, { "depth": 3, "text": "Embedded lists that grow on update", "anchor": "#embedded-lists-that-grow-on-update", "url": "https://apps.sectorgrowth.com/integrations/pega/#embedded-lists-that-grow-on-update" }, { "depth": 3, "text": "Pega’s own date format", "anchor": "#pegas-own-date-format", "url": "https://apps.sectorgrowth.com/integrations/pega/#pegas-own-date-format" }, { "depth": 2, "text": "Our approach", "anchor": "#our-approach", "url": "https://apps.sectorgrowth.com/integrations/pega/#our-approach" } ], "caseStudies": [], "guides": [ "https://apps.sectorgrowth.com/guides/migration-or-integration/", "https://apps.sectorgrowth.com/guides/how-sector-growth-scopes-an-integration/" ], "status": "published", "verifiedAt": "2026-09-28", "updatedAt": "2026-09-28", "authors": [ { "name": "Prash", "role": "Lead of Technical Integrations and AI Solutions" } ], "sources": [ { "title": "Pega Digital Experience (DX) API Overview", "url": "https://docs.pega.com/bundle/dx-api/page/platform/dx-api/dx-api-overview.html" }, { "title": "Considerations for choosing between a Pega API and a custom API", "url": "https://docs.pega.com/bundle/platform/page/platform/data-integration/considerations-choosing-between-pega-api-custom-api.html" }, { "title": "Data API performance and limitations", "url": "https://docs.pega.com/bundle/platform/page/platform/data-integration/data-api-performance-limitations.html" }, { "title": "OAuth 2.0 client registrations", "url": "https://docs.pega.com/bundle/platform/page/platform/security/oauth-2-client-registration.html" }, { "title": "Connect REST rules", "url": "https://docs.pega.com/bundle/platform/page/platform/data-integration/connect-rest-rules.html" }, { "title": "Pega Sales Automation API", "url": "https://docs.pega.com/bundle/sales-automation/page/sales-automation/additional-info/pega-sales-automation-api.html" }, { "title": "Pega Sales Automation Data Model", "url": "https://docs.pega.com/bundle/sales-automation/page/sales-automation-constellation/getting-started/sales-automation-data-model.html" }, { "title": "Deploying application changes to your staging or production environment", "url": "https://docs.pega.com/bundle/platform/page/platform/devops/deploying-app-changes-to-staging-or-prod.html" }, { "title": "Pega Sales Automation", "url": "https://www.pega.com/products/sales-automation" }, { "title": "Pega Customer Service", "url": "https://www.pega.com/products/customer-service" } ] }