Monday
Overview
Section titled “Overview”Signals reads items from a monday.com board on a recurring schedule and sends the mapped fields onward.
Monday is the one connector in this category that is not a CRM by construction. It is a work platform, and a CRM on monday.com is a board somebody designed. There is no guaranteed lead object, no standard email field and no built-in lead status, so what this connector can read depends entirely on how your board was built. Everything in Configuration follows from that.
Supported destinations
Section titled “Supported destinations”Destinations supported by Monday
| Category | Supported |
|---|---|
| Offline Conversions | |
| Lead Conversions | |
| Custom Audience |
Prerequisites
Section titled “Prerequisites”- The board holding the records you intend to sync, with the columns you intend to map already present.
- Administrator access to your monday.com account, on a plan that includes API access. You need it to install the Datahash app, authorize the connection and grant read access to the board you sync.
- A status column on the board you sync holding each item’s stage, such as New, Contacted, Qualified, Won or Lost. Each value maps to a conversion event, so an item left on a stale status reports the wrong one.
Authentication
Section titled “Authentication”In Studio, open Sources, find the CRM category, and click the Monday tile. Authentication is two steps.
- Install the Datahash app to enable secure access on your monday.com account, using the link on the screen.
- Click Sign in with Monday and authenticate your account.
Configuration
Section titled “Configuration”Instance Setup
Section titled “Instance Setup”Select the Integration Type based on where the data needs to be sent. The options are Offline Events, Audience, Meta CAPI CRM, Google Leads, TikTok Leads, Snapchat Leads and LinkedIn Leads. The choice decides which fields you are asked to map and which destinations the connection can feed, so settle it first. Then choose the board Signals reads from and give the instance a name.
monday.com has no fixed modules. Every board in your account is pulled through into the module list, so the options are your own board names rather than a standard set such as Deals or Contacts. Only boards the authenticating account can see will appear, and a private board will not appear until that account is added to it as a member.
Field mapping
Section titled “Field mapping”Map your board columns onto the schema Signals expects. Each field is a dropdown of the columns on the board you selected, so nothing has to be renamed on the board. What you are asked to map depends on the integration type.
| Group | Fields |
|---|---|
| Configuration | Event name, event time, last modified date, lead lifecycle stage. |
| Personal information | Email, phone, first name, last name, city, state, country, postcode, gender, date of birth, Facebook click ID, Google click ID, OpenAI identifier, source URL. |
| Product | Total value, currency, product type, name, category, ID, brand, price, quantity, transaction ID, number of items. |
Meta CAPI CRM asks for three fields only: the Meta lead ID, the last modified date column and the lead lifecycle status column. The lead conversion integration types ask for a similar short set.
Test connection
Section titled “Test connection”Click Test Connection before finishing. It checks both that the credentials still work and that the mapped columns actually contain data, so a mapping pointed at an empty column fails here rather than silently later.
Manage instance
Section titled “Manage instance”One instance is configured for one board. To read another board, configure it on a new instance from the Manage existing instance table. To change an existing one, open it from the Manage existing instance table, click the edit option in the menu to the top right, update the fields and click Finish.
Data & identifiers
Section titled “Data & identifiers”Only the fields you map are read. Personal identifiers are normalized and SHA-256 hashed before they are sent to any destination.
Email, phone, name and location are what destinations match on. Value, currency and product fields describe the conversion rather than the person, so they do not affect match rates.
Best practices
Section titled “Best practices”- Keep one board per purpose. Reading a board that mixes leads, customers and internal tasks sends all three to the destination.
- Ensure the board holds personal information such as email address and phone number. Destinations weight these highest, so items without them match at a much lower rate.
- Maintaining consistent formatting on the board helps match rates: email addresses in lowercase, phone numbers in E.164 format, and no trailing spaces.
- Name each instance for the board and integration type it serves, since a workspace often ends up with several.
Troubleshooting & FAQ
Section titled “Troubleshooting & FAQ”The board is not listed. It is probably private, or the authenticating account is not a member of it. Being an account admin is not sufficient for a private board.
A column is not listed. Check you selected the right board. Columns are per board, so a column you are thinking of may live on a different one.
Most items are being skipped. They have no email or phone value. A board where contact details are optional produces this and nothing about the connection looks wrong.
Low match rates at the destination. Usually unvalidated text columns holding identifiers. Convert them to typed columns and fix formatting at source.
Nothing is arriving at the destination. Confirm a destination is connected in the same project. A source on its own collects nothing.