Integrations
Let your agent work in Gmail, Google Calendar, Notion, GitHub, Slack and 1,000+ more apps through the same Webly connection.
Integrations let the agent you connected to Webly act in your other apps: read and send email, add calendar events, update a Notion page, open a GitHub issue or post in Slack. It uses the same Webly connection it already has, so there's nothing else to install. Composio keeps the sign-ins to your apps and runs the actions; Webly decides who can use which connection and counts the runs.
Integrations are rolling out workspace by workspace. Until they reach yours, agents don't see these tools.
Connecting an app
- In the dashboard, open Integrations in the sidebar, find the app and choose Connect. You sign in to the app in a new tab and come back to Webly.
- With an agent, just ask for the task ("send the launch email to the list in my Notion page"). If the app isn't connected yet, the agent gives you a link to sign in. It only says the app is connected once Webly confirms it.
You can disconnect an app at any time from the Integrations page, or ask your agent to. That revokes Webly's access to it.
Asking your agent
Describe what you want done in plain words, the way you'd say it to a person. The agent searches for the right tools with your words, follows the steps Webly knows work for that task, and then runs them. Anything that sends, posts, changes or deletes something in an app is real, so the agent asks you before doing it.
Teams
In a team workspace, everyone connects their own apps, and only they can use them. Owners and admins can also connect an app for the whole workspace, so every member's agent can use it (for example a shared support inbox). If you've connected the same app yourself, your own connection is used for you. Only owners and admins can remove a shared connection.
API keys don't belong to a person, so in a team they use the shared connections only, and they can't sign in to apps: connect the app in the dashboard first.
Your own MCP servers
On Hobby and Pro, you can add a remote MCP server, such as your company's own or a tool's public one, and your agents use its tools next to the apps. In Integrations → Your MCP servers, choose Add MCP server, then give it a name and its HTTPS address (the final MCP endpoint, with no key in it).
- No sign-in: its tools are ready at once.
- API key: you enter the key on a secure page after adding it. Webly never sees the key, and you don't paste it to your agent.
- OAuth: you sign in after adding it. This works with servers that support Dynamic Client Registration.
A server can have up to 500 tools, and a workspace up to 20 servers. When a server's tools change, choose Sync to fetch them again. In a team, servers you add are yours alone; owners and admins can add one for the whole workspace.
Plans
| Free | Hobby | Pro | |
|---|---|---|---|
| Apps | Any 2 at a time | All 1,000+ | All 1,000+ |
| Runs a month | 100 | 1,500 | 7,500 |
Every run counts, including ones that fail. Free can connect any app, two at a time: disconnect one to try another, or upgrade for unlimited apps. When you reach either limit, your agent tells you and gives you the link to upgrade. Runs reset at the start of each month (UTC).
For developers
The same actions are on the API under /v1/integrations (search, schemas, execute, connect, MCP servers and more), as MCP tools such as search_integration_tools, run_integration_tool and add_integration_mcp_server, and in the SDK as client.integrations. See llms.txt for the details.