How your agent works.
Markdown procedures the agent can read at runtime, written by humans who know the domain.
analytics 4
Copy event properties to contact fields
Copy a property your product sends with its events (a workspace name, a trial end date) onto the contact's custom fields, so journeys, segments and emails can use the latest value.
Analytics: Identify visitors and link tracking to CRM contacts
Link an anonymous analytics visitor to a known end-user / CRM contact so page-views and searches show up on the contact's journey.
Analytics: Track CMS entry views
Use the `_tracking` block that every CMS delivery response already ships to record per-entry views, keyed by stable entry id, without minting any key.
Analytics: Track website traffic
Mint a public `mn_track_*` API key, drop the one-line tracker script into your site, and query view events to understand what readers engage with.
bookings 1
cms 9
CMS: Author content with blocks
Define typed block types on a collection and author rich in-article content (callouts, galleries, product cards) whose embedded assets and entry references are validated, expanded on read, and tracked for deletion safety.
CMS: Design a collection
Turn "I need a blog / product catalog / FAQ / landing-page content store" into a working `cms_create_collection` call — pick field types deliberately, order fields for the editor, decide localization up front, and avoid the field-migration paper cuts.
CMS: Localize an entry
Configure locales, author one entry per language with its own slug, keep the locale variants linked, and switch the org's default locale without breaking already-published entries.
CMS: Migrate content in bulk
Move entries from an external CMS, or copy collections between Munin orgs and servers, idempotently — preserve references, rewrite assets, reconcile schema drift.
Preview a draft entry
Let editors view a draft CMS entry rendered by the customer frontend before publishing — configure the collection's previewUrl template, mint a signed preview link, and wire the frontend's draft-mode handler.
CMS: Publish an entry
Move a CMS entry through draft → published — immediate, scheduled, or rolled back — without losing work to optimistic-lock conflicts.
CMS: Review stale entries
On-demand review — find drafts that have stalled, published entries that haven't been touched in months, and orphaned assets. Reports findings with recommended actions to the operator you are working with, who decides what to act on via the existing CMS tools.
CMS: Revise an existing entry
Edit a live or draft article in place — reword a sentence, swap an image, add or remove a block — without regenerating the whole body, then preview and publish the change.
CMS: Upload an asset and embed it
Two-phase asset upload (request presigned upload → send binary → complete), embed in entries, and audit unused assets.
commerce 3
Commerce: Answer product questions
Answer "do you have…", "how much is…", and "is it in stock?" from the connected store's live catalog — search products, fetch variants and availability, and know when the KB is the better source.
Commerce: Check order status
Answer "where is my order?" — list a customer's recent orders, fetch one order's line items and shipment tracking, and know when to hand over to a human.
Connect Shopify order events
Send a Shopify store's order webhooks into Munin as product events (order.created, order.paid, order.fulfilled, order.cancelled), so journeys can start or branch on purchases and segments can filter on them. Munin stores the event, not the order.
connectors 2
Connectors: Connect a custom MCP server
Give the support agent live read access to a system Munin has no vendor adapter for — a proprietary CRM, a subscription database, an internal API — by pointing Munin at an MCP server the customer hosts. Covers the setup flow, the server contract (bearer auth + signed identity assertions), and a reference implementation to hand to the customer's developers.
Connectors: Connect an external system
Connect Shopify, Magento 2, Gastroplanner, Bing Webmaster Tools or Google Search Console so agents can answer order, booking and search-performance questions — create the vendor credential (pasted key or OAuth redirect), register the connection, test it, and understand the identity model that keeps customers scoped to their own data.
conv 15
Conv: Configure national ID redaction
Decide what Munin keeps when customers send national identity numbers, and clean up messages stored before the policy was set.
Conv: Escalate a conversation to a human
How an external chat-widget bot detects that a human/agent in Munin has replied and yields the conversation.
Promote a topic to auto-send
Decide from the review record whether a conversation topic is ready to answer without human review, promote it, and step it back when the numbers say so.
Recover a failed message delivery
Find outgoing email or SMS that never reached the recipient, read why the send failed, fix the cause, and re-queue the delivery with conv_retry_delivery.
Send images in replies
How to attach an image to a conversation reply, read the images a customer sent, and delete one.
Serve several sites from one organization
Run one support agent across several websites — one chat widget per site, a per-channel descriptor naming the site, each site's KB space and store connection pinned to its channel so answers never cross over.
Set a conversation's topic and title
When a new inbound conversation is created, read its first end-user message, tag it with the best-fitting topic (creating one only when confident none fit), and give it a short title if it doesn't already have one. Fires on every `conversation.created` event so the inbox is triaged the moment a message lands — without operator intervention.
Conv: Set up a chat widget
Provision a per-channel widget API key, push transcripts and image attachments via POST /v1/widget/messages, and wire the human-handoff webhook.
Conv: Set up email and chat-widget channels together
Stand up email + widget conversation channels for a new tenant in one pass — configure, test, hand off.
Conv: Set up an email channel
Configure SMTP outbound and optional IMAP inbound for an email channel, then verify the credentials.
Set up a voice or SMS channel
Configure a Vapi/Threll voice channel or Twilio/MessageBird SMS channel with non-secret config, hand off the API keys through a credential link, and verify the result.
Conv: Start an email conversation
Write to someone by email address when nobody has written in yet — a new thread from one of the org's email channels, sent at once by a person or parked as a draft when an agent starts it.
Stop a junk sender
Marking a conversation spam remembers the sender, so their next thread is settled at ingest instead of costing another agent pass. How the flag is set, what it changes, and how it comes off.
Conv: Strip the signature from an inbound email message
Cleanup pass that removes the sender's sign-off and contact block from an inbound email body that has already had its quoted reply stripped, then writes the cleaned body back via `conv_strip_message_signature`.
Conv: Track email opens
Turn on open tracking for an email channel, then read per-message and per-channel open numbers — and report them with the caveats that pixel tracking carries.
crm 8
CRM: Clean up contact data
Periodic curator pass — find duplicate / inconsistent contacts, file high-confidence pairs as structured merge proposals via crm_propose_merge. Designed to be run on a cadence by an admin agent (weekly is a good default). The operator reviews via crm_list_merge_proposals and resolves with crm_apply_merge_proposal / crm_dismiss_merge_proposal.
CRM: Deduplicate contacts
Consolidate two contact rows that are the same person — file the pair as a merge proposal with crm_propose_merge, then resolve it with crm_apply_merge_proposal or crm_dismiss_merge_proposal. Covers the one-off duplicate you hit during other work; the scheduled population sweep is skill://crm/clean-contact-data.
CRM: Extract a contact from a message
When a conversation closes, read the thread for identifying info the end-user volunteered about themselves (name, email, phone, title) and record it on that conversation's own CRM contact with `crm_apply_conversation_identity` — auto-applied, no proposal queue. Designed to fire on every `conversation.closed` event so visitor-volunteered identity becomes structured CRM data without operator intervention.
CRM: Find today's prospects
Give a seller a short daily list of companies in their territory that fit the org's ideal customer profile, each with a dated reason to call now. Candidates come from company-data sources connected alongside Munin (business registry, job ads, procurement notices, map listings); Munin is the memory — one crm_lookup_companies call drops every company already in the CRM, and the picks are stored as owned companies with a deal and the reason, so tomorrow's list never repeats today's.
CRM: Import and score leads
Bulk-import contacts, attach them to companies and a deal pipeline, log the source touchpoint, and seed AI summaries for downstream prioritization.
CRM: Onboard a new customer
Recommended sequence for capturing a new customer, attaching them to a company, and seeding the AI summary that drives later prioritization.
CRM: Progress a deal through the pipeline
Move a deal through pipeline stages with the right activity log at each gate, then refresh AI summary so prioritization stays fresh.
CRM: Repair an undeliverable address
Handle an email address mail can no longer reach — read the deliverability state on a contact, record a dead address so outreach stops sending, find the person's new address, and reopen the address once it works again. Deliverability is reachability, not consent; never fix it with do_not_contact.
identity 1
journeys 7
Build a journey
Turn a lifecycle goal ("convert trial users who invited no colleagues by day 5") into a journey draft — entry, waits, branches, emails, actions and a goal — then validate it. Agents draft and edit; publishing always needs a signed-in person in the Munin dashboard.
Journeys: Decide a step
Curator pass for an agent decide node in a live journey. Read the facts the node was allowed to see about one person, follow the node's instructions, and choose exactly one of its declared edges with a short reason. The journey continues on that edge; if you do not answer in time it takes the node's fallback edge.
Draft a journey from a brief
Turn an operator's plain-language goal ("convert trial users who invited no colleagues by day 5") into a validated, simulated journey draft — starting from the closest template, filling its parameters, adapting it with a rationale per step, and listing the open questions. A person publishes it.
Journeys: Draft a message step
Curator pass for an agent-drafted message in a live journey — an email, SMS, chat message or call opening. Rewrite the journey author's reference text for one person from the brief and the facts the step may see, ground every factual claim in the knowledge base, and submit it with its sources. A person reviews the draft before it is sent; if you do not answer in time, the reference version is filed instead.
Journeys: Fill fields for a step
Curator pass for an agent enrich step in a live journey. Read the facts the step may see about one person and fill the step's declared fields — written to the contact's custom fields and the journey context — leaving out anything the facts do not support. The journey continues either way.
Investigate a journey enrollment
Explain why one person is where they are in a journey — or why they never entered or left early — from the step trace, and decide whether to wait, fix the journey, or remove them. Read-only apart from an optional, operator-approved eject.
Optimise a live journey
Weekly pass over live journeys that opted in with settings.optimiser "weekly" — read goal conversion against the holdout, step and agent statistics and split results, then propose at most one change per journey as a new draft version with its hypothesis, rationale and evidence. A person reviews and publishes it; the optimiser never changes a live journey.
kb 5
KB: Create the first space
Stand up a fresh org's knowledge base — pick a space taxonomy, create the first space, optionally seed a welcome doc.
KB: Import articles in bulk from CSV or JSON
Generalized bulk import pipeline for KB articles from any structured source. Companion to import-from-google-docs — that one covers chunking; this one covers source handling and idempotency.
KB: Import knowledge from Google Docs (or any text source)
Bulk-load articles into the knowledge base, sized for vector search and FTS to perform well.
KB: Review and curate content
How an admin agent turns what a human knew — and the agent didn't — into KB documents, so the next end-user with the same question gets a real answer instead of another handover.
KB: Revise a document
Correct or extend an existing knowledge-base document in place with targeted text replacements — a changed price, a superseded step, a missing exception — without regenerating the body the agent answers from.
outreach 10
Design an email template
Build the org's branded email layout as an MJML template — logo, colours, fonts, footer and unsubscribe link — preview it with real content in both markdown and MJML form, fix the warnings, and save it, optionally as the org default.
Draft a changelog broadcast
Turn what shipped since the last changelog email into a customer-facing broadcast. Collect the changelog entries from the CMS (or the knowledge base), choose the few that matter to customers, write them up as release cards, and file the draft for approval.
Outreach: Draft a first-touch call
Draft the opening and talking points for a first-touch outbound call on a voice campaign. One pending proposal per (campaign, contact). Only a signed-in person in the Munin dashboard can place the call — an agent never can, on any host.
Outreach: Draft a first-touch email
Periodic curator pass that drafts personalised first-touch outreach emails for every enabled campaign. One pending proposal per (campaign, contact). Drafts go into the operator review queue — never auto-send. Runs weekly by default; the operator approves each draft before it leaves the org.
Outreach: Draft a first-touch text message
Draft first-touch SMS outreach for a campaign running on an SMS channel. One pending proposal per (campaign, contact), capped at 480 characters, plain text. Only a signed-in person in the Munin dashboard can approve a text — an agent never sends one.
Outreach: Draft a reply
Per-message curator pass that drafts a suggested reply when an inbound message lands on an outreach-originated conversation. Drafts go to the operator review queue — never auto-send. Triggered event-driven from `conversation.message.received` whenever the conversation has an `outreachCampaignId` and `agentMode='draft_only'`.
Outreach: Extract an outcome
After an outbound call ends or a prospect replies to an outreach email or SMS, read what they said and write it into the contact's custom fields, under the field schema the campaign declares. Auto-applied, no proposal queue. Fires on conversation.voice.call_ended and on inbound replies, for campaigns with a non-empty extractionSchema.
Outreach: Review pending proposals
Operator review pass over drafted outreach proposals — approve each pending draft (sending it now or scheduling it for a named time), dismiss it, or call off a scheduled send, plus the two agent-side corrections, revise and withdraw. Voice and SMS proposals are approved only in the Munin dashboard. In MCP App hosts this renders the interactive Munin Inspector panel.
Send a broadcast to a segment
Draft one email for every eligible contact in a CRM segment, such as a changelog, newsletter or announcement. Check who it reaches and who is excluded, send a test to a teammate, and hand it to a signed-in person to approve. Then follow delivery, replies and unsubscribes. Agents draft and monitor; only a person approves the send.
Set the send rules
Set the org-wide rules every marketing send follows — the default time zone, quiet hours, weekdays, a weekly cap per contact and a pause after a contact last wrote to the team. Campaigns, broadcasts and journeys all respect them, and a journey or campaign can only be stricter.
playbooks 6
Playbook: Customer acquisition (CRM + Conv)
End-to-end flow from a fresh lead list to first conversation — bulk-import contacts, send a welcome email, log the touchpoint, hand off to a human if interest signals fire.
Playbook: Data migration (server ⇄ server)
Move one org's data between two Munin servers, either direction, using the per-module export/import tools — in foreign-key order, threading the returned idMap so dependent records resolve their parents on the target.
Playbook: Frontend integration (Conv widget + Analytics + CMS)
Wire a freshly-scaffolded frontend (Lovable, Bolt, Replit, v0, Cursor, Claude Code, …) to a Munin tenant — chat widget, page-view tracker, and live CMS content — without rediscovering the same five gotchas every time.
Playbook: Publish and distribute (CMS + KB + Conv)
Author content in the CMS, mirror the parts that should be searchable to the KB, and announce the publish to a conversation channel.
Playbook: Support desk launch (Conv + CRM + KB)
Stand up a working support desk for a new tenant — channels, contacts, knowledge base — so the first ticket has tooling around it.
Playbook: Trial onboarding journey (Journeys + Analytics + Outreach)
Launch a journey that welcomes every new trial user, checks after five working days whether they invited a colleague, flags likely buyers for sales and offers help to the rest — then watch it run until the first-journey gate is met (no duplicate sends, a complete trace for everyone).
seo 2
SEO: Improve search performance
Close the loop between what people search for before they arrive and what they do after — read impressions and position from the connected search engine, find the page that should have answered, fix it, and submit it for recrawl.
SEO: Research keywords and competitor gaps
Use the org's own DataForSEO account to size keywords, find new ones, see what any domain ranks for, and list the keywords competitors win that the org does not — while keeping the spend on that account visible and bounded.
slack 1
social 3
Social: Attach a picture or video to a post
Put an image or video on a social post draft — including a file that exists only on somebody's machine, which goes through the CMS first — and understand when the file is read, what happens if it is gone by then, and why the asset needs a home rather than being left loose.
Social: Draft companion posts for an article
Turn one published article into three or four social posts that take genuinely different angles, tagged so later click figures show which angle earned the attention, and left for a person to pick from.
Social: Publish a reviewed post
Publish a social post draft through Munin from the calling person's own connected account, and handle the four ways it can refuse — no connection, a lapsed connection, a draft already decided, and a platform that rejected the post.