> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/other/bluetally.md).

# BlueTally

Connect BlueTally asset and employee data to Google Sheets, BigQuery, or Looker. Track equipment inventory and assignments without manual exports.

BlueTally is an asset management platform that helps companies track equipment, assign assets to employees, and manage their hardware inventory. It gives IT and ops teams a clear picture of what they own, who has it, and where it is.

Connecting BlueTally to Coupler.io lets you pull your asset and employee data into any destination — spreadsheets, dashboards, data warehouses, or AI tools — without manual exports.

**Why connect BlueTally to Coupler.io?**

* Sync asset inventory and employee records to Google Sheets, Excel, or BigQuery automatically
* Combine BlueTally data with other sources (HR systems, procurement tools) using Join or Append transformations
* Feed asset data into AI tools like ChatGPT or Gemini for analysis and reporting
* Keep stakeholders updated with live dashboards in Looker Studio without touching a CSV

## Prerequisites

* An active BlueTally account
* A BlueTally API key (available in your account settings)

## Quick start

{% hint style="success" %}
Start by connecting the **Assets** entity — it's the core of BlueTally and gives you the most immediate value for inventory tracking and reporting.
{% endhint %}

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to Coupler.io, go to the Data flows section, and click **Add data flow**.
{% endstep %}

{% step %}
**Select BlueTally as your source.** Search for BlueTally in the source catalog and select it.
{% endstep %}

{% step %}
**Enter your API key.** In BlueTally, navigate to your account settings and copy your API key. Paste it into the API key field in Coupler.io.
{% endstep %}

{% step %}
**Choose an entity.** Select either **Assets** or **Employees** depending on what data you want to pull. You can add more entities to the same data flow later.
{% endstep %}

{% step %}
**Set a start date.** Use the date picker to define how far back you want to pull data from BlueTally.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT or Gemini.
{% endstep %}

{% step %}
**Run your data flow.** Click **Run** to execute a manual sync and confirm your data loads correctly.
{% endstep %}
{% endstepper %}

## Available entities

| Entity    | Description                                                                             |
| --------- | --------------------------------------------------------------------------------------- |
| Assets    | Company assets and equipment tracked in BlueTally, including assignment and status info |
| Employees | Employee records managed in BlueTally, linked to asset assignments                      |

## BlueTally data overview

BlueTally exposes two core entities through Coupler.io: **Assets** and **Employees**. Together they give you a full picture of your hardware inventory — what you own, its current state, and who it's assigned to.

## Entities

| Entity    | What it contains                                                                            |
| --------- | ------------------------------------------------------------------------------------------- |
| Assets    | Equipment records including type, status, location, assigned employee, and purchase details |
| Employees | People records including name, department, and associated asset assignments                 |

## Assets — available fields

#### Identification & classification

| Field         | Description                                  |
| ------------- | -------------------------------------------- |
| Asset ID      | Unique identifier for each asset             |
| Asset name    | Human-readable name or label                 |
| Asset tag     | Internal tag or barcode number               |
| Category      | Type of asset (e.g., laptop, monitor, phone) |
| Manufacturer  | Brand or maker of the asset                  |
| Model         | Specific model name or number                |
| Serial number | Manufacturer serial number                   |

#### Status & location

| Field           | Description                                                    |
| --------------- | -------------------------------------------------------------- |
| Status          | Current state of the asset (e.g., active, in storage, retired) |
| Location        | Physical or logical location of the asset                      |
| Assigned to     | Employee the asset is currently assigned to                    |
| Assignment date | When the asset was assigned to the current user                |

#### Purchase & lifecycle

| Field           | Description                                |
| --------------- | ------------------------------------------ |
| Purchase date   | When the asset was acquired                |
| Purchase price  | Cost of the asset                          |
| Warranty expiry | Date the warranty expires                  |
| Notes           | Any additional notes recorded in BlueTally |

## Employees — available fields

#### Identity

| Field       | Description                        |
| ----------- | ---------------------------------- |
| Employee ID | Unique identifier for the employee |
| First name  | Employee's first name              |
| Last name   | Employee's last name               |
| Email       | Work email address                 |

#### Organization

| Field      | Description                                    |
| ---------- | ---------------------------------------------- |
| Department | Department the employee belongs to             |
| Location   | Office or site location                        |
| Status     | Active, offboarded, or other employment status |

## Common field combinations

* **Assets + Employees (Join):** Join on the "Assigned to" / Employee ID fields to create a unified view of who has what equipment
* **Assets by status:** Filter or aggregate the Assets entity by status to get counts of active, retired, or unassigned hardware
* **Assets by department:** Join assets with employees to break down inventory by department — useful for budget reporting
* **Warranty tracking:** Pull purchase date and warranty expiry fields to build a rolling expiry calendar

## Use cases by role

{% tabs %}
{% tab title="IT & Ops" %}

* Track full hardware inventory in a live Google Sheet or BigQuery table
* Monitor warranty expiry dates and flag assets approaching end-of-life
* Reconcile assigned vs. unassigned assets to identify spare capacity
* Use the Append transformation to combine asset data from multiple BlueTally accounts
  {% endtab %}

{% tab title="Finance" %}

* Aggregate asset purchase prices by department or category for budget reporting
* Track depreciation timelines using purchase date data
* Export asset data to Excel for cost center allocation or audit preparation
  {% endtab %}

{% tab title="HR & People Ops" %}

* Cross-reference employee offboarding lists against asset assignments to ensure equipment is returned
* Build onboarding reports showing which assets are ready to assign to new starters
* Connect to AI tools like ChatGPT or Gemini to generate equipment summaries by team
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* BlueTally data is filtered from a **start date** that you set when configuring the data flow — use the date picker to control how much historical data is included
* The **Assets** and **Employees** entities can be joined in Coupler.io using the assignment relationship — no need to do this manually in a spreadsheet
* If you manage assets across multiple BlueTally accounts, use the **Append** transformation to merge them into a single dataset
* Asset status values and category labels reflect exactly what is configured in your BlueTally account — there is no standardized taxonomy enforced by the API

## BlueTally common issues

### Connection issues

<details>

<summary>My API key is not being accepted</summary>

Double-check that you've copied the full API key from your BlueTally account settings — partial keys are a common cause of auth failures. Make sure there are no leading or trailing spaces when pasting the key into Coupler.io. If the key was recently regenerated in BlueTally, you'll need to update it in your Coupler.io data flow as well.

</details>

<details>

<summary>The data flow fails immediately after I save it</summary>

This usually means the API key is invalid or has been revoked. Go to BlueTally account settings, verify the key is active, and re-enter it in Coupler.io. If your BlueTally account has been suspended or downgraded, API access may have been disabled.

</details>

### Missing data

<details>

<summary>Some assets are not showing up in my export</summary>

Check the **start date** you set in the data flow configuration. If the start date is too recent, assets created or updated before that date will be excluded. Use the date picker to extend the range further back. Also confirm that those assets are not archived or deleted in BlueTally — archived records may not be returned by the API.

</details>

<details>

<summary>The Employees entity returns fewer records than expected</summary>

BlueTally may only return employees who have at least one asset assigned or who are marked as active. Offboarded employees with no active assignments may not appear. Check your BlueTally account directly to confirm which employee records are visible via the API.

</details>

### Permission errors

<details>

<summary>I get a "forbidden" or "unauthorized" error</summary>

Your API key may not have sufficient permissions to read Assets or Employees data. In BlueTally, check whether your account role allows API access. Some plans or user roles restrict API usage — contact your BlueTally account admin to confirm.

</details>

### Data discrepancies

<details>

<summary>Asset counts in Coupler.io don't match what I see in BlueTally</summary>

This is almost always caused by the start date filter. Coupler.io only pulls records from the date you specified onward. Set the start date as far back as needed, re-run the data flow, and compare again. Also check whether any assets have been deleted in BlueTally — deleted records are typically not returned by the API.

</details>

<details>

<summary>Category or status values look inconsistent in my destination</summary>

BlueTally passes through whatever values are stored in your account — there's no normalization. If your team has used inconsistent naming (e.g., "Laptop" vs. "laptop" vs. "Laptops"), those variations will appear in the export. Clean these up directly in BlueTally for consistent reporting.

</details>

## BlueTally FAQ

<details>

<summary>What entities can I pull from BlueTally?</summary>

Coupler.io supports two entities from BlueTally: **Assets** and **Employees**. Assets covers your equipment inventory including status, location, and assignment info. Employees covers people records including department and location. You can pull one or both in the same data flow.

</details>

<details>

<summary>How do I find my BlueTally API key?</summary>

Log in to your BlueTally account and go to your account settings. Your API key should be listed there. If you don't see one, you may need to generate it — check BlueTally's documentation or contact their support. Once you have the key, paste it into the API key field when setting up your data flow in Coupler.io.

</details>

<details>

<summary>What does the start date parameter do?</summary>

The start date tells Coupler.io how far back to pull data from BlueTally. Records created or updated before this date won't be included in the export. Use the date picker to set it as far back as your oldest relevant asset or employee record if you want a full historical export.

</details>

<details>

<summary>Can I combine Assets and Employees data in the same output?</summary>

Yes. Add both entities as sources in the same data flow and use the **Join** transformation in Coupler.io to link them. You can join on the employee assignment field in the Assets entity and the Employee ID in the Employees entity to get a single table showing who has which equipment.

</details>

<details>

<summary>Can I pull data from multiple BlueTally accounts?</summary>

Yes. Add each account as a separate source in the same data flow using its own API key, then use the **Append** transformation to combine the records into one dataset. This is useful if your organization has separate BlueTally accounts by region or business unit.

</details>

<details>

<summary>Which destinations can I send BlueTally data to?</summary>

Coupler.io supports a wide range of destinations including Google Sheets, Microsoft Excel, BigQuery, Looker Studio, and PostgreSQL. You can also send BlueTally data to AI tools like ChatGPT, Claude, Gemini, Cursor, Perplexity, or OpenClaw for analysis and summarization.

</details>

<details>

<summary>Why are some assets missing from my export?</summary>

The most common reason is a start date that's set too recently — assets created before that date won't be included. Archived or deleted assets may also be excluded by the BlueTally API. See the Missing Data section for more details.

{% hint style="info" %}
For a full list of data-related issues and fixes, see the [Common Issues](#bluetally-common-issues) article.
{% endhint %}

</details>

<details>

<summary>Can I automate the data sync on a schedule?</summary>

Yes, but you need to complete a successful manual run first — Coupler.io requires this before scheduling is available. Once your manual run confirms the data looks right, you can set a recurring schedule from the data flow settings.

{% hint style="info" %}
For tips on how often to refresh and how to set up your data flow for best results, see [Best Practices](https://docs.coupler.io/sources/category/other/bluetally/best-practices.md).
{% endhint %}

</details>


---

# 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://docs.coupler.io/sources/category/other/bluetally.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.
