Actions208
- Activity Feed Actions
- Availability Actions
- Call Actions
- Call User Actions
- Callback Actions
- Chat Actions
- Checklist Actions
- Company Actions
- Company Category Actions
- Component Actions
- CPU Actions
- Domain Actions
- Employee Actions
- HDD Type Actions
- IP Actions
- Mail Actions
- Manufacturer Actions
- Operating System Actions
- PC Actions
- Periphery Actions
- Project Actions
- Remote Support Actions
- Search Actions
- Service Actions
- Software License Actions
- Get Software Licenses
- Create Software License
- Get Software License by ID
- Update Software License
- Delete Software License
- Get Software License Types
- Create Software License Type
- Get Software License Type
- Update Software License Type
- Delete Software License Type
- Get Expiring Licenses
- Get Software License Assignments
- Get Software License Contracts
- Copy Software License
- Get Software License Properties
- Get Software License Types Treeview
- Ticket Actions
- Ticket Content Actions
- Ticket List Actions
- Ticket State Actions
- Timestamp Actions
Checklist → Check Item
AI-generatedSummary
Check or uncheck a checklist item associated with a specified linked entity (e.g., a ticket) in the TANSS system.
Inputs
- Auth Mode — Select which TANSS credential type to use for authentication; options are 'Generated Token' or 'User Login (Auto Refresh)' (default is 'User Login').
- Link Type ID (required) — Numeric identifier of the link type, e.g., 11 for tickets, specifying the kind of entity the checklist is linked to.
- Link ID (required) — Numeric ID of the linked entity such as a ticket to which the checklist item belongs.
- Check Item Body (required) — A collection of fields specifying the checklist item to update, including 'Item ID' (the checklist item's ID), 'Checklist ID', 'Main Checklist ID', 'Value' (1 to check, 0 to uncheck), 'Multi Select ID', and optional JSON 'Vars' for additional parameters.
Output shape
a single JSON object representing the updated checklist item status as returned by the TANSS API.
The operation uses the provided authentication mode. All inputs under 'Check Item Body' are used to build the request body. The output reflects the success or failure of checking/unchecking the specified checklist item, with no inherent pagination.