Get the inactivity policy

Get the workspace inactivity window that drives the derived inactive lifecycle event. Disabled at 30 days until set.

Outcome

Get the workspace inactivity window that drives the derived inactive lifecycle event. Disabled at 30 days until set.

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:read; required workspace access is read. 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.

Discover the target

topolo whoami --json
topolo actions get app_topolo_nurture.events.inactivity.get --detail --json
topolo resources topolo-nurture --json
topolo workspaces list topolo-nurture --json

Request

GET /api/events/inactivity-policy

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

Use an empty JSON object; verified credential and resource context are separate.

Exact input schema:

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Effects

Reads the policy without changing state.

Interpret the response

This is a workspace configuration or policy response, not an independently identified resource. Inspect its values and verify changes with the corresponding read action.

Confirm $.policy.enabled and $.policy.inactiveDays.

Exact success schema:

{
  "type": "object",
  "required": [
    "policy"
  ],
  "properties": {
    "policy": {
      "type": "object",
      "required": [
        "enabled",
        "inactiveDays"
      ],
      "properties": {
        "enabled": {
          "type": "boolean"
        },
        "inactiveDays": {
          "type": "integer"
        },
        "updatedAt": {
          "type": [
            "string",
            "null"
          ]
        },
        "updatedBy": {
          "type": [
            "string",
            "null"
          ]
        }
      }
    }
  }
}

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:

{}

CLI:

topolo actions validate app_topolo_nurture.events.inactivity.get --data @payload.json --json
topolo actions plan app_topolo_nurture.events.inactivity.get --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.events.inactivity.get --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json

MCP tool and arguments:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_nurture.events.inactivity.get",
    "input": {},
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "policy": {
    "enabled": false,
    "inactiveDays": 30,
    "updatedAt": null,
    "updatedBy": null
  }
}

HTTP 200. Confirm $.policy.enabled and $.policy.inactiveDays.

Refused request · invalid_input

Input · payload.json:

{
  "unsupported": "value"
}

CLI:

topolo actions validate app_topolo_nurture.events.inactivity.get --data @payload.json --json
topolo actions plan app_topolo_nurture.events.inactivity.get --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json

Captured local response · HTTP 422:

{
  "error": {
    "code": "invalid_input",
    "message": "The input does not match the action schema.",
    "details": [
      {
        "code": "unrecognized_keys",
        "keys": [
          "unsupported"
        ],
        "path": [],
        "message": "Unrecognized key: \"unsupported\""
      }
    ]
  }
}

HTTP 422. Preserve the refusal details and do not claim success.

Verify the result

Confirm $.policy.enabled and $.policy.inactiveDays.

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.

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

This action does not change service state.

Set the inactivity policy: Enable or disable the derived inactive event and set its window (1-365 days). When enabled, the Nurture scheduler records one inactive event per contact whose newest lifecycle event is older than the window, once per stretch of inactivity, and runs journey triggers for it.

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.