Zammad icon

Zammad

Consume Zammad REST API

Actions57

User Access Token → List

AI-generated

Overview

This node interacts with the Zammad API to manage User Access Tokens. Specifically, it supports listing all user access tokens, creating new tokens with specified labels, expiration dates, and permissions, and deleting tokens by ID. This node is useful for automating the management of API access tokens within Zammad, such as generating tokens for integrations or cleaning up unused tokens.

Use Case Examples

  1. List all user access tokens to audit current API access.
  2. Create a new user access token with specific permissions for a third-party integration.
  3. Delete a user access token that is no longer needed to maintain security.

Properties

Name Meaning
Authentication The authentication method to use for connecting to the Zammad API. Options include Basic Authentication, OAuth2 Authentication, and Token Authentication.
API The API to use for the operation. Options are REST API or CTI API.
Resource The resource to operate on, fixed to 'User Access Token' for this operation.
Operation The operation to perform on the User Access Token resource. Supported operations are 'list', 'create', and 'delete'.
label The label to assign to a new user access token (used in create operation).
expires_at The expiration date/time for the new user access token (used in create operation).
permissions The permissions to assign to the new user access token, specified as an array of permission strings (used in create operation).

Output

JSON

  • id - The unique identifier of the user access token.
  • label - The label assigned to the user access token.
  • expires_at - The expiration date/time of the user access token.
  • permission - The list of permissions assigned to the user access token.

Dependencies

  • Zammad API

Troubleshooting

  • Ensure the correct authentication method and credentials are configured; authentication failures will prevent API access.
  • Verify that the API endpoint URLs are correct and accessible from the environment where the node runs.
  • When creating tokens, ensure the permissions array is correctly formatted and contains valid permission strings.
  • If deletion fails, confirm the token ID exists and the authenticated user has permission to delete tokens.

Links

Discussion