guildly

The workspace

Connections

The connections tab links outside services to your team, so agents can read your email, post to Slack, update Notion, or manage GitHub, with you deciding exactly who gets access to what.

One-time setup

Connections run through Composio, a service that handles the sign-in flows. The first time here, you'll connect a Composio account: create one, generate an API key in their settings, and paste it in. You do this once.

Connecting a service

After that, connecting anything is a couple of clicks. Quick connect buttons cover the common ones: Gmail, Google Calendar, Slack, Notion, GitHub, Google Drive. Below them, a browser lists the full catalog by category, from communication tools to productivity apps. Each connection walks you through the service's own sign-in and permission screen.

For services without a managed integration, there's a custom app setup where you can bring your own developer credentials. This is the advanced path, and you'll rarely need it.

Who can use what

This is the part to pay attention to. Under Active connections, every connected service shows a row of your agents, and you grant or revoke access per agent with a click. Connecting Gmail does not mean every agent can read your email. It means the agents you explicitly grant can.

A sensible default: grant a connection only to the agent whose job needs it. Your social media agent gets the X connection, nobody else does.

Maintenance

If a connection breaks (services expire logins now and then), you'll see it flagged here with a Re-auth button, and the agent that needed it will tell you in chat. Removing a connection cuts off all agents at once.