Create issue
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.
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.
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.
The Pylon MCP integration connects your Dench AI CRM directly to Pylon MCP, so agents can read and act on your Pylon MCP data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
12 actions are available for agents to invoke on your behalf. Every call runs through Pylon MCP's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Pylon MCP and click Connect — you'll authorize access through Pylon MCP's own sign-in flow. No API keys or code required.
Ask an agent to use Pylon MCP in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Pylon MCP integration connects your AI CRM to Pylon MCP, so AI agents can work with your Pylon MCP data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Pylon MCP integration currently exposes 12 actions, including Create issue, Get account, Get contact, Get issue, Get issue messages, and Get me. Agents invoke them on your behalf from chat or from automations.
No. You connect Pylon MCP from your Dench workspace using Pylon MCP's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Pylon MCP's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Pylon MCP connection from your workspace settings at any time.