Setup Agent Discovery Signals
POST /agent/onboarding/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.
Authorizations
Parameters
Header Parameters
Responses
200
Successful Response
object
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.
object
object
Whether there are more pages
Items per page
Current page number (1-indexed)
Total number of items
422
Validation Error