Pylon

Availability

Core Standard Plus Pro Enterprise Flex Self-Managed Enterprise PyAirbyte

Support Level

Marketplace

Connector Version

0.0.8 (last updated 8 days ago)

Definition ID

f2e53e88-3c6b-4e5a-b7c2-a1d9c5e8f4b6

This page contains the setup guide and reference information for the Pylon source connector.

Prerequisites

• A Pylon account with an Admin role.
• A Pylon API token. Only Admin users can create API tokens. Generate one in your Pylon dashboard under Settings > API. For details, see Pylon's authentication guide.

Setup guide

Enter your API Token. This is the Bearer token used to authenticate all requests to the Pylon API.

Optionally, enter a Start Date in UTC format (YYYY-MM-DDTHH:MM:SSZ). This controls how far back the connector syncs data for the Issues stream and its child streams (Issue Messages and Issue Threads). If not provided, defaults to 30 days ago.

Supported sync modes

The Pylon source connector supports the following sync modes:

• Full Refresh | Overwrite
• Full Refresh | Append
• Incremental Sync | Append (Issues stream only)

Supported streams

The Pylon source connector supports the following streams:

• Accounts
• Activity Types
• Contacts
• Custom Fields
• Issues (Incremental)
  • Issue Messages
  • Issue Threads
• Issue Statuses
• Knowledge Bases
  • Knowledge Base Articles
• Tags
• Teams
• Ticket Forms
• User Roles
• Users

Stream notes

• Issues is the only incremental stream. It uses updated_at as its cursor field and the POST /issues/search endpoint, so incremental syncs capture all issue modifications, not just newly created issues. Data is fetched in 30-day windows because Pylon caps the updated_at filter at a 30-day range per request.
• Issue Messages and Issue Threads are child streams of Issues. They fetch data for each issue returned by the Issues stream, so the Start Date you configure indirectly limits these streams as well.
• Knowledge Base Articles is a child stream of Knowledge Bases.
• Custom Fields queries the Pylon API once for each of the three supported object types: account, issue, and contact.

Upgrading to 0.0.8

Connector version 0.0.8 switches the Issues stream from GET /issues (cursored on created_at) to POST /issues/search (cursored on updated_at) so that incremental syncs capture updates to existing issues, not just newly created ones. Connections upgrading from any earlier version automatically run a one-time state migration that rewinds the issues cursor and re-pulls history starting from:

• the Start Date you configured, if it is set, or
• 30 days before the first sync, if Start Date is unset.

If you need a longer backfill, set Start Date to the desired date before the first sync on 0.0.8. Subsequent syncs use the new updated_at cursor incrementally and do not re-pull history.

Limitations & Troubleshooting

Rate limiting

The Pylon API enforces per-endpoint rate limits. The endpoints used by this connector are limited as follows:

• POST /issues/search (Issues): 20 requests per minute
• GET /issues/{id}/messages (Issue Messages) and GET /issues/{id}/threads (Issue Threads): 20 requests per minute each
• Most other endpoints: 60 requests per minute

The connector handles rate-limited responses (HTTP 429) with exponential backoff and retries up to 3 times.

Reference

Config fields reference

Field

Type

Property name

string

api_token

string

start_date

Changelog

Expand to review

Version	Date	Pull Request	Subject
0.0.8	2026-05-07	76083	Switch the Issues stream to POST /issues/search cursored on updated_at for true incremental sync. State migration rewinds the issues cursor to the configured Start Date (or 30 days ago if unset) on the first sync after upgrade.
0.0.7	2026-04-28	77394	Update dependencies
0.0.6	2026-04-21	76721	Update dependencies
0.0.5	2026-03-31	75855	Update dependencies
0.0.4	2026-03-17	74921	Update dependencies
0.0.3	2026-02-24	73850	Update dependencies
0.0.2	2026-02-20	73693	Make start_date optional, default to 1 month ago
0.0.1	2026-02-20	73624	Initial release of Pylon source connector