Integrations
Connecting an app
Connect a tool from the web app or straight from the channel where Gini asked for it.
Two ways in, and the lazy one is fine.
Just ask for the work
Ask Gini for something that needs a tool it can't reach, and it hands you the connect link right there in the thread.
You: @Gini what's the deal with Northwind: where did it stall?
Gini: I need HubSpot for that. [Connect HubSpot]: takes about 20 seconds and I'll pick this back up.
Click, authorise, and Gini continues the job it was already doing. This is the path most people actually use, because it appears exactly when the tool becomes relevant.
Or connect ahead of time
Open Integrations
app.ginicomputer.com → Integrations. Shows everything available and what you've already connected.
Pick the tool and choose your scope
Where read-only is a meaningfully narrower grant, you'll be offered it here. Take it if Gini only needs to look. You can always widen later.
Authorise in the tool
You'll land on the tool's own consent screen: Google's, HubSpot's, GitHub's : showing exactly what's being granted. Read it. That screen is the real contract; ours is just a button.
Come back
You're returned to Gini and the connection shows as live. Nothing else to configure.
Connecting more than one account
Some tools let you connect several accounts: a personal Google account and a shared one, two workspaces. Where that applies, connecting again adds an account rather than replacing the one you have, and Integrations says so explicitly on the button.
Where it doesn't apply, connecting again repairs or replaces the existing connection.
API keys
A few tools connect with a key rather than OAuth. Paste it into the field in Integrations. It goes straight to the credential vault: it isn't logged, and it isn't shown back to you afterwards.
Use a key scoped as narrowly as the tool allows. If it offers read-only keys, use one.
Never paste a key into a channel
If Gini needs a credential it will send you to a form, never ask for it in chat. A key pasted into Slack is in Slack's history, in everyone's client, and in whatever else reads that channel. If you've done it, rotate the key.
Checking what you've connected
Integrations lists your connections, when each was connected, and its state. Anything expired or revoked shows as broken with a reconnect button. See Fixing a broken connection.
Worth a glance every couple of months. Connections you no longer use are worth removing for the same reason unused API keys are.
If the tool you want isn't there
Two options. If it has an MCP server (many tools now do), you can point Gini straight at it. If it doesn't, tell us; the catalog is driven by what customers ask for.