--- title: Atomicwork API Integration on Truto slug: atomicwork category: Helpdesk canonical: "https://truto.one/integrations/detail/atomicwork/" --- # Atomicwork API Integration on Truto **Category:** Helpdesk **Status:** Beta ## Unified APIs ### Unified User Directory API - **Activities** — Activities are the actions performed by users in the source application. - **Users** — The User object represents a User. - **Workspaces** — Workspaces represent concepts like teams, workspaces, projects in apps that support them ## MCP-ready AI tools Truto exposes 37 tools for Atomicwork that AI agents can call directly. - **list_all_atomicwork_service_catalog_categories** — List all service catalog categories in an atomicwork workspace. Returns: id, name, item_count, archived, created_at. Required: workspace_id. - **list_all_atomicwork_forms_requests** — List request form fields for requests in atomicwork. Returns form field data from the `data` array. Requires at least one of: `request_id`, `service_item_ids`, a combination of `channel_id` + `channel_type` + `request_form_type`, or `workspace_id` + `request_form_type`. - **create_a_atomicwork_request** — Create a new request in atomicwork. Returns the created request object including id, display_id, subject, status, and priority. - **list_all_atomicwork_assessment_forms** — Get the assessment form associated with a specific problem in atomicwork. Returns the assessment form data object. Required: workspace_id, problem_id. - **create_a_atomicwork_assessment_form** — Submit an assessment form for a specific problem in atomicwork. Required: problem_id. - **list_all_atomicwork_assets** — List all assets in atomicwork. Returns a paginated array of asset objects under the data field. - **create_a_atomicwork_asset** — Create a new asset in atomicwork. Required: asset_type_id and form_fields containing the asset's attributes such as display_name, serial_number, status, and assigned_to. - **create_a_atomicwork_change_management_change** — Create a change request in atomicwork. Accepts fields such as subject, change_type, status, priority, urgency, impact, requester, and custom_fields to populate the new change record. - **list_all_atomicwork_workspaces** — List all atomicwork workspaces. Returns: id, name, type, description, is_default, member_count, created_at. - **list_all_atomicwork_requester_entities** — List requester entities available for REQUEST forms in atomicwork. Returns: id, label, value, deactivated for each entity. - **list_all_atomicwork_audit_logs** — List audit logs in atomicwork. Returns log entries including id, event_type, module, event_at, and log_text, along with actor user details. Required: server. - **list_all_atomicwork_workspace_members** — List all members of an atomicwork workspace. Returns a collection of workspace member objects. Required: workspace_id. - **update_a_atomicwork_workspace_member_by_id** — Update a workspace member in atomicwork by id. Required: workspace_id and id. - **list_all_atomicwork_service_catalog_items** — List service catalog items in Atomicwork for a specific workspace and category. Returns items from the service catalog. Required: workspace_id, category_id. - **get_single_atomicwork_requests_id_by_id** — Get a single request by id in Atomicwork. Returns the full request object for the specified workspace. Required: workspace_id, id. - **get_single_atomicwork_requests_number_by_id** — Get a specific request in Atomicwork by id. Returns the full request object. Required: id. - **atomicwork_requests_number_partial_update** — Partially update an existing request in Atomicwork by id. Returns the updated request object. Required: id. - **delete_a_atomicwork_requests_number_by_id** — Delete a specific request in Atomicwork by id. Returns an empty response on success. Required: id. - **create_a_atomicwork_requests_v_2** — Create a new request in Atomicwork. Returns the created request object. - **list_all_atomicwork_requests_search** — List and search requests in an atomicwork workspace. Returns request data from the specified workspace. Required: workspace_id. - **list_all_atomicwork_requests_count** — Get the total count of requests in an atomicwork workspace. Returns the aggregate count of requests matching the query. Required: workspace_id. - **list_all_atomicwork_request_views** — List request views in atomicwork. Returns a collection of request view objects available in the system. - **list_all_atomicwork_request_priority_options** — List available request priority options in atomicwork for a given workspace. Returns priority option records from the workspace. Required: workspace_id. - **create_a_atomicwork_request_activity_note** — Create an activity note on an atomicwork request identified by its display ID. Required: display_id. - **list_all_atomicwork_request_trash** — List trash entries associated with a specific atomicwork request. Required: display_id. - **list_all_atomicwork_user_lists** — List all lists associated with a specific user in an atomicwork workspace. Returns the collection of user list records. Required: workspace_id, user_id. - **update_a_atomicwork_problem_task_by_id** — Update a task belonging to a specific problem in atomicwork. Required: problem_id and id. - **get_single_atomicwork_assets_id_by_id** — Get a single asset by id in Atomicwork. Returns the asset object. Required: id. - **update_a_atomicwork_assets_id_by_id** — Update an existing asset by id in Atomicwork. Required: id. - **list_all_atomicwork_assets_search** — List and search assets in Atomicwork. Returns a collection of asset records from the data field of the response. - **get_single_atomicwork_change_management_changes_number_by_id** — Get a specific change management change in atomicwork by id. Returns the full change record. Required: id. - **atomicwork_change_management_changes_number_partial_update** — Partially update a change management change in atomicwork by id. Sends a PATCH request to modify one or more fields on the specified change record. Required: id. - **create_a_atomicwork_change_management_changes_create_with_file** — Create a new change management change record with file attachments in atomicwork. Submits a multipart form payload to include both change metadata and associated files in a single request. - **create_a_atomicwork_change_trash** — Move a change to trash in Atomicwork change management. Required: display_id. - **list_all_atomicwork_change_activity_notes** — List activity notes for a specific change in atomicwork. Returns a collection of activity note records associated with the change. Required: change_id. - **create_a_atomicwork_user** — Create a new user in atomicwork via the settings API. Returns the created user object. - **create_a_atomicwork_attachment** — Create an attachment in atomicwork by submitting a multipart form data request to upload a file. ## How it works 1. **Link your customer's Atomicwork account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Atomicwork.** The Proxy API is a 1-to-1 mapping of the Atomicwork API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Sync IT assets and auto-create incident tickets from MDM platforms** — SaaS Management and MDM vendors can keep Atomicwork's asset inventory aligned with real device state and instantly file tickets when a device drifts from policy. This eliminates manual reconciliation between hardware management and ITSM. - **Power zero-touch onboarding from HRIS and lifecycle platforms** — HR and onboarding platforms can provision users in Atomicwork and trigger structured service catalog requests for laptops, software, and access the moment a new hire is finalized. This turns HR events into orchestrated IT workflows without manual handoffs. - **File change records directly from CI/CD and alerting pipelines** — DevOps and observability platforms can programmatically open Atomicwork change records with attached plans or vulnerability reports, setting urgency and impact based on alert severity. IT Ops stays compliant without slowing engineering deployments. - **Stream audit logs into SIEM and compliance platforms** — Security and compliance vendors can pull Atomicwork audit logs to verify that access changes map to approved requests and generate assessment forms when drift is detected. This closes the loop between identity governance and ticketed approvals. - **Embed ticket creation and status inside your product** — Any B2B SaaS tool can let end users file Atomicwork requests, attach context, and track status without leaving the host app. This reduces context switching for employees who already live in your product. ## What you can build - **Dynamic service catalog request forms** — Fetch workspace-specific catalog categories and items, then submit structured requests so Atomicwork's AI can auto-route and categorize them correctly. - **Two-way ticket sync with activity notes** — Create, update, search, and fetch Atomicwork requests by ID or number, and post activity notes back to keep both systems in lockstep. - **Asset lifecycle synchronization** — Create new assets, update status and assignment fields, and search the asset inventory to mirror hardware state from your MDM or CMDB. - **Change management automation with attachments** — Open change records with file attachments (Terraform plans, scan reports), then patch them as approvals or deployment outcomes progress. - **User and workspace provisioning** — Use the Unified User Directory API alongside native user creation to provision Atomicwork accounts, map workspace members, and update roles on lifecycle events. - **Compliance feeds for SIEM and GRC tools** — Pull Atomicwork audit logs on a schedule and correlate them with assessment forms to flag access drift and trigger automated remediation workflows. ## FAQs ### How does authentication work for connecting end-user Atomicwork accounts? Truto handles the full auth handshake and securely stores credentials per connected account. Your users connect their Atomicwork workspace once, and you call Truto's unified endpoints — no token refresh, storage, or rotation logic on your side. ### Can we create requests with workspace-specific custom fields? Yes. You can list service catalog categories and items along with forms metadata to discover the fields required per workspace, then submit them via the request creation endpoints so Atomicwork's AI can triage and route correctly. ### Does the integration support both incident tickets and change records? Yes. Requests (incidents/service requests) and Change Management are exposed as separate resources, including creation with file attachments for changes and partial updates for both as they progress through their lifecycle. ### How do we keep asset data fresh between our system and Atomicwork? You can poll the asset search and list endpoints on your preferred cadence and use the update endpoint to push status, assignment, or lifecycle changes back. Truto normalizes pagination so you can sync large inventories reliably. ### Can we pull audit logs for compliance and SIEM use cases? Yes. The audit logs endpoint is available for periodic retrieval, which you can stream into downstream SIEM, GRC, or data warehouse pipelines to correlate with identity and access events. ### What if we need an Atomicwork endpoint that isn't listed today? Truto ships new endpoints on request and maintains the underlying API quirks (pagination, rate limits, error normalization) so you don't have to. Reach out and additional Atomicwork tools can typically be added without changes to your integration code path. ## Related reading - [Connect Atomicwork to Claude: Handle change management & audit logs](https://truto.one/blog/connect-atomicwork-to-claude-handle-change-management-audit-logs/) — Learn how to connect Atomicwork to Claude via Truto's MCP Server. Automate change management, query audit logs, and streamline IT operations with AI tools. - [Connect Atomicwork to ChatGPT: Manage Service Requests & IT Assets](https://truto.one/blog/connect-atomicwork-to-chatgpt-manage-service-requests-it-assets/) — Learn how to connect Atomicwork to ChatGPT using a managed MCP server. Automate IT service requests, asset management, and change workflows with AI. - [Connect Atomicwork to AI Agents: Sync Service Catalogs & User Data](https://truto.one/blog/connect-atomicwork-to-ai-agents-sync-service-catalogs-user-data/) — Learn how to connect Atomicwork to AI agents using Truto's /tools endpoint. Bypass custom boilerplate and bind native ITSM capabilities directly to your LLM.