See our recent webinar → Introducing Agentic Support
Programmatically fetch information about customers and issues from Pylon, so the data your team relies on can live wherever you need it.
Open issues in Pylon programmatically from your own applications, letting you file tickets from any system your team already works in.
The API spans the full range of Pylon objects — accounts, contacts, issues, messages, tasks and projects, knowledge base, custom fields, custom objects, tags, macros, and more — so you can automate against whichever part of your workflow you need.
Webhooks fire on specific events inside Pylon and post to an endpoint you control, so downstream systems stay in sync the moment something happens.
As an Admin, generate an API token in Pylon to authenticate your requests. Note that only Admin users can create API tokens.
Use your token to access endpoints across Pylon's objects. See the API Reference for specifications on every available endpoint.
Go to the Webhooks page in Settings and specify your target endpoint URL, along with any custom headers. For example, a Bearer token for authorization to be sent with each webhook.
In Settings, go to Triggers and create a Trigger with the "Send webhook" action. Use the trigger's "When" and "If" conditions to control exactly when the webhook fires, and use templated variables to shape the webhook body to your desired format.
You can programmatically access and act on data in Pylon — common uses include fetching information about customers and issues, and creating issues programmatically.
The API Reference documents endpoints across a wide range of objects, including accounts, activities, contacts, issues, messages, custom fields, custom objects, tasks and projects, knowledge base, macros, tags, teams, surveys, and users.
Only Admin users can create API tokens.
Webhooks are HTTP callbacks triggered by specific events in Pylon. You define the behavior by creating a Trigger with a "Send webhook" action and setting its "When" and "If" conditions.
Yes. You can attach custom headers to each webhook (such as authorization tokens) and use templated variables to build the webhook body into exactly the format you want.
Pylon connects with the tools your team lives in — Slack, email, CRMs, ticketing systems,and more. Meet your customers where they are and streamline every support workflow.
Receive and respond to customer messages from Telegram
Manage B2B support directly in Slack channels alongside your team.
Connect Pylon to Granola to ingest call recordings
Sync Outlook Calendar meetings to customer records in Pylon
Automatically capture and log Google Meet call notes to Pylon
Automcatically link active incidents to affected customer conversations.
Enrich customer records with usage data from Amazon Redshift.
Create Shortcut stories from customer conversations automatically
Trigger PagerDuty incidents from critical customer-reported issues.
