TribeCRM keeps the core information about a person or organisation separate from the relationship that entity has with your business.
This structure affects how records are created, how Field Mapping works, and how associations are made from Enginy.
Key concepts
TribeCRM concept | What it represents |
Person | The basic identity of a person |
Organisation | The basic identity of a company or organisation |
Relationship Type | The classification of a Person or Organisation |
Contact Person | The relationship that links a Person to an Organisation |
Activity | An interaction or work item attached to a relationship |
Task | A type of activity, pending or completed |
TribeCRM explains this model in What is the Relationship and Activity Structure in Tribe?
Person
A Person holds data that belongs to the individual, such as first name, last name and contact details.
The same Person can take part in several Relationships without duplicating their basic information. For example, they can be a Contact Person for several Organisations.
Organisation
An Organisation holds a company's main data, such as name, main phone number, website or addresses.
It can also have several Relationship Types. An Organisation can be classified as both Customer and Supplier, depending on how TribeCRM is set up.
Relationship Type
The Relationship Type explains what relationship a Person or Organisation has with your business.
Common examples are Customer, Supplier, Prospect or Contact Person. Each environment can use different types, with their own fields, options and permissions.
That is why Enginy asks you to choose Contact Type for Contacts and Organization Type for Companies.
These options determine how the record is classified and which fields Enginy can use.
Contact Person
A Contact Person links a Person to an Organisation.
In Enginy:
The Contact provides the person's data.
The Company provides the Organisation.
The association is represented by a Relationship.
That is why Enginy needs a Company to create a new Contact in TribeCRM.
You can find more detail in How Do I Create a New Relation in Tribe CRM?
How Enginy and TribeCRM line up
In Enginy | In TribeCRM |
Contact | Person plus the selected |
Company | Organisation plus the selected |
Contact and Company association | Relationship between the Person and the Organisation |
Campaign email |
|
LinkedIn message |
|
Task |
|
The integration does not use a separate Lead object.
What happens when a Company is created
When you export a new Company, Enginy:
Creates the Organisation.
Applies the
Organization Type.Sends the configured fields.
Sets
AccountManagerwhen an owner is available.Stores the CRM ID for future updates.
If Enginy finds a match, it updates the existing record instead.
What happens when a Contact is created
When you export a new Contact, Enginy:
Finds or creates the associated Organisation.
Creates the Person.
Applies the
Contact Type.Links the Person to the Organisation.
Sends the mapped fields.
Stores the CRM ID.
If there is no associated Company, creation fails.
People linked to several organisations
TribeCRM allows a Person to be a Contact Person for several Organisations.
The association Enginy manages does not mean it will always add another Relationship. If you associate an existing Contact with a different Company, Enginy may change the Organisation on the Relationship it manages.
Test with a few Contacts first if your team uses several Organisations per person.
Where fields live
Fields can belong to the Person, the Organisation, a Relationship, a specific Relationship Type, or an Activity.
A field available for an Organisation classified as Customer may not exist for another one classified as Supplier.
Enginy reads your environment's model and shows the available fields in Field Mapping. If you change Contact Type or Organization Type, review your mappings before exporting again.
Activities
Enginy uses Activities to store:
Emails as
Activity_Email.LinkedIn messages as
Activity_LinkedInMessage.Other supported messages as a generic Activity.
Tasks related to a Contact or a Company.
Messages are not stored as Notes.
Activity_LinkedInMessage is only available if the LinkedIn module is enabled. You can review how this works in general in How Do I Create an Activity?
Tasks
Tasks are part of the Activities model.
Enginy uses Default Task Status when creating a Task and Completed Task Status when completing it. The mapped owner is stored as Assignee.
Deleting a linked Task from Enginy marks it as closed in TribeCRM. It does not delete its history.
Before you configure Field Mapping
Check:
Which Relationship Type should represent Contacts.
Which Relationship Type should represent Companies.
Which custom fields belong to those types.
Whether the OAuth user can read and edit the fields.
Whether a Person can be linked to several Organisations in your process.
Which statuses Tasks should use.
Whether the LinkedIn module is active.