monday.com

• Add the item's contact. Adds the address in the item's email column to a segment. It is subscribed only when the opt-in column you pick says yes.
• Send a Rasket template. Sends one of your published templates to the item's email column, for example when its status changes to Won.
• When a Rasket contact unsubscribes. Runs for the items on the board that carry that address, so you can set a column or post an update.
• When a Rasket email bounces. Runs for the items that carry the bounced address.

Every block runs as your Rasket project, so your suppression list, consent rules and plan limits apply to it exactly as they apply to the API.

• An admin of the Rasket project. Connecting is an admin's decision.
• A board with an email column. One address per item, in an Email or Text column.
• Their agreement. Only subscribe people who agreed to hear from you. A checkbox or status column for it lets Rasket subscribe only them.
• A verified sending domain and a published template, to send. The domains guide and the templates guide walk through both.

1. In Rasket, open Settings, then Integrations, then monday.com, and choose Connect monday.com.
2. Rasket says what it will read and do. Choose Continue to monday.com.
3. In monday.com, install Rasket on your account and approve.
4. You are back on Settings with “monday.com is connected.” Rasket has made an API key for this project named after your monday.com account.

A project connects one monday.com account, and an account connects to one project. Finish within ten minutes of choosing Continue, or start again.

1. On a board in monday.com, choose Automate and create an automation.
2. Pick when it runs, for example When status changes to Won, then add a Rasket action: Add the item's contact or Send a Rasket template.
3. Fill in the block's fields, as the table below describes, and turn it on.

A template is sent with two variables you can use in it: item_name, the item's name, and email, the address it was sent to.

Start an automation with When a Rasket contact unsubscribes or When a Rasket email bounces, then pick what monday.com does with the item: set a column, move it to a group, or post an update. The trigger runs for items that a Rasket action on that board has already handled, so it always has an item to act on.

• It never subscribes anybody without a yes. No opt-in column, or one that doesn't say yes, adds the contact as not subscribed. Campaigns skip them.
• It never subscribes anybody again. An unsubscribed contact stays unsubscribed, and suppressed addresses are never sent to.
• It never reads more than the item. Only the item a recipe runs on, its name and the columns you pick, and only while the recipe runs.

On Settings → Integrations → monday.com, choose Disconnect. Every Rasket block on the account's boards stops, and the API key they ran as is revoked. Uninstalling Rasket in monday.com does the same. Revoking the key in Settings → API keys stops the blocks too; reconnect to make a new one. Contacts and emails the blocks made stay in your project.

• 500 sends a day per monday.com account, on top of your plan. The block says so when the day's sends are used up.
• A retried recipe sends once. monday.com retries a block that fails; Rasket answers the retry with the first run's result.
• The last week of actions shows on Settings → Integrations → monday.com.

• “Rasket isn't connected”: the account is not connected to a project, or it was disconnected. Connect it from Settings.
• “Reconnect Rasket”: the API key was revoked. Reconnect from Settings.
• “The email column is missing”: the column the block uses was deleted. Pick the email column again.
• Skipped: the email column is empty: the item had no address, so nothing happened.
• “That monday.com account is connected to another Rasket project”: disconnect it in that project first.