Source connector

Creatio connector

Creatio integration for databases, warehouses and BI tools

No-code CRM and process automation platform for enterprise teams. Datrise captures Creatio entities such as no-code CRM processes, entities, and cross-team workflow orchestration, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Creatio OData 4 (OData 3 also supported via EntityDataService.svc, being phased out) authenticates with OAuth 2.0, username / password, incremental runs key on ModifiedOn.

Of the 3 objects, 3 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `creatio_no_code_crm_processes`) with a schema derived from the Creatio API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Creatio pipeline page, and join the waitlist to get the Creatio connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Creatio data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
no-code CRM processes	creatio_no_code_crm_processes	Upsert by primary key, incremental on updated-at
entities	creatio_entities	Upsert by primary key, incremental on updated-at
cross-team workflow orchestration	creatio_cross_team_workflow_orchestration	Upsert by primary key, incremental on updated-at

Creatio API: setup facts for the connector

Verified against the vendor documentation on 2026-09-21. Unknown values are left blank rather than guessed.

API	Creatio OData 4 (OData 3 also supported via EntityDataService.svc, being phased out)
Authentication	OAuth 2.0, username / password — OAuth 2.0 client_credentials grant via the Identity Service (`POST {IdentityServiceURL}/connect/token`) is the recommended method; the legacy alternative is forms authentication via `AuthService.svc/Login`, which returns BPMLOADER/.ASPXAUTH/BPMCSRF cookies that must be replayed on subsequent requests.
Pagination	offset — OData `$skip` and `$top` query parameters page through collections; `$count=true` returns the total element count for a collection.
Rate limit	Not published
Incremental cursor	ModifiedOn — `$filter=ModifiedOn gt <Edm.DateTimeOffset value>` (e.g. `2023-05-23T00:00:00Z`) filters a collection for records changed after a timestamp.
Webhooks	No
Bulk export	No
Deletes detectable	Not published

Official API reference

What bites when replicating Creatio

A single OData response is capped at up to 20,000 records and a batch request at up to 100 sub-requests, per the documented 'Limitations of OData protocol', so large collections must be pulled in bounded, paged calls rather than one request.
CSRF protection is enabled by default: POST/PUT/DELETE calls made under forms authentication (`AuthService.svc/Login`) must replay the `BPMCSRF` cookie from the login response, or the server returns HTTP 403 Forbidden.
OAuth 2.0 `client_credentials` access tokens default to a 3,600-second (1-hour) lifetime (`expires_in: 3600`); on cloud instances that value cannot be self-configured and requires contacting Creatio support, so a connector must handle token refresh rather than assume a long-lived token.
The built-in 'Webhook' feature is inbound only — out of the box it parses incoming events into Contact, Lead, Order, and Submitted form objects — so notifying an external system when a Creatio record changes has no native outbound-webhook subscription and instead requires building a custom business process with an HTTP request element.

Compare this against every other documented API

Popular destinations for Creatio

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Creatio connector FAQ

What Creatio data does the connector extract?: 3 objects: no-code CRM processes, entities and cross-team workflow orchestration. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Creatio integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Creatio data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Creatio → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Creatio pipeline with guided onboarding

Join the waitlist to get priority access for Creatio integrations with guided setup, schema-aware mapping, and production-grade incremental sync.