Send leads to monday CRM

What you need

An API token: monday, your avatar, Developers, then My access tokens. Copy the v2 token.

It carries its owner's own seat, so the boards it can write to are the boards that person can see. A board shared with somebody else will not be on the list.

Connect and route

1. In Destinations, connect monday with the token.
2. Pick the board. They are grouped by workspace and ordered by what you have been using.
3. Create a route -- which leads it takes, and which board they land on.
4. Map the columns. They are read from the board itself.

Columns are not text boxes

This is the part worth understanding, because getting it wrong is invisible. monday stores each column type in its own shape, and a plain string put into a typed column is not an error -- it is an empty cell. So each type is written the way monday reads it back:

A status label your board does not have is left out, not created. Creating labels from a lead answer would mean one typo becomes a permanent column value that somebody has to go and delete.

Columns monday computes or resolves against its own records -- people, mirrors, formulas, subtasks -- are not offered in the mapper at all. A person column needs a monday user id, and a lead answer is a string.

Errors that arrive as successes

monday's API answers 200 OK and puts the problem in an errors array. An unauthenticated call is a

1. We read that array, so a refusal is a failed dispatch with monday's own message on it.

What it does not do

It creates a top-level item. It does not create sub-items -- a sub-item belongs to a parent that a lead does not have -- and it does not update an item that already exists.