Request Comments: List 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:requests:list_comments
Tool description: Lists comments on a Zendesk request. Returns a maximum of 100 comments. A request in Zendesk is intended to be initiated by or on behalf of end users e.g. a customer. A request may be paired with a ticket (an admin/agent perspective of the same request).
Args schema:
{
"description": "Input schema for ZendeskListRequestCommentsTool.",
"properties": {
"request_id": {
"description": "The ID of the request",
"title": "Request Id",
"type": "integer"
},
"since": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Filters the comments from the given datetime. The datetime must be in ISO 8601 format. Example: 2019-01-01T00:00:00Z",
"title": "Since"
}
},
"required": [
"request_id"
],
"title": "ZendeskListRequestCommentsToolSchema",
"type": "object"
}
Output schema:
('application/json', 'application/json: Payload from API')