Connect your tools
Connect the tools your companies run on, send setup links, and keep every connection syncing.
Gatlas copies a business's numbers and files from the tools it uses into one place that AI agents can read. This playbook helps a person connect those tools for each company and keep every connection syncing.
How to run
Run the section the person's prompt names. If it names none, ask what they want to do and pick the section that fits. The prompt may name a company, a tool or a contact; use them, and ask for what it leaves out.
Do each step yourself where your tools allow. Pause only for a sign-in, an approval or a click the person must make. A section with no Gatlas tool in it is planning: draft in this chat, and leave each click in Gatlas to the person.
Ask one question at a time, and wait for the answer before the next. Never ask for a key or a password in this chat: a key goes only into Gatlas's own pages. Before you change anything in Gatlas, tell the person exactly what will change and wait for their yes. Never delete anything.
Before you start
The sections that use Gatlas's tools need this agent connected to Gatlas. Check that you can see Gatlas tools such as list_companies. If you cannot, stop and walk the person through Connect Gatlas to your agent first, then come back here.
Connect a tool
Help the person connect the tools of their business, or of the company the prompt names, to Gatlas. Ask which tools it runs on, such as accounting, commerce, payments or CRM.
For each one, tell them whether they sign in to approve access or create an API key, and for a key, where in the tool's settings it lives and which permissions it needs. Check each tool against the Connecting tools page in the Gatlas help center.
The person connects each tool in Gatlas themselves with Connect a tool: You connect it when they hold the login, or Someone else connects it to send a setup link to whoever does. Never ask them to paste a key into this chat.
Send a setup link
Help the person send a setup link so a contact at one of their companies can connect that company's own tools to Gatlas. The contact opens the link without a Gatlas account and signs in to each tool, which takes most people a few minutes. The link expires after 7 days.
Use list_companies to find the company the link is for, unless the workspace has one company. Ask which tools to include, and draft a short note to the contact that says what the link does and what to have ready. Once the person says yes, create the link with mint_setup_link and give it to them to send.
Before you change anything in Gatlas, tell the person exactly what will change and wait for their yes. Never delete anything.
Check the first sync
Check whether the first sync of the person's company, or of the company the prompt names, has landed. Use list_connections and tell them, for each connection, its status, when it last synced and whether its data is fresh. The first sync starts within minutes of connecting, then runs every 24 hours.
If a connection shows an error or needs reconnecting, explain why in plain words and tell them what to do next in Connections, under Sources in the Gatlas dashboard's sidebar.
Reconnect a tool
A tool stopped syncing because Gatlas's access to it expired or was revoked; the prompt names the tool and its company when it knows them. Use list_connections to find it, marked [REAUTH], and tell the person in plain words what went wrong and who can reconnect it: whoever signed in first, or another user with access to the same account.
If they fix it themselves, they do it from Connections, under Sources in the Gatlas dashboard's sidebar. If someone else should, and the person says yes, create a reconnect link for that connection with mint_setup_link and draft a short note that tells them what to sign in to.
Before you change anything in Gatlas, tell the person exactly what will change and wait for their yes. Never delete anything.
Fix a failing sync
A tool is failing to sync in Gatlas; the prompt names the tool and its company when it knows them. Use list_connections to find it and read its status. Explain in plain words what is likely wrong, whether the cause is on the tool's side or in how it is connected, and what the person should do next.
The person retries the sync themselves, from Connections, under Sources in the Gatlas dashboard's sidebar.
Catch up a company that stopped syncing
One of the person's companies, the one the prompt names when it names one, has not synced in more than 48 hours, so Gatlas marks it No sync in 2 days. Use list_connections to see which of its connections are behind and why, and tell the person in plain words.
For each one, give them the next step: wait for its next run, retry it from Connections, under Sources in the Gatlas dashboard's sidebar, or reconnect it.
Remind a contact about a setup link
A Gatlas setup link the person sent is not finished yet, and it expires soon. The prompt names the contact, the company and the day it expires when it knows them.
Draft a short, warm reminder. Say that the link connects the company's tools to Gatlas without a Gatlas account, that it takes a few minutes, and that they need a sign-in to each tool. Leave a place for the link, which the person adds themselves. If the link runs out, they send a new one from Setup links in Gatlas.
Keep syncs healthy
Help the person decide where Gatlas alerts should go. Gatlas can post to a Slack channel when a sync fails, a connection stops syncing on schedule, or access is about to expire.
Ask who fixes broken connections and which channel they watch, for each company if they run several. Then give them a short plan of which channel the alerts go to and who acts on them. The person connects Slack under Automations in Gatlas themselves.