Recompute segment membership

Outcome

Re-evaluate one segment and record who entered and who exited. It always evaluates the workspace's own active Nurture contacts (fields email, first_name, last_name, locale, timezone, source and every attribute key), including contacts a connector synced in with connectors.sync; it never reads a remote system. Recent lifecycle events are joined by contact id.

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.segments.recompute --detail --json
topolo resources topolo-nurture --json
topolo workspaces list topolo-nurture --json
topolo actions get app_topolo_nurture.segments.list --detail --json

• id: segments record id in the selected workspace.

Request

POST /api/segments/{id}/recompute

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

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

• Records membership entries and exits for the segment; contacts themselves are not changed.

Interpret the response

The returned identifier path is $.segmentId for segment. Empty lists do not discover a target.

Call app_topolo_nurture.segments.members.list and confirm the member count equals $.total.

Exact success schema:

{
  "type": "object",
  "required": [
    "segmentId",
    "evaluated",
    "entered",
    "exited",
    "total"
  ],
  "properties": {
    "segmentId": {
      "type": "string"
    },
    "evaluated": {
      "type": "integer"
    },
    "entered": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "exited": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "total": {
      "type": "integer"
    }
  }
}

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": "seg_5a37efa6266547cc94ba208903123dbc"
}

CLI:

topolo actions validate app_topolo_nurture.segments.recompute --data @payload.json --json
topolo actions plan app_topolo_nurture.segments.recompute --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.segments.recompute --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.segments.recompute",
    "input": {
      "id": "seg_5a37efa6266547cc94ba208903123dbc"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "segmentId": "seg_5a37efa6266547cc94ba208903123dbc",
  "evaluated": 4,
  "entered": [
    "nct_08d797fb395b4a4199a35d787aee9aaa",
    "nct_40311e789ec240839361828fdde02e5e",
    "nct_7636d78d579049eea2c656cf1d064750",
    "nct_b03dfece6989497abe7a7f6877ef429b"
  ],
  "exited": [],
  "total": 4
}

HTTP 200. Call app_topolo_nurture.segments.members.list and confirm the member count equals $.total.

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": "seg_81a16be615ac4949984b381fdfb90919"
}

CLI:

topolo actions validate app_topolo_nurture.segments.recompute --data @payload.json --json
topolo actions plan app_topolo_nurture.segments.recompute --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.segments.recompute --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.segments.recompute",
    "input": {
      "id": "seg_81a16be615ac4949984b381fdfb90919"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "segmentId": "seg_81a16be615ac4949984b381fdfb90919",
  "evaluated": 4,
  "entered": [
    "nct_040a5d000d134236a344523c608685ae",
    "nct_3db89636a94449988024645b597819fa",
    "nct_56e316a48bc94710babbb9e2a10121d3",
    "nct_7e6d0b11b5e64396bc84f06da9969035"
  ],
  "exited": [],
  "total": 4
}

HTTP 200. Call app_topolo_nurture.segments.members.list and confirm the member count equals $.total.

Verify the result

• Call app_topolo_nurture.segments.members.list and confirm the member count equals $.total.

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 segments to find a valid id in this workspace.
• segment_archived (HTTP 409): Recompute an active segment instead.

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

Membership always reflects the latest recompute; fix the rules or contact data and recompute again.

Related actions

• List segment members: List the contacts currently in a segment as of its last recompute, newest entries first.
• Recompute segment membership: Re-evaluate one segment and record who entered and who exited. It always evaluates the workspace's own active Nurture contacts (fields email, first_name, last_name, locale, timezone, source and every attribute key), including contacts a connector synced in with connectors.sync; it never reads a remote system. Recent lifecycle events are joined by contact id.

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.