OneDesk is an all-in-one platform combining help desk and project management functionalities, enabling teams to manage customer support and project tasks seamlessly.
Create 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.
Delete 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).
Deletes 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)
Delete 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.
Delete a OneDesk message by its numeric ID. The operation can also report success when the message is absent.
Delete a OneDesk project by its ID. This operation is unavailable through this tool; use the OneDesk web application to delete the project instead.
Delete 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}
Tool to delete a specific task. Use when you need to remove an existing task by its ID after confirming its details.
Deletes 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)
Tool to delete a timesheet by its ID. Use when you need to remove a specific timesheet after confirming it's no longer needed. Example: {'timesheet_id': 123}
Delete a OneDesk user by unique user ID. The action returns success and status information for recognized responses, including permission and rate-limit errors; other failures can raise an error.
Retrieve 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.
Retrieve 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.
Retrieve OneDesk comments or discussion posts, optionally passing an item ID to filter by the associated work item. Returns the comments found; an empty list can also result when the response does not contain a recognized comment list.
Retrieve 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.
List feedback items from OneDesk. This operation is currently unavailable in this action; use the OneDesk web application to view feedback instead.
Retrieve details of a OneDesk issue by its numeric ID, including available title, description, status, priority and timestamps. Use this to inspect an issue for tracking or reporting.
List issues from OneDesk. This operation is currently unavailable in this action; use the OneDesk web application to view and manage issues instead.
List messages from OneDesk. This operation is currently unavailable in this action; use the OneDesk web application to view messages instead.
List requirements from OneDesk. This operation is currently unavailable in this action; use the OneDesk web application for requirement management instead.
Retrieves 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.
Retrieve 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}
Retrieve details of a OneDesk timesheet entry by ID, such as its user, project, duration and date when available. If details cannot be retrieved, the result may contain only the requested ID; this does not confirm the timesheet exists.
Retrieve 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.
The Onedesk integration connects your Dench AI CRM directly to Onedesk, so agents can read and act on your Onedesk data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
24 actions are available for agents to invoke on your behalf. Every call runs through Onedesk's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Onedesk and click Connect — you'll authorize access through Onedesk's own sign-in flow. No API keys or code required.
Ask an agent to use Onedesk in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Onedesk integration connects your AI CRM to Onedesk, so AI agents can work with your Onedesk data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Onedesk integration currently exposes 24 actions, including Create Worklog Entry, Delete Attachment, Delete Comment, Delete Customer, Delete Message, and Delete Project. Agents invoke them on your behalf from chat or from automations.
No. You connect Onedesk from your Dench workspace using Onedesk's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Onedesk's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Onedesk connection from your workspace settings at any time.