Tickets: Search Tool
Usage
All Portia tools using API endpoints that require OAuth are built with plug and play authentication support. They use Portia client credentials including client ID, client name and redirect URL. Such tools will raise a Action Clarification
with an OAuth link as the action URL. The portia.wait_for_ready()
method must be used in this scenario: Portia's OAuth server will listen for the authentication result and resolve the concerned clarification, allowing your plan run to resume again.
For more on this, please visit to the section on running Portia tools (↗).
Configure your Zendesk tools with Portia AI
You will need to provide the subdomain of your Zendesk account to use with Portia AI. This is because Zendesk creates a unique subdomain for each account.
Configure access in Portia AI
- Log into your Portia dashboard ↗
- Navigate to the Manage Org tab.
- Enter the subdomain of your Zendesk account. Your subdomain is the part of your Zendesk URL before the
.zendesk.com
domain. For example, if your Zendesk URL ishttps://portialabs.zendesk.com
, your subdomain isportialabs
.
You are now ready to call Zendesk tools on our cloud!
Tool details
Tool ID: portia:zendesk:tickets:search
Tool description: Searches for tickets in Zendesk based on a natural language query or the Zendesk API syntax. Returns up to 1000 tickets that match the query.
Args schema:
{
"description": "Input schema for ZendeskSearchTicketsTool.",
"properties": {
"query": {
"description": "The query to search for. It can be a natural language query or use the syntax of the Zendesk API.",
"title": "Query",
"type": "string"
}
},
"required": [
"query"
],
"title": "ZendeskSearchTicketsToolSchema",
"type": "object"
}
Output schema:
('application/json', 'application/json: Payload from API for searching Zendesk tickets. This includes most core ticket information like ID, subject, description, status, priority, and type. It excludes comments.')