myITprocess
Overview
myITprocess is Kaseya's vCIO / strategic IT planning platform for MSPs.
The Bumblebee integration exposes the full myITprocess Public API through a
single send_request tool — the agent chooses the endpoint
(e.g. /clients, /reviews, /recommendations) and query parameters based
on the request.
The public API is read-only, so Bumblebee can list and retrieve data but cannot create or modify myITprocess records.
Prerequisites & Setup
Before setting up the myITprocess integration, you need:
- A myITprocess tenant
- Account access with permission to manage API keys
- An API key generated from Account Settings → API Keys
Create an API Key in myITprocess
- Sign in to your myITprocess tenant as an administrator
- Open Account Settings
- Select the API Keys tab
- Click Add API key, give it a descriptive name (e.g. Bumblebee)
- Copy the key immediately — store it somewhere secure
Vendor documentation:
- Public API overview: help.myitprocess.kaseya.com
- Knowledge base article: helpdesk.kaseya.com
- Swagger UI: reporting.live.myitprocess.com
Configure in Bumblebee
- Go to the Integrations page in Bumblebee
- Select myITprocess
- Paste your API Key
- Save the configuration
- Run a test request (e.g. list clients) from the validation card
API Limits
- 50 requests per minute per IT Provider
Bumblebee handles 429 responses with exponential backoff and retry.
Available Tools
Core (1 tool)
- send_request — Thin wrapper around the myITprocess Public API. Required: endpoint (str, e.g.
"/clients"or"/recommendations/42/configurations"). Optional: method (str, default"GET"), params (object, query string), data (object, request body — reserved for future write endpoints).
The agent selects the myITprocess endpoint and parameters based on the workflow. Supported resources include:
| Resource | List endpoint | Notes |
|---|---|---|
| Clients | /clients | All clients, active and inactive |
| Reviews | /reviews | Active client reviews |
| Categories up for review | /reviews/categories/overdue | Categories whose review is overdue |
| Users | /users | Active myITprocess users |
| Initiatives | /initiatives | Strategic initiatives |
| Findings | /findings | Review findings |
| Meetings | /meetings | Upcoming, in-progress, past, cancelled |
| Recommendations | /recommendations | All recommendations |
| Recommendation configurations | /recommendations/{id}/configurations | IT Glue configurations linked to a recommendation |
All list endpoints accept three shared optional query parameters:
queryFilters— list of filter objects withfield,predicate(equal,notEqual,greaterThan,lessThan,contains),condition, and optionaloperator(and,or).sortingRules— list of sort objects withfieldanddirection(asc,desc).paginationRule— object withpage(default 1) andpageSize(default 100).
Dotted field paths address nested fields (e.g. client.name). Arrays are not filterable/sortable.
Example calls
# First page of clients
send_request(
endpoint="/clients",
params={"paginationRule": {"page": 1, "pageSize": 100}},
)
# Active clients only, newest first
send_request(
endpoint="/clients",
params={
"queryFilters": [
{"field": "isActive", "predicate": "equal", "condition": True}
],
"sortingRules": [{"field": "createdDate", "direction": "desc"}],
},
)
# IT Glue configurations linked to a recommendation
send_request(endpoint="/recommendations/42/configurations")