Configure intent tracking

Create or update a LinkedIn keyword-engagement signal linked to an ICP. Send id to update; without one the signal already linked to the ICP, then the workspace's unlinked keyword signal, is updated, and one is created only when neither exists. Tracking observes evidence; creating a signal does not prove anybody has intent.

POSThttps://app.trygtm.com/api/v1/signals/intent

Scope: write
MCP tool: configure_intent_tracking

Headers

Idempotency-Keystringoptional: A key unique to this write, up to 255 characters. A retry carrying the same key returns the first response instead of running again. Kept for 24 hours.

Body

idstring | nulloptional: An existing keyword signal's UUID from list_signals, to update it. Without one, the tool updates the keyword signal already linked to this ICP, then the workspace's unlinked keyword signal, and only then creates one. Omit or use null to create one, or to let the tool find the existing one. Never invent or guess an ID.
namestringrequired: The signal's name.
icp_idstringoptional: The ICP people engaging with these topics are judged against, from list_icps. Omitted, the workspace's default ICP (or its only one) is used.
keywordsstring[]required: Buying-relevant topics to watch for engagement with, 3 characters or more each.
statusstringoptionaldefault: active: active sweeps on the next tick; paused and draft do not sweep.activepauseddraft

Request

curl -X POST https://app.trygtm.com/api/v1/signals/intent \
  -H "Authorization: Bearer $TRYGTM_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Q4 logistics leaders",
    "keywords": [
      "route optimization",
      "last mile"
    ]
  }'

Response

{
  "data": {
    "id": "e1f2a3b4-c5d6-4e7f-8a9b-0c1d2e3f4a5b",
    "name": "Route optimisation chatter",
    "status": "active",
    "next_run_at": "2026-09-18T10:00:00.000Z",
    "icp_id": "f0e1d2c3-b4a5-4697-8877-66554433aa11",
    "action": "updated",
    "note": "Tracking is configured. Actual observations depend on the intent runtime, provider configuration and available credits."
  }
}