iSolutions HubBETA
Agent

Connect your agents to where work happens.

An agent that only lives in our app is half useful. Integrations send agent capabilities into the tools your team already opens — Gmail for inbox replies, and any compatible data tool for live data. Telegram and Discord approval channels launch in the next release.
What you get
MCP servers · 3 of 10
Bring your own — any compliant MCP URL
live
  • internal-knowledge
    https://mcp.acme.com/knowledge
    BEARER
  • billing-context
    https://mcp.internal.dev/billing
    HEADER
  • support-docs
    https://docs.example.com/mcp
    OPEN
Pass any MCP server you already run7 slots free
Inside the workflow
Configure once → agent reaches every connected channel.

Why teams pick it

  • Bring any compatible live-data tool
  • Sign-in via password or custom header
  • Up to 10 live-data tools on the Business plan

What you can do with it

Where teams put integrated agents to work.
  • Gmail replies in your voice

    Connect Gmail; the AI scans inbound mail and drafts replies in your voice (AI Inbox feature).
  • Live data tools

    Connect outside tools (web search, code helper, your own data sources) and the agent uses them mid-conversation.
  • Team visibility on Discord (next release)

    Agent runs and reply decisions will announce themselves in a Discord channel so the whole team sees activity without checking the app. Launching in the next release.
  • Email approvals on Telegram (next release)

    Agent drafts replies; the Telegram bot pings you for approval — tap once and the email sends. Launching in the next release.

Integrations FAQ

Other agents

Stop copy-pasting between tools.

Wire one agent into one channel today. The whole-team workflow gets cheaper from there.