Trigger on event
- Listen for a new event
- Parse and validate the payload
- Take an action with the linked tool
12 tools available
Pylon is an AI-native B2B customer support platform that unifies ticketing, chat, knowledge base, and account intelligence across channels like Slack Connect, Microsoft Teams, email, and in-app chat.
Connect Pylon MCP to Definable to automate repetitive tasks, sync data with the rest of your stack, trigger on real-world events. Personas call Pylon MCP's 12 tools directly from chat or scheduled flows. You can wire it into any persona to read, write, and react when an event fires.
Every Pylon MCP action below is a callable tool any Definable persona can invoke.
Create a new issue/ticket in Pylon. Requires an organization ID, account ID, title, and body HTML. Optionally specify requester, priority, assignee, team, and tags.
Get full details for a Pylon customer account. Pass either the account ID (UUID) or external ID. Returns account details including name, domain, owner, tags, custom fields, and linked channels.
Get full details for a Pylon contact (customer). Pass the contact ID (UUID). Returns contact details including name, email, account, and custom fields.
Get full details for a Pylon support issue/ticket. Pass either the issue ID (UUID) or issue number. Returns title, body, state, metadata, custom fields, and nested account/assignee/requester info.
Get the full message history for a Pylon issue. Pass either the issue ID (UUID) or issue number. Returns all messages in chronological order with author info.
Get the currently authenticated user's details. Returns the user's name, email, role, and teams. No parameters required.
Get full details for a Pylon user (team member). Pass the user ID (UUID). Returns user details including name, email, role, and teams.
Search for customer accounts in Pylon. Returns a lightweight summary of accounts matching the specified filters. Supports filtering by custom fields using the custom_field_filters parameter - pass the custom field slug as the field name. For user-type custom fields (e.g. Salesforce AE owner), you can pass a Pylon user name or user ID as the value. Supports cursor-based pagination - use the returned cursor to fetch additional pages. To get full account details including custom fields, external IDs, and linked channels, use the account resource: account://{accountId}
Search for issues/tickets in Pylon. Returns a lightweight summary of issues matching the specified filters. Supports cursor-based pagination - use the returned cursor to fetch additional pages. To get full issue details including body, custom fields, and nested account/assignee/requester info, use the issue resource: issue://{issueId}
Update an existing customer account in Pylon. You can update the name, owner, tags, and custom fields. Use the get_custom_fields tool with object_type 'account' to discover available custom field slugs. Use the get_account tool to get full account details before updating.
Update an existing issue/ticket in Pylon. You can update the state, assignee, team, and tags. Use the issue resource (issue://{issueId}) to get full issue details before updating.
Upload one or more files (e.g. PDFs) into the Files tab of an account. Files with a matching filename are overwritten. Max 5 files per call, max 10 MB per file.
Anything Pylon MCP exposes through its API. Common model context protocol workflows on Definable include automate repetitive tasks, sync data with the rest of your stack, trigger on real-world events. Personas can call any of the 12 Pylon MCP tools directly, then chain the result into another integration without you writing code.
Pylon MCP uses DCR_OAUTH on Definable. You connect once from the integrations page, scoped to the permissions you choose, and from then on any persona that has the integration enabled can act on your behalf. Tokens are encrypted at rest and rotated automatically.
Yes — every Definable plan, including Starter, includes access to all 12 Pylon MCP tools. You only need a separate Pylon MCP subscription if Pylon MCP itself charges per seat or per API call.
Every call from a persona to Pylon MCP is logged with the user, persona, prompt, and response. Tokens never leave Definable's secrets vault, scopes are configurable per persona, and you can revoke access at any time from the integration page.
Sign up for Definable, open the integrations page, find Pylon MCP, and connect via OAuth or API key. You can immediately attach Pylon MCP to any persona and start running workflows. The free Starter plan includes 5,000 credits/month.
Definable exposes all 12 Pylon MCP actions as callable tools — including `Create issue`, `Get account`, `Get contact`, plus 9 more. Each tool gets a typed parameter schema so personas know exactly how to call it.
Wire it up in minutes. No coding required.