> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/billing-and-invoicing/integrating-with-tabs.md).

# Integrating with Tabs

Sync customers, contracts, invoices, and revenue from Tabs into Drivetrain. This guide covers generating an API key for the read-only integration setup.

[Tabs](https://www.tabs.com/) is an AI-native revenue automation platform that streamlines contract ingestion, billing, cash application, revenue recognition, and reporting. Connecting Tabs to Drivetrain lets you automatically sync your customers, contracts, invoices, payments, and revenue data, so your models and reports always reflect the latest billing activity.

This guide walks you through generating a Tabs API key and then adding Tabs as a data source in Drivetrain.

{% hint style="info" %}
The Tabs connector is **read-only** — Drivetrain only pulls data from Tabs and never writes anything back.
{% endhint %}

### Prerequisites

To connect Tabs to Drivetrain, you need:

* A Tabs account with **admin access** (only admins can create API keys).
* Access to your Drivetrain workspace with permission to add data sources.

### What Drivetrain syncs from Tabs

Once connected, Drivetrain can pull the core entities of the Tabs data model:

* **Customers** — the businesses you bill, with contacts and custom fields.
* **Contracts** — agreements defining dates, payment terms, and obligations.
* **Invoices** — itemized requests for payment, with line items and dates.
* **Payments** — recorded receipts that settle outstanding invoices.
* **Revenue & reports** — recognized revenue, ARR, and cash-forecasting data.

### Tabs Setup — Generate an API key

Tabs authenticates API requests with an Authorization-header API key. You will generate one in the Tabs app and paste it into Drivetrain.

#### Step 1: Open Developers in Tabs

Log in to Tabs and, from the left side navigation menu, click **Developers**. You must be an admin in Tabs to create a key — if you are not, ask your Tabs admin to create one for you.

#### Step 2: Create the API key

On the **API Keys** tab, click **+ Create API key**. Give the key a recognizable name (for example, **Drivetrain Integration**) so you can identify it later, then click **Create key**.

#### Step 3: Copy and store the key

Tabs displays your new key only once. Click **Copy** and store it somewhere secure — you will paste this value into Drivetrain in the next section.

{% hint style="warning" %}
Treat the API key like a password. Never expose it publicly or commit it to source control. If a key is ever compromised, contact Tabs Support to revoke and reissue it.
{% endhint %}

### Drivetrain Setup — Add Tabs as a data source

#### Step 1: Open Data and add a source

In Drivetrain, go to **Data** in the left navigation, then click the **+** button to add a new data source.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-426b3a0fd6e37542c0b484d085dbb56cf653d025%2Fimage%20-%202026-07-01T121656.615.png?alt=media" alt=""><figcaption></figcaption></figure>

#### Step 2: Select the Tabs connector

In the **Connect a datasource** window, search for **Tabs** and select it under **Billing & Invoicing**.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-f45f7bda173352c5a012c019f7372f2f3fd5b457%2Fimage%20-%202026-07-01T121659.101.png?alt=media" alt=""><figcaption></figcaption></figure>

#### Step 3: Enter your API key

On the **Connect your Tabs account** screen, paste the API key you copied from Tabs into the **API Key** field, then click **Submit**. The connector form has a single field — just the API key.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-92245aea85997f9d216f52f1f36fc7c12e081990%2Fimage%20-%202026-07-01T121702.284.png?alt=media" alt=""><figcaption></figcaption></figure>

#### Step 4: Confirm the connection

Tabs now appears as a connected data source and begins syncing. Your Tabs data — customers, contracts, invoices, payments, and revenue — will populate in Drivetrain once the initial sync completes.

{% hint style="info" %}
If you run into any issues connecting Tabs or do not see your data after syncing, reach out to your Drivetrain CSM and we will be happy to help.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://integrations.drivetrain.ai/integration-guide/readme/billing-and-invoicing/integrating-with-tabs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.