Connect Gorelo
Gorelo is a cloud RMM + PSA platform for MSPs — remote monitoring and management of endpoints alongside a ticketing/CRM system for clients, contacts, and alerts. Connecting Gorelo to StackJack lets…
Written By Christopher Scaminaci
Last updated 6 days ago
Gorelo is a cloud RMM + PSA platform for MSPs — remote monitoring and management of endpoints alongside a ticketing/CRM system for clients, contacts, and alerts. Connecting Gorelo to StackJack lets your AI assistant work with your Gorelo clients, contacts, RMM agents, and tickets through its public API.
Connecting Gorelo gives your AI a focused set of gorelo_ MCP tools — MCP (Model Context Protocol) tools are the standardized commands an AI assistant can call through StackJack. With them, your AI can:
- Look up your clients (companies) and their locations, and the contacts (people) attached to them
- Inventory your RMM agent devices and your custom (non-agent) assets, with full detail
- Create, update, and delete clients and contacts
- Raise alerts against a client
- Work tickets end to end — list, read, open, update, and delete them, and read the ticket statuses, tags, and types needed to fill them in
- Read and post ticket conversations — comments, side conversations, and approvals, including uploading a file to a ticket
- Track time — list, read, log, amend, and delete time entries across tickets and tasks
- Read billing setup — billing roles, work types, and contracts, and download an invoice PDF
- Resolve your organization's own users and groups (technicians and teams) for ticket assignment
How StackJack authenticates to Gorelo
Gorelo uses an API key sent in the X-API-Key header on every request. Generate it from Settings → Integrations, open the API integration with the cog icon, and choose its permission scope. There is no OAuth or refresh-token flow. Gorelo's public API guide does not publish an automatic-expiration schedule, so plan an intentional replacement and revoke the old key when rotation is complete.
Per-key scopes matter. When you create a key in Gorelo you pick which areas it can touch — contacts, clients, assets, billing, time, alerts, tickets, organization. If a tool returns a 403, it means the key lacks that endpoint's scope, not that your whole account is blocked. Grant the key the areas your AI needs and the 403 goes away.
Regions
Gorelo is region-hosted. StackJack shows a Region dropdown — US (api.usw.gorelo.io) or AU (api.aue.gorelo.io) — that sets the host StackJack calls. Pick the region your Gorelo account lives in. The two regions expose the same tools; only the host differs.
Before you begin
- In StackJack: you need a role that can manage connectors (tenant Owner, a co-owner, or an Administrator).
- In Gorelo: you need admin access to Settings → Integrations to configure the API integration.
- Know your region — US or AU, which you'll select in StackJack.
Step 1 — Create an API key in Gorelo
- Sign in to Gorelo as an admin and go to Settings → Integrations.
- Click the cog icon for API, then choose Generate New Key.
- Enter a descriptive name (for example, "StackJack Integration") and an optional description.
- Choose the permission scope the key should grant. Include at least Clients (read) so StackJack's save-time validation can list clients, plus the areas your AI will use.
- Click Generate and copy the key.
Step 2 — Add the credentials in StackJack
- In the StackJack portal, open Connectors.
- Select the Gorelo tile to open its details drawer.
- Use How To Connect to review the inline steps, then choose Configure in the drawer footer.
- Choose your Region (US or AU). The connection host is set from your choice.
- Paste your Gorelo API key and click Save.
What happens when you save
- The API key is stored encrypted in Azure Key Vault — never in the StackJack database, and never shown back to you.
- If this is the first time you configure Gorelo, a Free-tier subscription for the connector is created automatically so its Free tools work right away.
- StackJack immediately live-validates the key by listing clients. The credential remains saved if that upstream check fails so you can correct the region or scope without re-entering every field.
- The Configure form collapses while the details drawer stays open. The drawer shows Connected and Valid after success, or Needs Attention with a Re-test action after failure.
Because validation reads your clients, the key needs at least the Clients (read) scope to validate cleanly. A key scoped only to ticket creation can still be valid for that purpose but will report a 403 during save-time validation.
Plans and available tools
See the generated Gorelo tool reference for the current inventory, plan assignment, input schemas, and destructive-action labels.
Gorelo has no per-user sign-in for its API, so all AI traffic authenticates as the single API key — there is no per-user attribution. Current pricing and quotas are shown in the portal's Billing page and at checkout.
Deleting is real, and it is a soft delete. Gorelo's public API does expose delete operations, and StackJack surfaces them as clearly labeled destructive tools. Each one deactivates the record rather than erasing it, so history survives and the record disappears from lists. Two are worth knowing before you ask your AI for one: deleting a ticket also deletes its time entries, and deleting a client or contact is refused outright when other records still depend on it, telling you what is in the way instead of quietly detaching it. The Gorelo web app warns and proceeds in those cases; the API stops. Deleting something already deleted is safe to repeat.
What the Gorelo public API does not expose. There is no way to list or read your uptime checks — your AI can delete one by its ID, but it can only learn that ID from a ticket the check is linked to, or from the Gorelo web app.
Rate limits
Gorelo publishes no numeric API quota. StackJack applies a conservative per-tenant pace (about 120 requests per minute) and honors any 429 backoff, so a long inventory read is usually just slower. Pacing is not a guarantee: retries are bounded, so a wide enough read can still come back throttled or time out. Narrow the read, honour any retry delay the vendor sends, and check whether a write landed before repeating it — see Retrying a failed or timed-out write.
Rotating or replacing the credentials
Create a replacement under Settings → Integrations → API, update the saved key in Gorelo's StackJack details drawer, and choose Re-test. After the replacement works, use Revoke on the old key in the same Gorelo API settings. Revocation is immediate.
Disconnecting Gorelo
Choose Disconnect in the Gorelo details drawer and confirm. StackJack deletes its stored credential and stops making Gorelo calls. Disconnecting does not revoke the upstream API key; revoke it separately under Settings → Integrations → API. Connector subscription changes are separate from credential disconnection.
Troubleshooting
Gorelo tools
gorelo_ · 46 tools · Free 25 · Pro 21
Contacts
Clients
Assets
Billing
Time Entries
Alerts
Tickets
Ticket Conversations
Attachments
Uptime
Organization
More in Connector guides
Connect Acronis Cyber Protect CloudConnect Action1Connect AddigyConnect AlertOpsStill need help? Ask the team