Why does the test send fail on some templates?

Templates used as automation steps are listed as active, but the test send returns a 404 that says the template id does not exist. It is logged as a product issue. Regular templates work.

What did the test show?

A partial result. Templates were listed, and test sends worked on regular templates. Automation-step templates failed with a 404.

Is this prompt tested?

Partly. It is marked partly works, not tested, because of the automation template failure. Treat any template you have not sent a test for as unchecked.

Can I run this in the Claude connector?

The connector tool list includes the template tools, but it creates drafts only and never sends campaigns. We tested this prompt on the Brevo MCP server, so connector behavior is untested.

Where does the test email go?

To the address you name. Name it yourself, because an empty recipient list sends to your default test list. The recipient must be a contact on at least one list and not blocked.

PROMPT USE CASE

Check your welcome and order emails with one prompt

Your assistant lists your transactional templates, sends test versions to an address you name and checks which senders and domains are verified. Automation-step templates can fail the test send, so read the limits.

Read the setup guide See the MCP server

Transactional messaging illustration: email, SMS and WhatsApp messages sent in a flow

In short

Ask your assistant to send your Welcome and Order confirmation templates to a test address. It lists templates with templates_get_smtp_templates and sends tests with templates_send_test_template. Regular templates work. Automation-step templates are listed as active but return a 404 on test send.

How it works

MCPmcp.brevo.com/v1/brevo/mcp

Use the Brevo MCP server for this one. The Brevo connector
creates drafts only.

Send my Welcome and Order confirmation transactional templates
to a test address, then tell me which of my senders and domains
are verified.

Send my Welcome and Order confirmation transactional templates
to a test address, then tell me which of my senders and domains
are verified.

Send my Welcome and Order confirmation transactional templates
to a test address, then tell me which of my senders and domains
are verified.

Send my Welcome and Order confirmation transactional templates
to a test address, then tell me which of my senders and domains
are verified.

Read the MCP setup guide

Partly works. Test sends work on regular templates. Automation-step templates fail with a 404.

Why it works

Regular templates work

Test sends of regular transactional templates worked in our test. Check the result in your own inbox.

Automation templates fail

Templates that belong to an automation step are listed as active, but the test send returns a 404 saying the template id does not exist.

Recipients have rules

A test recipient must exist in your contacts, not be blocked and belong to at least one list. Tests are capped at 50 a day.

Frequently asked questions

Check your templates before customers do

Connect the MCP server and send yourself a test of each template.

Read the docs

Check your welcome and order emails with one prompt

In short

How it works

Set it up in four steps

Create an MCP token

Connect your assistant

Name the test address

Paste the prompt and read the result

Why it works

Frequently asked questions

Why does the test send fail on some templates?

What did the test show?

Is this prompt tested?

Can I run this in the Claude connector?

Where does the test email go?

Check your templates before customers do

Frequently asked questions

Why does the test send fail on some templates?

What did the test show?

Is this prompt tested?

Can I run this in the Claude connector?

Where does the test email go?