- Category: customer support
- Auth: API_KEY
- Composio-managed OAuth available? N/A
- Tools: 24
- Triggers: 0
- Slug:
ONEDESK - Version: 20261101_00
Tools
Create Worklog Entry
Create Worklog Entry
Slug:
ONEDESK_CREATE_WORKLOGCreate a worklog entry to track time spent on a work item (task, ticket, project, etc.). Records the start and finish time, work hours, completion percentage, and billability. Use this after obtaining a valid item_id from actions like GET_TASK_DETAILS.Input Parameters
Output
Delete Attachment
Delete Attachment
Slug:
ONEDESK_DELETE_ATTACHMENTDelete a specific attachment from OneDesk by its ID. To use this tool, provide the attachment_id. Note that the OneDesk Public API has limited attachment management capabilities. Attachments are typically associated with items (tickets/tasks) and can be viewed via GET_ATTACHMENTS when fetching item details. Returns deleted=True if the attachment was successfully deleted (200/202/204). Returns deleted=False if the attachment was not found (404).Input Parameters
Output
Delete Comment
Delete Comment
Slug:
ONEDESK_DELETE_COMMENTDeletes a comment from OneDesk by its ID. Use this tool to permanently remove a comment when it’s no longer needed. Note: OneDesk’s Public API has limited DELETE support for comments. This action tries multiple possible endpoints to maximize compatibility. Comments may be referred to as “conversations” in the API. Example: {‘comment_id’: 12345} Returns: Deletion status with context about success/failure (e.g., comment not found, permission denied)Input Parameters
Output
Delete Customer
Delete Customer
Slug:
ONEDESK_DELETE_CUSTOMERDelete a OneDesk customer by ID. The operation can also delete a user record with that ID. It reports success when deletion is accepted and false when the record is not found.Input Parameters
The unique identifier of the customer to delete from OneDesk. This can be a numeric ID or alphanumeric string.
Output
Delete Message
Delete Message
Delete Project
Delete Project
Delete Requirement
Delete Requirement
Slug:
ONEDESK_DELETE_REQUIREMENTDelete a requirement from OneDesk. Requirements in OneDesk are work items used for product development, feature requests, and specifications. They are one of the core work item types (tickets, tasks, requirements, issues). IMPORTANT: This operation may not be supported by all OneDesk Public API versions. If deletion fails, the API may only support soft-delete or archiving through status updates. Use when you need to permanently remove a requirement by its internal numeric ID. Example: {‘requirement_id’: 12345}Input Parameters
Unique internal ID of the requirement to delete. This is the numeric ‘id’ field returned by OneDesk API, not the externalId.
Output
Delete Task
Delete Task
Delete Ticket
Delete Ticket
Slug:
ONEDESK_DELETE_TICKETDeletes a ticket from OneDesk by its internal ID. Use this tool to permanently remove a ticket when it’s no longer needed. The ticket will be moved to the ‘Deleted Items’ project and scheduled for permanent deletion after 7 days. Note: OneDesk’s Public API has limited DELETE support. This action tries multiple possible endpoints to maximize compatibility. Example: {‘ticket_id’: 123} Returns: Deletion status with context about success/failure (e.g., ticket not found, rate limited, permission denied)Input Parameters
Output
Delete Timesheet
Delete Timesheet
Delete User
Delete User
Get Attachments
Get Attachments
Slug:
ONEDESK_GET_ATTACHMENTSRetrieve attachments for a specific item by its external ID by extracting attachment data from the item response. An empty result can mean that attachments were not included in the response.Input Parameters
External ID of the item (ticket/task) to retrieve attachments from. Required because the Public API only supports fetching items by external ID.
Output
Get Comment Details
Get Comment Details
Slug:
ONEDESK_GET_COMMENT_DETAILSRetrieve detailed information for a specific comment by its ID. This action attempts to fetch comment details from OneDesk using the comment ID. It tries multiple endpoint patterns to maximize compatibility with different API versions. Note: The OneDesk Public REST API has limited support for retrieving comments. If the comment ID doesn’t exist or the endpoint is not available, this action will fail.Input Parameters
Output
Get Comments
Get Comments
Get Feedback Items
Get Feedback Items
Get Feedback Details
Get Feedback Details
Slug:
ONEDESK_GET_FEEDBACK_DETAILSRetrieve detailed information about a specific item in OneDesk by its internal ID. This endpoint retrieves ANY type of item (Tickets, Tasks, Feedback, etc.), not just feedback items. Use this action when you have an item’s internal ID and need comprehensive details including: - Basic info (title, description, status, priority) - Creator and assignee information - Project association - Timestamps and lifecycle state - Direct web URL to view the item The internal ID is the numeric ID shown in the OneDesk application.Input Parameters
Internal ID of the item to retrieve (works for tickets, tasks, feedback, and all other item types)
Output
Get Issue Details
Get Issue Details
Get Issues
Get Issues
Get Messages
Get Messages
Get Requirements
Get Requirements
Get Task Details
Get Task Details
Slug:
ONEDESK_GET_TASK_DETAILSRetrieves comprehensive details of a specific task/item in OneDesk by its ID. Use this tool when you need complete information about a task including its title, description, status, assignee, priority, due date, and project association. OneDesk uses ‘items’ to represent various work units including tasks, tickets, issues, and requirements. Returns detailed task information if found, or raises an error if the task doesn’t exist or you don’t have permission to access it.Input Parameters
Unique numeric identifier of the task/item to retrieve (must be a positive integer, e.g., 1, 2, 123)
Output
Get Tickets
Get Tickets
Slug:
ONEDESK_GET_TICKETSRetrieve tickets from OneDesk by querying a range of item IDs. API LIMITATION WORKAROUND: The OneDesk Public API does not provide a direct endpoint to list all tickets. This action works around this by: 1. Querying individual items by ID within the specified range (start_id to end_id) 2. Filtering results to return only items with type=‘Ticket’ 3. Limiting results to the max_tickets parameter How it works: - The action queries items sequentially from start_id to end_id - Only items with type=‘Ticket’ are included in the results - Stops after collecting max_tickets tickets or reaching end_id - Non-existent IDs and non-ticket items (tasks, folders, etc.) are skipped Best practices: - Use smaller ranges (e.g., 1-50) for faster responses - Adjust start_id based on your known ticket ID ranges - Use max_tickets to limit the number of results The OneDesk Public API endpoint used: GET /rest/public/items/id/{id}Input Parameters
Output
Get Timesheet Details
Get Timesheet Details
Get Worklogs
Get Worklogs
Slug:
ONEDESK_GET_WORKLOGSRetrieve OneDesk worklogs with optional object, user and date-range filters. Use limit and offset for pagination; the limit defaults to 100 and permits up to 1,000 entries.Input Parameters
Filter worklogs up to this date (ISO 8601 format: YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ). If not provided, no end date filter is applied.
Filter worklogs from this date onwards (ISO 8601 format: YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ). If not provided, no start date filter is applied.
Filter worklogs by specific object ID (e.g., ticket, task, or project ID). If not provided, returns all worklogs.