Ranla is built so engineering is not the email desk. Connect a repo and the agent installs tracking with a pull request you review. Call the API, drop in an SDK, or brief over MCP when you want the editor. Same suppression list for transactional and lifecycle.
Same agent that drafts and asks. Your other agents talk with it. Send rules still hold.
https://mcp.ranla.ai/mcpConnect the repo. The agent reads the codebase, wires the events audiences and automations need, and opens a pull request. It can also recommend missing events and write those next. You merge.
REST at api.ranla.ai. Official packages (@ranla/node, CLI, framework helpers) so password resets and lifecycle triggers share one domain and one suppression list.
Put Ranla on the agent team you already run. They talk to each other over MCP. Approvals still land in Slack or the app before anything sends.
Automations · Audiences · Transactional · AI agent · Analytics · Docs · All solutions · Pricing
Ranla is built so engineering is not the email desk. Connect a repo and the agent installs tracking with a pull request you review. Call the API, drop in an SDK, or brief over MCP when you want the editor. Same suppression list for transactional and lifecycle.
Scan, instrument, open a PR. Connect the repo. The agent reads the codebase, wires the events audiences and automations need, and opens a pull request. It can also recommend missing events and write those next. You merge.
No. Ranla is the email platform: automations, audiences, transactional mail, and a built-in agent. Send from code, not a second console. REST at api.ranla.ai. Official packages (@ranla/node, CLI, framework helpers) so password resets and lifecycle triggers share one domain and one suppression list.
Connect a GitHub repo, or analytics. Then talk in the agent window: templates, campaigns, automations. It still asks before it sends.