Pylon is a B2B customer support platform that helps teams manage customer issues, conversations, accounts, and knowledge bases across channels such as Slack, Microsoft Teams, email, and in-app chat. The Pylon REST API exposes this data—issues, messages, contacts, accounts, teams, and more—so it can be extracted for analytics, reporting, and integration with other systems.
Power end-to-end data operations for your Pylon API with Nexla. Our bi-directional Pylon connector is purpose-built for Pylon, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Pylon or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Pylon workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating a Pylon credential, you need an API token from your Pylon account. The Pylon API uses Bearer token authentication, with the token sent in the Authorization header of every request.
To obtain your Pylon API token, follow these steps:
Sign in to your Pylon account at app.usepylon.com. API tokens can be generated by Admin users.
Navigate to Settings > API Tokens in the Pylon dashboard, or go directly to the API Tokens settings page.
Create a new API token and give it a descriptive name (e.g., "Nexla Integration"). Actions performed with the token are attributed to this name in Pylon.
Copy the generated token immediately and store it securely, as you will need it to configure your Nexla credential.
To confirm the token is valid, you can call the /me endpoint, which returns details about the organization associated with the token. For complete information about API authentication and available endpoints, see the Pylon API documentation.
After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Pylon API token in the API Key field. This token is sent as a Bearer token in the Authorization header for all API requests to Pylon and must be kept confidential.
If your API token is compromised, revoke it in your Pylon dashboard under Settings > API Tokens and generate a new one. The API token grants access to your Pylon organization data and should be treated as sensitive information.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Pylon connector tile, then select the credential that will be used to connect to Pylon, and click Next; or, create a new Pylon credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Pylon endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
[Rest API] List Users
This endpoint template retrieves users from your Pylon organization. Use this template when you need to access the list of users, such as agents and team members, for analysis, reporting, or integration purposes.
This endpoint fetches data from the /users endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
[Rest API] List User Roles
This endpoint template retrieves user roles from your Pylon organization. Use this template when you need to access role definitions to understand permissions and access levels assigned to users.
This endpoint fetches data from the /user_roles endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
[Rest API] List Accounts
This endpoint template retrieves accounts from your Pylon organization. Use this template when you need to access account records that represent the companies or organizations you support.
This endpoint fetches data from the /accounts endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
[Rest API] List Contacts
This endpoint template retrieves contacts from your Pylon organization. Use this template when you need to access the individual people associated with your accounts for analysis, reporting, or integration purposes.
This endpoint fetches data from the /contacts endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
[Rest API] List Teams
This endpoint template retrieves teams from your Pylon organization. Use this template when you need to access team definitions to understand how support responsibilities are organized.
This endpoint fetches data from the /teams endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
[Rest API] List Issues
This endpoint template retrieves issues from your Pylon organization. Use this template when you need to access support issues, including their status and metadata, for analysis, reporting, or integration purposes.
This endpoint fetches data from the /issues endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
[Rest API] List Issue Messages
This endpoint template retrieves issue messages from your Pylon organization. Use this template when you need to access the individual messages exchanged within support issues.
This endpoint fetches data from the /issue_messages endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
[Rest API] List Issue Threads
This endpoint template retrieves issue threads from your Pylon organization. Use this template when you need to access the conversation threads associated with support issues.
This endpoint fetches data from the /issue_threads endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
[Rest API] List Tags
This endpoint template retrieves tags from your Pylon organization. Use this template when you need to access the tags used to categorize and organize issues and other records.
This endpoint fetches data from the /tags endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
[Rest API] List Custom Fields
This endpoint template retrieves custom fields from your Pylon organization. Use this template when you need to access the custom field definitions configured for your account.
This endpoint fetches data from the /custom_fields endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
[Rest API] List Knowledge Bases
This endpoint template retrieves knowledge bases from your Pylon organization. Use this template when you need to access the knowledge bases that hold your support articles.
This endpoint fetches data from the /knowledge_bases endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
[Rest API] List Knowledge Base Articles
This endpoint template retrieves knowledge base articles from your Pylon organization. Use this template when you need to access the individual articles published across your knowledge bases.
This endpoint fetches data from the /knowledge_base_articles endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
[Rest API] List Ticket Forms
This endpoint template retrieves ticket forms from your Pylon organization. Use this template when you need to access the ticket form definitions used to capture support requests.
This endpoint fetches data from the /ticket_forms endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
[Rest API] List Activity Types
This endpoint template retrieves activity types from your Pylon organization. Use this template when you need to access the activity type definitions that describe events tracked in Pylon.
This endpoint fetches data from the /activity_types endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
[Rest API] List Issue Statuses
This endpoint template retrieves issue statuses from your Pylon organization. Use this template when you need to access the set of statuses that issues can move through in your support workflow.
This endpoint fetches data from the /issue_statuses endpoint. Nexla automatically handles pagination to retrieve all available records.
For detailed information about the response structure and available fields, see the Pylon API documentation.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Pylon data sources can also be manually configured to ingest data from any valid Pylon API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Pylon data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
