Recipes: ready-made patterns
A recipe is a starting project that is already wired together. You pick one from Graphs → New graph, insert it into an existing project from the editor's Patterns, or ask the Builder.
Channel, agent and tools are already connected correctly.
Each recipe lists what is left to set, such as a token or the name of a mailbox.
The six recipes
| Recipe | What it contains | To fill in |
|---|---|---|
| Telegram assistant | A Telegram bot and an agent that replies | The bot token (or the name of a secret) |
| Web app with an assistant | An app for organization members with an assistant that uses the app's functions | App name and a one-line description |
| Mailbox assistant | A mailbox managed by an agent that can also write, search and reply | The part before the @ |
| Phone receptionist | A phone line, opening hours and an agent that answers by voice and transfers calls | SIP host, account, password, voice keys |
| Agent with your code | An agent, a TypeScript workspace with its functions and a database | Description of the code and the database |
| Team of agents | A front-desk agent that asks a specialist and hands the conversation to a colleague | Role of the specialist and the colleague |
After creation, every recipe requires the same steps: choose the model (or keep the default), rewrite the agent's instructions, save and build, then connect the missing tools or channel.
Related pages
How to create a new agent
Step by step: project, agent node, instructions, model, tools, channel, testing and publishing.
Channels: how people reach agents
Web app, Telegram, mailbox, phone, scheduler and MCP server: how they connect and how you control who can use them.
Multiple agents that collaborate
Delegating a task, handing over the conversation, splitting work into subtasks.
Have an agent to take to production?Let’s talk.
We show you TeraBrain NX on your case: systems to connect, access and controls.