monday.com templates let you create ready-made boards (and multi-board solutions) from a predefined structure. The use_template mutation installs a template as a background job and immediately returns a process_id. Because an installation can take anywhere from a few seconds to several minutes, you poll template_installation_status with that process_id to track progress and retrieve the created board IDs.

How to find a template ID

There is currently no public query to list installable templates. To get a template_id:

• From the monday.com UI: Open the template in the Template Center and copy the numeric ID from the page URL. This is the AppFeature ID you pass as template_id.
• As an authorized partner: Use the internal app_features query if you have access. A public discovery API is not yet available.

Queries

Get template installation status

• Required scope: none beyond a valid API token
• Returns a TemplateInstallationStatusResult describing the current state of a template installation, or null if the process_id is unknown, expired, or belongs to a different account
• Can be queried directly at the root

query {
  template_installation_status(process_id: "c072acaf68e0be9fd0e451f0884383b6") {
    process_id
    status
    is_complete
    is_failed
    board_ids
    board_ids_map {
      source_board_id
      created_board_id
    }
  }
}

Arguments

Fields

Mutations

Use template

Required scope: workspaces:write

Installs a template as a background job. Returns a Template containing a process_id. Pass that process_id to template_installation_status to poll for completion and retrieve the created board IDs.

mutation {
  use_template(template_id: 1234567890, destination_workspace_id: 9876543210) {
    process_id
  }
}

Arguments

Polling pattern

The installation runs asynchronously, so the recommended flow is:

1. Call use_template and store the returned process_id.
2. Poll template_installation_status with that process_id every 2–5 seconds.
3. Stop polling when is_complete is true, is_failed is true, or the result is null (the record expired).

# Step 1: start the installation
mutation {
  use_template(template_id: 1234567890, destination_workspace_id: 9876543210) {
    process_id
  }
}

# Step 2: poll until done (every ~3 seconds)
query {
  template_installation_status(process_id: "c072acaf68e0be9fd0e451f0884383b6") {
    status
    is_complete
    is_failed
    board_ids
    board_ids_map {
      source_board_id
      created_board_id
    }
  }
}

A successful COMPLETE response looks like this:

{
  "data": {
    "template_installation_status": {
      "status": "COMPLETE",
      "is_complete": true,
      "is_failed": false,
      "board_ids": ["1234567890", "1234567891", "1234567892"],
      "board_ids_map": [
        { "source_board_id": "9876543210", "created_board_id": "1234567890" },
        { "source_board_id": "9876543211", "created_board_id": "1234567891" },
        { "source_board_id": "9876543212", "created_board_id": "1234567892" }
      ]
    }
  }
}

Important caveats

• Board content is not ready during IN_PROGRESS. board_ids is populated incrementally as boards are created, but during IN_PROGRESS they exist as empty shells — no items, broken mirror columns, no automations. It is safe to store the IDs early, but do not read from or write to board content until status == COMPLETE.
• Records expire after 1 hour. Polling template_installation_status more than 1 hour after the use_template call returns null.
• Timeout safety net. A stuck IN_PROGRESS record is converted to FAILED after 30 minutes to prevent indefinite polling.
• Cross-account security. Querying a process_id that belongs to a different account returns null (indistinguishable from an expired or invalid process_id).
• Rate limiting. Polling is capped at 60 requests per minute per account by default.

Error cases

The use_template mutation can return the following errors: