AI App Builders

AI app builders can use Migma when an app needs real email creation, sending, campaign workflows, contacts, webhooks, or delivery logs. Use agent registration first for agent access. If a fallback key is needed, create it from Settings → Developers → API Keys. Create webhooks from Settings → Developers → Webhooks. Start with Create → Set up Migma with agent when the builder has a coding agent or repo-aware assistant. Migma copies the /setup handoff prompt so the agent audits the app, creates or reuses emails, and wires backend sends safely. Use the surface your builder supports:

Agent handoff for first-time app setup from Migma
REST API for production app code
SDK for TypeScript and Node.js apps
CLI for terminal-capable builders
Setup workflow when a coding agent can inspect and edit the repository
MCP when the builder supports MCP tools

Best path

Copy the setup handoff

In Migma, open Create, click Set up Migma with agent, then copy the prompt.

Paste into the builder agent

Use the agent that can inspect and edit the app repository.

Approve access

Let the agent use agent registration first. Add a fallback API key only when needed.

Review the dry-run

Before live sends, confirm the agent mapped each trigger to the right emailId and added a smoke test.

Builder guides

Lovable

Add Migma to Lovable backend sends.

Bolt

Add Migma to Bolt app email triggers.

v0

Use Migma from server routes or server actions.

Replit

Use Migma from Replit apps, agents, and jobs.

Builder checklist

Prefer the handoff prompt

Use Set up Migma with agent instead of manually writing a long integration prompt.

Keep secrets server-side

Store MIGMA_API_KEY in the builder’s server-side environment or secret manager.

Create or choose a brand

Use a Migma brand/project so emails use the right logo, colors, sender, and audience context.

Prepare email IDs

Generate or select emails in Migma, then store returned emailId values in backend config.

Wire sends in backend code

Send only from server routes, jobs, or trusted functions. Do not send directly from browser code.

Add dry-run checks

Test that each app trigger selects the right emailId without sending duplicates.

Suggested prompt

Use Migma's /setup workflow for this app.
Fetch https://docs.migma.ai/llms.txt first.
Use agent registration before asking me for an API key.
Audit email triggers, templates, providers, queues, webhooks, and jobs.
Create or reuse Migma emails, store emailId values server-side, and add a dry-run before live sends.

When to use each surface

Surface	Use it for
Agent handoff	Copy the right setup prompt from Migma into the builder agent
Setup workflow	App audit, mapping existing emails, backend send wiring
REST API	Production app integration
SDK	Node.js and TypeScript apps
CLI	Terminal workflows and agent scripts
MCP	Agent work inside MCP-capable builders

Setup Workflow

Agent-guided app wiring.

Agent Handoff

Copy setup and selected-email prompts from Migma.

API Quickstart

Send your first API request.

SDK

Use Migma from Node.js or TypeScript.

Webhooks

Trigger app workflows from Migma events.

​Best path

​Builder guides