run_warmup_sends
Fire a warmup send pass immediately instead of waiting for the hourly run.
›Run a warmup pass now and then show me updated warmup stats.
What it does
Triggers the warmup portion of the pipeline on demand. The hourly scheduler already does this, so the tool is mostly for setup and debugging — you have just added a pool account and want to confirm the loop closes without waiting until the top of the hour.
It shares the pipeline lock with every other send path. If a run is already in progress you get `busy: true` rather than a second concurrent pass, which is what stops a manual trigger from doubling a day of warmup volume.
The useful pattern is to pair it with `warmup_stats` immediately afterwards. Fire a pass, read the counts, and confirm the reply side moved rather than only the send side. That two-call loop is how you verify a new pool account is genuinely receiving, which is the one thing worth checking manually before you trust the ramp to run unattended.
Parameters
None. Call it with an empty object — there is nothing to configure.
* required · Maps to POST /api/warmup/run
What comes back
Send-pass result, or `busy: true` if the pipeline is already running.
The thing people get wrong
Calling it repeatedly does not warm faster. Daily allowances are enforced per mailbox, so extra passes find nothing left to send.
Use it with
More warmup tools
See all 22 tools and the connection string on the MCP server page.