Grok Bot can research a launch and write the brief. Then the work usually stops at copy: someone still has to build the email, apply the brand, select an audience, configure the sender, approve delivery, and read the results somewhere else.
Connect Migma and Grok Bot can carry that job from brief to editable campaign. Migma supplies the brand context, email tools, opted-in audience, sending controls, and results. Grok Bot remains the working conversation.
How do I run email marketing from Grok Bot?
Give Grok Bot the agent-ready guide at docs.migma.ai/grok.md. Grok Bot should find Migma Remote MCP, ask before adding the connection, open Migma for access approval, and verify setup with a read-only brand request.
| Step | What happens |
|---|---|
| Connect | Grok Bot reads the Migma guide and presents the Remote MCP connection |
| Approve | You review the Migma account, return destination, and requested access |
| Verify | Grok Bot lists the brands available to that account |
| Create | Migma produces editable branded emails and returns previews |
| Prepare | Grok Bot assembles an opted-in audience, sender, subject, and timing for review |
| Approve | You confirm the exact delivery details in the current conversation |
| Improve | Migma returns campaign stats and delivery logs for the next brief |
Migma is not yet a verified Grok Bot Marketplace listing. Current setup is agent-guided Remote MCP. Availability and authentication can vary by Grok build, account, and workspace policy. Check current Grok Bot requirements before setup.
Give Grok Bot one focused email-marketing job
Create one Bot for campaign research, branded drafts, audience preparation, approval, and results through Migma. A focused job makes its decisions easier to review and keeps campaign work tied to the Migma access you approve.
Use this Bot description:
You are my email marketing Bot. Use Migma for brand context, editable emails, opted-in audiences, campaigns, and results. Begin with read-only checks. Prepare work for review. Before delivery, show the audience, eligible recipient count, sender, subject, timing, timezone, and final previews, then ask for approval.
Grok Bot and Migma have different jobs:
| Grok Bot job | Migma job |
|---|---|
| Research current product facts | Store lasting brand facts and approved knowledge |
| Turn a goal into a campaign plan | Create one email or a complete series |
| Coordinate feedback | Return preview images and editable canvas links |
| Prepare the launch | Work with opted-in lists, segments, senders, and campaigns |
| Ask for a decision | Show the exact delivery details for approval |
| Summarize performance | Return stats and delivery logs for the next brief |
Connect Migma to Grok Bot
You need a Migma account, Grok Bot desktop with plugins or MCP connections allowed, and a browser for the Migma access review. Team admins may need to allow the Migma server URL.
1. Give Grok Bot the setup guide
Open your email-marketing Bot and paste:
Help me use Migma for email marketing with Grok Bot. Read this guide and walk me through connection, access approval, verification, and the first draft: https://docs.migma.ai/grok.md
Grok Bot should read the guide, present the exact Migma Remote MCP endpoint, and ask before adding it.
2. Review Migma access
Your browser opens Migma. Sign in, confirm the account, review the app and return destination, then review each requested permission. Select Allow when the access matches the job.
Draft creation uses email read and write access. Test or direct delivery uses email send access. campaign:write covers campaign creation, sending, and scheduling, so treat it as delivery-capable access.
If browser OAuth cannot complete, use claim-code only when that Grok build can poll Migma and securely store the one-time credential. Claim-code authenticates direct requests; it does not repair the hosted connector. Complete setup only after a read-only brand call and durable connected state are verified.
3. Verify the connection
Ask:
Use Migma to list the brands I can access. Return their names and ask me which brand to use. Keep this check read-only.
Setup passes when Migma returns the correct brands and changes nothing.
4. Prove the workflow with one draft
Run one small job before a full campaign:
Use brand [name]. Create one welcome email for existing subscribers. Keep it as a draft. Return the preview and Migma canvas link. Do not send.
Success means one draft, one preview, one canvas link, and no delivery.
Use one active write path for each job. Before switching paths, pause current work, wait for in-flight work, list drafts read-only, reconcile versions, then continue. This avoids duplicate drafts.
Three useful jobs for Grok Bot and Migma
Launch an email series
Start with one brand, one audience, one action, and approved product facts. For a current launch, ask Grok Bot to research primary sources and create a dated fact checklist before writing.
Then ask:
Use Migma with brand [name]. Create three emails for existing customers: announcement, proof, and last call. Use the approved fact checklist from this conversation. Keep every email as an editable draft. Return every preview and Migma canvas link.
For product imagery, pass up to five public HTTPS image URLs through migma_generate_email.images. Verify expected assets in every returned preview. If an asset is missing, generate a replacement draft with the structured image references.
Ask for targeted changes by email and section:
In the proof email, move the customer quote above the CTA and cut the opening to two sentences. Keep the approved facts, links, and other two emails unchanged. Return the updated preview.
Prepare a permission-based newsletter
Use an existing opted-in list or segment, or import a permission-based CSV. After import, ask Grok Bot to report created, updated, skipped, and failed counts. Then list the available sending domains and From addresses.
Create a campaign draft from one approved email:
Create a campaign draft from approved email ID [id]. Audience: [list or segment]. Sender: [address]. Subject: [subject]. Proposed schedule: [date, time, timezone]. Show the audience, eligible recipient count, sender, subject, proposed schedule, and final preview. Do not call send or schedule. Pause for my approval.
Keep Grok Bot approval controls enabled. When Auto Review is available, add a narrow Require Approval rule for external email. Keep sends, schedules, exports, deletes, and audience changes behind approval. xAI’s approval guidance explains these controls.
Review every value. Approve only when audience, count, sender, subject, timing, timezone, and preview match the intended campaign.
Review results and write the next brief
After delivery, ask:
Use Migma to show stats and recent delivery logs for campaign [name or ID]. Explain the strongest click signal, bounces, and complaints in plain language. Turn the strongest trustworthy signal into a brief for the next email. Return the analysis and draft brief for review.
The next brief now starts from recorded clicks, bounces, and complaints instead of memory.
Save one safe weekly routine
Test workflow once in a normal conversation. Then save preparation as a routine:
Every Monday at 9:00 AM, review last week’s Migma results for brand [name]. If data is missing, stale, or has no trustworthy click signal, report that and create nothing. Otherwise create at most one draft and use one stable idempotency_key for retries of that run. If work is partially complete, report what finished and stop. Show the preview and reasoning. Do not send, schedule, export, delete, or change the audience.
This automates preparation while keeping delivery behind a fresh decision. See xAI’s skills and routines guide for current routine controls.
Does Migma need to stay open?
After connection passes the read-only check, draft work can continue in Grok Bot. Recheck access after reconnecting. Browser approval, sender or domain setup, and detailed canvas review may open Migma.
All your Bots share one cloud computer. Browser sessions, files, and command-line credentials may be available across Bots, so separate Bots are not a security boundary. Review Grok Bot security and privacy before signing in.
Related guides
Prefer another work surface? Read Migma guides for Claude, ChatGPT, Slack, and Telegram.
Start with the Migma for Grok Bot guide. Connect one account, pass the read-only brand check, and create one draft before saving a routine.
Frequently Asked Questions
Is Migma listed in the Grok Bot Marketplace?
Migma is not yet a verified Grok Bot Marketplace listing. Current setup uses the agent-ready guide at https://docs.migma.ai/grok.md to add Migma Remote MCP with your approval.
Can Grok Bot send a Migma campaign?
A connection with campaign:write can create, send, and schedule campaigns. Keep delivery behind explicit approval after reviewing the audience, recipient count, sender, subject, timing, timezone, and final preview.
Does Migma need to stay open?
After the connection passes the read-only check, draft work can continue in Grok Bot. Recheck access after reconnecting. Open Migma for sign-in, sender or domain setup, and detailed canvas review.
