Overview
person.run supports outbound automation delivery and survey connector workflows as managed platform capabilities. Public clients should use study/task APIs to produce outputs, then configure delivery behavior through first-party product surfaces.
- Automation platforms: Zapier, Make, n8n
- Survey connectors: Typeform and Qualtrics payload shapes
- Managed destination subscriptions and delivery operations
- Delivery logs, replay, and test sends in first-party operational tooling
Public API boundary
NoteIntegration transport endpoints under
/integrations/* are private operational surfaces. They are intentionally excluded from the public OpenAPI spec and SDK generation.Public endpoints for integration-ready workflows
| Endpoint | Purpose |
|---|---|
POST /studies | Create a study for a population + skill pairing |
POST /studies/{studyId}/runs | Execute the study and produce task records/results |
GET /tasks/{taskId}/results | Read generated outputs for downstream automation |
GET /tasks/{taskId}/turns | Read turn-level transcript artifacts |
GET /tasks/{taskId}/scores | Read scoring artifacts for routing/triage |
POST /schedules | Automate recurring study/task creation and execution |
Create and run a study
Use public study/task/schedule APIs to create the workload that managed integrations consume.
Create study
curl -X POST "$API_BASE_URL/studies" \
-H "Content-Type: application/json" \
-H "x-api-key: $PERSON_API_KEY" \
-d '{
"tenantId": "11111111-1111-1111-1111-111111111111",
"populationId": "22222222-2222-4222-8222-222222222222",
"skillId": "33333333-3333-4333-8333-333333333333",
"name": "Q1 Messaging Study"
}'Start study run
curl -X POST "$API_BASE_URL/studies/$STUDY_ID/runs" \
-H "Content-Type: application/json" \
-H "x-api-key: $PERSON_API_KEY" \
-d '{
"tenantId": "11111111-1111-1111-1111-111111111111",
"maxConcurrency": 6
}'Configure delivery
After runs are live, configure automation destinations, test sends, and replay behavior in dashboard operations views. This keeps delivery transport internals private while preserving stable public API contracts.
Operations and replay
Delivery rows persist per destination + event and include attempt counts and replay relationships.
TipUse destination test-send before activating workflows in production, then use replay to recover transient downstream failures without re-running the upstream persona task.