Slack
Communication
AI agent integrations · MCP connectors
Connect AI agents to the tools where work happens
Give agents approved access to the context and actions they need—without treating every app, tool, or credential as unlimited authority.
Actions across your tools
Describe the outcome. Offloop agents take the supported actions.
Post launch update
Create rollout issue
Open pull request
Update launch brief
Check release health
Update opportunity
Launch campaign
Create Jira issue
Draft launch email
Create invoice
Update contactConnected work
Turn connected context into work the team can review.
Reply to a thread
Update a project
Send a message
Create a pull request
Create an issue
Draft an email
Run a customer report
Update a launch brief
Respond to a support issue
Update an opportunity
Create an invoice
Explore the connector catalog
Search the tools your team already uses. Connection availability depends on workspace configuration; executable actions remain curated and permission-bound.
50 connectors
Catalog ≠ unlimited execution authority
Discord
Communication
Google Meet
Communication
Outlook
Communication
Zoom
Communication
Fireflies
Communication
Salesforce
CRM & support
HubSpot
CRM & support
The catalog reflects supported provider families in the Offloop codebase. A connector appears for a workspace only when its authorization strategy is configured and enabled. Individual read, write, and trigger actions are exposed separately.
Questions about connectors
How integrations work, what agents can do, and where access stops.
What are AI agent integrations?
AI agent integrations connect an agent to approved business tools so it can use relevant context and carry out explicitly allowed actions instead of working from a disconnected chat window.
What is an MCP connector?
Model Context Protocol (MCP) is one way to expose tools and context to an AI system. Offloop treats the protocol as transport—not as permission to run every action a provider offers.
What can an Offloop agent do in a connected app?
That depends on the connector and the access granted. Offloop exposes a curated set of actions with bounded inputs, and the workspace keeps the resulting work visible.
How is connector access controlled?
Connections are scoped to the authorized account and supported actions. Revoking a connection blocks future use; protected or consequential steps can remain subject to explicit review.
Does a listed integration give an agent unlimited access?
No. Catalog availability is not execution authority. An agent can use only the actions and credentials that Offloop and the connected account explicitly allow.
Bring your tools into the work