Skip to content
Help center

Connecting sources

Connect your tools yourself, or send a setup link to the person who can.

How connecting works

A source is one tool connected to your business, such as its accounting system or its web shop. Admins and above connect sources. Go to Sources, choose Add source, pick the tool, and follow the steps for that tool below. With several companies, you pick the company first, and each source belongs to one of them. The Catalog tab lists every tool Gatlas connects to. Azure Cost Management and Power BI are available on the Platform plan.

The first sync starts by itself within about five minutes, and after that the source syncs every 24 hours. To change that, open the source and use the Schedule box: it offers Manual and intervals from every 5 minutes to every 24 hours. Sync now on the source's page runs one at once.

Gatlas pulls in everything the account you connect with can read. For a tool you sign in to, Gatlas then shows Configure streams with every stream selected, except the few a tool leaves for you to choose, such as Microsoft Teams message text. Keep the selection or change it, then choose Save configuration; Skip and sync everything keeps the streams already selected. You can change the selection later under Streams on the source's page.

Some tools ask what to read before anything syncs: Google Drive asks for folders, SharePoint and OneDrive for libraries or folders, Azure Cost Management for subscriptions and Power BI for semantic models. None of them syncs until you pick at least one, and an Azure source left without subscriptions for 24 hours has to be connected again. A database asks which schema to read. Stripe and PostHog also come with starter views, ready to query.

Gatlas also has connectors for Google Ads and Pleo that it does not offer for new sources, so they are not listed below. A source already connected to one keeps syncing it, and an admin can still reconnect it.

Tip

You do not need the logins yourself. A setup link lets whoever holds them connect their own tools without a Gatlas account. See Delegated setup below.

When a stream cannot be read

Some tools let an account read only part of what Gatlas syncs, depending on the user's role, the tool's plan or the permissions a key was given. Under Streams on the source's page, Gatlas marks such a stream with one of these labels, followed by the reason and what would let Gatlas read it:

  • Unavailable: Gatlas checked the connection before syncing and found it cannot read this stream, for example because the connected user is not an admin or the key lacks a permission.
  • Limited: Gatlas checked the connection before syncing and found it reads this stream with less in it, for example names the tool hides by a privacy setting.
  • Skipped last sync: the latest sync asked for the stream and the tool refused it. The other streams still synced.

Either way you can keep the stream selected or untick it. To unlock it, do what the reason names in the tool itself, such as giving the key a permission or upgrading the plan, or reconnect as the user it names; the next sync reads the stream. Each tool's note below says which roles, plans and permissions it needs, and lists under Stream limits every limit its streams can show, with what lifts it.

Microsoft sources need an admin's approval

SharePoint and OneDrive, Microsoft Teams, Azure Cost Management and Power BI each ask for their own Microsoft 365 permissions, so a Microsoft 365 admin approves each one on its own: approving one does not approve another. The connect form shows the source's approval link beside the sign-in, with a Copy button, to send to your admin before you sign in. A setup link that asks for a Microsoft source shows the same links, to send to the company's admin first. Each entry below says whether the approval is needed and what else the admin sets up, such as a role or a tenant setting.

Sign in with a work account in the organization whose data you want. A guest in another company's Microsoft 365 types that company's domain in the Microsoft 365 domain field first; Azure Cost Management refuses guest accounts. To reconnect, sign in with the same account, or for Azure Cost Management any work account of the same organization. Gatlas refuses a sign-in that does not match and changes nothing.

Reconnect a source

When a source shows Reconnect needed, the tool has stopped accepting Gatlas's access, usually because a password changed, a key or token was revoked, or the approval expired. Nothing new arrives from it until it is reconnected. Only an organization admin can reconnect a source; anyone else sees a note asking them to ask an admin.

Open the source and choose the button in the warning at the top, or the same action in the source's menu. The menu offers it on a source that still works too, so you can reconnect it before its access runs out. For tools you sign in to, it is called Reconnect: sign in again with an account that can see the same data, and the source keeps syncing the same account as before. For tools that use a key, it is called Update credentials, Update app credentials or Update database credentials: paste the new one. For most tools, Gatlas checks it before replacing the old one, and if the check fails, nothing changes.

If only someone else can sign in to the tool, send them a link instead. Each action above has a twin with the same verb: Send a link to reconnect, Send a link to update credentials, Send a link to update app credentials or Send a link to update database credentials, beside the action wherever it appears. The link names the company (your business, with one) and the tool, and the source's label when there is more than one source of that tool. They open it with no Gatlas account, sign in, and the same source syncs again with its history and settings. The link reconnects that one source and does nothing else, works once and expires after 7 days. Sending a new one replaces the old one.

Some tools cannot be reconnected in place, and Gatlas says so when you try. Delete the source and add it again. The new source starts without the old one's sync history or settings, so check any views that use it afterwards.

Remove a source

Admins and owners can delete a source. Open it, open the menu beside Sync now and choose Delete, then confirm. Deleting removes the source, its sync history and every row it has synced into Gatlas, and it cannot be undone. Views, reports and dashboards built on that data lose it too. To stop syncing but keep the data, set the source's Schedule to Manual instead.

Tools you sign in to

Choose Connect with the tool's name, sign in on the tool's own page and approve access. There is no key to copy. Gatlas reads from these tools, and writes to one only when you set it up to: a reverse sync writes a view into a Google Sheet. Some sign-ins ask for more than Gatlas uses, because the tool offers no narrower option: QuickBooks and e-conomic among them, as their entries below explain.

QuickBooks

Sync invoices, customers, bills, payments, and chart of accounts from QuickBooks Online.

How to connect. Sign in to QuickBooks as an admin of the company: Intuit lets only an admin connect an app. If the login has several companies, Intuit asks which one to connect; pick this company.

What Gatlas reads. Gatlas reads your chart of accounts, journal entries, invoices, bills, customers, vendors, and items, and never posts transactions. Intuit's sign-in asks for full accounting access because QuickBooks offers no read-only option.

How to repair it. Choose Reconnect on the source's page.

e-conomic

Import invoices, customers, products, and journal entries from Visma e-conomic.

How to connect. Switch to this company inside e-conomic first (top right, “administrate <company>”). e-conomic approves whichever company you are in, and its approval screen cannot pick another.

What Gatlas reads. Gatlas reads your accounts, vouchers, invoices, customers, and products, and never posts entries. e-conomic's approval screen grants an app role that includes editing, because e-conomic's invoice-lines data is only readable with that role.

How to repair it. Choose Reconnect on the source's page.

Xero

Sync accounting data including invoices, contacts, accounts, bank transactions, and more.

How to connect. Sign in to Xero as a user who can open the organization. If that login has approved Gatlas for several Xero organizations, Gatlas asks which one belongs to this company. Xero limits how many organizations one app can connect; if Xero refuses because a connection limit is reached, write to team@gatlas.ai.

What Gatlas reads. Read-only access to accounts, invoices, credit notes, payments, contacts, bank transactions, items, tax rates and organization details. Gatlas does not write to Xero.

How to repair it. Choose Reconnect on the source's page.

Embankment

Fund administration: the ledgers, balances and fund structure Embankment keeps in Entrilia.

How to connect. Sign in on Embankment's own page with the service account Embankment provides for integrations, not an employee login, so the connection outlasts any one person. Gatlas reads what that account may read. If syncing stops for more than seven days, someone has to approve the connection again.

What Gatlas reads. Read-only access to the fund data Embankment's API exposes to the connected account: ledgers, balances and fund structure. Gatlas reads whatever that account is entitled to see and never posts, edits or deletes anything in Embankment or Entrilia.

How to repair it. Choose Reconnect on the source's page.

Wrike

Sync delivery data: projects, folders, tasks and the hours logged against them, with users, workflows and custom fields from Wrike.

How to connect. Sign in to Wrike as the user whose projects should sync. Gatlas sees only what that user sees, so use an admin or a user with access to every relevant project. Wrike asks you to approve read-only access and, if you belong to several Wrike accounts, to pick one. Time logs require a Wrike Business plan or higher. If that user resets their password or is deactivated, the connection needs a reconnect.

What Gatlas reads. Read-only access to the projects, folders, tasks (titles, status, dates, assignees, custom fields, effort), time logs, users, spaces, workflows and custom fields the connected Wrike user can see. Gatlas never reads task descriptions, comments or attachments, and never creates, edits or deletes anything in Wrike.

How to repair it. Choose Reconnect on the source's page.

ClickUp

Sync delivery data: tasks, lists and the time logged against them, with members, statuses, custom fields and goals from ClickUp.

How to connect. Sign in to ClickUp as a workspace owner or admin, so Gatlas can read everyone's time entries. Gatlas sees only what that user sees. ClickUp asks which workspaces to allow; tick the one for this company. If you tick several, you choose the workspace next. ClickUp has no read-only option, so the approval covers what the user can do. Gatlas only reads. A personal API token also works. Create one in ClickUp under Settings, Apps, as a workspace owner or admin, because it acts as the user who created it.

What Gatlas reads. Read-only access to the spaces, folders, lists, tasks (names, status, dates, assignees, tags, checklists, custom field values), time entries, members, groups, statuses, custom field definitions and goals the connected ClickUp user can see. Task and time entry descriptions are dropped before anything is stored, and comments, docs, chat and attachments are never read. Custom field values are kept, text fields included: they are structured fields your team configured. Tasks deleted in ClickUp stay in Gatlas until someone runs a full refresh from the source page. ClickUp's access cannot be limited to reading, but Gatlas never creates, edits or deletes anything in ClickUp.

How to repair it. Choose Reconnect on the source's page.

Stream limits. What the stream picker can say about these streams, and what lifts each limit:

  • time entries: Reading everyone's time entries needs a ClickUp Workspace owner or admin, and the connected user is neither. Reconnect ClickUp as a Workspace owner or admin to sync time entries.

Google Sheets

Sync a Google Sheets spreadsheet into Gatlas as a table.

How to connect. Sign in with a Google account that can open the spreadsheet. Google asks you to allow Gatlas to see and edit your spreadsheets, because Gatlas can also write results back to a sheet you choose. As a source, Gatlas only reads. Gatlas syncs one spreadsheet per connection. If the account has several, an admin picks the right one under Spreadsheet on the source's page. If Google says it hasn't verified this app, choose Advanced, then continue to Gatlas. A Google Workspace admin can block apps Google has not verified; if the sign-in is refused, ask that admin to allow Gatlas.

What Gatlas reads. Reads the one spreadsheet you pick from those the signed-in account can open. Google's consent screen also asks for edit access, which Gatlas uses only when you set up a sync that writes results back to a sheet.

How to repair it. Choose Reconnect on the source's page.

Google Drive

Sync files from the Drive folders you pick into the Library, where prompts turn them into documents.

How to connect. Sign in with a Google account that can see the folders and approve the access Google asks for, then pick the folders to sync. Everything inside them, subfolders included, is copied into Gatlas. If Google says it hasn't verified this app, choose Advanced, then continue to Gatlas. A Google Workspace admin can block apps Google has not verified; if the sign-in is refused, ask that admin to allow Gatlas.

What Gatlas reads. Read-only access to files in the Drive folders you select. Gatlas copies documents for analysis and never modifies or deletes your files.

How to repair it. Choose Reconnect on the source's page.

SharePoint and OneDrive

Sync files from the SharePoint libraries and OneDrive folders you pick into the Library, where prompts turn them into documents.

How to connect. Sign in with a Microsoft 365 work account that can open the SharePoint sites or OneDrive folders you want, then pick them. Most organizations require an administrator to approve Gatlas first: ask your Microsoft 365 admin to open gatlas.ai/api/oauth/microsoft/admin-consent/start and approve Gatlas for the organization, then connect. Gatlas sees only what the signed-in account can see, and the connection stops working if that account is disabled or an admin signs it out everywhere.

What Gatlas reads. Read-only access to the SharePoint libraries and OneDrive folders you select. Microsoft's consent screen asks to read all files and sites the account can open, because Microsoft offers no narrower permission that works without per-site setup by an administrator. Gatlas copies documents from the locations you select and never modifies or deletes your files.

How to repair it. Choose Reconnect on the source's page.

Microsoft Teams

Sync teams, channels, members and Teams usage reports, plus channel messages when you select them.

How to connect. Your Microsoft 365 admin must approve Gatlas for Microsoft Teams before anyone can connect: ask them to open gatlas.ai/api/oauth/microsoft/admin-consent/start?source=microsoft_teams and approve Gatlas for the organization. Then sign in with a Microsoft 365 work account that is a member of the teams you want, because Gatlas reads the channels that account belongs to. Usage reports also need a reports role on that account, such as Reports Reader, which your admin assigns. Gatlas reads Teams once a day, as Microsoft requires. Message text and per-person usage are not synced until someone selects them in the source's streams.

What Gatlas reads. Read-only access to the teams, channels and members the connected account can see, and Microsoft 365 usage reports for Teams. For members, Gatlas stores names, roles and Microsoft 365 user ids, never email addresses. Channel message text, authors and mentions, and usage per named person, are stored only if someone selects those streams after connecting. Gatlas never reads 1:1 or group chats, and never posts, edits or deletes anything in Teams.

How to repair it. Choose Reconnect on the source's page.

Stream limits. What the stream picker can say about these streams, and what lifts each limit:

  • Every stream: Your Microsoft 365 admin has not approved Gatlas to read this. Ask your admin to open gatlas.ai/api/oauth/microsoft/admin-consent/start?source=microsoft_teams and approve Gatlas, then reconnect Teams.
  • Every usage report stream and report settings: Needs a Microsoft 365 admin role that can read usage reports, such as Reports Reader. Reconnect as an account that has one, or ask your admin to assign the role.
  • user activity daily and device usage daily: This account can read totals but not per-person detail. Reconnect as an account with the Reports Reader role, or ask your admin to assign it.
  • user activity daily, team activity daily and device usage daily: Names are hidden by your Microsoft 365 report privacy setting. A Global Administrator can show them in the Microsoft 365 admin center: Settings, Org Settings, Services, Reports.

Azure Cost Management

Sync daily and detailed Azure cost, actual and amortized, with budgets, subscriptions and resource groups, for the subscriptions you grant Gatlas.

How to connect. Sign in with a work account that belongs to the Microsoft tenant holding your Azure subscriptions. Guest accounts are refused. If your organization blocks user consent, an administrator first approves Gatlas at gatlas.ai/api/oauth/microsoft/admin-consent/start?source=azure_cost. That sign-in or approval adds the Gatlas application to your tenant. Then an Azure administrator assigns the Gatlas application the Cost Management Reader role on each subscription to include, and you pick those subscriptions here within 24 hours. On an Enterprise Agreement, the enterprise administrator also turns on AO view charges. Gatlas reads cost only and cannot change anything in Azure.

What Gatlas reads. Read-only access to cost for the Azure subscriptions you select: daily cost detail in the actual and amortized views, a daily summary by resource group and service, budgets, and the subscriptions and resource groups themselves, with tags stored exactly as you set them. Gatlas reads as its own application, with the Cost Management Reader role your Azure administrator assigns it. The Microsoft sign-in only proves which tenant is yours: Gatlas keeps no access for the person who signs in, and never changes anything in Azure.

How to repair it. Choose Reconnect on the source's page.

Stream limits. What the stream picker can say about these streams, and what lifts each limit:

  • Every stream: Gatlas reads only the subscriptions where the Gatlas application holds the Cost Management Reader role. Ask an Azure administrator to assign the role on each subscription to include.
  • Every stream: On an Enterprise Agreement, subscription readers see no costs unless the enterprise administrator turns on 'AO view charges'. Ask the enterprise administrator to turn it on.
  • Every stream: On a Microsoft Customer Agreement, subscription readers see no costs unless the billing profile's 'Azure charges' policy is on. Ask a billing profile owner to turn it on.
  • Every stream: On an Enterprise Agreement, costs stay hidden unless the enterprise administrator turns on 'DA view charges'. Ask the enterprise administrator to turn it on.
  • Every stream: On an Enterprise Agreement bought through a partner, Azure shows no costs until the partner publishes the enrollment's prices. Ask the partner to publish them.
  • billing accounts: Needs a billing role for Gatlas (billing Reader for MCA, EnrollmentReader for EA). Without one this stream is empty and is skipped. Nothing to do. Gatlas reads cost through your subscriptions.
  • cost details actual: Enterprise Agreement and Microsoft Customer Agreement only. Pay-as-you-go subscriptions use usage_details_actual. Select the usage_details streams for pay-as-you-go subscriptions.
  • cost details actual and cost details amortized: Cost files larger than 100 MB are not read on demand. The daily_costs stream still reads this subscription. For its cost detail, write to team@gatlas.ai.
  • cost details amortized: Enterprise Agreement and Microsoft Customer Agreement only. Pay-as-you-go subscriptions use usage_details_amortized. Select the usage_details streams for pay-as-you-go subscriptions.
  • usage details actual and usage details amortized: Pay-as-you-go (MOSA) subscriptions only, read through an API Microsoft is retiring. Nothing to do. When no selected subscription is pay-as-you-go, this stream reads nothing.
  • daily costs: A daily summary by resource group and service. For CSP customers it shows retail prices, and only if your partner turned on cost visibility. Ask your Microsoft partner to turn on cost visibility.

Power BI

Sync the tables of the Power BI semantic models you pick, beside their refresh history and column statistics.

How to connect. Most organizations need their Microsoft 365 admin to approve Gatlas for Power BI first: ask them to open gatlas.ai/api/oauth/microsoft/admin-consent/start?source=powerbi and approve Gatlas for the organization. Your Power BI admin must also allow the "Semantic Model Execute Queries REST API" tenant setting. Then sign in with a Microsoft 365 work account that has Build permission on the finance models, and pick the models. A Contributor or higher in their workspaces reads every row; an account with less sees only its own rows of a model with row-level security. Gatlas only reads, and never refreshes a model.

What Gatlas reads. Read-only access to the Power BI semantic models you select. Microsoft's consent screen asks to read every workspace and semantic model the account can open, because Power BI offers no narrower permission. Gatlas reads the tables of the models you select, as the signed-in account sees them, and never changes or refreshes them. It does not store the email addresses of model owners or users.

How to repair it. Choose Reconnect on the source's page.

Stream limits. What the stream picker can say about these streams, and what lifts each limit:

  • dataset refreshes: Reading a model's refresh history needs Write permission on it, and the connected account does not have it. Give the account Write on the model, or the Contributor role or higher in its workspace, to sync refresh history.
  • Each table of a selected model: Power BI refused to run queries on this model for the connected account. That needs Build permission on the model, and the Power BI admin must allow the Semantic Model Execute Queries REST API setting. Give the account Build on the model, or the Contributor role or higher in its workspace, and ask the Power BI admin to allow that setting.
  • Each table of a read-only model: The connected account can read this model but not change it, so if the model uses row-level security Gatlas reads only the rows that account may see. Connect as a Contributor, Member or Admin of the model's workspace to read every row.
  • Each table of a DirectQuery or composite model: This model reads its source live, so each Gatlas sync runs queries against that source. Nothing to change if that load is acceptable. Otherwise deselect the model's tables, or switch the model to import mode.
  • Each table of a selected model: Gatlas cannot read this table in queries it can check: too many of its rows share one value of every whole-number column it can split on. Add a whole-number column with more distinct values to the table in the model, such as a row number, or deselect the table.

Google Analytics 4

Pull sessions, page views, events, and traffic source data from GA4 properties.

How to connect. Sign in with a Google account that can see the Analytics property. If it can see several, Gatlas starts with the first, and an admin picks the right one under GA4 property on the source's page. If Google says it hasn't verified this app, choose Advanced, then continue to Gatlas. A Google Workspace admin can block apps Google has not verified; if the sign-in is refused, ask that admin to allow Gatlas.

What Gatlas reads. Read-only access to daily sessions, page views, events, traffic sources, visitor locations, and devices for the GA4 property you connect.

How to repair it. Choose Reconnect on the source's page.

Tools that use a key or token

Create a key or token in the tool's own settings, read-only where the tool offers it, then paste it into Gatlas and choose Connect. Each note below says where the key lives.

Shopify

Sync orders, customers, products, inventory, and payouts from your Shopify store.

How to connect. Create an app in the Shopify Dev Dashboard with the store owner's account, install it on the store with read-only access scopes, and paste its Client ID and Client secret. Gatlas uses them to request a new access token each time it syncs, so the connection does not expire. The connect form walks you through creating the app, the read-only permissions to grant and the plan and account it needs.

What Gatlas reads. Read-only access to orders, draft orders, abandoned checkouts, refunds, fulfillments and transactions, customers, products and collections, inventory and locations, gift cards, store pages and blog posts, and Shopify Payments payouts and disputes. Gatlas never modifies your store.

How to repair it. Choose Update app credentials on the source's page.

Stripe

Pull charges, customers, subscriptions, invoices, and payouts from Stripe.

How to connect. Create an API key in Stripe under Developers → API keys. A restricted key with read-only access is recommended (it starts with rk_); a secret key (sk_) also works.

What Gatlas reads. Read-only access to charges, payments, refunds and disputes, customers and their cards, subscriptions, invoices and credit notes, products, prices and coupons, payouts, transfers, balance transactions and events. Gatlas does not modify your Stripe account.

How to repair it. Choose Update credentials on the source's page.

HubSpot

Sync contacts, companies, deals, tickets, engagements, and lists from HubSpot CRM.

How to connect. A HubSpot super admin creates a service key under Development, Keys, Service keys, ticks the scopes below and copies its token. The access token of a legacy private app with the same scopes also works. Gatlas only reads. The scopes: crm.objects.contacts.read, crm.objects.companies.read, crm.objects.deals.read, tickets, crm.objects.owners.read, crm.lists.read.

What Gatlas reads. Gatlas reads contacts, companies, deals, tickets, engagements, and lists, and does not modify your CRM. HubSpot's tickets scope includes editing, because that is how HubSpot grants reading tickets.

How to repair it. Choose Reconnect on the source's page.

Attio

Sync CRM data including companies, people, deals, notes, and tasks.

How to connect. Create an API key in Attio under Settings → Developers → API Keys and paste it into the API Key field. Give it read access to Record Permission, Object Configuration, Note, Task and User Management. Gatlas marks a stream whose scope is missing as unavailable.

What Gatlas reads. Read-only access to company, people and deal records, notes, and tasks. Gatlas does not write to Attio.

How to repair it. Choose Update credentials on the source's page.

Stream limits. What the stream picker can say about these streams, and what lifts each limit:

  • companies: This Attio access token cannot read companies: it is missing a scope they need. In Attio's developer settings, give the token read access to Record Permission and Object Configuration. The next sync picks it up.
  • people: This Attio access token cannot read people: it is missing a scope they need. In Attio's developer settings, give the token read access to Record Permission and Object Configuration. The next sync picks it up.
  • deals: This Attio access token cannot read deals: it is missing a scope they need. In Attio's developer settings, give the token read access to Record Permission and Object Configuration. The next sync picks it up.
  • notes: This Attio access token cannot read notes: it is missing a scope they need. In Attio's developer settings, give the token read access to Note, Object Configuration and Record Permission. The next sync picks it up.
  • tasks: This Attio access token cannot read tasks: it is missing a scope they need. In Attio's developer settings, give the token read access to Task, Object Configuration, Record Permission and User Management. The next sync picks it up.

folk

Sync CRM data from folk: people, companies, groups, deals from every pipeline, and custom fields.

How to connect. Create an API key in folk under Settings → API → New API key (Premium or Enterprise plan). The key sees only what its creator sees, so create it from a user who is a member of every group whose people, companies and deals should sync.

What Gatlas reads. Read-only access to people, companies, groups, deals, custom fields, and note metadata (never note bodies), limited to what the key's user can see. Gatlas never creates, edits, or deletes anything in folk.

How to repair it. Choose Update credentials on the source's page.

PostHog

Sync product analytics including events, persons, feature flags, cohorts, and insights.

How to connect. Your PostHog personal API key (phx_), created under Settings → Personal API Keys with read access. Not the project API key (phc_): that one can send data but cannot read it. You also need the project ID, found under Settings → Project in PostHog, and the region your PostHog account is hosted in, US or EU.

What Gatlas reads. Read-only access to events, persons, feature flags, cohorts, and insights. Gatlas does not write to PostHog.

How to repair it. Choose Update credentials on the source's page.

Notion

Sync databases and users from Notion workspaces.

How to connect. Your Notion internal integration token from notion.so/my-integrations. Then share each database Gatlas should read with that integration in Notion; it sees nothing else.

What Gatlas reads. Read-only access to pages and databases you explicitly share.

How to repair it. Choose Update credentials on the source's page.

Traede

Fashion & lifestyle ERP: orders, invoices, credit notes, products, customers, shipments.

How to connect. Log in to app.traede.com as the user whose data should sync, go to Settings → API Keys and create a new key, then paste it into the Access Token field. Traede calls it an API key, but it is an access token that carries that user's permissions, so use an account that can read everything you want synced.

What Gatlas reads. Read-only access to orders, invoices, credit notes, shipments, products, and customers. Gatlas does not write to Traede.

How to repair it. Choose Update credentials on the source's page.

Lattice

Sync people and org data: users, departments, goals, goal updates, review cycles, and tags.

How to connect. A Lattice admin creates the API key under Admin → Platform → API keys. The key inherits that admin's permissions. Pick the data residency your workspace uses: a key works only in its own region.

What Gatlas reads. Read-only access to users, departments, goals, and review-cycle metadata. Gatlas never reads peer feedback or written performance reviews, and does not write to Lattice.

How to repair it. Choose Update credentials on the source's page.

Cal.com

Sync bookings, event types, and availability schedules from Cal.com.

How to connect. Your Cal.com API key from Settings → Developer → API keys. A key sees what its owner sees: pick Personal for your own bookings, or Organization (Organizations plan, org admin's key) for every member's.

What Gatlas reads. Read-only access to bookings, event types, and availability schedules. Gatlas never books, reschedules, or cancels anything.

How to repair it. Choose Update credentials on the source's page.

Mercury

Sync US business banking: accounts and balances, every transaction, cards, statements, treasury, recipients, and Mercury's change events.

How to connect. A Mercury admin creates the API token under Settings → Tokens. Choose the Read Only type: it needs no IP whitelist and Gatlas only reads. Mercury shows the value once and deletes tokens that go unused for 45 days.

What Gatlas reads. Read-only access to accounts and balances, transactions, cards (never card numbers), statements, treasury and credit accounts, recipients, categories, invoices, users, and change events. Gatlas never sends money, manages recipients, or changes anything in Mercury.

How to repair it. Choose Update credentials on the source's page.

Franklin

Sync business card spend from Franklin: transactions from the last 90 days, settled and pending, with their receipt details.

How to connect. Paste an API key from Franklin. Each key reads one company, the one chosen when the key was created, so a second company needs its own key. Franklin returns only transactions from the last 90 days, so the first sync starts there, and Gatlas keeps every transaction it has synced after it passes 90 days. Franklin's API is in beta.

What Gatlas reads. Read-only access to transactions from the last 90 days (card spend, top-ups and cashback) and the details of their receipts (file name, type and size, never the files). Gatlas never edits transactions or uploads receipts in Franklin.

How to repair it. Choose Update credentials on the source's page.

Aircall

Sync call activity: calls, users, teams, phone numbers, and tags from your Aircall phone system.

How to connect. An Aircall admin creates an API ID and API token together under Company Settings → API Keys. Aircall shows the token once, and regenerating a key issues a new ID and a new token together.

What Gatlas reads. Read-only access to call records (timing, duration, outcome, direction, agent, tags, comments), users, teams, phone numbers, and tags. Gatlas never reads call recordings or voicemail audio, never reads contacts, and never places, edits, or deletes anything in Aircall.

How to repair it. Choose Update credentials on the source's page.

Adversus

Sync outbound dialer activity: leads, sessions, calls, appointments, sales, and campaigns from Adversus.

How to connect. An Adversus admin creates an API user under User administration (Admin or “Custom routes” access). Its username and password are the credential; there is no token.

What Gatlas reads. Read-only access to leads, dialer sessions, call records, appointments, sales, campaigns, users, teams, projects, products, and pools. Gatlas never reads call recordings, SMS, mails, or contacts, and never dials, edits, or deletes anything in Adversus.

How to repair it. Choose Update credentials on the source's page.

Arrivy

Sync field-service jobs: scheduled and unscheduled jobs, their statuses, crew, equipment, templates, and customers from Arrivy.

How to connect. Open your API page in Arrivy (app.arrivy.com/api_info) and copy the Auth Key and the Auth Token. Paste both. The key can change data in Arrivy; Gatlas only reads. Arrivy may need to turn on API access for your plan, and only keys from an Arrivy admin can read job templates. Gatlas shares Arrivy's limit of 30 requests a minute with your other Arrivy integrations.

What Gatlas reads. Read-only access to jobs (scheduled and unscheduled, with their crew, equipment, customer and custom fields), each job's statuses, crew members, equipment, groups, job templates and customers. Crew instructions, customer notes and status notes are dropped before anything is stored. End-customer names and contact details are kept, because they tie jobs to customers. Crew names are kept, and crew email and phone are dropped. A job deleted in Arrivy whose date is more than 90 days past stays in Gatlas until someone runs a full refresh from the source page. Arrivy's keys cannot be limited to reading, but Gatlas never creates, edits or deletes anything in Arrivy.

How to repair it. Choose Update credentials on the source's page.

Stream limits. What the stream picker can say about these streams, and what lifts each limit:

  • Every stream: Arrivy may need to turn on API access for your plan. Ask Arrivy, then copy the keys again.
  • Every stream: Gatlas shares Arrivy's limit of 30 requests a minute with your other Arrivy integrations. If syncs run slow, sync every 4 hours instead of every hour.
  • tasks: Some windows held more than 50 jobs starting in the same hour and were read page by page. Deleted jobs in those windows are kept until the next full refresh. Run a full refresh to clear deleted jobs.
  • tasks: The job read stopped to stay inside Arrivy's 30 requests a minute. Nothing to do. The next sync continues from the month it reached.
  • task status history: Status history for some jobs was deferred to the next sync, because Arrivy allows 30 requests a minute. Nothing to do. The next sync continues where this one stopped.
  • task status history: Status history needs the tasks stream in the same sync. Select tasks as well.
  • templates and template statuses: This Arrivy key cannot read job templates. Keys from an Arrivy admin can.
  • customers: Customers refresh once a day on this account to stay inside Arrivy's 30 requests a minute. Nothing to do. Jobs stay fresh on every sync.

OnlinePOS

Sync point-of-sale data: order-line sales, end-of-day journals, products, and venues from OnlinePOS.

How to connect. Ask OnlinePOS support for an API token for the venue, and enter it with the venue's firma ID (its OnlinePOS customer number). One connection covers one venue.

What Gatlas reads. Read-only access to order-line sales, end-of-day journals, products, product groups, and the venue's terminals. Gatlas never reads loyalty or gift cards, and never creates orders or edits anything in OnlinePOS.

How to repair it. Choose Update credentials on the source's page.

Databases

Gatlas reads the tables in the schema you name directly from the database, every table unless you narrow them later under Streams on the source's page.

Supabase / PostgreSQL

Pull tables directly from any PostgreSQL database or Supabase project.

How to connect. Enter the host, port, database, schema (public unless you name another), username and password, using a database role that can only read. Tick Include views to sync views as well.

What Gatlas reads. Direct read access to the tables in the schema you name in your PostgreSQL database.

How to repair it. Choose Update database credentials on the source's page.

Delegated setup

When someone else holds the logins, send them a setup link. They connect their own tools on a Gatlas page without an account, and their credentials go straight into encrypted storage. You never see them.

  1. Go to Sources, open the Setup links tab and choose Generate setup link. With several companies, you can also start from Setup link on a company's page.
  2. With several companies, pick the company. Under Sources, choose They choose to let the recipient pick from every tool Gatlas connects to, or You choose to ask for exactly the tools you name.
  3. Under Link expires in, keep 7 days or choose 30 days.
  4. To have Gatlas email the link, fill in the recipient's name and email under Send via email.
  5. Choose Generate link. Gatlas shows the link with a Copy button so you can send it yourself, and emails it as well if you filled in a recipient.

The recipient opens a page titled with the company's name (your business's, with one) and chooses Connect beside each tool. When they chose the tools themselves, they finish with That's everything; when you named the tools, the link completes once each one is connected.

Follow progress in the Status column of the Setup links tab: Pending, In progress, Completed, Expired or Revoked. Gatlas does not notify you when a link is completed, so check the tab. While a link is still active, the menu on its row offers Copy link and, when you gave an email, Resend email.

Note

A setup link expires after 7 days unless you chose 30. You can revoke one at any time from the Setup links tab, and it stops working at once.