HelpSpot
for LuumenAI
Read HelpSpot queues and request history, then update requests as approved steps
Connect HelpSpot and Luumen can read your queues the way you do: saved filters, inbox, search across customers and states, and the full history of any one request. When something needs to change — a reassignment, a status move, a note on the thread — Luumen shows the exact update first and waits for your approval by default. Access uses an API key.
The HelpSpot toolbox
10 tools: 7 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Current UserReturn the connected HelpSpot staff user's identity, defaults, and support capabilities without authentication tokens.
- ReadGet RequestReturn one support request with normalized history and optional time total; fail clearly when HelpSpot returns its sparse HTTP-200 missing-request shape.
- ReadList FiltersList the connected staff user's saved and built-in queue filters, including symbolic selectors such as inbox and myq.
- ReadList Saved ResponsesList reusable response templates available to the connected staff user, either all templates or the user's ten most-used templates.
- ReadList Support OptionsList IDs and labels used to categorize, assign, route, or set the status of HelpSpot requests.
- ReadRun FilterReturn one cursor-controlled page of request summaries from a saved or built-in HelpSpot queue filter.
- ReadSearch RequestsSearch support requests by text, customer, state, assignment, or date and return one concise cursor-controlled page.
- WriteCreate RequestCreate a staff-side support request with an initial customer-visible or internal note. Approval by default
- WriteSet Request SubscriptionSubscribe or unsubscribe a staff user from updates to one support request. Approval by default
- WriteUpdate RequestUpdate request, customer, assignment, and state fields and optionally append one customer-visible or internal note. Approval by default
One prompt, start to finish
What a governed HelpSpot run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create request, set request subscription, update request — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to HelpSpot — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Put HelpSpot to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.