Add prospect signal
add_prospect_signalRecords a first-party signal your own system knows about a Golden List prospect, turning it into their strongest research signal, reworking their scores, and triggering the prospect.signal webhook. Sends nothing.
Instructions
Records a first-party signal the customer's own system knows about a Golden List person: it joins their research as a found signal with the intent as evidence, becomes their strongest signal, reworks their scores, writes their {{signal_line}} for it, and the campaign's webhook hears prospect.signal. Review mode applies. Returns created (false when that keyword was already recorded for the person) and the person's research row. Sends nothing. 400 carries a plain reason; 404 means the campaign is unknown or archived.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"campaign_id": "<campaign_id>",
"candidate_id": "<candidate_id>",
"intent": "<intent>",
"keyword": "<keyword>"
},
"name": "add_prospect_signal"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| intent | Yes | What happened, in a sentence, for example 'Booked a demo from the pricing page'. | |
| keyword | Yes | A short label for the signal, for example demo_booked; one signal per person and keyword. | |
| source_url | No | A link to the record or page behind it, when there is one. | |
| campaign_id | Yes | ||
| candidate_id | Yes | The prospect's candidate_id from get_prospect_intelligence or signal_search rows. |