• Source
  • Sales & Support Analytics
  • Alpha
  • 21 entities
  • Read & write

Move Pylon data anywhere it matters.

Load Pylon accounts, activity types and audit logs into the warehouse or AI app you already run.

Source

Pylon

  • Snowflake
  • BigQuery
  • Postgres
  • Databricks
  • Claude
Streams
19
Entities
21
Actions
7
Destinations
50+
Standard support
1.0.0

Overview

What is the Airbyte Pylon connector?

The Airbyte Pylon connector extracts data from Pylon and loads it into 50+ destinations such as Snowflake, BigQuery, Databricks or Postgres, with full refresh and incremental sync. It publishes 19 streams you can select per connection.

  • 01

    Sync to your warehouse

    Land 19 Pylon tables in 50+ destinations on a schedule you control.

  • 02

    Live entity actions

    Read, create, update and delete Pylon records at runtime through typed entity actions.

  • 03

    Context store search

    Query synced Pylon data with filters, sorting and semantic search, without spending Pylon API rate limits.

  • 04

    Incremental syncs

    Pull only the records that changed since the last run instead of reloading everything.

19 streams

Every table you can sync from Pylon

  • Accounts
    Primary keyid
    Sync modesFullIncr.
  • Activity Types
    Primary keyid
    Sync modesFullIncr.
  • Audit Logs
    Primary keyid
    Sync modesFullIncr.
  • Contacts
    Primary keyid
    Sync modesFullIncr.
  • Custom Fields
    Primary keyid
    Sync modesFullIncr.
  • Issues
    Primary keyid
    Sync modesFullIncr.

Setup

Live in six steps

  1. Log in to your Airbyte Cloud account.

  2. Click Sources, then click + New source.

  3. Select Pylon as the source type.

Configuration fields

Pylon configuration fields
FieldTypeDescription
api_token*stringCreate a token under Settings > Integrations & dev > API tokens in Pylon. The token's role controls which streams you can read. Add Airbyte's IP addresses to any IP allowlist on the token. Choose Region to match the token prefix: pylon_api_eu_ means EU, pylon_api_ means US; for older tokens without a prefix, choose the region where your Pylon tenant is hosted.
num_workersintegerThe number of concurrent workers used to read Pylon data. Pylon rate limits are shared by every integration using your organization's API tokens. Lower this value if other tools also call Pylon.
regionstringSelect the region where your Pylon tenant is hosted. US uses https://api.usepylon.com and tokens prefixed with pylon_api_. EU uses https://api.eu.usepylon.com and tokens prefixed with pylon_api_eu_. Defaults to US. For older tokens without a prefix, choose the region where your Pylon tenant is hosted.
start_datestringStart syncing issues updated since this date, in UTC, using the format YYYY-MM-DDTHH:MM:SSZ. Applies only to issues and its child streams, issue_messages and issue_threads. On every sync, messages and threads are re-read for every issue updated since this date. All other streams always sync in full. Defaults to 30 days ago.

Supported Pylon actions

  • List

    Read live records straight from the Pylon API.

  • Create

    Write a new record back into Pylon.

  • Get

    Fetch a single record by ID.

  • Update

    Patch fields on an existing record.

  • Delete

    Remove a record.

  • Context Store Search

    Query synced data with filters and sorting, with no API rate limits.

  • Semantic Search

    Natural-language search across synced Pylon records.

Full parameter-level details live in the Pylon entity reference.

Hybrid deployment

Sovereign by architecture, not by policy.

The data plane runs in your environment. Records, credentials and keys stay with you; the control plane only receives configuration and job metadata.

  • Cloud
  • OSS
  • Hybrid

Your environment

DataConnectorsCredentialsKeys

↕ metadata only

Airbyte control plane

OrchestrationMonitoringUI

What teams build with Pylon

List all open issues in Pylon

Show me all accounts in Pylon

List all contacts in Pylon

What teams are configured in my Pylon workspace?

Show me all tags used in Pylon

List all users in my Pylon account

Show me the custom fields configured for issues

List all ticket forms in Pylon

What user roles are available in Pylon?

Show me details for a specific issue

Get details for a specific account

Show me details for a specific contact

Reply to the customer on an issue saying we are looking into it

Send a message to the customer on the billing issue

Assign an issue to a specific team member

Change the status of an issue to waiting_on_customer

Close an issue as resolved

Delete a test issue

What are the most common issue sources this month?

Show me issues assigned to a specific team

Which accounts have the most open issues?

Analyze issue resolution times over the last 30 days

List contacts associated with a specific account

FAQ

Pylon connector questions

Do I need more than one Pylon connection?

No. One Pylon authorization powers both the scheduled syncs that land data in your destination and the entity actions your agents call at runtime.

Do Pylon entity actions need a sync to run first?

No. Entity actions read and write through the Pylon API as they are called, so they work immediately. Context store search is the exception: it queries data Airbyte has already synced, which is what lets it filter and sort without spending API rate limits.

What data can I sync from Pylon with Airbyte?

19 streams, including Accounts, Activity Types, Audit Logs, Contacts, Custom Fields, Issues, Issue Messages, Issue Threads and more.

Does the Pylon connector support incremental sync?

Yes. The Pylon connector supports incremental sync on selected streams, and full refresh on every stream.

Where can I run the Pylon connector?

Run the Pylon connector on Cloud, OSS, Hybrid. Hybrid deployments keep the data plane in your environment while the control plane orchestrates syncs.

Didn't find your answer? Talk to sales

Start syncing Pylon in minutes.

Free 14-day trial. One connection powers your scheduled syncs and your live Pylon actions.