Duaer

Integrations

Use Zammad in Duaer

In Duaer, the Zammad node works with Zammad from a workflow. It offers 21 operations on Group, Organization, Ticket, and User.

Add Zammad to a Duaer workflow

  1. On the Duaer canvas, open the node panel, search for Zammad, and connect it after the previous node.
  2. Under Authentication, choose Basic Auth or Token Auth, then pick or create the matching credential (Zammad Basic Auth API or Zammad Token Auth API) in Credential to connect with. Refer to Zammad credentials.
  3. Pick a Resource and an Operation. For example, to create a ticket, pick Ticket and Create.
  4. Fill the fields that operation shows, such as Title, Group Name or ID, Customer Email Name or ID, and Article.
  5. Select Execute step and check the output.

Zammad operations in Duaer

The Zammad node in Duaer offers these operations, grouped by resource:

  • Group: Create, Delete, Get, Get Many, Update
  • Organization: Create, Delete, Get, Get Many, Update
  • Ticket: Create, Delete, Get, Get Many, Update
  • User: Create, Delete, Get, Get Many, Get Self, Update

Use Zammad as a tool for an AI Agent in Duaer

In the Tool input of an AI Agent, search for Zammad and add it. The agent decides when to call it. For a field the model should fill, select the sparkle next to it or write $fromAI('name', 'what to put here'); fixed values stay as you set them.

Call a Zammad endpoint the node does not cover

Add an HTTP Request node, set Authentication to Predefined Credential Type, pick Zammad Basic Auth API as the credential type, and select the same credential. Duaer signs the request with it, so you only fill in the method and URL. Refer to custom operations.

Questions

Which Zammad operations does Duaer support?

Duaer's Zammad node offers 21 operations on Group, Organization, Ticket, and User. For example, Group has Create, Delete, Get, Get Many, and Update.

Which credential does Zammad use in Duaer?

Duaer's Zammad uses Zammad Basic Auth API or Zammad Token Auth API, depending on the method you choose under Authentication.

In this section