“Get a campaign started.”
Your assistant reads the brand brief, uses an approved template and prepares an email draft for your team.
Agent instructions → API draft → Human review
LESS ABRACADABRA. MORE ACTUAL TOOLS.Your agent's
Your agent's
got brains.
Give it tools.
APIs. Webhooks. Agent instructions. A little elbow grease. Give your AI assistant a clearer path from “great idea” to “here's your draft.”
Call it an agent, an assistant or your dot. We'll call it a team effort.
“Beep boop.
Business is good.”
Business is good.”
ENGAGE / THE AGENT TOOLBOXSMART ASSISTANTS. USEFUL CONNECTIONS. HUMAN CONTROL.
THE RIGHT TOOLS FOR THE JOB
You wouldn't fix a pipe
with a pep talk.
Same goes for your agent. A clever prompt helps. Clear instructions, defined permissions and a way to work with your marketing data help it get somewhere.
Engage brings the practical pieces into the picture: APIs for actions, webhooks for updates and files for getting information in and out. Agent Markdown guides are the next piece of the toolbox.
“I'm not saying I'm a plumber.
I'm saying the connections matter.” — Moe
OPEN THE TOOLBOX
Less guesswork.
More “got it.”
Four useful ways to help your people, software and assistants work with Engage. Pick a tool and take a look.
THE SOCKET SET
A proper way to ask.
APIs give authorized software a structured way to work with Engage. Prepare campaign drafts, work with templates and read results within the permissions granted to the connection.
Existing foundation: scoped API access and draft-only campaign writes. The examples here illustrate a workflow; they are not an API reference.
Download starter .md ↗Pseudocode, not executable API syntax. Use the authenticated API documentation for actual endpoints and schemas.
Explore the tools. No credentials needed, and no live requests are made.
PUT THE TOOLS TO WORK
A few very useful
“what ifs.”
Illustrative workflows for the agent-friendly direction. Each starts with a clear task and ends with something a person can check.
“Keep me in the loop.”
An event update reaches your connected system, which can help your team follow progress without another manual check.
Supported event → Webhook → Connected workflow
“What should we learn?”
Give an assistant authorized report data and ask for a plain-language summary with ideas for the next campaign.
Permitted report data → Summary → Your next decision
MOE BROUGHT A TOOL BELT. AND SOME COMMON SENSE.
Helpful doesn't mean
hands off the wheel.
An agent should have a clear job, appropriate access and a sensible stopping point.
Give it the right keys.
Choose permissions for the job. Keep credentials private and outside prompts, screenshots and Markdown instructions.
Let drafts be drafts.
Existing API campaign writes are draft-only. A proposal isn't permission to send. People review the audience and message.
Respect the audience.
Channel consent and opt-outs still matter. An AI assistant doesn't turn a contact file into permission to send.
NO ROBOT LANGUAGE REQUIRED
Frequently asked.
Moe-ly answered.
What is the agent toolbox?
It's the way we present Engage's connection tools together: APIs, webhooks, import/export workflows and proposed agent Markdown guides. It gives teams and their assistants a clearer starting point for working with email and SMS marketing.
Will this work with my agent, assistant or dot?
That depends on whether your assistant can use the required tools and authenticate to Engage. We aren't claiming a native connection to every assistant. APIs and files provide useful building blocks; specific supported integrations and setup instructions will be documented separately.
What are agent MD files?
They're plain-text instructions written in Markdown. They can explain the brand, available tools, permitted tasks and review steps. They do not install an integration or grant access. The downloadable starter on this page is a proposed template, not live product documentation.
What is the difference between APIs and webhooks?
An API lets an authorized connection ask for information or perform a supported action. A webhook lets a system send an update when a supported event occurs. Think “ask for an update” versus “tell me when it happens.”
Can an agent send a campaign on its own?
The existing campaign-write API is draft-only. This concept does not introduce autonomous sending. Sending permissions and any approval workflow must follow the capabilities and controls of the actual product.
Can we use CSV files instead?
Yes, file-based workflows are part of the toolbox story. Use the supported import/export options and actual file formats. Imports should preserve existing opt-outs and handle email and SMS permissions independently.
Is the AI on this page live?
No. This is an interactive marketing concept. The tool examples are illustrative, and the starter Markdown is a reusable planning template. No live API calls are made, no agent is connected and no messages are sent.
Does the robot costume improve performance?
Only Moe's confidence. The useful part is the toolbox.
A LITTLE MAGIC. A LOT OF PRACTICAL.
Let your agent
bring more than
good intentions.
Give it a brief. Give it tools. Keep your team in charge.
Get the agent starter file ↓First, let's Meet Engage ↗