Something not working? Start here.
The fastest route is usually to ask Hoopi itself — type /help in your workspace and it will route you. Otherwise, the common issues are below.
Setup & install
Adding Hoopi, inviting the team, workspace settings.
Connections
Authorizing tools, scopes, expired tokens.
Tasks & results
Why an output looked wrong and how to correct it.
Standing work
Schedules, owners, failures and retries.
Billing & credits
Usage, rollover, top-ups and invoices.
Admin & security
SSO, permissions, approvals and audit logs.
The six things that come up most
The token has almost certainly expired or been rotated. An admin can re-authorize that single connection from Workspace settings → Connections; nothing else is affected and standing jobs resume on their next run.
Check the job's thread — failures post there with the reason and a retry button. The most common causes are an expired connection, a source system rate-limiting a large pull, or a schedule set in a different timezone than expected.
Reply in the thread with the correction and point at a good example. Hoopi writes the correction into the relevant skill, which you can then open and edit directly under Workspace settings → Skills.
Approval rules are set per action class by your admins. If an action has been approved unmodified for a month, that is usually a good candidate to drop the gate on — review it under Workspace settings → Approvals.
Admins can top up immediately from Billing, or enable auto top-up with a monthly ceiling. Usage by requester is exportable as CSV if you want to see where it went first.
Standing work has an owner independent of who created it, so reassign the owner under Automations. Connections they authorized should be re-authorized by someone still with the company; Hoopi flags these as orphaned in the admin panel.
About the product
Hoopi is an AI teammate that lives in Slack or Teams. You message it like a colleague, it connects to the systems your company already runs on, and it returns finished work — reports, drafts, updated records, working internal tools — with its sources and reasoning attached.
A chat assistant answers in a window. Hoopi has scoped access to your stack, so it can read the CRM, cross-check the warehouse system, update the ticket and post the result. It also keeps team context between requests, so what you teach it once holds.
Adding Hoopi to your workspace takes a couple of minutes. Most teams connect their first three systems and get a delivered task back inside the first session. A full rollout across a department typically lands in one to two weeks.
More than 3,400 tools, including the CRMs, drives, ticketing systems, finance platforms, data warehouses, ad networks and email providers most teams run. If something is missing, Hoopi can work with any documented API, and our team will build the connector for enterprise plans.
No. Your content, credentials and outputs are never used to train any model. Data is encrypted in transit and at rest, and you can delete a workspace and its history at any time.
Hoopi asks before any irreversible action — external sends, payments, deletions, published posts. Your admins choose which actions need approval and who can give it. Connections can be left read-only indefinitely.
No. You buy credits for the team, and everyone can use Hoopi. Adding a colleague costs nothing; the only thing that moves your bill is how much work you hand over.
Every request consumes credits based on the model tier and how much work it takes. Quick lookups run 100–300 credits, multi-system workflows 500–1,500, and full project builds 2,000–5,000. Unused credits roll over, and you can cap spend.
All systems operational
Live status, incident history and scheduled maintenance are published at status.hoopi.com.
Give Hoopi your worst recurring task
Start free with $100 in credits. No card, no per-seat licence, no migration — just hand over one job and see what comes back.
$100 in credits included · Team plans from $100/month · Cancel any time