Outcome
Get which of the organization's Nexus WhatsApp connections this workspace sends WhatsApp template steps through when the enrolled contact's seat has no number of its own (seats.whatsapp.set); connectionId null: the organization default. A step whose send Nexus refuses for want of a connection holds as whatsapp_not_configured; a refusal of Engage's access holds as whatsapp_not_permitted.
Before you start
- Verify the intended environment, signed-in credential, authorized organization and the action permission workspace:read.
- Discover and select an authorized canonical Engage workspace. Pass resourceType=workspace and resourceId separately from action input.
Discover the target
topolo whoami --json
topolo actions get app_topolo_engage.sending.whatsapp.get --json
topolo workspaces list topolo-engage --json
Set ENGAGE_WORKSPACE_ID to the identifier of the selected authorized workspace.
Input contract
This action accepts an empty input object ({}). Resource context is supplied separately when required.
Validate, plan and execute
Build payload.json from the current schema and discovered identifiers. The action description above defines its behavior, limits, side effects and declared errors.
: "${ENGAGE_WORKSPACE_ID:?Set ENGAGE_WORKSPACE_ID to your selected workspace identifier}"
topolo actions validate app_topolo_engage.sending.whatsapp.get --data @payload.json --json
topolo actions plan app_topolo_engage.sending.whatsapp.get --resource-type workspace --resource-id "$ENGAGE_WORKSPACE_ID" --data @payload.json --json
Execute the unchanged validated read.
: "${ENGAGE_WORKSPACE_ID:?Set ENGAGE_WORKSPACE_ID to your selected workspace identifier}"
topolo actions call app_topolo_engage.sending.whatsapp.get --resource-type workspace --resource-id "$ENGAGE_WORKSPACE_ID" --data @payload.json --json
For MCP, use topolo_get_action, topolo_validate_action, topolo_plan_action and topolo_call_action. Pass resource context separately where required; confirm:true is required for mutations.
Captured successful requests and responses
Captured HTTP 200 · captures real settings routes, schema refusals, permissions, scope, read-back and recovery without network access
Action input
{}
Actual local response
{
"whatsapp": {
"connectionId": null,
"updatedAt": null,
"updatedBy": null
}
}
Source test: captures real settings routes, schema refusals, permissions, scope, read-back and recovery without network access. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.
Captured HTTP 200 · captures real settings routes, schema refusals, permissions, scope, read-back and recovery without network access
Action input
{}
Actual local response
{
"whatsapp": {
"connectionId": "conn_whatsapp_fixture",
"updatedAt": "2026-10-06T08:30:00.000Z",
"updatedBy": "user_1"
}
}
Source test: captures real settings routes, schema refusals, permissions, scope, read-back and recovery without network access. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.
Captured HTTP 200 · captures real settings routes, schema refusals, permissions, scope, read-back and recovery without network access
Action input
{}
Actual local response
{
"whatsapp": {
"connectionId": null,
"updatedAt": "2026-10-06T08:30:00.000Z",
"updatedBy": "user_1"
}
}
Source test: captures real settings routes, schema refusals, permissions, scope, read-back and recovery without network access. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.
Effects and response meaning
- Get which of the organization's Nexus WhatsApp connections this workspace sends WhatsApp template steps through when the enrolled contact's seat has no number of its own (seats.whatsapp.set); connectionId null: the organization default. A step whose send Nexus refuses for want of a connection holds as whatsapp_not_configured; a refusal of Engage's access holds as whatsapp_not_permitted.
Verify the outcome
- Check the response against the declared output schema and the requested operation. For mutations, use the action-specific read described in the action description before any dependent operation.
Recover
For an uncertain result, inspect current retained state with a read action before retrying. Do not replay a mutation unless its contract explicitly guarantees idempotency.
Refused requests
No refusal response for this action is present in the selected capture set.
Error recovery
Related actions
- Get sending settings
- Update sending settings
- Get compliance footer
- Update manual compliance footer
- Connect compliance footer to Brand kit
- Disconnect compliance footer from Brand kit
- Get sender health policy
- Update sender health policy
- Update WhatsApp sending settings
Evidence and limits
-
/api/sending-settings/whatsapp -
Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.
-
Widget/bootstrap use actual app handler but mocked worker runtime and app identity.
-
No gateway execution, live permissions, external delivery or deployed proof.
These are local route captures with synthetic identity and simulated dependencies. They do not prove live authorization, gateway execution, production state, or external delivery.