Documentation
integrations.disconnect

integrations.disconnect

Category: Integrations
Risk Level: High
Allowed action_type: disconnect

What this action is

Disconnect a third-party integration.

When to use it

Use this action when you are about to disconnect a third-party integration.

Real-world example

Example: your AI agent proposes an operation that would result in integrations.disconnect. Before you apply the side effect, validate the exact payload with ASG.

When not to use it

Do not use integrations.disconnect for planning, drafting, or simulation. Only call ASG when your system is prepared to execute on PASS or stop on WARN/BLOCK.

Allowed action_type values

This field is enforced. If it is not listed, do not send it.
disconnect

Canonical payload (This will PASS)

json
{
  "action_kind": "integrations.disconnect",
  "action_type": "disconnect",
  "ai_output": {},
  "context": {
    "account_id": "example",
    "actor_user_id": "example",
    "idempotency_key": "example",
    "request_id": "example",
    "system_instructions": "example",
    "user_input": "example",
    "workflow": "example",
    "workflowName": "example"
  }
}

Required context

FieldRequiredTypeConsequence
account_idRequiredstringBLOCK: Missing required context (account_id).
actor_user_idRequiredstringBLOCK: Missing required context (actor_user_id).
idempotency_keyRequiredstringBLOCK: Missing required context (idempotency_key).
request_idRequiredstringBLOCK: Missing required context (request_id).
system_instructionsRequiredstringBLOCK: Missing required context (system_instructions).
user_inputRequiredstringBLOCK: Missing required context (user_input).
workflowRequiredstringBLOCK: Missing required context (workflow).
workflowNameRequiredstringBLOCK: Missing required context (workflowName).

Decision behavior (PASS / WARN / BLOCK)

AI Safety Gate is fail-closed by design. If validation or approval polling cannot be safely completed (missing required context, invalid responses, timeouts, or unexpected errors), execution must stop.
StatusWhat ASG returnsWhat you must do
PASSAllowed by safety policy.Execute the action.
WARNReview required by safety policy.Do not execute. Persist decision_id and wait for human approval. Approval does not modify policies and does not change the original decision — it authorizes execution for this specific decision_id.
BLOCKBlocked by safety policy.Do not execute. Fix payload/context and re-validate.

Policy behavior

This ActionKind is evaluated against managed policies derived from the managed policy catalog.
Related policies: Data policies
Policy summarySeverityRequired contextThresholdsApprovalRemediation
Block when required integration context is missing.BLOCKworkflow, workflowName, system_instructions, user_input, actor_user_id, account_id, request_id, idempotency_keyInclude the required context fields so the gate can make a deterministic decision and record an auditable event.

Approval behavior

This ActionKind has no managed WARN policies in the managed catalog, but WARN can still occur (for example, schema mismatch normalization).
WARN requires human approval. Approval authorizes execution for the same decision_id and does not modify policies or change the original decision record.
WARN responses include a decision_id and an approval_token.

Common errors

MistakeWhat happensFix
Using an unknown action_kindBLOCK: Unknown action_kind. Supported action_kind values: money.move, money.refund, money.credit, money.payout, billing.change, billing.cancel, identity.role_change, identity.auth_change, identity.user_create, identity.user_delete, admin.access, data.export, data.import, data.read, data.write, data.delete, data.purge, data.share, messaging.send, messaging.broadcast, messaging.webhook, integrations.connect, integrations.disconnect, integrations.scope_change, workflow.execute, workflow.modify, support.case_update.Fix: Unknown action kind
Using an unsupported action_typeBLOCK: Unknown action_type for action_kind integrations.disconnect. Supported action_type values: disconnect.Use one of the allowed values listed above.
Omitting required contextBLOCK: Missing required context (workflow, workflowName, system_instructions).Fix: Missing context
Sending the wrong JSON typesWARN: Schema mismatch. Proceeding with enforcement using normalized input.Fix: Schema mismatch
Approval token generation failsApproval token generation failed. Blocking by default.Treat as BLOCK (fail closed). Retry validation later.

Copy-paste examples

Minimal

json
{
  "action_kind": "integrations.disconnect",
  "action_type": "disconnect",
  "ai_output": {},
  "context": {
    "account_id": "example",
    "actor_user_id": "example",
    "idempotency_key": "example",
    "request_id": "example",
    "system_instructions": "example",
    "user_input": "example",
    "workflow": "example",
    "workflowName": "example"
  }
}

Full

json
{
  "action_kind": "integrations.disconnect",
  "action_type": "disconnect",
  "ai_output": {},
  "context": {
    "account_id": "example",
    "actor_user_id": "example",
    "idempotency_key": "example",
    "request_id": "example",
    "system_instructions": "example",
    "user_input": "example",
    "workflow": "example",
    "workflowName": "example"
  }
}
Legal & Responsibility Notice
Summary
Informational only
Provided for general guidance. Not legal, compliance, security, or professional advice.
You control implementation
You are responsible for policies, prompts, integrations, workflows, and regulatory requirements.
Liability limitation
To the maximum extent permitted by law, the company disclaims liability for losses arising from use of this documentation or implementations based on it.