Creatio — Partner connector
Partner connectors developed by our Tech Partners and published on the Boomi Platform provide seamless integration solutions for customers. Customers initiate support for these connectors through the Boomi Support Portal, which routes tickets to the respective partner. The partner or their designated third party is responsible for ongoing support, including troubleshooting, bug fixes, and resolving related issues.
The Creatio — Partner connector lets you move data between the Boomi Enterprise Platform and Creatio, the AI-native no-code platform for CRM and workflow automation. Instead of exposing raw Creatio objects, the connector works against integration flows — named, versioned data contracts defined inside Creatio by the SolutionsMetrix Boomi Connector package. A flow describes a whole record graph: a root object, its detail collections, and its expanded lookups.
Each flow is published to Boomi as a single object type. At design time the connector retrieves the flow's XML Schema and hands it to the Boomi mapping editor, so you build the map against the exact document the Creatio endpoint accepts. At run time the connector sends that document back to Creatio, where a single call inserts or updates the entire graph, matching existing records by the business keys declared in the flow. The same flow can be read back with the Get operation, which returns the identical document shape — so a flow round-trips: read, map, write.
Because the profile comes from Creatio itself, changes made to a flow in Creatio (a new column, a new detail, a new lookup) reach Boomi by re-browsing the object, with no connector update and no hand-written schema.
Benefits
- No schema maintenance. Profiles are generated from live Creatio metadata as XML Schema, including detail collections, expanded lookups, nillable elements, and occurrence constraints. Re-browse the object type to pick up a changed flow.
- One call per record graph. A parent record, its details, and its lookups are written in a single request. Creatio resolves lookups, matches on business keys, and decides insert versus update per node — Boomi does not need branching, per-entity calls, or ID round-trips.
- Insert-or-update without pre-checks. Records are matched on the keys the flow declares, so no query-then-branch pattern is needed to avoid duplicates.
- Native Creatio behavior. Writes go through the Creatio entity layer, so object events, business processes, and audit continue to work as they do for a user-entered record.
- Traceability inside Creatio. Every call is recorded in the Creatio integration log with a per-record outcome, so a business user can see what arrived, what changed, and what failed, without access to Boomi.
- Round-trip reads. The Get operation returns a record graph in the same shape that the write operation accepts, making Creatio usable as both a source and a target.
- Standards-based authentication. The connection uses the OAuth 2.0 support built into the Boomi Enterprise Platform, with the client credentials grant against the Creatio Identity Service. Boomi stores the client secret encrypted, requests the access token, and reuses it across executions until it expires. No user passwords are stored, and no user sessions are maintained.
Connector configuration
To configure a connector to communicate with Creatio, set up two components:
- Creatio — Partner connection: holds the Creatio instance URL, the OAuth 2.0 settings (client ID, client secret, and the Identity Service access token URL, entered in the platform's standard OAuth 2.0 field), and the SolutionsMetrix customer ID and license key. Reuse a single connection for every operation against the same Creatio instance and environment. The connection can be tested from the Boomi user interface before it is saved.
- Creatio — Partner operation: represents an action within a single integration flow. The flow and its version are determined by the object type you select when browsing, so no additional operation fields are required.
This design provides reusable components: create a single connection and reuse it across operations, then override the connection settings per environment with environment extensions.
Supported actions:
| Action | Description |
|---|---|
| Get | Reads one record graph from Creatio by the flow root's business key and returns it as XML matching the flow profile. If no record matches the key, the operation returns no document. |
| Execute | Sends a mapped XML document to Creatio, which inserts or updates the entire record graph in a single call. The answer is an UpsertResult XML envelope: an overall success flag, counters for inserted/updated failures, and one outcome element per record. The connector publishes the schema of that envelope as the operation's response profile, so a process maps the answer instead of parsing it by hand. |
Create, Update, Delete, and Query actions are not supported by this connector: writes are covered by Execute, which performs an insert-or-update, and reads are covered by Get. Execute can still remove data: where a flow declares a detail collection authoritative, detail rows the incoming document no longer carries are deleted from the parent record.
Prerequisites
To use the Creatio — Partner Connector, you need the following:
- A Creatio instance — cloud or on-site — running Creatio 8.3.3 or later, reachable from the Boomi Runtime over HTTPS. The version requirement comes from the SolutionsMetrix Boomi Connector package, which specifies 8.3.3 as the required platform version; the connector itself communicates over HTTPS and OAuth 2.0 and is not tied to any Creatio release.
- The SolutionsMetrix Boomi Connector package installed in that Creatio instance, with at least one integration flow configured and published. The connector has no function without it.
- An OAuth 2.0 client (client credentials grant) registered in the Creatio Identity Service, and the absolute URL of that service's token endpoint. The OAuth 2.0 field of the connection accepts the full URL, not a path. On-site installations run the Identity Service on a separate address from the application, so the token endpoint is typically not under the application URL.
- Access rights in Creatio, granted to the OAuth client's user, for every object the flow touches: read for Get, read and write for Execute.
- A Customer ID and a License Key, both issued by SolutionsMetrix. Get and Execute refuse to run without a valid license. Browsing object types and testing the connection do not require one, so a process can be built while the license is being issued.
- A Boomi Runtime (Cloud, basic runtime, or runtime cluster) must be able to reach both the Creatio application URL and the Identity Service token endpoint.
Tracked properties
This connector has no predefined tracked properties. Refer to the topic Adding tracked fields to a connector operation to learn how to add a custom tracked field.
