Built-in connectors

Built-in connectors are Granular's own connections to ten popular tools: Notion, Linear, GitHub, Slack, Higgsfield, Asana, Sentry, Stripe, Vercel and Cloudflare. You add them once in Settings → Connectors, sign in or paste a token, and then the agent can use them in Claude, Codex and Gemini chats.

A connector lets the agent work inside another app, for example reading a Notion page or filing a Linear issue. For the bigger picture, see Connectors.

The connectors

• Browser sign-in means you approve access on the app's own website. There's no key to paste.
• API key means you paste a key or token the app gives you. An API key is a long password that lets software use your account.

Looking for something else?

• Google (Gmail, Calendar, Drive, Docs, Sheets and more) is connected through Discover apps. See Connect an app.
• Figma isn't a built-in connector. You can add Figma's own Dev Mode server as a custom connector. See Custom connectors.
• Any other tool with a connection address can be added as a custom connector.

Before you start

• An account with the app you want to connect.
• For GitHub: a personal access token. You can create one from the form.
• For Slack: a Slack app with a bot token (it starts with xoxb-), and Node.js installed on your computer. Node.js is a free program that Slack's connector runs on; get it from nodejs.org. None of the other built-in connectors need Node.js, even though their setup note in the app still mentions it.

Where to find them

1. Open Settings and click Connectors.
2. Click the Discover apps tab. Built-in connectors you haven't added yet are there, each with a Connect button.

Once you add one, its card moves to the Connected tab. Each card says Granular under its name.

Connect a browser sign-in connector

This covers Notion, Linear, Higgsfield, Asana, Sentry, Stripe, Vercel and Cloudflare.

1. In Discover apps, click Connect on the card.
2. Optional: in Account name, type a label such as Work. It helps you tell two accounts of the same app apart.
3. Click Add & sign in. This saves the connector; it doesn't open your browser yet.
4. The card is now under Connected with an orange ! in its corner, meaning Sign in to finish connecting. Click the card. Its status reads Needs sign-in: reconnect.
5. Click Reconnect. Your browser opens on the app's own website.
6. Sign in there and approve access.
7. Come back to Granular. The card shows Connected.

You have about three minutes to finish in the browser before Granular stops waiting.

A browser only opens when you click Reconnect or Finish sign-in in Settings. It never opens by itself in the middle of a task. If a connector isn't signed in, chats simply leave it out until you sign in.

Connect GitHub with a token

1. In Discover apps, click Connect on GitHub.
2. Optional: type an Account name.
3. Click Get a key. GitHub's token page opens in your browser.
4. Create a token. A fine-grained token (limited to the repos you choose) or a classic token both work. Give it repo access, and read:org if you need your organisation's data.
5. Copy the token, then paste it into the box in Granular.
6. Click Add.
7. Click the new GitHub card, then click Test. It shows Connected when the token works.

Connect Slack with a bot token

1. Make sure Node.js is installed (see Before you start).
2. In Discover apps, click Connect on Slack.
3. Optional: type an Account name.
4. Click Get a key to open Slack's app page. Create a Slack app and give it a bot token.
5. Paste the bot token into the box in Granular.
6. Click Add.
7. Click the new Slack card, then click Test.

Some Slack workspaces also need a team ID. Slack's built-in connector has no box for it, so in that case add Slack as a custom connector instead.

Use a Vault key instead of pasting

GitHub and Slack can use a key you already keep in the Vault, so you don't paste it twice. The Vault entry must:

• use the exact environment name the form shows: GITHUB_PAT for GitHub, or SLACK_BOT_TOKEN for Slack, and
• have In sessions ticked.

The form checks for you:

• "GITHUB_PAT is in your Key Vault: sessions will use it. Nothing to paste." You can click Add without pasting anything.
• "GITHUB_PAT is in your Key Vault but not shared with sessions." Click Enable it in the Vault, tick In sessions, and come back.
• "Best kept in your encrypted Key Vault: never a plain file." There's no Vault entry yet. Click Add it to the Vault, or paste the key into the box below to store it with this connector instead.

A key you paste into the connector itself is used before a Vault key of the same name.

What you'll see

On the card, in the top right corner:

• a check mark when the connector is working,
• an orange ! when it needs you, with the action Sign in to finish connecting or Check the connection (its calls are failing),
• nothing yet if it was added but never tested.

The bottom of the card says On in all chats, or Off, next to its on/off switch.

In the drawer (click the card), the status next to the main button is one of:

Under the name you'll also see how it runs, such as Browser sign-in · 12 tools, and Signed in as with the account name when the app tells Granular who you are.

Test, reconnect or finish a sign-in

The main button in the drawer changes with the connector's state:

• Reconnect: signs in to a browser sign-in connector, the first time or again when a sign-in expired.
• Test: a token connector that hasn't been checked yet. It checks the connection and your token.
• Re-test: checks a token connector again.
• Finish sign-in: completes a browser sign-in you started but didn't approve.

After it runs, a note shows the result, for example Notion (Work): connected (12 tools).

Change or undo it

Click the card to open its drawer.

• Choose which projects can use it: next to Available in:, click All projects and tick only the projects you want. All projects includes projects you add later. See Sessions and projects.
• Turn it off everywhere: switch off On in the drawer (or the switch on the card). It stays saved, and your sign-in stays, but no chat can use it. Switch it on again to bring it back.
• Rename it: next to Account name, click Rename, type the new name and press Enter. Press Esc to cancel.
• Change the token (GitHub, Slack): under Settings, click Edit settings, paste the new token and click Save. Leave the box empty to keep the current token. Browser sign-in connectors have no settings to edit; use Reconnect instead.
• Remove it: click Remove. Granular asks Remove … ? Sessions lose it. Click Remove to confirm, or Keep it. Removing deletes this connector's saved token or sign-in from your computer.

To use two accounts of the same app, connect it twice with different account names, such as Work and Personal. Each account is its own card. See Connector accounts.

Which models can use them

All ten built-in connectors work in Claude, Codex and Gemini chats. The connect drawer shows this as Any model. To choose which connectors a particular chat uses, see Connectors in chat.

Limits

• Your computer only. Connectors and their tokens stay on the computer where you added them. On another computer, add them again.
• Slack needs Node.js. The others don't.
• GitHub uses a token, not a browser sign-in.
• Google and Figma aren't built-in connectors. Use Google through Discover apps, and Figma as a custom connector.
• Connectors take up room. Each connector's tools use part of what the AI model can hold at once. With many connectors on, a smaller model can run out of room.

Troubleshooting

If you see "Needs sign-in: reconnect"
The sign-in expired or never finished, so chats leave this connector out. Click Reconnect and approve access in your browser.

If you see "Sign-in didn't finish: click to complete"
A sign-in was started but not approved. Click Finish sign-in and approve access in the browser window that opens.

If you see "Sign-in started but didn't finish. Complete the sign-in in the browser (approve access), then click Reconnect again."
The browser page was closed or blocked before you approved. Click Reconnect again and finish in the browser.

If you see "Sign-in timed out - try again and complete the browser sign-in."
Granular waited about three minutes and no approval arrived. Click Reconnect and approve sooner.

If you see "Signed in, but calls are failing"
The connector is signed in, but its last real action failed. Read the reason under the status; if it's cut off, click Show full error. Click Reconnect. If it keeps failing, the problem is usually on the app's side or with your account's access there.

If you see "Browser sign-in unsupported: use a token"
That server refuses browser sign-in from Granular. Remove it and connect with a token instead, for example as a custom connector.

If you see "That token was rejected. Check it hasn't expired and has repo access (and read:org for org data), then paste it again."
Your GitHub token has expired or lacks access. Create a new one with repo access (and read:org for organisation data), then click Edit settings, paste it and click Save.

If you see "Missing credential - add it and save first."
The connector has no saved token, and no matching Vault key with In sessions ticked. Click Edit settings and paste the token, or add it to the Vault under the name the form shows.

If you see "The server did not respond in time."
The connector started but didn't answer. Click Test again. For Slack, check that Node.js is installed.

If you see "The server stopped before it finished starting up: … If this keeps happening, remove the connector and add it again."
The connector couldn't start. For Slack, the most common cause is that Node.js isn't installed. Otherwise, click Remove, then connect it again from Discover apps.

If the agent says an app isn't among its tools
Check that the card is On, shows Connected, is available in this project under Available in:, and is switched on for the chat. See Connectors in chat.

Related