Agents

Setup Agent Discovery Signals

Create the global custom column behind each observable trigger.

Takes no body. A signal is defined ONCE for the account and every list patches the same column - that is what makes cross-campaign analysis possible at all, and why the column is global rather than list-scoped.

Triggers nothing can observe come back as research rather than being quietly created: they are real and useful, but they belong in the copy rather than in the targeting. Promising to watch something nothing watches is a program that never fires and a failure nobody can see.

post/agent/onboarding/discovery/signals

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/agent/onboarding/discovery/signals
  • Auth: HTTP bearer

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Response

Successful Response

dataOnboardingPayload required

An open envelope for an onboarding or discovery result.

Open on purpose. Discovery state carries a per-field coverage matrix whose field set is the product's own onboarding questionnaire - it changes as the questionnaire does, and a pinned mirror would silently DROP a field the customer had answered. On a surface whose whole job is "what do we still not know about you", a dropped field reads as an answered question.

Changes

No recorded changes to this operation across all 2 revisions of this API.