Skip to content

Helpdesk · Beta

Atomicwork
API integration

Ship Helpdesk features without building the integration. Full Atomicwork API access via Proxy, normalized data through Unified APIs, and 30+ MCP-ready tools for AI agents — all extensible to your exact use case.

Built for specific customer use cases. Issues are resolved quickly.

Talk to us
Atomicwork

Use Cases

Why integrate with Atomicwork

Common scenarios for SaaS companies building Atomicwork integrations for their customers.

01

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.

02

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.

03

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.

04

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.

05

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

Ship these features with Truto + Atomicwork

Concrete product features your team can ship faster by leveraging Truto’s Atomicwork integration instead of building from scratch.

01

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.

02

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.

03

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.

04

Change management automation with attachments

Open change records with file attachments (Terraform plans, scan reports), then patch them as approvals or deployment outcomes progress.

05

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.

06

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.

SuperAI

Atomicwork AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

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.

Why Truto

Why use Truto’s MCP server for Atomicwork

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 500+ integrations.

01

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

02

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

03

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

04

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

05

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

06

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

Unified APIs

Unified APIs for Atomicwork

Skip writing code for every integration. Use Truto’s category-specific Unified APIs out of the box or customize the mappings with AI.

Unified User Directory API

Activities

Activities are the actions performed by users in the source application.

View Docs

Users

The User object represents a User.

View Docs

Workspaces

Workspaces represent concepts like teams, workspaces, projects in apps that support them

View Docs

How It Works

From zero to integrated

Go live with Atomicwork in under an hour. No boilerplate, no maintenance burden.

01

Link your customer’s Atomicwork account

Use Truto’s frontend SDK to connect your customer’s Atomicwork account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

02

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

03

Call our API, we call Atomicwork

Truto’s Proxy API is a 1-to-1 mapping of the Atomicwork API. You call us, we call Atomicwork, and pass the response back in the same cycle.

04

Unified response format

Every response follows a single format across all integrations. We translate Atomicwork’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about Atomicwork on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

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.

Atomicwork

Get Atomicwork integrated into your app

Our team understands what it takes to make a Atomicwork integration successful. A short, crisp 30 minute call with folks who understand the problem.

Talk to us