Create contact person

Outcome

Add a named person to a contact. The first active person becomes primary automatically; choosing another primary moves that designation.

Before you start

• Verify the intended environment, authenticated identity and specifically approved organization context.
• The published application permission is contacts:write. Discover the exact granted canonical Books workspace and bind it separately from action input.
• Approve the actual mutation, accounting inputs and any provider/recipient effects before CLI --confirm or MCP confirm:true. Fixture identifiers and simulated provider responses authorize no live operation.

Discover the target

topolo whoami --json
topolo actions get app_topolo_books.contacts.people.create --detail --json
topolo resources topolo-books --json
topolo workspaces list topolo-books --json

• Set BOOKS_WORKSPACE_ID to the exact granted workspace returned by discovery.
• contactId: Exact contact.id from contacts.list/get; a name or email address is not an id.

Request

POST /api/contacts/{contactId}/people

Inspect and test this action. Save the reviewed input as payload.json; supply credential/resource context separately.

Input fields

Inspect nested fields and the complete input schema.

Effects

• Adds a named person to the contact. The first active person becomes primary automatically.

Interpret the response

Read $.person.id for the returned contact_person identifier. Empty collections and nullable fields do not discover a target.

Call app_topolo_books.contacts.people.list for the contact and confirm the returned person.

Inspect the success schema. CLI/MCP add their own transport envelope; CLI --detail requests the full result.

Worked examples

Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.

Run a reviewed request

Save the input from the selected worked example as payload.json. Validate and inspect the plan before calling the action; refused examples demonstrate errors and are not instructions to execute.

CLI:

topolo actions validate app_topolo_books.contacts.people.create --data @payload.json --json
topolo actions plan app_topolo_books.contacts.people.create --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_books.contacts.people.create --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --confirm --detail --json

MCP tool and arguments for the first successful example:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_books.contacts.people.create",
    "input": {
      "contactId": "con_fd6a873dbd044b81864e7d4abb07e444",
      "name": "Jordan Lee",
      "email": "jordan@contoso.example"
    },
    "resourceType": "workspace",
    "resourceId": "<exact granted workspace id>",
    "confirm": true,
    "detail": true
  }
}

Successful response · HTTP 201

Input · payload.json:

{
  "contactId": "con_fd6a873dbd044b81864e7d4abb07e444",
  "name": "Jordan Lee",
  "email": "jordan@contoso.example"
}

Captured response · HTTP 201

{
  "person": {
    "id": "cps_0c6c894496784b5d8c2e8298a868d140",
    "organization_id": "org_contact-people-route_muvnpzsz4",
    "workspace_id": "ws_contact-people-route_muvnpzsz4",
    "contact_id": "con_fd6a873dbd044b81864e7d4abb07e444",
    "name": "Jordan Lee",
    "job_title": null,
    "email": "jordan@contoso.example",
    "phone": null,
    "is_primary": 1,
    "status": "active",
    "created_at": "2026-10-05T19:42:55.623Z",
    "updated_at": "2026-10-05T19:42:55.623Z"
  }
}

HTTP 201. Call app_topolo_books.contacts.people.list for the contact and confirm the returned person.

Refused response · auth_error

Input · payload.json:

{
  "contactId": "con_4a1b2c",
  "name": "Priya Shah",
  "jobTitle": "Finance Director",
  "email": "priya@example.com",
  "isPrimary": true
}

Captured response · HTTP 401

{
  "error": "API key validation failed"
}

HTTP 401. SDK error code auth_error. Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.

Verify the result

• Call app_topolo_books.contacts.people.list for the contact and confirm the returned person.

Errors and recovery

• auth_error (HTTP 401): Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.

These are observed local refusals. Shared authentication, schema validation and resource authorization can also refuse before the route. Preserve the actual error, details and request id.

Recovery boundary

Archive the returned person.

Related actions

• List contacts: List customers and suppliers. Filter to one role or include archived contacts, search across name, legal name, email, phone, tax number and city, and sort by name, city, country or when the contact was added.
• Archive contact person: Archive a person without removing the contact record. If they were primary, another active person becomes primary.

Evidence

Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.