# monday.com Nimbata's monday.com integration puts your phone calls on your monday.com boards. When someone calls one of your tracking numbers, Nimbata can create an item for the caller on the board you choose, fill its columns with call details, and post a note to the item's updates. When the caller is already on a board, Nimbata can update their item instead. Inside monday.com, Nimbata's item view lists the calls from an item's phone number, with a link to each call in Nimbata. **Before you start** - Permissions: monday.com, under Integrations, in your Nimbata role - A monday.com account, and access to the boards you want calls on. - The **monday.com** tile on your Nimbata Integrations page. monday.com is not yet available on every Nimbata account, and on a plan that does not include it, **Go to integration** offers an upgrade instead. - The Nimbata project whose calls you want to send: the integration is set up per project. ## Install and connect Nimbata needs two things in monday.com: its app installed in your monday.com account, and a connection between that account and a Nimbata project. Connecting from Nimbata does both. 1. (1) **Open the monday.com integration** In Nimbata, go to **Integrations**, check that the right project is open, and click **Go to integration** on the **monday.com** tile (1). [The monday.com tile on the Integrations page, with Go to integration marked 1] *Open the monday.com tile (1).* 2. (1) **Click Add to monday** Click **Add to monday** at the top of the page (1). [The monday.com integration page before it is connected, with the Add to monday button marked 1, above the Caller not found and Caller found sections and Send Test and Save] *Click Add to monday (1). The two sections below fill in once monday.com is connected.* 3. **Install and authorize the app** monday.com opens in a pop-up. If the Nimbata app is not installed in your monday.com account yet, monday.com asks you to install it first. Then allow Nimbata access: it asks to read and write your boards, post updates, and read your account and its users. 4. **Check the connected account** Back in Nimbata, the page shows the name of your monday.com account next to **monday.com**. ### If you installed Nimbata from the monday.com marketplace Installing the app from the monday.com marketplace adds it to your monday.com account, but does not connect it to a Nimbata project. Connect it from Nimbata with **Add to monday**, as above. If monday.com sends you on to Nimbata after the install, sign in to Nimbata if asked. The monday.com integration opens with a **Finish connecting monday.com** banner that names your monday.com account and the open project: check that it is the right project and click **Connect** (1). Nimbata confirms with "monday.com connected." and offers **Back to monday.com**. Finish within 10 minutes, or the request expires and you connect again with **Add to monday**. [The Finish connecting monday.com banner on the monday.com integration page, naming the monday.com account and the project, with Cancel and the Connect button marked 1] *Check the account and the project in the banner, then click Connect (1).* ## Configure monday.com In Nimbata, your monday.com boards are what Nimbata writes to, and each board's columns are the fields it fills. Nimbata reads them live from your account, so a new board or column is there the next time you open the page. Each setup, such as **monday.com Settings 1**, has two sections: **Caller not found**, what Nimbata creates when the caller is not on your board, and **Caller found**, what it does when they are. There is no default configuration: you choose the boards and columns. To send different calls to monday.com in different ways, click **Set up monday.com** to add another setup; each workflow picks the setup it sends. 1. (1) **Choose what a new caller creates** In **Caller not found**, click **Add board** (1) and pick the board for new callers. Then click **Add column** for each column to fill, and choose the call fields or your own text that go into it. Besides the board's columns, you can fill: - **Item Name**: the item's name. If you leave it out, Nimbata names the item after the first phone, email or text value you mapped. - **Update (note)**: a note posted to the item's updates, for example the tracking source and a link to the recording. - **Group**: the group the item goes into, on a board with more than one group. [The monday.com Caller not found section: a new item on the Leads board with Item Name, Phone, Status and Source mapped and an Update (note), and the Add board button marked 1] *Caller not found: a new item on the Leads board, with its columns and a note. Add board (1) adds another board.* 2. (1) **Configure what happens when a caller is found** In **Caller found**: 1. Pick the **Board** and the **Phone column** (1) that Nimbata searches for the caller's number. Until you pick them, every call creates a new item instead of updating the one already on the board. 2. Choose how to handle duplicates (2), when the caller's number is on more than one item: **Handle first**, **Handle all** or **Ignore all**. 3. Add the board to update, the same board as in the matching settings, and on its **Update** tab (3) map the columns to change on the caller's item. Mapping **Item Name** renames the item; mapping only **Update (note)** adds a note to the item without changing its columns. The **Create** tab adds a new item instead, even when the caller is found. [The monday.com Caller found section: Board set to Leads and Phone column set to Phone, marked 1, the duplicates question with Handle first chosen, marked 2, and the Leads board on the Update tab, marked 3, with Status and Update (note) mapped] *Pick the board and phone column to search (1) and how to handle duplicates (2), then map what to change on the Update tab (3).* > **Note:** Nimbata can fill text, long text, phone, email, numbers, status, dropdown, date, link, country and hour columns. A status or dropdown label that does not exist yet is added to the column. When a value does not fit its column (letters in a numbers column, say), Nimbata still writes the item and names the columns it left out in the result. ## Test the integration 1. **Click Send Test and Save** Click **Send Test and Save** at the bottom of the page. A panel opens with a box for each call field your setup uses, filled in from your project's latest call. 2. **Send a test event** Change the values if you like, keep a **Caller ID**, and click **Send event**. The test runs exactly like a call and writes to your board: if the Caller ID is found in the phone column you chose, your **Caller found** actions run, otherwise your **Caller not found** actions. The panel shows the result, such as "Item created successfully in Leads. ID: ...", or "Nothing to do." when that path has nothing set up. 3. **Save the setup** Click **Save**, and delete any test items you do not want to keep on the board. ## Send calls with a workflow Nimbata sends a call to monday.com when a workflow with a **monday.com** action runs for it. A workflow that runs when a call ends, with no filter, sends every call, and its filters (for example call outcome or tracking number) narrow it down. monday.com is available in workflows for inbound and outbound calls, not for forms or text messages. 1. **Create a workflow** Go to **Workflows**, click **Create** and choose **From Scratch**. Keep the **Inbound Call** trigger with **Call Ends**, and add any filters you need. 2. (1) **Add the monday.com action** Click the **+** plus sign, select **Perform action**, and choose **monday.com** under **Integrations**. Pick your setup under **Select configuration** (1), then click **OK**. [The monday.com pop-up of the workflow builder, with the monday.com Settings 1 setup selected and marked 1] *Pick the monday.com setup to send (1), then click OK.* 3. (1) **Enable the workflow** Click **Enable** (1). [A workflow firing on Inbound Call, Call Ends, with a monday.com action sending monday.com Settings 1, and the Enable button marked 1] *The workflow sends every inbound call to monday.com when it ends. Click Enable (1).* Detailed guide: [Create a workflow](https://help.nimbata.com/workflows/workflows#create-a-workflow) ## Check it worked The monday.com page now shows the workflow that uses the integration. Place a test call to one of your tracking numbers: once it ends, the item appears on your board. [The connected monday.com integration for the Harbor & Pine Plumbing account, used in 1 workflow, with monday.com Settings 1 used by the monday.com calls workflow] *The page shows Used in 1 workflow, and the setup lists the workflow that sends it.* ## See an item's calls in monday.com Nimbata's item view shows, on any item, the calls Nimbata has from that item's phone number: its phone columns, and the phone column you chose for caller matching. Add it to an item from the item's views in monday.com, as you add any app's item view (see monday.com's [item card guide](https://support.monday.com/hc/en-us/articles/360017143959-The-Item-Card)). The view lists the latest 20 calls, newest first. Each shows whether it was answered, missed, went to voicemail or was blocked, how long the caller talked (or the phone rang), the source and the tracking number dialled, and **Open in Nimbata** to open the call. [Nimbata's item view in monday.com: Calls from (415) 555-0123, with an answered call that talked 4:12 from Google Ads to (415) 555-0142 and a missed call that rang 0:25, each with Open in Nimbata] *The item view lists the calls from the item's phone number, each with Open in Nimbata.* - When your monday.com account is not connected to a Nimbata project yet, the view shows **Connect Nimbata** and a button that opens the monday.com integration in Nimbata, where you click **Add to monday**. - When the item has no phone number, the view says so: add a phone column with the caller's number to the item. - A monday.com guest sees an item's calls only on a shareable board they are subscribed to. ## Disconnect monday.com - **In Nimbata:** open the three-dot menu at the top of the monday.com page and click **Disconnect**. The project stops sending calls and its setups are kept. The Nimbata app stays installed in your monday.com account. - **In monday.com:** when an admin uninstalls the Nimbata app, Nimbata disconnects every project connected to that monday.com account and clears their caller matching board and column. Their setups are kept, so you can reconnect later. - **Remove the setup:** **Remove setup**, in the same three-dot menu, permanently deletes the project's monday.com setups and connection. It is greyed out while workflows use monday.com. ## Limitations - Nimbata lists your active boards, up to 1,000, and leaves out sub-item boards. - People, connected board, mirror, formula, file, location, rating, week and world clock columns cannot be filled. - Caller matching searches one board and one phone column per project, and compares the last 7 to 10 digits of the number. - monday.com receives calls only: form submissions and text messages cannot be sent to it. ## Troubleshooting ### You don't see monday.com on the Integrations page monday.com is not yet available on every Nimbata account. If your plan doesn't include it, **Go to integration** on the tile offers an upgrade instead of opening the page. ### The monday.com tile says Disconnected The project's setup is saved but it is no longer connected to monday.com, for example because it was disconnected or the Nimbata app was uninstalled in monday.com. Nothing is sent until you reconnect: open the integration and click **Reconnect** in the red **Disconnected.** banner, or **Add to monday**. [The monday.com tile on the Integrations page with a red Disconnected badge] *A disconnected integration shows a red Disconnected badge on its tile.* ### Every call creates a new item - Pick a **Board** and a **Phone column** in **Caller found**: without them, Nimbata cannot recognise a caller. - If Nimbata warns "Recognised callers will not be updated: this searches a different board from the one the actions below write to", pick the same board in the matching settings and in the **Caller found** actions. - If it says "This board has no phone or text column to match against.", add a phone column to the board, or pick another board. - Check that the number in the item's phone column is the caller's number: Nimbata compares the last 7 to 10 digits. ### A test or a call reports an error | Message | What to do | | ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Please provide a valid caller id | Fill in the **Caller ID** box in the test panel. | | Item requires a name: map a call field to Item Name, or to a phone, email or text column. | Map **Item Name**, or a phone, email or text column. | | Not written (the value does not fit the column, or the column is gone from the board): ... | The item was written without the columns named. Map a value that fits each column, or remove the columns that are no longer on the board. | | monday.com could not be read, so only the item name and note were written. | Nimbata could not read the board's columns this time. The item was still written, with its name and note: fill in the columns it lists by hand, or send the test again. | | monday.com is not connected. Connect monday.com again to continue. | Click **Add to monday** to connect again. | ### The item view says your session could not be confirmed Reopen the item in monday.com. "You do not have access to this item's calls." means your monday.com account cannot see this item, and "monday.com could not be reached just now." clears when you reopen the item. ### Calls are not reaching monday.com - Check that a workflow with a **monday.com** action is enabled, and that its filters let the call through. - Check that the workflow's monday.com action uses the setup you configured, under **Select configuration**. - Check that the monday.com page still shows your account, and connect again with **Add to monday** if it does not. - Send a test from **Send Test and Save** to see the error monday.com returns.