# monday.com recipes

> Text people when an item on a monday.com board changes.

Two recipes for monday.com. Each names its trigger and the BlueBot step, lists the fields to map and says how to test it with your own number before anyone else gets a text.

## How monday.com connects

- **[Zapier](https://usebluebot.com/docs/zapier)**: BlueBot’s Zapier app has a Send Text action and instant triggers for incoming texts and every change of state.
- **[Make](https://usebluebot.com/docs/make)**: BlueBot’s Make app sends texts and starts scenarios when a text comes in or changes state.

## Text when an item’s status changes

| Part             | What it is                                         |
| ---------------- | -------------------------------------------------- |
| Trigger          | When a status column changes on a monday.com board |
| Action           | BlueBot’s **Send Text** action                     |
| Connects through | [Zapier](https://usebluebot.com/docs/zapier)                             |

### Steps

1. Keep each person’s phone number in a column on the board.
2. Start a Zap with monday.com’s trigger for a changed column value and pick the status column.
3. Add a Filter by Zapier step for the status you text about, then BlueBot’s Send Text action with the phone column in To.

### Map the fields

| BlueBot field                | Map it to                                                                                                                                   |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| To                           | The person’s mobile number from monday.com. US numbers can leave off the +1.                                                                |
| Text                         | Hi {{first_name}}, {{item_name}} is ready. Reply here if you have any questions.                                                        |
| `{{first_name}}` in the text | monday.com’s first name field.                                                                                                              |
| `{{item_name}}` in the text  | monday.com’s item name field.                                                                                                               |
| Metadata                     | `source` set to `monday`, and `record_id` set to the record’s id, so the status and reply webhooks for this text can find the record again. |
| Service                      | Auto, the default: iMessage when the person uses it, otherwise SMS through your iPhone.                                                     |

### Test it

Put your own number in **To** and press **Test step**. A text arrives on your phone from your own number, and Zapier shows the message BlueBot returned with `state: "queued"`. Then map monday.com’s field back into **To** and turn the Zap on.

## Add each text to a board

| Part             | What it is                                                                         |
| ---------------- | ---------------------------------------------------------------------------------- |
| Trigger          | A text comes in (BlueBot’s message.received webhook)                               |
| Action           | BlueBot’s **Watch Incoming Texts** module starts it, and monday.com takes the text |
| Connects through | [Make](https://usebluebot.com/docs/make)                                                                 |

### Steps

1. Start a scenario from BlueBot’s webhook for incoming texts.
2. Add monday.com’s module that creates an item on your requests board.
3. Put the sender’s number in the item’s name and the words of the text in a column.

### Map the fields

| From BlueBot    | Into monday.com                                                                                                                                              |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **From**        | The phone number to find the person by in monday.com. It’s in E.164 (`+15555550123`); search by the last 10 digits if monday.com stores numbers another way. |
| **Text**        | The words, for a note, a row or a message. Null when the person sent only a picture.                                                                         |
| **Received At** | When it came in, in UTC.                                                                                                                                     |
| **Files**       | Pictures and voice memos. Each `url` works for an hour, so copy a file you want to keep.                                                                     |
| **Chat ID**     | Set when the text came in a group chat; null for a one-to-one text.                                                                                          |

### Test it

Press **Run once** in Make, then text your BlueBot number from another phone you’ve texted through BlueBot before. The scenario runs with that text. BlueBot copies texts from people you’ve texted through it, unless you set **Which chats to copy** to **Everything**.

## Before you turn it on

- Text only people who asked to hear from you. Anyone who replies STOP goes on your stop list, and BlueBot cancels texts to them. [Stop words](https://usebluebot.com/docs/concepts/stop-words)
- A text that can’t go yet waits with a hold rather than failing: quiet hours, your Mac away, a daily limit. [Holds](https://usebluebot.com/docs/concepts/holds)
- [monday.com with BlueBot](https://usebluebot.com/integrations/monday) on the integrations page says what else the two do together.