> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getmailr.com/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> Mailr is a direct-mail marketing platform for US home-services contractors. Each postcard is personalized with an AI-enhanced image of the recipient's own home and a unique QR code that leads to a personalized landing page. Campaigns can target a neighborhood the customer draws on a map, the homes around past jobs they upload or import, or fire automatically from their CRM. Mailr does not mail an uploaded recipient list. When answering questions, prefer the exact steps and UI labels from these docs, and direct users to app.getmailr.com to sign in. For anything involving account-specific data, billing disputes, or mail that appears lost, direct the user to support@getmailr.com.
# Automate campaigns from your CRM
> Set up automations so a won deal or completed job in your CRM automatically mails the neighbors around that address, with built-in over-mailing guardrails.
An **automation** is a standing rule that starts a mailing campaign for you when something happens in your CRM. Win a deal or close out a job, and Mailr finds the neighbors around that address and mails them — no wizard, no clicks. This page covers where automations live, how to build one, what happens when one fires, and the guardrails that stop your neighborhoods from being over-mailed.
## Where automations live
Open **Campaigns → Automations** in the sidebar of [the Mailr app](https://app.getmailr.com). The section is titled **Campaign Triggers**, and your rules sit under **Active automations** — *"Automations that create mailing campaigns from CRM events."*
Only the workspace **Owner** can create, edit, or delete automations. Everyone else can open the page and read them. If you're not the Owner you'll see:
> *"Only the organization owner can create or edit automations and API keys. You can view existing automations here."*
Ask your Owner to make the change, or see [Team & roles](/account/team-and-roles).
## Create an automation
Give it an **Automation name** you'll recognize later, like "Roof replacements — 100 neighbors".
Each connected CRM contributes its own trigger — for example, fire when a job hits a chosen status, or when a deal reaches a chosen stage. The exact event names available for your CRM are listed on its page under [Connect your CRM](/integrations/overview). If you haven't connected a CRM yet you'll see *"Connect your CRM to trigger this automation — Campaigns fire straight from your jobs and deals once your CRM is connected."* When no CRM is connected, Mailr offers Zapier instead, under *"Using a different CRM? Trigger from Zapier instead"* — a **Deal Won / Job Completed** tile and a **Custom Campaign Trigger** tile. See [Zapier](/integrations/zapier). If your own software posts events to Mailr, a **Trigger from your API** row appears here as well — see [Custom integration](/integrations/custom).
*"How many neighbors to mail around each install address."* Set **Neighbors per install** anywhere from **10 to 500**. The job address itself is never mailed.
*"Only mail homes that match. Applied to the neighbors found around each install address."* Filters like home value and year built work the same way they do in the campaign wizard — see [Targeting](/campaigns/targeting).
Choose **Card type** (Home Render or Classic), **Industry**, **Card template**, **Render style**, and the **QR code landing page** — one of your published pages, or your own URL. These are the same choices as [creating a campaign](/campaigns/create-a-campaign).
The same four audience settings as a manual campaign, from **Standard (recommended)** through **Send to everyone**. Details in [Do-not-mail & opt-outs](/campaigns/opt-outs-and-suppression).
*"Mail the same audience several times over the following weeks."* Presets are **Single drop**, **3 drops · every 2 weeks** (days 0, 14, 28), **4 drops · monthly** (days 0, 30, 60, 90), and **Custom**. You can set custom offsets in days, up to **12 drops**; each drop you add defaults to two weeks after the last. The render style and card size stay locked across the series; each drop can use a different template.
Your rule appears as a card with a plain-English recap — **"Fires when** … **— only if** …**"** — plus tiles for Recipients, Property filters, Card type, Template, Render style, and Landing page, and an **Active** / **Disabled** pill. The card is also badged with the trigger's source: your CRM's name, **Deal Won**, **Custom Trigger**, or **Your API**.
Follow-up drop series are **charged up front** when the campaign is created, not drop by drop. A 4-drop automation holds credits for all four mailings at once.
To pause a rule without losing it, toggle it to **Disabled**. To remove it for good, use **Delete** on the automation card.
## What happens when an automation fires
How fast a trigger reaches Mailr depends on your CRM — some send events instantly, others are checked hourly (see the [integrations overview](/integrations/overview) for your CRM's speed). Once Mailr has the event, the campaign shows up in your campaign list within a few minutes.
When it fires, the campaign **submits itself for review automatically**. Credits are held (not charged), and it lands in **Submitted** without any click from you. Automation-created campaigns carry an **Automated** pill in your campaign list. From there it follows the normal path — see [Campaign statuses & timelines](/campaigns/statuses-and-timelines).
**Keep a credit balance if you run automations.** If your balance won't cover the mailing, the campaign is left as a **Draft**, nothing is held, and it retries on a later pass once you top up. Turn on the **Automation held — needs credits** email in [Workspace settings](/account/workspace-settings) so you hear about it, and top up from **Workspace → Billing** — see [Credits and pricing](/billing/credits-and-pricing).
You don't approve each automated campaign yourself. Mailr reviews them like any other campaign. If you want to stop one, open it while it still says **Submitted** and press **Withdraw submission** — the hold is released and it goes back to Draft.
## Protection against over-mailing
There is **no per-day send cap, no quiet-hours setting, and no per-recipient frequency setting** to configure. These four guardrails do that job instead, and they're on by default:
| Guardrail | What it does |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Duplicate-trigger protection** | The same CRM deal never triggers twice, and the same address can only re-trigger after **30 days**. |
| **Automatic suppression** | Every triggered job address is added to your suppression list as a **Customer**, so later campaigns skip it (a campaign explicitly set to **Send to everyone** can still reach it). |
| **Mail cooldown** | A household that already got a postcard is skipped for the number of days in **Mail cooldown (days)** — default **30**. |
| **Customer cooldown** | Customers added within **Customer cooldown (months)** — default **24** — are skipped in **Standard** mode. |
Both cooldowns are yours to change in [Workspace settings](/account/workspace-settings). Your do-not-mail list is always skipped regardless of either one.
If the page says automations are disabled and none are firing across your whole workspace, that's a temporary pause on Mailr's side, not a problem with your rule. Contact [support](/resources/contact-support) if you see it.
## Next steps
What Submitted, In production, and Mailed actually mean.
The suppression list your automations respect.
Keep a balance so automations don't wait as drafts.
Fixes for held, stuck, and rejected campaigns.