Outcome
Archive a contact so segments stop matching it and imports no longer update it. The record is kept; use erase for a right-to-erasure request.
Before you start
- Verify identity and pin the intended organization and environment before discovering the action.
- Discover a granted Nurture workspace. The application permission is workspace:write; required workspace access is read_write. A permission alone does not supply a workspace grant.
- Organization and workspace come from verified context. Select resourceType/resourceId separately from action input; body fields cannot grant a different organization or workspace. The first authorized product action can initialize an identity-only workspace mirror.
- Obtain authorization for the documented effect or personal-data export before supplying CLI --confirm or MCP confirm:true.
Discover the target
topolo whoami --json
topolo actions get app_topolo_nurture.contacts.archive --detail --json
topolo resources topolo-nurture --json
topolo workspaces list topolo-nurture --json
topolo actions get app_topolo_nurture.contacts.list --detail --json
id: contacts record id in the selected workspace.
Request
POST /api/contacts/{id}/archive
Save action input as payload.json. The reviewed plan separates path identifiers, query fields and HTTP body. Set NURTURE_WORKSPACE_ID from granted resource discovery; it is separate from action input.
Inspect and test this action in the signed action console. A test response still requires the verification below.
Input fields
| Field | Required | Type | Constraints |
|---|---|---|---|
id | Required | string | contacts record id in the selected workspace. {"minLength":1,"maxLength":64} |
Exact input schema:
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"maxLength": 64
}
},
"required": [
"id"
],
"additionalProperties": false
}
Effects
- Sets the contact's status to archived; the next segment recompute removes it from every segment. Nothing is deleted.
Interpret the response
The returned identifier path is $.contact.id for contact. Empty lists do not discover a target.
Call app_topolo_nurture.contacts.get and confirm status is archived.
Exact success schema:
{
"type": "object",
"required": [
"contact"
],
"properties": {
"contact": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
},
"email": {
"type": "string"
},
"emailHash": {
"type": "string",
"description": "Org-scoped salted SHA-256 address key shared with @topolo-io/audience."
},
"firstName": {
"type": [
"string",
"null"
]
},
"lastName": {
"type": [
"string",
"null"
]
},
"locale": {
"type": [
"string",
"null"
]
},
"timezone": {
"type": [
"string",
"null"
]
},
"attributes": {
"type": "object"
},
"source": {
"type": "string",
"enum": [
"manual",
"csv",
"signup",
"connector"
]
},
"sourceRef": {
"type": [
"string",
"null"
]
},
"status": {
"type": "string",
"enum": [
"active",
"archived"
]
},
"createdAt": {
"type": "string"
},
"updatedAt": {
"type": "string"
}
}
}
}
}
Worked examples
Actual dispatcher and migration-created SQLite or Worker handlers; identity/workspace and external service dependencies are simulated. Fixture identifiers and timestamps are synthetic. These responses establish no live authorization, paid generation, credential provisioning or message delivery. Replace synthetic identifiers using credential-scoped discovery. A local success is not evidence of a deployed effect, configured provider or delivered message.
Successful request
Actual dispatcher and migration-created SQLite; verified identity/workspace and external CRM, Engage, Notify, Consent, Nexus, Brand, Generator, Voice and delivery dependencies are simulated. No live authorization, paid generation or external delivery is established.
Input · payload.json:
{
"id": "nct_741a688b4fb249309a57f390ca45da1a"
}
CLI:
topolo actions validate app_topolo_nurture.contacts.archive --data @payload.json --json
topolo actions plan app_topolo_nurture.contacts.archive --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.contacts.archive --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --confirm --json
MCP tool and arguments:
{
"tool": "topolo_call_action",
"arguments": {
"actionId": "app_topolo_nurture.contacts.archive",
"input": {
"id": "nct_741a688b4fb249309a57f390ca45da1a"
},
"resourceType": "workspace",
"resourceId": "<identifier returned by resource discovery>",
"confirm": true
}
}
Captured local response · HTTP 200:
{
"contact": {
"id": "nct_741a688b4fb249309a57f390ca45da1a",
"email": "dee@example.com",
"emailHash": "1d4bc6c21d44139f3aea2a2ca517dc3c64fb1214c60e4e9d52ec3fa068da30a2",
"firstName": null,
"lastName": null,
"locale": null,
"timezone": "Asia/Tokyo",
"attributes": {},
"source": "manual",
"sourceRef": null,
"status": "archived",
"createdAt": "2026-10-04T00:32:35.023Z",
"updatedAt": "2026-10-04T00:32:35.038Z"
}
}
HTTP 200. Call app_topolo_nurture.contacts.get and confirm status is archived.
Another supported request
Actual dispatcher and migration-created SQLite; verified identity/workspace and external CRM, Engage, Notify, Consent, Nexus, Brand, Generator, Voice and delivery dependencies are simulated. No live authorization, paid generation or external delivery is established.
Input · payload.json:
{
"id": "nct_12a9dc94e25046d2a73f22553d3f9d64"
}
CLI:
topolo actions validate app_topolo_nurture.contacts.archive --data @payload.json --json
topolo actions plan app_topolo_nurture.contacts.archive --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.contacts.archive --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --confirm --json
MCP tool and arguments:
{
"tool": "topolo_call_action",
"arguments": {
"actionId": "app_topolo_nurture.contacts.archive",
"input": {
"id": "nct_12a9dc94e25046d2a73f22553d3f9d64"
},
"resourceType": "workspace",
"resourceId": "<identifier returned by resource discovery>",
"confirm": true
}
}
Captured local response · HTTP 200:
{
"contact": {
"id": "nct_12a9dc94e25046d2a73f22553d3f9d64",
"email": "person2@example.com",
"emailHash": "3090a516e3b91da78e87b6f667154002193cf5d23bfee141646aa6363494c30a",
"firstName": "First2",
"lastName": "Last2",
"locale": null,
"timezone": null,
"attributes": {
"company": "Acme"
},
"source": "connector",
"sourceRef": "crm:crm_c2",
"status": "archived",
"createdAt": "2026-10-04T00:32:36.410Z",
"updatedAt": "2026-10-04T00:32:36.413Z"
}
}
HTTP 200. Call app_topolo_nurture.contacts.get and confirm status is archived.
Refused request · not_found
Actual dispatcher and migration-created SQLite; verified identity/workspace and external CRM, Engage, Notify, Consent, Nexus, Brand, Generator, Voice and delivery dependencies are simulated. No live authorization, paid generation or external delivery is established.
Input · payload.json:
{
"id": "nct_missing"
}
CLI:
topolo actions validate app_topolo_nurture.contacts.archive --data @payload.json --json
topolo actions plan app_topolo_nurture.contacts.archive --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
Captured local response · HTTP 404:
{
"error": {
"code": "not_found",
"message": "Contact was not found in this workspace."
}
}
HTTP 404. Preserve the refusal details and do not claim success.
Verify the result
- Call app_topolo_nurture.contacts.get and confirm status is archived.
Errors and recovery
organization_required(HTTP 403): Select an organization available to the verified caller before choosing a Nurture workspace.permission_denied(HTTP 403): Grant the credential the required Nurture workspace permission.workspace_required(HTTP 409): Create a Nurture workspace, or pass the workspace resource context.invalid_input(HTTP 422): Correct the fields named in error.details using inputSchema, then retry.not_found(HTTP 404): List contacts to find a valid id in this workspace.
Auth or gateway failures may precede this handler. Preserve the exact response shape, error string/code, request id and credential context; no synthetic fixture establishes live credential access.
Recovery boundary
Archiving cannot be undone and imports never unarchive; create a new contact only for a genuinely new person.
Related actions
- List contacts: List the contacts Nurture holds for the caller's workspace, ordered by email, optionally filtered by status and a prefix search on email, first or last name. Pages of up to 200; pass nextCursor back as cursor for the next page.
Evidence
Actual dispatcher and migration-created SQLite or Worker handlers; identity/workspace and external service dependencies are simulated. Fixture identifiers and timestamps are synthetic. These responses establish no live authorization, paid generation, credential provisioning or message delivery. Test scenario and capture digests are retained with each fixture.