Resolve the ticket, not just answer it.
A support agent that can only reply still hands the work to a person. With Hoook it can look up the order, issue the refund and update the ticket.
await hoook.triggers.deploy({ userId, id: "stripe-payment-failed", webhookUrl })
✓ listening to Stripe for u_42
invoice.payment_failed · verified · deduplicated
POST https://your-app.com/agent/events
agent: opened Linear issue ENG-812 and told #billing
The same integration, shipped.
Without Hoook
- The bot answers, then escalates anything that needs an action
- People copy details between the helpdesk, billing and the CRM
- Integration work crowds out the agent your customers pay for
- Every API change is a fire drill for whoever built that connector
With Hoook
- The agent checks the order, issues the refund and closes the loop
- Every system updated in one step, with the history in the ticket
- Your team builds the agent. Integrations come from Hoook
- API changes are absorbed before they reach your users
How Hoook works for support agents
- 01
Add Hoook to your agent
Install the SDK or add the hosted MCP server. No infrastructure to run.
Claude Codeclaude mcp add --transport http hoook https://mcp.hoook.io
✓ Connected to Hoook
tools: github, linear, slack, notion, stripe and more
> Open a Linear issue for each failing test and post the list in #eng
Hoook linear.create_issue ×4, slack.send_message(#eng)
✓ 4 issues opened. Summary posted.
- 02
Your users connect their apps
Connect Link signs them in to tools like Zendesk and Stripe. Hoook keeps the tokens.
connect.tsconst { token } = await hoook.connect.createToken({ userId: "u_42" })
→ open Connect Link inside your app
u_42 signs in to HubSpot · scopes: crm.objects.deals
✓ account apn_7Kx2 connected
await hoook.accounts.list({ userId: "u_42" })
[{ "app": "hubspot", "id": "apn_7Kx2", "healthy": true }]
- 03
Ship the actions
Your agent calls prebuilt tools, and reacts to triggers as events happen.
Your agent, on ClaudeHoook connected Find the HubSpot deals that went quiet this month and send each owner a nudge from my Gmail.
Hoookhubspot.search_dealsHoookgmail.send_emailFive deals have had no activity for 21 days. I sent a short nudge to each owner from your Gmail.
5 emails sentMessage your agent - 04
Hoook keeps it running
Token refresh, retries, rate limits and API changes are handled on our side.
Managed auth Connected accountsWhich connected accounts need attention this week?Connected accounts8,412Refreshed today1,134Need reconnecting3Hoook · connected accountsrefresh: 10 minutes before expiry revoked: pause calls, ask the user to reconnect secrets: encrypted, never returned to your code
Tokens refreshed today, by app612Google318Slack204HubSpot3Revoked1,134 tokens refreshed on their own today. Three users revoked access, and each was asked to reconnect.
Reconnect emails sent
claude mcp add --transport http hoook https://mcp.hoook.io
✓ Connected to Hoook
tools: github, linear, slack, notion, stripe and more
> Open a Linear issue for each failing test and post the list in #eng
Hoook linear.create_issue ×4, slack.send_message(#eng)
✓ 4 issues opened. Summary posted.
What Hoook takes off your plate.
Triage as tickets arrive
A trigger on each new ticket lets the agent tag, route or answer it.
Actions with guardrails
Refunds and account changes can wait for a person to approve.
Context from every tool
Orders, payments and past conversations in one view for the agent.
The numbers behind agent integrations
Public documentation from the providers, and our own figures, each labelled with its source.
is how long Stripe keeps retrying a webhook your endpoint did not accept, so the same event can arrive late or more than once.
Stripe webhooks documentationautomatic redeliveries of a failed GitHub webhook. If your endpoint was down, the event is gone unless you redeliver it.
GitHub webhooks documentationof prebuilt tools and triggers, across the apps your users already work in.
Hoook app catalogueBuilt for agents that act.
Works with your helpdesk
Zendesk, Intercom and more, with the same tools either way.
No double refunds
Writes carry idempotency keys, so a retry never acts twice.
Every action logged
See what the agent changed, in which account, and when.
Built for sensitive data
Encrypted credentials and access scoped per user.