> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lightdash.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pylon

> Query support issues, accounts and contacts of a Pylon workspace live from Explore and AI agents

The Pylon [live data source](https://docs.lightdash.com/integrations/live-data-sources) reads one Pylon workspace. Lightdash turns each query into a Pylon search and shows the records Pylon returns. Support data stays in Pylon. It's a [level 2](https://docs.lightdash.com/integrations/live-data-sources#integration-levels) integration: its API filters records, without totals.

## Before you start

* **Live data sources enabled** for your organization. See [Live data sources](https://docs.lightdash.com/integrations/live-data-sources).
* **Admin role** in the Lightdash project.
* **A Pylon API token.** A Pylon admin creates it in **Settings** → **API Tokens**. The token decides which workspace the source reads.

## Connect Pylon

1. On the nav bar, click **Browse** → **Semantic Layer**.
2. In the sidebar, select **Live data sources**, then click **Add**.
3. Select **Pylon**.
4. Enter a **Name**, such as `Pylon`. People see this name in Explore and agents use it to refer to the source.
5. Enter the **API token**, then click **Test access**.
6. Click **Add source**.

Lightdash adds **Issues**, **Accounts** and **Contacts** tables to Explore. Lightdash sets the source's [explore prefix](https://docs.lightdash.com/integrations/live-data-sources#explore-prefix) from its name.

## Dimensions

Each table lists records, one row per issue, account or contact.

| Table | Dimensions |
| - | - |
| Issues | Number, Title, State, Source, Account, Account ID, Assignee, Team ID, Tags, Created, Updated, Resolved, First response (minutes), Resolution time (hours), Touches, CSAT score |
| Accounts | Account ID, Name, Domain, Type, Owner, Tags, Created, Last customer activity, Last team activity |
| Contacts | Contact ID, Name, Email, Account, Account ID, Portal role |

Dates are UTC days. **Assignee** and **Owner** are teammates' email addresses. **Tags** are comma separated, and **Is** keeps records with any of the values. **State** is `new`, `waiting_on_you`, `waiting_on_customer`, `on_hold`, `closed` or a custom status.

None of the tables has metrics, so a query can't count or average records.

## Supported features

| Feature | Available |
| - | - |
| Filters on dimensions, with several values each | Yes |
| Filters on metrics | No |
| OR filters and nested filter groups | No |
| Table calculations, custom metrics and custom dimensions | No |
| Period-over-period comparisons, pivots and date zoom | No |

Account and assignee filters match by name and email. Lightdash looks the IDs up in Pylon first, which adds a call.

## Limits

| Limit | Value |
| - | - |
| Default date range | Last 30 days on **Created**, when an Issues query has no filter on it |
| Most rows per query | 9,999 |
| Timeout | 30 seconds per request |
| Queries at once | 2 per source |
| Calls per minute | 100 per source |
| Calls per hour | 3,000 per source |

When a query matches more than 9,999 records, Lightdash shows an error rather than a partial result. Narrow the date range or add a filter.

## Example questions

* *"Open issues assigned to me, oldest first."*
* *"Issues from the last 7 days that are still open."*
* *"Accounts with no customer activity this quarter."*

## Troubleshooting

**Pylon rejected the API token.** Ask a Pylon admin for a new token and update the source.

**The Pylon API token can't read this.** Pylon API tokens are created by admins in **Settings** → **API Tokens**. Ask an admin to create one.

**Pylon couldn't run this search.** Check the filter values.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.