Outcome
Stop using a connector: it no longer syncs or delegates eligibility. Contacts it synced stay in Nurture with their source, and nothing in the remote system changes. Repeating it is harmless.
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 admin. 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.connectors.disconnect --detail --json
topolo resources topolo-nurture --json
topolo workspaces list topolo-nurture --json
topolo actions get app_topolo_nurture.connectors.list --detail --json
id: connectors record id in the selected workspace.
Request
POST /api/connectors/{id}/disconnect
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 | connectors 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 connector status to disconnected.
Interpret the response
The returned identifier path is $.connector.id for connector. Empty lists do not discover a target.
Call app_topolo_nurture.connectors.list and confirm the status is disconnected.
Exact success schema:
{
"type": "object",
"required": [
"connector"
],
"properties": {
"connector": {
"type": "object",
"required": [
"id",
"provider",
"capabilities",
"status"
],
"properties": {
"id": {
"type": "string"
},
"provider": {
"type": "string"
},
"capabilities": {
"type": "array",
"items": {
"type": "string",
"enum": [
"contact_source",
"suppression_sync",
"interaction_writeback",
"consent",
"lead_handoff"
]
}
},
"config": {
"type": "object",
"additionalProperties": {
"type": "string"
}
},
"status": {
"type": "string",
"enum": [
"active",
"paused",
"disconnected"
]
},
"lastSyncAt": {
"type": [
"string",
"null"
]
},
"lastSyncCursor": {
"type": [
"string",
"null"
]
},
"lastError": {
"type": [
"string",
"null"
]
},
"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": "con_22aa9b969cca481a962fed38b53f41c8"
}
CLI:
topolo actions validate app_topolo_nurture.connectors.disconnect --data @payload.json --json
topolo actions plan app_topolo_nurture.connectors.disconnect --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.connectors.disconnect --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.connectors.disconnect",
"input": {
"id": "con_22aa9b969cca481a962fed38b53f41c8"
},
"resourceType": "workspace",
"resourceId": "<identifier returned by resource discovery>",
"confirm": true
}
}
Captured local response · HTTP 200:
{
"connector": {
"id": "con_22aa9b969cca481a962fed38b53f41c8",
"provider": "topolo_crm",
"capabilities": [
"suppression_sync"
],
"config": {
"crmWorkspaceId": "crm_2"
},
"status": "disconnected",
"lastSyncAt": null,
"lastSyncCursor": null,
"lastError": null,
"createdAt": "2026-10-04T00:32:36.268Z",
"updatedAt": "2026-10-04T00:32:36.276Z"
}
}
HTTP 200. Call app_topolo_nurture.connectors.list and confirm the status is disconnected.
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": "con_22aa9b969cca481a962fed38b53f41c8"
}
CLI:
topolo actions validate app_topolo_nurture.connectors.disconnect --data @payload.json --json
topolo actions plan app_topolo_nurture.connectors.disconnect --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.connectors.disconnect --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.connectors.disconnect",
"input": {
"id": "con_22aa9b969cca481a962fed38b53f41c8"
},
"resourceType": "workspace",
"resourceId": "<identifier returned by resource discovery>",
"confirm": true
}
}
Captured local response · HTTP 200:
{
"connector": {
"id": "con_22aa9b969cca481a962fed38b53f41c8",
"provider": "topolo_crm",
"capabilities": [
"suppression_sync"
],
"config": {
"crmWorkspaceId": "crm_2"
},
"status": "disconnected",
"lastSyncAt": null,
"lastSyncCursor": null,
"lastError": null,
"createdAt": "2026-10-04T00:32:36.268Z",
"updatedAt": "2026-10-04T00:32:36.275Z"
}
}
HTTP 200. Call app_topolo_nurture.connectors.list and confirm the status is disconnected.
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": "con_missing"
}
CLI:
topolo actions validate app_topolo_nurture.connectors.disconnect --data @payload.json --json
topolo actions plan app_topolo_nurture.connectors.disconnect --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
Captured local response · HTTP 404:
{
"error": {
"code": "not_found",
"message": "Connector was not found in this workspace."
}
}
HTTP 404. Preserve the refusal details and do not claim success.
Verify the result
- Call app_topolo_nurture.connectors.list and confirm the status is disconnected.
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 connectors 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
Connect the same provider again; the row is reactivated with the settings you send.
Related actions
- List connectors: List the connectors in the caller's Nurture workspace (any status) with their enabled capabilities, config, last sync time, resume cursor and last error. A workspace that still has the retired settings.crmWorkspaceId link gets an equivalent TopoloCRM connector (contact_source) on this call.
- Connect a provider: Connect one provider to this workspace with the chosen capabilities and its non-secret config (topolo_crm: crmWorkspaceId; topolo_engage: engageWorkspaceId, plus optional campaignId and seatId, checked in Engage). Calls act as the caller's credential; no secret is stored. One connector per provider per workspace; reconnecting a disconnected one reactivates it with the new settings. Capabilities: contact_source (connectors.sync copies remote contacts into Nurture, source connector, source_ref crm:<id>); suppression_sync (connectors.sync pushes unsubscribed, hard_bounce, complaint and manual_block events for those contacts to TopoloCRM, and eligibility.reserve also reserves in TopoloCRM, stricter wins); interaction_writeback (records sends on the CRM timeline; nothing writes yet); lead_handoff (TopoloCRM: a task per newly qualified CRM-linked lead; TopoloEngage: enrol each newly qualified lead into the chosen campaign from the chosen seat, creating the Engage contact when missing).
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.