Pylon API
Arcade Unoptimized
Tools that enable LLMs to interact directly with the pylon API.
Author:Arcade
Version:
0.2.1Auth:No authentication required
82tools
82require secrets
Pylon API provider: a toolkit that lets LLMs call Pylon endpoints to programmatically manage accounts, contacts, issues, knowledge bases, projects, users and training data. It exposes schema-driven endpoints for CRUD, batch operations, imports, searches and workflow actions.
Capabilities
- Unified CRUD and workflow operations across accounts, contacts, issues, projects, knowledge bases, tags and training data without calling individual endpoints manually.
- Schema-first GET_REQUEST_SCHEMA / EXECUTE pattern to build and validate request payloads and required path/query parameters.
- Advanced search, bulk updates, imports/exports, redaction and AI-generated reply workflows for content and issue management.
- Organization, team and user administration plus role retrieval for integration and automation.
Secrets
- token: PYLON_SECRET_TOKEN (example: provide as a Bearer token via the Authorization header or set as an environment variable PYLON_SECRET_TOKEN).
Available tools(82)
82 of 82 tools
| Tool name | Description | Secrets | |
|---|---|---|---|
Creates a new activity for a specified account.
Use this tool to add a new activity to an account by providing the account's internal or external ID. It will confirm the creation of the activity.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 1 | ||
Create a highlight for a specified account.
This tool is used to create a highlight for an account, using either an internal account ID in UUID format or an external ID in string format. It should be called when there is a need to add or update a highlight for an account.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 1 | ||
Generate an AI response for a specific issue.
This tool creates an AI-generated response for a given issue by specifying the issue ID. It should be called when an automated response is required for issue resolution or documentation.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 1 | ||
Create a new custom field in the system.
Use this tool to add a custom field to your database or application configuration. It allows for extending the available data fields to include additional, personalized information.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | 1 | ||
Creates a note on an issue to track additional details.
This tool should be called when there's a need to add a note or comment to an existing issue to provide further information or updates.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 1 | ||
Create a reply to an existing issue.
Use this tool to add a comment or response to an existing issue when interaction or follow-up is required.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 1 | ||
Create an issue thread for an existing issue.
Use this tool to initiate a discussion thread related to a specific issue by providing the issue ID. This helps in organizing conversations around particular issues efficiently. | 1 | ||
Create and publish an article in a knowledge base.
This tool allows the creation of a new article in a specified knowledge base, including optional translations. If the article is set to publish, translations will also be published.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 1 | ||
Create a new milestone in a project management system.
This tool is used to create a milestone within a project management application. It should be called when there's a need to add a new milestone to track progress or set goals in a project. The tool confirms the creation of the milestone. | 1 | ||
Creates a new user account.
This tool should be called to create a new user account when registration or account opening is requested.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | 1 | ||
Create a new collection in a knowledge base.
This tool is used to create a new collection within a specified knowledge base by providing the knowledge base ID.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 1 | ||
Create a new contact in the system.
This tool creates a new contact by sending the necessary details to the endpoint. Use it when you need to add a new person's contact information to the database.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | 1 | ||
Create a new issue in the system.
This tool is used to create a new issue in the system. It should be called whenever there's a need to log or track a new issue or task.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | 1 | ||
Create a new project seamlessly.
This tool is used to create a new project. It should be called when a user wants to initialize or start a new project within a system. | 1 | ||
Create a new tag within the system.
This tool is used to create a new tag by sending a POST request to the /tags endpoint. It should be called when a user wants to add a new tag to the system for organizational or categorization purposes.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | 1 | ||
Create a new team for collaboration.
Use this tool to create a new team on the platform, facilitating collaboration and organization. It returns details about the newly created team. | 1 | ||
Create a new route redirect for a knowledge base.
This tool is used to create a new route redirect within a specified knowledge base. It should be called when you need to add a redirect to manage or alter the routing within a knowledge base.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 1 | ||
Create a new task with specified parameters.
Use this tool to create a task. It should be called when a new task needs to be added to the system, specifying necessary parameters. | 1 | ||
Create a new training data configuration.
Call this tool to set up a new training data configuration for your application. It is used when you need to initialize or update your training data setup. | 1 | ||
Delete an existing account.
This tool deletes an existing account based on the provided account ID. Call this tool when you need to permanently remove an account. | 1 | ||
Delete a specific highlight from an account.
Use this tool to delete a specific highlight by providing the account ID and highlight ID. It should be called when a user wants to remove a highlight linked to an account. | 1 | ||
Delete an existing article from a knowledge base.
Call this tool to remove an article from a knowledge base by specifying the knowledge base and article IDs. | 1 | ||
Delete an existing contact by ID.
This tool deletes a contact by its ID. It should be called when a user needs to remove a contact from the system. | 1 | ||
Delete an existing project using its ID.
Use this tool to delete an existing project by providing the project ID. It allows you to manage and remove projects that are no longer needed. | 1 | ||
Delete an existing tag by ID.
Use this tool to delete an existing tag by specifying its ID. It confirms whether the deletion was successful. | 1 |
Page 1 of 4(25 of 82)
Last updated on