Actions57
- User Actions
- Organization Actions
- Group Actions
- Ticket Actions
- Article Actions
- Priority Actions
- State Actions
- Tag Actions
- Mention Actions
- Online Notification Actions
- Object Actions
- User Access Token Actions
User → Me
AI-generatedOverview
This node interacts with the Zammad REST API to perform various operations on different resources such as users, organizations, groups, tickets, mentions, tags, states, priorities, articles, online notifications, objects, and user access tokens. Specifically, for the 'User' resource and 'Me' operation, it retrieves information about the currently authenticated user. This is useful for workflows that need to fetch user profile details or verify the identity of the API user.
Use Case Examples
- Retrieve the current user's profile information to personalize a workflow.
- Check the authenticated user's details before performing user-specific actions.
Properties
| Name | Meaning |
|---|---|
| Authentication | The authentication method to use for connecting to the Zammad API. |
| API | The API to use for the request, either REST API or CTI API. |
Output
JSON
id- The unique identifier of the user.login- The login name of the user.firstname- The first name of the user.lastname- The last name of the user.email- The email address of the user.created_at- Timestamp when the user was created.updated_at- Timestamp when the user was last updated.roles- Roles assigned to the user.preferences- User preferences and settings.
Dependencies
- Zammad API
Troubleshooting
- Authentication errors due to incorrect credentials or token. Verify the authentication method and credentials used.
- API endpoint errors if the resource or operation parameters are incorrect. Ensure the 'resource' is set to 'User' and 'operation' to 'Me' for this use case.
- Network connectivity issues preventing API requests. Check network settings and API availability.
Links
- Zammad API Documentation - Official documentation for Zammad REST API endpoints and usage.