Skip to main content
The Pylon live data source 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 integration: its API filters records, without totals.

Before you start

  • Live data sources enabled for your organization. See 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 from its name.

Dimensions

Each table lists records, one row per issue, account or contact. 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

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

Limits

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.