AI receptionist
Answers in your tone, captures the name, the service and the preferred time, and hands the thread to a person the moment its own confidence drops.
Automation engine
Your number, working the night shift.
Flows, an AI receptionist, and first-class n8n and MCP access — all on the number your customers already message, and all on the phone that never left the owner's pocket.
Recipes that ship tonight
Pick one, fill in the parameters, turn it on. Every one of these is a tested, pre-validated shape rather than a blank canvas — and each opens in the same builder afterwards, so the first edit is not a rewrite.
Speed-to-lead
A new lead gets a WhatsApp message inside a minute, then two follow-ups if nothing comes back. Once, not forever.
Appointment reminders
A reminder 24 hours out and again at two, each with a one-tap confirm. No-shows drop fast.
Out-of-hours reply
The greeting and away messages coexistence takes away from the phone, put back — and this one is on the free tier for that reason.
Order updates
Confirmed, shipped, delivered. Shipping states from Shopify or WooCommerce become messages a customer actually reads.
Send from a spreadsheet
A row is a recipient. The sheet stays the thing the business runs on, and Cosend only ever sees the sheets you pick.
Fourteen more in the library, and the same pipeline underneath all of them: a recipe, a sentence describing what you want, or the builder — three entry points into one thing, not three products.
Triggers and actions
The actions are a fixed catalogue, not an open-ended scripting surface. Adding one is a reviewed change to Cosend — which is what makes it safe to let an AI author a flow and deploy it, because there is nothing for it to invent.
| Trigger | Fires on |
|---|---|
| whatsapp.message_received | An inbound message, with keyword and type filters |
| whatsapp.message_status | sent · delivered · read · failed |
| whatsapp.session_expiring | The 24-hour window closes in N minutes |
| contact.created | Contact lifecycle. Also updated and tagged |
| lead.created | A lead from a form, a webhook, a sheet or an ad |
| appointment.upcoming | A set offset before an appointment — 24 hours, 2 hours |
| schedule.cron | A time, in your timezone |
| webhook.inbound | A signed POST from your systems |
| manual | You press Run — or an agent asks for a test run |
| Action | Does |
|---|---|
| whatsapp.send_text | Reply inside the open 24-hour window |
| whatsapp.send_template | Start a conversation with an approved template |
| whatsapp.send_media | Images, documents, audio. Also send_interactive for buttons and lists |
| contact.upsert | Create or update a contact. Also tag, untag and set_field |
| conversation.assign | Route a thread to a person. Also set_mode and note |
| ai.generate | Write an answer. Also ai.classify and ai.agent |
| human_takeover | Flag the thread and go quiet |
| condition | If and else. Also switch, foreach and parallel |
| delay | Wait — minutes or days. Long waits are split and resumed, not held open |
| http.request | Call your API mid-flow, against your own domain allowlist |
| sheets.append_row | Write a row back. Also find_row and update_row |
| calendar.create_event | Book. Also list_slots and cancel_event |
| notify.owner | Reach a human out of band. Also push, email and webhook |
Anything a customer wrote is marked as untrusted all the way through. A message body can be passed to an action as data, and it can never be the thing that decides whether a destructive action runs, or steer what the AI was told to do. That is enforced by the compiler when the flow is saved, not by a warning in the docs.
Nothing is a black box
The five properties every automation gets, whether you built it from a recipe, described it in a sentence, or drew it.
- Retries are free
- Every side-effecting step carries an idempotency key derived from a stable id — the message, the lead, the appointment. A retry that already happened is deduplicated for 24 hours rather than sending twice.
- Failure is loud
- Every flow has a failure handler. A failed run writes its events, fires the notify rail and shows up as a run you can open — rather than as a message a customer never received.
- Cost is bounded before the run starts
- Every flow has a timeout, every step has a timeout, every loop is sliced, and every run carries a budget it cannot exceed. An automation cannot become a bill.
- Rollback is instant
- The version is part of what gets deployed, and the dispatcher reads which one is live on every event. Going back a version takes effect on the next message, not on the next deploy.
- Every run is inspectable to the payload
- A run opens as a per-step trace: what fired it, what each step received, what it returned, and where it stopped.
Three ways in
Same engine, same catalogue, same run history. The difference is where you sit.
The built-in engine
No code and no servers. Build in the dashboard, watch the runs, roll back a version in one click.
What each plan includes →The n8n node
Drop Cosend into workflows you already have, and reach the thousand other apps n8n speaks to. On every plan, including Free.
The n8n node →The MCP server
Let Claude or your own agent author, validate, deploy and repair automations — with the same gates a person gets.
The MCP server →One connection, free, with a hundred runs a month.
Not a trial and not a sandbox. Connect a number and turn on a recipe tonight.