ChuskyIntegrations
Your tools.
One connected worker.
Connect Chusky to the tools you already run on, with thousands of apps through one connection. Give the task once. Let the work move across the right channels, meetings, and apps.
6,000+ tools through one connection
The next step belongs in your tools.
Connect Chusky to the tools you already run on, with thousands of apps through one connection. Chusky can work within 1,000+ tools on your behalf, using the accounts and permissions you choose.
Integration group
Communication
Start the work and receive the outcome in the channels people already use.
Telegram
iMessage
SMS
X
Integration group
Calls and meetings
Handle business calls and carry meeting decisions into the follow-up.
Twilio
Zoom
Google Meet
Microsoft Teams
Webex
Integration group
CRM and sales
Keep customer records, deal stages, and next actions connected.
HubSpot
Salesforce
Integration group
Productivity
Bring messages, schedules, notes, and files into the same piece of work.
Gmail
Google Calendar
Notion
Box
Integration group
Payments
Prepare and complete supported payment work under your approval rules.
Stripe
Integration group
Agents and AI
Let compatible systems give work to Chusky and receive the result.
MCP — both ways
A2A
One task, several tools
The handoff should not become your job.
A conversation often needs more than one app. Chusky can carry the same task across the connected steps, keeping the outcome and the controls together.
Start with the customer.
A call, message, website chat, or meeting gives Chusky the request and the context behind it.
Bring in what the work needs.
Chusky can read the relevant email, calendar event, account note, file, or customer record through the connections you allow.
Complete the next useful step.
It can prepare the reply, book time, save a document, update HubSpot or Salesforce, or pause for approval before a sensitive action.
Return with proof.
The result comes back with the available provider receipt, created file, updated record, or clear explanation of what still needs attention.
Slack
Keep team requests close to the conversation.
Send a request from the messages you already use.
Telegram
Ask for work and receive updates on the go.
iMessage
Reach Chusky through a linked private conversation.
SMS
Keep a simple text-message way to reach Chusky.
X
Bring supported X conversations into your workflow.
Web chat
A workspace for requests, files, and progress.
CLI
Work with Chusky from your terminal.
How connections behave
Access follows the work, not the other way around.
A connection gives Chusky a way to work in an app; it does not give every conversation unlimited access. The workspace owner decides what is available, and consequential actions remain visible.
01
Connect once
Authorize the app you want Chusky to work with and keep that connection attached to the right workspace.
02
Give context
Describe the outcome, the relevant project, and any limits. Chusky uses that context to choose the next useful step.
03
Stay in control
Review sensitive actions, inspect the result, and disconnect access whenever the work no longer needs it.
Workspace-scoped access Reviewable actions Context carried forward
Bring your stack
Start with one workflow, then expand naturally.
You do not need to reorganize your tools around Chusky. Start with a task that crosses two or three apps, prove the handoff, and add more capability as Chusky earns its place in the workflow.
Beyond connected apps
One integration layer, several ways to work.
Connected business apps are only one part of the system. Chusky can combine them with its own controlled tools, research, files, MCP servers, A2A, and the channels where people already communicate.
Native tools
Built-in operations
Tool discovery, memory, files, artifacts, tasks, approvals, and run inspection are exposed through Chusky’s own controlled tool surface.
Research
Current information
Web and provider research can inform a task, while Chusky keeps research evidence distinct from a confirmed external action.
MCP
Bring another host
MCP lets a compatible client discover Chusky capabilities through a remote endpoint with a project scope and stable caller identity.
A2A
Let another system hand off the work
Compatible systems can reach Chusky through A2A alongside MCP. Keep the caller identity, tools, and allowed actions connected to the request.
Start when something changes
The event can be the invitation.
A new email, calendar update, HubSpot deal change, or Slack event can start work without another message from you. Connect the source and decide what the next step should be.
A new customer message.
Bring in the relevant context, prepare a reply, and wait for your review when the next send needs approval.
A deal moves forward.
Keep the customer record and next task together. Prepare the follow-up that belongs to the new stage.
When something changes
Connections are inspectable and recoverable.
Tokens expire, providers change schemas, and accounts are sometimes disconnected. A good integration experience should explain what is missing, preserve the original work, and let you reconnect the same account instead of silently creating a duplicate.
Before execution
Chusky checks that the app, account, action, and required arguments are available before claiming it can proceed.
During execution
Provider errors, approvals, missing connections, and uncertain transport states remain visible as distinct run states.
After recovery
Resume the existing run or mission after reconnecting. Use the provider receipt and a fresh readback to verify a write.