Fire a trigger event

Fire a trigger event

Validates an event payload, upserts the contact it describes and starts one run of every published automation listening to that trigger.

For event-driven lifecycle and transactional email. Always pass an idempotency key, such as the event name, user id and event timestamp.

Set up

Use the first option your agent supports.

MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

{ "mcpServers": { "brew": { "url": "https://brew.new/api/mcp" } } }

Call the MCP tool fire_trigger_event.

Server URL: https://brew.new/api/mcp

CLI (official)

Install the command, then confirm it runs.

brew install getbrew/tap/brew-cli
brew-cli --version

Run brew-cli automations triggers fire.

Set $BREW_API_KEY in your environment first (get a key: https://brew.new/settings/api).

API (official)

• Base URL: https://brew.new/api
• Endpoint: POST /v1/automations/triggers/{triggerEventId}/fire
• Auth: send the header Authorization: Bearer $BREW_API_KEY
• Get a key: https://brew.new/settings/api
• Docs: https://docs.brew.new/api-reference/api/api-introduction

Before doing anything else, make one read-only call to confirm access.

Rules

• Ask the user before anything that sends messages, costs money, or changes data.
• Never print API keys.