Skip to main content

Configure Field Mapping, overwrite and warnings in TribeCRM

Field Mapping tells Enginy which Enginy field corresponds to each TribeCRM field, and what happens when TribeCRM already holds a value.

Field Mapping tells Enginy which Enginy field corresponds to each TribeCRM field. It also defines what happens when TribeCRM already holds a value.

Initial mappings

Enginy sets up basic mappings when you connect TribeCRM.

Contacts

Enginy field

TribeCRM field

First name

FirstName

Last name

LastName

Professional email

EmailAddress

Phones

PhoneNumber

Mobile phone

MobilePhoneNumber

Job title

Title

Organizations

Enginy field

TribeCRM field

Name

Name

Website

Website

Description

CoCDescription

Phone number

PhoneNumber

You can keep, remove or extend these mappings. The available fields depend on the Contact Type, the Organization Type and the OAuth user's permissions.

A field available for export is not necessarily available in the same way during an import. Always check the result of a test in both directions.

Field Mapping sections

  • Field Mapping matches Enginy and TribeCRM fields.

  • Fixed value fields always sends the same value.

  • Manual export fields asks for a value during a manual export.

  • Engagement fields uses data linked to supported activity.

  • Custom fields appear according to the data model of the selected type.

Sections available in Field Mapping

Rules for existing values

Sync with TribeCRM

During an export, Enginy keeps the value that already exists in TribeCRM and can fill the field in if it is empty.

This name does not switch on bi-sync. TribeCRM does not automatically send that field back to Enginy.

Enginy overwrites TribeCRM

Enginy can replace the existing value during the next export.

Use this option when Enginy should be the source of truth for that field.

Empty values

If the Enginy field is empty, Enginy skips the value. It does not use an empty value to clear the content in TribeCRM.

Compatibility indicators

Blue check

No known incompatibility was detected.

It does not guarantee that TribeCRM will accept any value. Permissions, allowed options, format and field rules all play a part.

Yellow warning

The types may need adapting. This is common with Enumeration, dates or other formats that do not line up exactly.

Red error

The combination cannot be used. Choose another destination.

Read-only fields usually appear disabled in the selector. An error points to an invalid mapping, not to every record in the export failing.

No indicator

The absence of a warning does not confirm compatibility. TribeCRM can return types or custom fields that Enginy cannot classify conclusively.

Note: The icons are a first check. The definitive test is to export a record and review the value in TribeCRM.

Enumerations

An Enumeration only accepts options defined in TribeCRM. The value sent from Enginy has to match a valid option.

If it does not match, Enginy can skip that field and process the rest of the Contact or Organization.

Check capitalisation, spaces and option names. If both systems use different labels, normalise the data before exporting or choose a text field.

Types and custom fields

The TribeCRM interface can show types such as Email address, Phone number, URL, Number, Currency, Yes/No, Time and Date or List box. Enginy receives technical types from the API and reduces them to compatibility categories.

Test any complex custom field with a single record, especially:

  • Enumerations and lists.

  • Dates.

  • Currency and Percentage.

  • Fields with several values.

  • Required fields.

  • Fields tied to a specific Relationship Type.

If you change Contact Type or Organization Type, review your mappings. A field may exist for Customer and not for Supplier.

If a field is not written

Check:

  1. The field is included in Field Mapping.

  2. The Enginy value is not empty.

  3. The field is not read-only.

  4. The OAuth user can modify it.

  5. The Enumeration option exists.

  6. The field belongs to the selected type.

  7. The overwrite rule allows an existing value to be changed.

  8. The field is supported in the operation you are running.

A Contact or Organization can be created even if one specific custom field is skipped. Review the full record and the report before repeating the export.

Validate before scaling up

  1. Export an existing Contact.

  2. Check the matching and the updated values.

  3. Export a new Contact with an associated Company.

  4. Repeat the test with an Organization.

  5. Review custom fields and Enumerations.

  6. Save the configuration with Save Changes.

Which records Enginy may create

Two settings decide whether Enginy creates a record in TribeCRM that it could not match. They are the most common reason a contact "never arrived".

The creation toggles

In Sync configuration you will find two switches, both on by default:

  • Create contacts in TribeCRM when no match is found

  • Create companies in TribeCRM when no match is found

Turn one off and Enginy updates what it matches and skips the rest. Nothing new is created for that entity.

Required fields for creation

Each row in the Field mapping table has a checkbox in the Required column. Tick it and a record missing that field is skipped instead of created.

Good to know: This never blocks an update. A record that already exists in TribeCRM keeps being updated as usual, because the rule only gates creation.

Three things worth knowing before you use it:

  • One configuration covers every CRM. The check runs on the Enginy values, before they are translated into TribeCRM field names. If you connect a different CRM later, the same rules apply.

  • 0 and false count as filled in. A field is only missing when it is empty, contains nothing but spaces, or is an empty list.

  • Turning creation off does not erase your selection. The list stops applying while the toggle is off, and comes back untouched when you turn it on again.

The checkbox is disabled while creation is off for that entity. Enable the matching toggle in Sync configuration first.

The rule that always applies

Always: A contact with no email, no phone, no LinkedIn URL and no CRM ID cannot be exported at all, whatever you configure here. Enginy would have no way to match or identify it in TribeCRM.

This sits on top of TribeCRM's own requirement that a new Contact needs an associated Company. Both have to be satisfied for the Contact to be created.

Where you see the effect

Export to CRM checks your selection before running and tells you how many records are missing required fields. If every record in the selection would be skipped, it blocks the export with None of these contacts will be created in your CRM.

These rules also apply to automatic campaign syncs, not just manual exports.

Did this answer your question?