Workspace-level integrations
Connectors are third-party services your AI agents can use as tools. Unlike agent-scoped skills, a connector is authorised once per workspace and every agent with the matching skill toggled on gets access.
#Concept
A skill like google_calendar adds tools to an agent — but those tools need something to talk to. A connectoris the authorised link between the workspace and the external service (in this case, a specific Google account's Calendar).
Workspace-level was a deliberate choice: you connect once, and every agent in the workspace can use it. Perfect for teams — the owner does the OAuth dance, everyone else just toggles the skill on their agents.
Only workspace owners can add or remove connectors. Members can see the connection status, but can't change it.
#Google Calendar
Currently the only connector shipped. Lets agents check availability and book meetings on the workspace's selected calendar.
Connecting
Open Connectors
Navigate to /dashboard/connectors. You'll see the Google Calendar card at the top.
Click Connect
You're redirected to Google's consent screen. Sign in with the Google account whose calendar you want to expose to your agents. Grant the requested scopes:
calendar.events— create, update, and cancel events.calendar.readonly— list calendars and read events for availability checks.
Pick a calendar
By default the connection uses your primary calendar. Click the calendar chip on the Connectors card to switch — the picker lists every calendar you have write access to.
Enabling on an agent
Open the agent
Go to /dashboard/ai/agents → open the agent → scroll to Skills.
Toggle Google Calendar
Tick the checkbox next to Google Calendar (recognisable by the branded logo + CONNECTOR badge). The expanded panel shows the connection status — green if the workspace is already connected, amber with a Connect CTA if not.
Set the agent's timezone
Above the System Prompt, pick the correct timezone (e.g. Asia/Baku). This drives the ISO offsets in every calendar tool call.
Save + test
Save the agent and open the Sandbox. Ask something like “Do you have any openings tomorrow between 2 and 6 PM?” — you should see the agent call listCalendarEvents and respond with a real availability answer.
What this looks like end-to-end
Agent → listCalendarEvents(timeMin: tomorrow 14:00, timeMax: tomorrow 16:00) → free slot found.
Agent → createCalendarEvent(summary: "Konsultasiya — Aygün Rəhimova", start: 2026-07-09T15:00:00+04:00, end: 2026-07-09T15:30:00+04:00, attendees: ["aygun@example.com"]).
The event lands on the connected calendar; the customer receives a Google Calendar invite by email with an RSVP button.
Disconnecting
Click Disconnect on the Connectors card. This does two things:
- Revokes the refresh token via
oauth2.googleapis.com/revoke. - Deletes the local connection row from the workspace.
Any agent with google_calendar enabled will get an error the next time it tries to use a calendar tool. The skill itself stays enabled — reconnect the workspace and it starts working again immediately.
Google flags calendar scopes as “sensitive” and requires app verification before removing the “unverified app” consent-screen warning. Until verification completes, new users clicking Connect will see an Advanced → Continue screen — the flow still works, it's just less clean.
#Coming soon
Every connector uses the same pattern (workspace OAuth + per-skill tools). On the roadmap:
- Notion — read/write pages from an agent.
- Bitrix / HubSpot / Pipedrive — first-class CRM connectors.
- Stripe — payment link generation from a conversation.
Missing something you need? Email us — connector priority is driven by real customer requests.