Create Signal Rule
Add a trigger rule (admin+): when a new signal matches its kinds and keywords, `notify` (flag the signal and send a `signal.triggered` webhook) or `enroll` up to `max_leads` of the company's leads into an active sequence. Enrolling checks reachability, consent and suppressions per lead; contact pressure, calling windows and send caps apply when steps run. 409 over `SIGNALS_MAX_RULES`.
API key access
admin scope with an API key (ro_pat_...). A signed-in session uses the caller's role./api/v1/signal-rulesAccess token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).
In: header
Header Parameters
Id of the workspace to act on (must be a member).
1 <= length <= 200"notify" | "enroll"Signal kinds it matches (empty: any).
items <= 5Matches when any keyword is in the signal's title, detail or evidence (case-insensitive;
empty: any), e.g. ["VP Sales", "Head of Sales"].
items <= 20The (non-archived) sequence an enroll rule enrolls into; it must be active to enroll.
uuidLeads of the company enrolled per signal (default 5).
int641 <= value <= 100Response Body
curl -X POST "http://localhost:8000/api/v1/signal-rules" \ -H "X-Workspace-Id: string" \ -H "Content-Type: application/json" \ -d '{ "name": "string", "action": "notify" }'{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"workspace_id": "0967198e-ec7b-4c6b-b4d3-f71244cadbe9",
"name": "string",
"enabled": true,
"kinds": [
"hiring"
],
"keywords": [
"string"
],
"action": "notify",
"sequence_id": "7cd84c09-94f4-486c-9c49-de3b9cf3f74f",
"max_leads": 0,
"created_by_id": "9377d689-01fb-4abf-8450-3368d2c1924f",
"fired_count": 0,
"last_fired_at": "2019-08-24T14:15:22Z",
"created_at": "2019-08-24T14:15:22Z",
"updated_at": "2019-08-24T14:15:22Z"
}{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string",
"input": null,
"ctx": {}
}
]
}