Guides Put your agent to work Integrations

Connect hundreds of integrations

Integrations let your agent see the parts of your real life that live in other apps: your calendar, email, notes, messages, and work tools. Start with the smallest useful set. For most people, that means Google Calendar and Gmail.

You have two good paths. Use plugins if your harness supports them. Use One if plugins are not available, or if you want one connector layer that can reach lots of apps.

For agents Open this if your user sent you the guide.

Set up integrations for the user. Prefer harness plugins when available. If plugins are not available, use One.

For plugins: install Gmail and Google Calendar integrations, authenticate the user in the browser, then verify with read-only checks.
For One: if npm is missing on Windows, tell the user to install Node.js from nodejs.org, then continue.
Install One if needed: npm install -g @withone/cli. If you need a no-install fallback, use npx -y @withone/cli ....
Authenticate the user with One: one init --auth browser. This opens a browser window for the user to sign in and auto-installs the packaged One skill for supported agents. If One is already initialized but logged out, use one login.
If this workspace uses local skills, make sure ./skills/one/SKILL.md exists. If it does not, copy the packaged One skill into ./skills/one from the installed @withone/cli package.
Have the user connect Gmail and Google Calendar in the One UI. If they prefer the command-line shortcut, one add gmail and one add google-calendar open the same kind of browser OAuth flow.
Verify connections with one --agent list, then run harmless read-only checks: show the next three calendar events and count unread email.
Do not send email, create invites, delete files, post messages, or modify external data without explicit user confirmation.

Option 1: plugins

Easiest when available. Claude Code plugins can connect apps directly inside Claude Code. Codex plugins are the matching path if your Codex account includes them, such as the $100/month account.

Option 2: One

Best fallback, and very flexible. One gives your agent one command-line tool for Gmail, Google Calendar, Slack, Notion, Google Drive, and many other services.

Option 1: use plugins

Ask your agent to install the right plugins

In Claude Code, use Claude Code plugins. In Codex, use Codex plugins if your account includes them. You can say:

"Install the Gmail and Google Calendar integrations for this workspace, then verify them with read-only checks."

Connect only what you actually want it to use

Start with calendar and email. Add Slack, Notion, Drive, or anything else later, after the first two feel useful. Smaller setup means fewer permission screens and less to troubleshoot.

Require confirmation for anything public

Tell your agent it can read first, but it should ask before sending email, creating meetings with guests, posting messages, deleting files, or changing anything other people can see.

A good plugin setup prompt

Paste this into your agent:

"Set up integrations for Gmail and Google Calendar using plugins if my harness supports them. After connecting, prove it works with read-only checks: show my next three calendar events and a count of unread emails. Do not send, delete, invite, or modify anything without asking first."

Option 2: use One

Windows note

One is an npm package. On Windows, install Node.js first from nodejs.org. The Node.js installer includes npm. After that, your agent can install One.

Ask your agent to install One

Paste this into your agent:

"Install the One CLI with npm, then help me connect Gmail and Google Calendar."

The command your agent should run is:

npm install -g @withone/cli

Authenticate One in the browser

Your agent should run One's browser auth setup. A browser window will open so you can sign in or create your One account yourself:

one init --auth browser

This also installs One's packaged skill for supported agent apps. If One is already initialized but needs a fresh sign-in, your agent can run one login instead.

Install the One skill locally if needed

Some workspaces load skills from a local ./skills folder. If yours does, ask your agent to make sure ./skills/one/SKILL.md exists. The One CLI includes the skill files, so the agent can copy them into place after installing @withone/cli.

Connect Gmail and Google Calendar

After One opens in your browser, use Add Connection to connect the starter apps:

Google Calendar, so your agent can read your schedule and create events when you ask.
Gmail, so your agent can summarize, draft, and help triage email.

If you want the agent to open the connection screens for you, it can run one add gmail or one add google-calendar. That is just a shortcut to the browser approval flow. No API key handoff needed.

Have your agent verify the connections

Your agent should check the connected platforms:

one --agent list

A good verification is concrete and harmless: "show my next three calendar events" or "tell me how many unread emails I have." That proves the connection works without changing anything.

A good One setup prompt

Paste this into your agent:

"Set up One for this workspace. If the One CLI is missing, install it with npm install -g @withone/cli, or use npx -y @withone/cli if you cannot install globally. Authenticate me with one init --auth browser, or one login if One is already initialized. Make sure the One skill is installed for this agent, and if this workspace uses ./skills, make sure ./skills/one/SKILL.md exists. Then have me connect Gmail and Google Calendar in the One UI, run one --agent list, and verify with read-only checks. Do not send email, create calendar invites, delete anything, or modify external data without asking first."

Make "draft first, send on approval" a standing rule

Once your agent can reach email, calendar, and chat tools, it can also send things out into the world under your name. Rather than remembering to ask every time, write the habit down once so your agent always follows it. Your agent keeps its standing instructions in a file called AGENTS.md at the top of its workspace. Ask your agent to add this rule to that file:

When sending email or messages, draft the message first and show me the recipient and the full text. Do not send until I reply with approval. This applies to new emails, replies, messages, and texts.

You can say: "Add a rule to my AGENTS.md that you always draft emails and messages first, and never send until I approve." Once it's in AGENTS.md, every future session follows it without you having to bring it up again.

What to do next

Once calendar and email work, set up a morning brief. This is where integrations start feeling useful: your agent can look at your schedule, notice important email, and hand you a short plan for the day.

Stuck? Get help Next: Set up a daily brief

Stuck or need help?

Send a message and it comes straight to me. Tell me where you got stuck and I'll write back.

Rather have it done for you?

If following the steps yourself isn't how your brain works today, that's fine. On a Zoom call you share your screen and hand me control, and I set it up for you, right there on your own computer. You watch it come together and end the call with a working setup, nothing left on your plate.

Pick a time below. No pitch, no pressure, no homework beforehand.