Despliegue en cuentas

Plan a bulk dashboard deployment to accounts

dashboards.bulk.deploy_plan

From a workspace, computes the deployment plan of up to 30 templates (published system templates or the workspace's published ones; ids from dashboards.templates.list) over its active accounts (all, or child_org_ids): for each template × account, whether it is new, already_deployed or incompatible (missing_platforms: platforms the account has no connection for), and the suggested data_source_mapping (the first connection of each platform; the internal CRM source is always available). counts has how many items are in each status over the whole plan; data, the items, filtered by status (use status new to get the ones to deploy) and paginated by cursor (limit 50 by default). Writes nothing; pass the new items to dashboards.bulk.deploy. Owners and admins of the workspace.

Alcance

dashboards:read

Permiso

Ver el módulo · Solo owner, admin

Tool del MCP

dashboards_bulk_deploy_planEn la superficie completa; en la compacta, mb_execute_operation con id: "dashboards.bulk.deploy_plan".

Costo declarado: hasta 1500 lecturas y 0 escrituras por llamada (cuentan en el cupo diario).

Parámetros

Respuesta

Errores

Ejemplo

curl -X POST "https://api.mb-suite.com/v1/dashboards/bulk/deploy-plan" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "template_ids": [
    "TEMPLATE_ID"
  ]
}'

Probar con tu API key de prueba

Con una API key de prueba el pedido va siempre a tu organización de práctica: datos de ejemplo que puedes reiniciar.

curl -X POST "https://api.mb-suite.com/v1/dashboards/bulk/deploy-plan" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "template_ids": [
    "TEMPLATE_ID"
  ]
}'

Create dashboards in many accounts at once

dashboards.bulk.deploy

From a workspace, creates up to 200 linked dashboards in its accounts, one per deployment (template_id, template_source SYSTEM or INHERITED, child_org_id, data_source_mapping; typically the new items of dashboards.bulk.deploy_plan). Each one is checked in its account as if the person did it there: an active account of this workspace that the credential reaches, edit access to Dashboards in it, a published template, and data sources connected to that account. A failed item does not stop the rest: results says, per item, the new dashboard_id or the error code. Outside the screen it requires a dry run and a confirm_token: the dry run runs the same checks item by item and names each template and account with what would happen (created, or the error code). Owners and admins of the workspace.

Pide confirmación: primero dry_run: true (vista previa y confirm_token, que vale 10 minutos y una sola vez), después el mismo cuerpo con confirm_token. En unas pocas, solo con ciertos datos: la descripción dice cuándo. Por qué y cómo: Vista previa y confirmación.

Alcance

dashboards:write

Permiso

Editar en el módulo · Solo owner, admin

Tool del MCP

dashboards_bulk_deployEn la superficie completa; en la compacta, mb_execute_operation con id: "dashboards.bulk.deploy".

Eventos que puede emitir

dashboards.dashboard.created

Costo declarado: hasta 700 lecturas y 200 escrituras por llamada (cuentan en el cupo diario).

Parámetros

Respuesta

Errores

Ejemplo

curl -X POST "https://api.mb-suite.com/v1/dashboards/bulk/deploy" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "deployments": [],
  "dry_run": true
}'

Probar con tu API key de prueba

Con una API key de prueba el pedido va siempre a tu organización de práctica: datos de ejemplo que puedes reiniciar.

curl -X POST "https://api.mb-suite.com/v1/dashboards/bulk/deploy" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "deployments": [],
  "dry_run": true
}'