Flexible business data models
Caraer stores business data as objects, properties, records, and relations. An object defines an entity type, a property defines a field, and a record stores one entity. Relations connect records, such as a contact working for a company.
Why integrate
Section titled “Why integrate”Your integration can fit the customer’s existing model. Let an installer choose the object and fields your product needs, then use those selections for mappings and permission requests. The same integration can work with different company schemas without hard-coding their display labels.
What you could build
Section titled “What you could build”An enrichment service could add information to customer-selected contact records and connect each contact to its employer. If one person appears in several business contexts, extended objects let that record share an identity and value set across those contexts.
Start integrating
Section titled “Start integrating”Read the data model guide, inspect the company’s objects and properties in the API reference, and choose one object for your first integration. Use app settings for configurable mappings and record relationships for links.
Shared property definitions affect every object that uses them. Extending a record does not copy it or grant additional access. Keep schema changes deliberate and check shared properties and extended objects before changing either.