How to Build Notifications with AI Agents
An AI agent can build your entire messaging layer: the templates, the channel routing, the multi-step journeys, the preference logic, and the code that calls all of it. Not trigger it. Build it. That only works when every object in the platform is reachable by API, which is the difference between an agent that ships something and an agent that fills in a form someone else made. Here's how to set up an agent against Courier, prompt it so it produces work you'd merge, design templates and journeys with it, put a model inside a running flow, and make the result repeatable enough to run in CI.
Highlights
- Set up your agent: MCP, the CLI, and the Courier skill, with configs you can paste.
- Prompt for work you'd merge: what a complete prompt contains, and how to make an agent verify itself.
- Design templates and journeys: one document that renders everywhere, and flows built from a sentence.
- Put a model in the flow: the AI node, eight working scenarios, and how to pick a model.
- Make it repeatable: templates as code, environments, and governance that holds up in CI.
Contents
