Connect Crewhu

Crewhu is a customer satisfaction (CSAT) and employee recognition platform built for MSPs. It sends a one-click survey when a ticket is resolved, replied to or signed off, scores the answers, and turns them into badges, contests, prizes and dashboards. Your Crewhu account holds your own employees and the survey answers from all of your clients.

Connecting Crewhu to StackJack gives your AI assistant a family of crewhu_ MCP tools. MCP (Model Context Protocol) tools are the standardized commands an AI assistant can call through StackJack. With them, your AI can:

• Read the survey answers - the rating, the comment, the client and the ticket behind each one, and which technicians were credited, for client reporting and QBR preparation
• Resolve people - turn the employee ids on a survey, a badge or a prize redemption into names, departments and positions, so satisfaction can be reported per technician
• Read recognition activity - the badges available, and the badges given, to whom, and for which survey
• Read prizes - the prize catalog and the redemption history
• Update a contest leaderboard (on Pro plans) - push the results of an External Metric into a Crewhu contest, for example "tickets closed per technician this week"

How StackJack authenticates to Crewhu

Crewhu gives you a single Open API access token. You paste it into StackJack and that is the whole setup: no client ID, no second secret, no web address to enter, and nothing to renew on a schedule.

What you need in Crewhu

• An Open API token. Crewhu's pricing page lists the Open API on the Listen, Recognize and Grow plans. Crewhu also names a fourth current plan, Listen+, and still has older legacy plans, and it does not document whether either of them includes the Open API. The pricing page also describes each connection as a premium integration, and Crewhu does not say whether that is charged per token, so ask Crewhu if the option is missing or you are asked to pay.
• The Integration permission on your Crewhu profile. Only a profile that can reach Settings > Integrations can create a token.
• For the contest update only: a Crewhu plan that includes Automated Contests (Crewhu's pricing page ticks it for the Grow plan only), the Contests Update via API switch turned on under Settings > Contests, an External Metric that already exists in Crewhu, and the Contests permission on the profile that set it up.

Steps

1. Open Integrations in Crewhu. Sign in, then go to Settings, then Integrations. Some Crewhu pages call the same screen Settings > General > Integrations.
2. Add an integration. Click +Add, type a description such as "StackJack", and confirm. A description that names StackJack makes it obvious what to deactivate later.
3. Copy the token. Click Copy Token. Treat it as a password: anyone holding it can read your survey answers, which include your clients' contact details.
4. Paste it into StackJack. Open Connectors, choose Crewhu, and paste the token as the Open API Access Token. There is nothing else to enter.
5. Run a Test Connection. StackJack asks Crewhu for a single employee, which reads almost nothing and changes nothing.

Crewhu does not say how long a token lasts. As far as Crewhu documents, a token stays valid until someone deactivates it under Settings > Integrations. If you think a token has been exposed, deactivate it there, create a new one, and paste the new one into StackJack.

What to know before your AI uses this connector

Everything is account-wide, and there is no customer filter

One token covers your whole Crewhu account. Your individual client companies exist in Crewhu only as data inside each survey (the customer's name, contact name, email and phone), not as separate accounts, and Crewhu offers no way to ask for one client's surveys. The only filters it documents are the date a survey was last updated and whether it is active.

So "CSAT for Acme last quarter" is done in two steps: your AI asks for that quarter's surveys by date, reads them page by page, and filters on the customer details itself. Ask your AI to name the date window first. Without one, the whole survey history is read, one page of at most 100 at a time.

The rating is a string, and deleted surveys are left out by default

Each survey carries a rating of 5 (positive), 0 (neutral) or -5 (negative) as text, plus a separate label you can customize in Crewhu. Averaging the labels gives nonsense, so ask your AI to work from the rating.

By default StackJack asks Crewhu for active surveys only, because a report that counts deleted or never-completed surveys is wrong. Ask your AI to include inactive surveys if you really want both.

Paging

Crewhu returns up to 100 records per page and numbers pages from 1. Your AI keeps asking for the next page until Crewhu says there is none. Crewhu documents a lower default of 20 per page and, on one older page, a higher maximum of 1,000; StackJack uses the 100 from Crewhu's current reference.

The contest update replaces, it does not add

The one tool that changes anything pushes External Metric results into a contest. Crewhu says the update "won't sum up with the existing results, but replace it with the last update", and contests drive rewards, so a wrong call overwrites standings your employees can see. It is marked destructive, needs the Pro tier, and is the only tool that does.

Crewhu does not document what a repeated update does, or what a successful one answers, so check Settings > Contests > View Updates Log before you send an update again. Crewhu records every update there, which is also where to look if a leaderboard does not move.

Whether your AI application asks you to confirm before running a destructive tool depends on that application's own settings. See Destructive tools and confirmation and review that setting before you let an assistant near the contest tool.

Survey answers contain personal data

Each survey includes your client's contact name, email and phone, the free-text comment they wrote, and the IP address they answered from. StackJack returns all of it exactly as Crewhu holds it and does not remove anything, so anything your AI application does with a survey follows that application's own data rules.

Plans and limits

Reading is available on the Free tier. Updating a contest is Pro. Business reaches the same tools as Pro and differs by monthly call quota.

See the generated Crewhu tool reference for the current inventory, plan assignment, input schemas, and destructive-action labels.

Crewhu publishes no rate limit, so StackJack paces requests conservatively and backs off on its own if Crewhu throttles it. Pacing smooths a burst; it does not guarantee that every call arrives. If a wide read comes back throttled or times out, narrow the date window and try again, and check whether a write landed before repeating it. See Retrying a failed or timed-out write.

Several Crewhu accounts

If you hold more than one Crewhu account, add one connection per account from the connector's card, name each one after the account, and your AI names it on each call. Omit the name and the call runs against your default connection. Pin an endpoint to one connection when an AI should never reach past a single account. See Several connections of one connector.

This separates whole accounts only. Inside one account there is still no client separation, as described above.

Troubleshooting

"Crewhu did not receive an Open API token" - no token reached Crewhu, usually because the token field is empty. Create a token under Settings > Integrations (+Add, then Copy Token), paste it into the Crewhu connector, and run Test Connection.

"Crewhu rejected the Open API token" - the token is not one Crewhu recognizes. It may have been deleted, or copied with a character missing. Create a new one and paste it in. You need the Integration permission on your Crewhu profile to create one.

"Crewhu says the Open API token has been deactivated" - check Settings > Integrations. Switch the integration back on, or create a new token. Crewhu says integrations holding a deactivated credential will not work.

"Crewhu answered 403 Forbidden" - Crewhu's reference lists this status without saying what causes it. Check that the token is still active and that your Crewhu plan includes the Open API. For the contest update, also check that your plan includes Automated Contests and that Contests Update via API is switched on.

"Crewhu could not read the filter" - the date window was not a UTC date-time such as 2026-06-01T00:00:00.000Z. Ask your AI to use that form.

A report covers the wrong clients, or the whole history - the date window was missing or too wide. Crewhu has no customer filter, so narrow by date first and let your AI filter on the customer details inside each survey.

The contest leaderboard did not change - check the three prerequisites (a plan with Automated Contests, the Contests Update via API switch, and an existing External Metric whose code matches), and read Settings > Contests > View Updates Log in Crewhu for the reason.

Nothing works at all and the token is definitely right - confirm the integration is active in Crewhu and that the token was created in the Crewhu account that holds the surveys you are asking about.

Crewhu tools

crewhu_ · 7 tools · Free 6 · Pro 1

Surveys

Employees

Recognition

Prizes

Contests