trigger_send
Raechly staff only: run the send pipeline now, instead of waiting for the hourly run.
›Trigger the send pipeline now and then show me the last 20 activity entries.
What it does
Sending runs by itself every hour, so customers never need this tool; for them the call does nothing. Raechly staff use it to check a fix without waiting.
Runs the whole pipeline on demand — warmup progression, then warmup sends, then every campaign lead currently due. The hourly scheduler runs the same code path, so this is not a special manual mode, just an early start.
Every guardrail still applies. Send windows, per-mailbox and per-domain and per-campaign caps, the hard daily ceiling, address validation and the suppression list all run exactly as they would at the top of the hour. Triggering manually cannot be used to push past a limit.
The run is single-flighted. If a pass is already in progress you get `busy: true` back as an HTTP 409 rather than a second concurrent run.
The most common use is verification rather than urgency: you have just finished setup and want to confirm the whole chain works end to end without waiting for the top of the hour. Follow it with `list_activity` and you will know within seconds whether anything actually left the building.
Parameters
None. Call it with an empty object — there is nothing to configure.
* required · Maps to POST /api/trigger-send
What comes back
Pipeline run summary, or `busy: true` if a run is already in progress.
The thing people get wrong
Triggering outside a campaign send window sends nothing for that campaign. The window is evaluated per lead in the campaign timezone, not per run.
Use it with
More campaigns tools
See all 147 tools and the connection string on the MCP server page.