Email pre event briefing
Email the campaign owner's own inbox a pre-event briefing: days until the conference, new qualified prospects since the owner last acted (split by whether their first message is ready), the top 5 by fit, and the side events (or, when none are known, people posting their stand, hall or time). It never emails anyone else and never contacts a prospect. At most one briefing per campaign per 10 minutes: a repeat inside the window returns status duplicate and sends nothing. Returns status: sent, duplicate, suppressed (the address is on the do-not-email list), no_event_date (the campaign has no start date yet), or error.
Request
curl -X POST "https://sayintel.com/api/public/v1/campaigns/<campaign_id>/briefing/email" \
-H "Authorization: Bearer $SAYINTEL_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{}'Try it out
Sent as a bearer token to this site only, and kept in this tab's session storage. It is never written to disk or sent anywhere else.
Path parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| campaign_id | path | string | yes | — |
Response
{
"ok": true,
"tool": "email_pre_event_briefing",
"kind": "write",
"data": { ... },
"error": null
}Notes
- Scope required: write. How scopes work.
- Accepts Idempotency-Key. A retry with the same key replays the first result instead of repeating the work.
- Same capability over MCP as the tool email_pre_event_briefing. MCP setup.