Integrations & Mapping

All integration recipes are designed to provide you full freedom for your workflows. Besides the mandatory account and audiences, you can define which action or event occurred to trigger the automation.

Understanding Mapping

When you define the mapping for an account or campaign, please keep in mind that it is always about the target of your automation. This means you will see on the left side the target destination and on the right side the source. The app tries to support you in the mapping as best as possible by limiting the possible mapping options. If you miss a certain column or field, it means the data types are incompatible. You can solve this by converting the column type in your monday.com board or the merge field in Mailchimp audience.

Some fields and columns are marked with an asterisk (*). You must ensure they are mapped for the automation to work.

Field Type Mapping Guide

Dropdown Fields

The integration will not create new values for dropdown fields in your Mailchimp audience. Any unknown values sent from monday.com will be rejected by Mailchimp, causing the integration to fail.

For this reason, we recommend mapping dropdown fields only with dropdown columns. This allows you to define the possible values in advance and avoid errors. Since Mailchimp is expecting a single selection and monday.com supports multiple for the dropdown column, you should limit the selection to 1 in your column settings: column name > ... > settings > customize X column > limit selection to 1 label.

Address Fields

The mapping needs to provide the address information in one of the following formats to the automation. You can provide the information from a single column, or you combine multiple columns as a single input in the contact fields of the automation sentence.

Supported Address Formats

• [Address Line 1], [City], [State Abbreviation] [Zip Code], US
• [Address Line 1], [Address Line 2], [City], [State Abbreviation] [Zip Code], US
• [Address Line 1], [City], [State Abbreviation] [Postal Code], CA
• [Address Line 1], [Address Line 2], [City], [Postal Code] [Zip Code], CA
• [Address Line 1], [Postal Code], [City], [Country Abbreviation]
• [Address Line 1], [Address Line 2], [Postal Code], [City], [Country Abbreviation]

[Country Abbreviation] is the two-letter code (e.g. FR for France) based on ISO 3166-1. A complete list of all countries is available on Wikipedia.

Address Examples

• 123 Main St, Anytown, CA 90210, US
• 456 Elm Ave, Apt 2B, Springfield, IL 62704, US
• 9 Maple Avenue, Toronto, ON M5V 2T6, CA
• 27 Queen Street West, Suite 500, Vancouver, BC V6C 3E8, CA
• Unter den Linden 77, 10117 Berlin, DE
• 10 Downing Street, Flat 2B, SW1A 2AA, London, GB

Phone Fields

While Mailchimp accepts pretty much any value as a phone number, monday.com is much more selective. In addition to the number, the integration also needs to provide the country.

For US and CA phone numbers, the country is automatically detected. For all other countries you have to use the international format (E.164 format) which requires the country code in the beginning (e.g., +44 for UK).

Data Type Compatibility

Mapping Best Practices

Planning Your Mapping

1. Audit existing data in both platforms before mapping
2. Standardize dropdown values across platforms
3. Test with sample data before full deployment
4. Document your mappings for future reference

Common Mapping Patterns

• Email Address: Always map to required email fields
• First/Last Name: Map to separate name fields when available
• Company: Map to organization or company fields
• Tags: Use automation triggers for tag synchronization
• Custom Fields: Ensure field types match between platforms

Troubleshooting Mapping Issues

• Missing fields: Check data type compatibility
• Validation errors: Verify data format requirements
• Sync failures: Review mapping for required fields
• Partial syncs: Check for field-level permission issues