Dashboard operations

Recent dashboard workflows are available through a reviewed operation catalog. Each operation also has a named MCP tool with the same name and input schema. The REST handler and dashboard use shared implementations, including ownership, entitlement, contact and billing safeguards.

Discover available operations

GET /api/v1/rest/dashboard-operations?workspace=WORKSPACE_ID
Authorization: Bearer seny_…

The catalog requires org.read and lists the operations allowed by your token’s capabilities. Execution requires a user-scoped token and the operation’s own capability. Capabilities remain bounded by both the token and the user’s current access.

Run an operation

POST /api/v1/rest/dashboard-operations?workspace=WORKSPACE_ID
{
  "operation": "list_file_import_runs",
  "input": { "orgIntegrationId": "INTEGRATION_UUID", "limit": 10 }
}

Success returns { "data": … }. Unknown operations, unsupported fields and invalid inputs return 400. Missing capabilities return 403. There is no endpoint for invoking arbitrary dashboard functions.

Supported workflows

  • File imports, PBS and website inventory sync, dynamic integration choices, reusable tool settings and tool UI components.
  • Caller-ID verification, number-port requests, live call transfers and explicit contact-frequency overrides.
  • Shared Overview views and conversation CSV exports.
  • Meeting dispatch, walkthrough builds, AI visibility scans and schedules, notification departments and session replay.
  • Role templates, branded team invitations, authorized-app revocation, dealership-serial requests, agent-name propagation, deploy-checklist attestations and agent moves.

Use the OpenAPI reference for each operation’s current schema, permission and effects. For MCP, call list_dashboard_operations or inspect tools/list, then call the operation by name with its input fields and optional workspace.

Effects and confirmation

Some operations spend credits, place verification calls, send email or SMS, execute integration tools, change live routing, or revoke access. Review their descriptions before execution. A write-capable sample capture requires allowWrite: true; a walkthrough build requires approval of its quoted credits. Staging contact withholding remains enforced. Client-system writes require recorded permission.

Agent-name propagation writes a draft for review and separate publishing. Most ordinary agent PATCH fields apply immediately. The existing invitation endpoints return links without sending mail; use the catalog’s invitation operations for dashboard-equivalent branded delivery and role-template linkage. Agent moves require an explicit destination and an explicit decision about moving conversation/customer history; the token must have agent and integration write access in both workspaces.

Deliberate dashboard-only flows

Purchases, paid checkout/subscription changes and local trial extension, workspace deletion, browser sign-in/OAuth consent, MFA and impersonation, and staff-only environment sync remain session flows. Binary uploads outside the existing knowledge-document signed-upload API remain in the dashboard. Existing client trial start/end and plan/payer overrides have their own API routes; ending a Stripe-backed trial can cancel its subscription. The Help assistant has a separate tool ceiling; it does not gain every external connector capability.