EMAIL & COMMUNICATION · FOR AI AGENTS
Novu Cloud
Operate notification workflows and subscriber preferences through agent tools.
Use Novu Cloud’s MCP server, APIs and SDKs to manage workflows, inspect subscriber and delivery activity, and trigger notifications through configured channel providers.
Your integration checklist
- Capabilities
- What you need from your owner
- Create a Novu Cloud account in the intended region, configure a development environment and connect the required delivery providers. Define subscriber identifiers, preferences and the workflow before enabling real recipients.
- Authentication
- Use OAuth with a supported MCP client or an environment-bound API key as a bearer token. US MCP is https://mcp.novu.co/ and EU MCP is https://eu.mcp.novu.co/. OAuth defaults to Development; select the intended environment explicitly.
- Your first task
- Read the environment and a known workflow, then inspect one test subscriber’s preferences before triggering a controlled notification.
- Billing & payment
- Cloud plans include workflow-run allowances, with paid tiers for higher volume and additional limits. Connected delivery providers have their own accounts and charges; a Novu allowance does not make every channel send free.
- Agent payment support
- Not verified. Programmatic usage does not establish autonomous checkout support.
- Operational limits
- Workflow, delay, digest and retention limits vary by plan. Hosted account MCP connects to Novu Cloud, not a self-hosted instance. A provider failure does not automatically select another provider.
ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK
Resolve the subscriber, environment and delivery provider before triggering
Editorial recommendation · Reviewed 2026-10-21
When to choose this service
Choose Novu Cloud when an agent must coordinate notification workflows across channels and preserve subscriber preferences and delivery visibility.
The dependency is an operated notification system with stored subscriber state, workflows and connected delivery accounts. Producing notification text does not maintain those resources or deliver through the provider.
Suggested workflow
- Resolve the environment and stable subscriber ID. Inspect preferences, the selected workflow and the active integration for each intended channel.
- Trigger one controlled event and retain the workflow transaction reference. Inspect execution and the provider outcome before treating the notification as delivered.
- Check delayed or digested steps and retention against the workflow’s recovery window. Expand to real recipients only within the authorized audience and budget.
Acceptance checks before real work
- Verify OAuth environment selection or the API key’s bound environment.
- Confirm subscriber preferences and the actual provider account before a send.
- Distinguish workflow acceptance from channel delivery and recipient action.
If the workflow fails
Inspect the failed step and provider error before triggering another workflow. Reconcile any completed channel sends first; retrying the entire workflow can contact the recipient twice.