OneDesk is an all-in-one platform combining help desk and project management functionalities, enabling teams to manage customer support and project tasks seamlessly.
OneDesk is an all-in-one platform combining help desk and project management functionalities, enabling teams to manage customer support and project tasks seamlessly. On Nagent, Onedesk is exposed as a fully-configurable customer support integration that any agent can call — 24 actions, and API key authentication. No code is required to wire Onedesk into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Onedesk to automate the kinds of tasks customer support teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Onedesk into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Onedesk, with input parameters and output schema. Drop these into any step of an agent built in Helix.
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
Number of work units (hours) logged, non-negative
ID of the work item (task, ticket, project, etc.) to log time against
Whether this work is billable
Comments or notes describing the work performed
Start date and time of the work period in ISO 8601 format
Percentage of work completion (0-100)
Finish date and time of the work period in ISO 8601 format
Lifecycle status ID for the worklog entry (optional)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
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
Unique identifier of the attachment to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
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
Unique identifier of the comment to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_DELETE_CUSTOMERDeletes a customer from OneDesk using the DELETE /customers/{id} endpoint. This action permanently removes the customer record from the OneDesk account. Returns: - success=true: Customer was successfully deleted (HTTP 200/202/204) - success=false: Customer not found or already deleted (HTTP 404) Example usage: {'customer_id': '12345'}
Input parameters
The unique identifier of the customer to delete from OneDesk. This can be a numeric ID or alphanumeric string.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_DELETE_MESSAGEDeletes a message from OneDesk by its unique message ID. Returns success if the message is deleted or doesn't exist (idempotent operation). Use this when you need to permanently remove a message from the system.
Input parameters
The unique numeric identifier of the message to delete from OneDesk
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_DELETE_PROJECTDelete a project in OneDesk by its ID. **API LIMITATION**: The OneDesk Public API does not support DELETE operations. DELETE requests return 405 Method Not Allowed on /rest/public/items endpoints. The public API only supports: - POST /items/ (create) - GET /items/id/{id} (retrieve by ID) - GET /items/externalId/{externalId} (retrieve by external ID) - GET /organization/profileAndPolicy (organization info) **Alternatives**: - Use OneDesk web application to delete projects manually - Contact OneDesk support for private API access - Use ONEDESK_GET_ISSUE_DETAILS if you need to check item status This action will fail with a clear error explaining the limitation.
Input parameters
Unique identifier of the project to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
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
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_DELETE_TASKTool to delete a specific task. Use when you need to remove an existing task by its ID after confirming its details.
Input parameters
Unique identifier of the task to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
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
Unique identifier of the ticket to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_DELETE_TIMESHEETTool 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}
Input parameters
Unique identifier of the timesheet to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_DELETE_USERDeletes a user from OneDesk by their unique user ID. This action permanently removes the specified user from the OneDesk account. Use this only after confirming the user should be removed from the system. **Important Notes:** - The OneDesk Public API has limited user management capabilities - There is no public API endpoint to list or create users - User IDs must be obtained through other means (e.g., OneDesk web application, internal systems) **Returns:** - success=True with status_code 200/204 if user was successfully deleted - success=False with status_code 404 if user was not found - success=False with appropriate status_code for other errors (403 for permission denied, 429 for rate limited, etc.) Example: {'user_id': '12345'}
Input parameters
The unique identifier of the user to delete from OneDesk
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_GET_ATTACHMENTSRetrieve attachments for a specific item by its external ID. IMPORTANT: The OneDesk Public API (/rest/public) has limited functionality and does NOT provide: - A dedicated attachments list endpoint - Ability to list all attachments across items - Endpoints to retrieve items by internal ID This action retrieves attachments by fetching an item via its external ID and extracting attachment data from the item response. You must know the external ID of the item in advance. Supported endpoints: 1. GET /rest/public/items/externalId/{externalId} - Fetch item by external ID 2. POST /rest/public/items/ - Create new items (not used here) 3. GET /rest/public/organization/profileAndPolicy - Get organization info (not used here)
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
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
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
The unique identifier of the comment to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_GET_COMMENTSAttempts to retrieve comments (discussion posts) from OneDesk. **IMPORTANT LIMITATION**: The OneDesk Public REST API does not provide an endpoint to list or retrieve comments. According to OneDesk's API documentation, the public API only supports: - Creating items: POST /rest/public/items/ - Retrieving items by external ID: GET /rest/public/items/externalId/{externalId} - Getting organization info: GET /rest/public/organization/profileAndPolicy Comments can be created via the API but cannot be retrieved or listed through the public API. This action documents this limitation clearly. **Alternative approaches**: 1. Use the OneDesk web application directly to view comments 2. Request access to OneDesk's private/internal API from OneDesk support 3. Use OneDesk's webhook system to receive comment events in real-time 4. If you have a comment ID, try ONEDESK_GET_COMMENT_DETAILS For more information, visit: https://onedesk.com/dev/
Input parameters
Filter comments by associated item (ticket/task) ID (not supported by public API)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_GET_FEEDBACKRetrieve all feedback items from OneDesk. **IMPORTANT LIMITATION**: The OneDesk Public API does not provide a GET endpoint to list feedback items. The public API only supports: - Creating items via POST /rest/public/items/ - Retrieving specific items by external ID via GET /rest/public/items/externalId/{externalId} - Getting organization info This action will always fail with an informative error message explaining this API limitation. **Alternative approaches:** - Use the OneDesk web application for viewing feedback - Retrieve feedback by external ID if you have it - Use OneDesk webhooks to receive feedback data as events - Contact OneDesk for private/internal API access
Input parameters
Page number for pagination, starting at 1
Number of items per page for pagination, max 100
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
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
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_GET_ISSUE_DETAILSRetrieve comprehensive details of a specific issue by its ID. This action fetches full information about an issue including its title, description, status, priority, creation/update timestamps, and other metadata. Use this when you need detailed information about a specific issue that you have the ID for. Returns essential issue information that can be used for reporting, tracking, or further processing. The response includes both basic fields (title, description) and advanced tracking information (status, priority, timestamps).
Input parameters
Unique identifier of the issue to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_GET_ISSUESRetrieve a list of issues from OneDesk. **API LIMITATION**: The OneDesk Public API does not provide an endpoint to list or retrieve issues. The public API only supports: 1. Creating items via POST /rest/public/items/ 2. Retrieving specific items by external ID via GET /rest/public/items/externalId/{externalId} 3. Getting organization info via GET /rest/public/organization/profileAndPolicy **Alternatives**: - Use the OneDesk web application directly to view and manage issues - Request access to OneDesk's private API (contact OneDesk support) - Use OneDesk's webhook system for issue event notifications - Use ONEDESK_GET_ISSUE_DETAILS action if you have a specific issue's external ID This action will raise an ExecutionFailed error to document this limitation.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_GET_MESSAGESTool to retrieve a list of messages from OneDesk. **IMPORTANT LIMITATION**: The OneDesk Public API does not provide an endpoint to list or retrieve messages. The public API only supports: 1. Creating items via POST /rest/public/items/ 2. Retrieving specific items by ID via GET /rest/public/items/id/{id} 3. Retrieving specific items by external ID via GET /rest/public/items/externalId/{externalId} 4. Getting organization info via GET /rest/public/organization/profileAndPolicy **Alternatives**: - Use the OneDesk web application directly to view messages - Request access to OneDesk's private API (contact OneDesk support) - Use OneDesk's webhook system for message event notifications - Retrieve specific messages by ID if you have the message ID This action will raise an ExecutionFailed error to document this API limitation.
Input parameters
Maximum number of messages to return
Offset for pagination
Search text within message bodies
Direction of the message, e.g. 'inbound' or 'outbound'
Filter messages by associated ticket ID
Filter messages by contact/customer ID
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_GET_REQUIREMENTSRetrieve a list of requirements from OneDesk. **IMPORTANT LIMITATION**: This action cannot function as intended because the OneDesk Public API does not provide an endpoint to list or retrieve requirements. The OneDesk Public API (/rest/public) only supports: - Creating items: POST /rest/public/items/ - Get by external ID: GET /rest/public/items/externalId/{externalId} - Organization info: GET /rest/public/organization/profileAndPolicy There is no endpoint to: - List all requirements - Search for requirements - Query requirements by criteria - Get requirements by any identifier other than external ID Alternative approaches: 1. Use OneDesk web application for requirement management 2. Contact OneDesk support for private API access 3. Use webhooks to receive requirement data as events occur 4. Use ONEDESK_GET_REQUIREMENT_DETAILS if you have a specific requirement's external ID This action will always fail with a clear error message explaining the limitation.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
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
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
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
Ending item ID for the range to query (inclusive, must be >= start_id)
Starting item ID for the range to query (inclusive, must be >= 1)
Maximum number of tickets to return (1-100)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_GET_TIMESHEET_DETAILSTool to retrieve details of a specific timesheet entry. Use when you have the `timesheet_id` and need full metadata (user, project, hours, dates). Tries multiple endpoint/header variants and gracefully falls back in restricted environments.
Input parameters
Unique identifier of the timesheet to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ONEDESK_GET_WORKLOGSRetrieve a list of worklogs from OneDesk with optional filtering and pagination. This action attempts to list worklogs by trying multiple candidate endpoints and parameter formats. Note: The OneDesk Public API has limited endpoint support. If no worklogs endpoint is available, this action will return an empty list. Consider using the OneDesk web interface or private API endpoints for full worklog access. Use this action to: - List all worklogs in your OneDesk organization - Filter worklogs by object (ticket/task/project), user, or date range - Paginate through large worklog lists using limit and offset parameters
Input parameters
Maximum number of worklogs to return. Defaults to 100, maximum 1000.
Number of worklogs to skip for pagination. Defaults to 0.
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 by specific user ID. If not provided, returns worklogs for all users.
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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 89 agents privately built on Nagent that already use Onedesk.
Build on Nagent
Connect Onedesk to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Onedesk, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Onedesk is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Onedesk is connected, you configure its 24 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Onedesk steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Onedesk event fires, the agent kicks off automatically.
Every Onedesk action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Onedesk ships with 24 pre-built customer support actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Onedesk together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Onedesk-based workflows tailored to your business.