monday CRM

Connect monday once and the customers who connect to your service arrive as contacts that keep themselves current. Nothing to configure, no field mapping to set up by hand — and nothing is ever written to a board you already had.

New to the shared model? Start with the CRM integrations overview — what syncs, what never does, and how consent works.

Before you start

• A monday account you can install an app into.
• Nothing else — the allus portal creates and holds everything this step needs; there is no account client to create yourself.

Step 1 — connect your allus account

In the allus portal, open Configuration → Integrations and click Connect next to monday CRM. The portal does the allus half by itself: it creates a service for you (alerts go to your allus account's own email), publishes its request fields (first name, last name, email, phone, address), registers its own data client and its webhook — then hands you to this integration's own setup page for step 2.

You can add more request fields in the portal at any time. The integration never removes or rewrites a row you added; each one simply shows up in monday as its own column.

Step 2 — authorize monday

Press Connect monday CRM. You are sent to monday's own authorization screen, over OAuth 2.1 with PKCE. The integration asks for:

Approving sends you back to the integration's status page. That is the whole setup.

What it creates in monday

The integration works on one board of its own, called allme contacts in the language you connected in. It is created on the first connection and is the only board the integration ever touches.

• Each connected customer is one item on that board. The item's name is composed from the first and last name they shared; if they shared neither, it is their allme share code.
• Each synced field is one column. The five standard fields get stable columns (First name, Last name, Email, Phone, Address); any extra request field you configured gets its own column, titled with the label you gave it.
• One extra column, allme ID, holds the customer's allme share code. It is what keeps an item matched to the right person for the life of the connection.

Every column is a plain text column. monday's typed columns want a second value the integration does not have — a country code alongside a phone number, coordinates for a location — and inventing one would put a plausible but wrong value on your record. A phone number is stored in international + form where the customer provided one; an address is written as one line.

What lands where

How a customer is matched to an item

On the first contact the integration looks for an existing item on its board before creating one: by allme ID, then by email, then by an international phone number. A search that finds more than one candidate is treated as no match — a duplicate item is easy to merge, while writing one person's details onto another's is not.

Documents and signed flows

A document your customer signs, or a contract flow they complete, shows up as an update on their item's timeline — the same object regular notes use, so nothing new to look for. Each update names the document (or the flow) and the date, and a document that later changes status — signed, accepted, cancelled — gets a follow-up update saying so, including how it was signed when that applies.

This needs no setup on your side: it activates automatically once your integration is fully connected.

Rate limits

The API allowance the integration spends is your monday plan's, and lower plans allow on the order of a thousand calls a day. Two things keep it modest: only changed fields are written — never a whole record refresh — and each run applies at most a small batch, spaced out, leaving the rest to the next run a few minutes later. If monday asks the integration to slow down it waits for exactly as long as monday asks and loses nothing.

Uninstalling

monday tells the integration when you uninstall its app — it is the only CRM here that does. When that happens:

1. Syncing stops immediately and the monday credentials are discarded.
2. Everything the integration holds for you is deleted within seven days, comfortably inside the ten monday's marketplace terms allow. Reconnect inside that window and nothing is lost.
3. Your monday board and its items stay exactly as they are. The purge removes the integration's own records, never anything in your account.

Your allus service is not removed by an uninstall, because the integration cannot act on your allus account without your credentials. Use Disconnect on the integration's status page for a clean teardown of both sides, or delete the service in your portal.

If something looks wrong

The integration's status page carries a sync health card: one row per customer whose data it currently cannot apply, with the repair. Rows clear themselves as soon as that customer syncs again, so an empty card means everything is flowing.

Next

CRM integrations overview · How the connection model works · Account clients · Webhooks