HubSpot + Creatio integration

Creatio builds its sales product around processes. Leads move through an out-of-the-box lead management process, opportunities through another, and Creatio’s no-code tools let a team reshape both or build its own. So when marketing adopts HubSpot beside it, the integration has to hand work into those processes and read their outcomes back, as well as copy records.

What marketing wants from the pairing is specific. The person who filled in a form, opened the nurture emails and crossed a score threshold should arrive in Creatio as a lead a seller can qualify, and marketing should see which of those leads turned into opportunities and how far they went. Creatio’s model makes that exact, because a Creatio lead is a qualified need attached to a contact or an account rather than a person, and one contact can hold several.

HubSpot’s own Creatio app covers the people and the companies. Everything that carries the pipeline sits outside its shared data, and that gap is what this page is about. The Creatio plan matters too: Growth, Enterprise and Unlimited set different limits on API traffic and process runs, and those limits shape the design. Where Creatio is being replaced rather than kept, the migration or integration guide is the better starting point.

Four objects do the work. Accounts become HubSpot companies and contacts become contacts, both ways, keyed on the Creatio Id, a GUID that every record carries and that no rename changes. Email matches a contact the first time, and the Id holds the pair after that. Where both systems edit the same contact, we give each field one owner: Creatio for what its processes read, HubSpot for marketing source and subscription status.

Leads are the object to get right. Because a Creatio lead is a need rather than a person, it maps to a HubSpot custom object associated to the contact, never to the contact itself. HubSpot creates the lead when a contact qualifies, Creatio’s lead process takes it from there, and the qualification status comes back so marketing can see what happened to each handoff.

Opportunities move one way into HubSpot as deals, associated to the company. Creatio’s opportunity process owns the stage, and HubSpot reports on it without editing it. Activities and orders stay out of a first build.

The shape is a watermark sync over OData 4. A service authenticates with the OAuth 2.0 client credentials grant, taking a bearer token from Creatio’s identity service, which expires after an hour in Creatio’s documented example. It reads each object with a filter on ModifiedOn, sorted and paged, and stores the last timestamp per object, so a restart resumes rather than reloads. A response stops at 20,000 records, which sets the page size for a backfill.

Writes into HubSpot are batch upserts keyed on the Creatio Id, followed by a separate association pass that links leads to contacts and opportunities to companies. Writes into Creatio create and update leads through the same OData service, carrying the HubSpot record id.

Where a seller needs a change in seconds, a Creatio business process can start on an object signal when a record is added, modified or deleted, and call the service through a Call web service element. That push is a fast path only. The watermark read still runs, because a process call that fails after its retries leaves nothing behind for us to replay.

The deciding question for Creatio is whether the pipeline has to be visible in HubSpot. If marketing only needs clean people and companies, HubSpot’s app does that with no build and should be tried first. If it needs leads handed into Creatio’s process and opportunities reported back, the app’s shared data stops short, and a keyed service is the route.

The Creatio plan matters as well. On Growth, OData calls are capped per licence per day and custom business process runs are capped at 50,000 elements a month per environment, so both the polling cadence and any process push are sized against the plan. Enterprise and Unlimited carry neither cap. A per-task automation platform adds nothing the service does not, and it spends the same capped calls.

1. Scope. We confirm the Creatio plan and deployment, list the objects in scope, and walk the lead process with whoever owns it in Creatio.
2. Architect. Leads as a custom object on the contact, opportunities one way, the Creatio Id as the key on every record, and a watermark cadence sized to the plan’s caps.
3. Build. The service is registered as an OAuth client in a Creatio development environment and pointed at a HubSpot sandbox, with a portal allowlist that fails closed.
4. Validate. We run a paged backfill with counts per object, then hand one lead from HubSpot through Creatio’s process and back.
5. Operate. We watch the watermark and, on Growth, the daily OData count, and replay any window a failed run skipped.