To access Field Mapping, go to Integrations → Pipedrive → Configure → Step 2: Field Mapping.
Important: Pipedrive applies light coercion between some field types, but will reject clearly invalid values. Always review yellow warnings before saving.
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 Pipedrive Field Type Should I Use?
Use this table as a reference when selecting the destination Pipedrive field for each Enginy field.
Enginy field | Recommended Pipedrive field type | Notes |
First name, Last name, Job title, Email, Phone | text / email / phone | Standard fields. Fully compatible. |
Number of employees, Years in role, Growth % | number / monetary | Map to a Pipedrive numeric field. |
Created at, Last activity at CRM | date / datetime | Enginy sends dates as YYYY-MM-DD for date fields. Map to a date or datetime field, never to a text field. |
Outreach Stage, Sequence Status | select (single) | Value must match an existing option exactly. |
Languages, Sub-industries | enum (multi-select) | Values must match existing options exactly. |
LinkedIn URL, Domain, Website | url / text | Both types are compatible in Pipedrive. |
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 Pipedrive boolean field. |
Yellow Warning: What to Do
Pipedrive applies light coercion between some field types but will reject clearly invalid values. A yellow warning means the mapping requires your attention before saving.
1. Text mapped to a Select (dropdown) field
If you map an Enginy text field to a Pipedrive select field, the export will fail if the value does not match one of the configured options exactly.
How to fix it:
Create an AI Variable with output type One off and define the tag options to exactly match the Pipedrive select field options.
For Fixed Value or Engagement fields: enter the exact option value directly in the field mapping configuration.
For Manual Export fields: enter the exact option value at the time of export.
2. Date field mapped to a Text field
Enginy sends date fields (such as Created at or Last activity at CRM) as YYYY-MM-DD for Pipedrive date fields. 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 Pipedrive date or datetime field.
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 Pipedrive cannot process the value.
How to fix it: Remove the mapping and select a Pipedrive field with a compatible type. Use the reference table above to choose the correct type.
2. Read-only Pipedrive field
The destination field in Pipedrive 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 Pipedrive field, or contact your Pipedrive administrator to confirm field permissions.
Common Pipedrive 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 Pipedrive text field | Value may not be stored correctly | Map to a Pipedrive date or datetime field instead |
Mapping an Enginy text field to a Pipedrive select field without matching option values | Export fails | Use an AI Variable (One off) with the exact Pipedrive option values |
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 Pipedrive field you are trying to map
The error message or icon you are seeing
A screenshot of the Field Mapping configuration if possible
