To access Field Mapping, go to Integrations → TribeCRM → Configure → Step 2: Field Mapping.
Important: TribeCRM field types depend on your organization's data model configuration. If you are unsure about the field types available in your TribeCRM setup, contact your TribeCRM administrator.
Understanding the Status Icons
Icon | Status | What it means |
✓ Blue | Compatible | The field types match. No action needed. |
! Yellow | Warning | The field types may be incompatible. Review this mapping carefully before saving. |
✕ Red | Error | The mapping cannot be applied. The export will fail for any record using this mapping. |
Warning: Do not save a configuration with red icons. Exports will fail for all records using that field mapping.
Which TribeCRM Field Type Should I Use?
Use this table as a reference when selecting the destination TribeCRM field for each Enginy field.
Important: The field types available in TribeCRM depend on your organization's data model. The types listed below are the standard TribeCRM field types. If your setup uses custom fields, contact your TribeCRM administrator to confirm the correct type to use.
Enginy field | Recommended TribeCRM field type | Notes |
First name, Last name, Job title, Email, Phone | text | Standard text fields. Fully compatible. |
Number of employees, Years in role, Growth % | number | Map to a TribeCRM number field. |
Created at, Last activity at CRM | date | Map to a TribeCRM date field. Never map to a text field. |
Outreach Stage, Sequence Status | text | TribeCRM does not enforce option validation — ensure values match your expected options manually. |
LinkedIn URL, Domain, Website | text | Map to a standard text field in TribeCRM. |
Personal emails, Other phones | text | Use Professional email and Mobile phone instead where possible to avoid sending arrays. |
Boolean fields (e.g. verified) | boolean | Map to a TribeCRM boolean field. |
Yellow Warning: What to Do
1. Date field mapped to a Text field
Enginy stores date fields (such as Created at or Last activity at CRM) as full date-time values. If the destination field is a plain text field, the value may not be stored correctly.
How to fix it: Map Enginy date fields to a TribeCRM date field.
2. Text mapped to an incompatible field type
If you map an Enginy text field to a TribeCRM field with an incompatible type, the export may fail or store the value incorrectly.
How to fix it: Check the field type in your TribeCRM configuration and select a compatible destination field. If you are unsure, contact your TribeCRM administrator.
Red Error: What to Do
A red icon means the mapping will always fail. There are two reasons this happens:
1. Incompatible field types
The field types on both sides are incompatible and TribeCRM cannot process the value.
How to fix it: Remove the mapping and select a TribeCRM field with a compatible type. Use the reference table above as a guide, and confirm with your TribeCRM administrator if needed.
2. Read-only TribeCRM field
The destination field in TribeCRM is read-only and cannot be updated by Enginy. This typically affects system-generated fields.
How to fix it: Remove the mapping and choose a writable TribeCRM field, or contact your TribeCRM administrator to confirm field permissions.
Common TribeCRM Mapping Mistakes
Mistake | What happens | How to fix it |
Mapping a Company field in the Contacts tab (or vice versa) | Export fails with a field mapping error | Verify that only Contact fields appear under Contacts, and only Company fields under Companies |
Mapping an Enginy date field to a TribeCRM text field | Value may not be stored correctly | Map to a TribeCRM date field instead |
Mapping to a read-only or system field | Export fails | Choose a writable field instead |
Saving mappings with red icons | All records using that mapping fail to export | Fix or remove any red-icon mappings before saving |
Need More Help?
If you have reviewed your mapping configuration and the export still fails, contact our support team with:
The name of the Enginy field and the TribeCRM field you are trying to map
The error message or icon you are seeing
A screenshot of the Field Mapping configuration if possible