---
ref: tool:brew/fire-trigger-event
name: Fire a trigger event
company: company:brew
workflows: []
access: [mcp, cli, api]
tags: [capability:track-events, category:email, has:api, has:cli, has:mcp]
docs: https://docs.brew.new/api-reference/public-v1/automations/fire-a-trigger
updated: 2026-10-11
---

# 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.

Note: Require a published listening automation. Reuse the event's idempotency key on retries. On a confirmation request, obtain approval and repeat with confirmed:true and the returned confirmation_id. Unsubscribe and domain-purpose rules apply.

## 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.

```json
{ "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.

```sh
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 anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.