Pylon
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 Statuses
- Knowledge Bases
- Tags
- Teams
- Ticket Forms
- User Roles
- Users
Stream notes
- Issues is the only incremental stream. It uses
created_atas its cursor field and syncs data in 30-day windows, as required by the Pylon API. - Issue Messages and Issue Threads are child streams of Issues. They retrieve data for each issue returned by the Issues stream, so the Start Date configuration indirectly affects these streams.
- 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.
Limitations & Troubleshooting
Rate limiting
The Pylon API enforces per-endpoint rate limits. The Issues endpoint allows 10 requests per minute, while most other endpoints allow 60 requests per minute. The connector handles rate-limited responses (HTTP 429) with exponential backoff and retries up to 3 times.