Pylon MCP integration for AI agents.
Connect AI agents to Pylon through 13 structured actions, including get account, create account, and create contact. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 13
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Pylon integration exposes
The Pylon Agent App exposes 13 provider-backed actions for communication and productivity work. Its current contract lets an authorized agent fetch one pylon account by account id or external id, create a pylon account, and create a pylon contact. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Pylon account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Pylon capabilities.
Showing 12 of 13 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_accountREADFetch one Pylon account by account ID or external ID.
INPUTS: id
create_accountWRITECreate a Pylon account.
INPUTS: name / account_type / domains / primary_domain / external_ids
create_contactWRITECreate a Pylon contact.
INPUTS: name / email / account_id / account_external_id / avatar_url
create_issueWRITECreate a Pylon issue with a title, HTML body, and requester or account context.
INPUTS: title / body_html / account_id / requester_id / requester_email
create_issue_noteWRITECreate an internal note on a Pylon issue.
INPUTS: id / body_html / attachment_urls / message_id / thread_id
get_contactREADFetch one Pylon contact by contact ID with optional paginated account context.
INPUTS: id / cursor / limit
get_issueREADFetch one Pylon issue by ID or issue number.
INPUTS: id
get_meREADFetch the Pylon organization associated with the API token.
list_issue_messagesREADList messages, replies, and internal notes on one Pylon issue.
INPUTS: id / cursor / limit
list_issuesREADList Pylon issues within a required time range of up to 30 days.
INPUTS: start_time / end_time / cursor / limit
search_accountsREADSearch Pylon accounts with a filter and optional fuzzy text search.
INPUTS: filter / search_text / cursor / limit
search_contactsREADSearch Pylon contacts with a filter and optional fuzzy text search.
INPUTS: filter / search_text / cursor / limit
INPUT CONTRACTS
Know what the action needs before it runs.
get_account
idOPTIONAL- The Pylon account ID or external ID.
create_account
nameREQUIRED- The account name.
account_typeOPTIONAL- The account type.
domainsOPTIONAL- Domains for the account, without a leading scheme.
primary_domainOPTIONAL- The primary domain, which must be included in domains when domains are provided.
external_idsOPTIONAL- External IDs associated with the object.
create_contact
nameREQUIRED- The contact name.
emailOPTIONAL- The contact email address.
account_idOPTIONAL- The account that this contact belongs to.
account_external_idOPTIONAL- The external ID of the account that this contact belongs to.
avatar_urlOPTIONAL- The square .png, .jpg, or .jpeg avatar URL for the contact.
create_issue
titleREQUIRED- The issue title.
body_htmlREQUIRED- The HTML content of the issue body.
account_idOPTIONAL- The account this issue belongs to.
requester_idOPTIONAL- The contact this issue is on behalf of.
requester_emailOPTIONAL- The requester email address. Pylon creates a contact when none exists.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account
Fetch one Pylon account by account ID or external ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_accountControl Create Account
Create a Pylon account. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_accountVerify with Get Contact
Fetch one Pylon contact by contact ID with optional paginated account context. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_contactSAFETY BOUNDARY
Operate Pylon with explicit limits
- Authorize Pylon with API key and grant only the provider access required by the selected actions.
- 5 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Pylon rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Pylon task completed successfully.
CONNECTION MODEL
API key
Pylon API token sent as a Bearer token. Generate it in the Pylon dashboard under Settings > API tokens: https://app.usepylon.com/settings/api-tokens.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 5
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Pylon.