SherpaDesk and Zammad Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Build support workflows between SherpaDesk and Zammad on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about SherpaDesk and Zammad

Detailed info you need to know about SherpaDesk and Zammad integrations in WEXTL. Explore which modules apps support and how you connect them.

  • SherpaDesk

    • Support
    • 2 triggers
    • 17 searches
    • 10 actions

    IT help desk and service management: tickets, tasks, assets, accounts, invoices, time entries and knowledge.[5]

  • Zammad

    • Support
    • 53 searches
    • 83 actions

    Open-source help desk and customer support ticketing system.[6]

How to connect SherpaDesk to Zammad

Set up your SherpaDesk and Zammad integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between SherpaDesk and Zammad work in WEXTL?

WEXTL exposes actions and triggers for SherpaDesk and Zammad that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

SherpaDesk triggersZammad actions

SherpaDesk modules

  • Add a Ticket Response Posts a reply on a SherpaDesk ticket, with an Action such as response and the Note Text of the post.
  • Create a Ticket Opens a ticket from a Subject and an Initial Post, tied to an Account ID (-1 for none). Use Tech ID to assign a technician, Class ID for a class and Location ID for a location.
  • Create a Time Entry Logs Hours of work in SherpaDesk, with a Note Text describing the work. Use Ticket Key to log it against a ticket, or turn on Is Project Log for a project, and No Invoice to keep it off invoices.
  • Create a Todo Adds a todo to SherpaDesk from its Title. Add Text for the description, Assigned ID for who does it and Due Date for when. Turn on Notify to tell the assignee.
  • Create an Asset Adds an asset to SherpaDesk under a Name. Use Category ID, Type ID, Make ID, Model ID and Status ID to classify it, and Location ID to place it in one of your locations.
  • Get a Location Shows a single location from your SherpaDesk account.
  • Get a Profile Looks up the profile of the signed-in SherpaDesk user.
  • Get a Ticket Retrieves one ticket from SherpaDesk by either its ticket key or its number.
  • Get an Invoice Fetches one SherpaDesk invoice by its Invoice ID. Use Action to run a command on it, such as sendEmail.
  • Get Ticket Counts Counts tickets by state: Open All, Open As Tech, On Hold, Waiting, Unconfirmed and Parts On Order, plus New Messages and Reminder.
  • Get Tickets by Keys Pulls several tickets in one call. Use Keys to give a comma-separated list of ticket keys or numbers.
  • List Accounts Lists SherpaDesk accounts with their Name, Primary Contact and Locations. Turn on Is With Statistics to add statistics, or Is Open Tickets to keep accounts that have open tickets.
  • List Assets Shows the assets recorded in SherpaDesk. Use Limit to stop after a set number of records.
  • List Invoices Fetches the invoices in SherpaDesk. Use Limit to cap the number of invoice records.
  • List Locations Gathers the locations in SherpaDesk. Use Limit to read fewer of them.
  • List Organizations Finds the organizations in SherpaDesk, each with a Key, a Name and its Instances.
  • List Projects Looks up projects with their Open Tickets, Closed Tickets, Logged Hours and Remaining Hours. Use Account to stay within one account and Is With Statistics to add project statistics.
  • List Queues Browses the ticket queues in SherpaDesk. Use Sort By to order them by a field.
  • List Task Types Collects the task types used on time entries. Use Account or Project to limit the result to one account or project.
  • List Tickets Searches tickets by Status such as open, closed or allopen. Use Account for one account, Role for your part on the tickets, and Query with the value all to search every ticket.
  • List Time Entries Reads logged time. Use Type for a query kind such as recent, and Tech, Account or Project to focus on one person or client.
  • List Todos Pulls the todos in SherpaDesk. Use Is Completed to filter by completion, All Item Types to include every item type, and Is Sub View for the sub-view.
  • Make an API Call Calls the SherpaDesk REST API directly with a free-form request under your saved credential.
  • Update a Profile Changes the Skype handle on the profile of one user in SherpaDesk.
  • Update a Time Entry Edits a logged time entry. Change the Hours, Note Text, Task Type ID or Tech ID, and turn on Is Project Log to mark it a project log.
  • Update a Todo Turn on Is Completed to mark a SherpaDesk todo as complete.
  • Upload a File Uploads a File to SherpaDesk. Attach it to a ticket with Ticket or to an asset with Asset, and use File Name to rename it.
  • Watch Accounts Polls SherpaDesk for accounts that were not there on the previous run, each with its Name and Primary Contact. Use Limit to set how many are taken at once.
  • Watch Projects Finds projects that appeared since the last scheduled check. Every project arrives with its Name, Account Name and Estimated Hours.

Zammad modules

  • Add a Knowledge Base Answer Attachment Attaches a File to a knowledge base answer under the File Name that readers see, including its extension such as setup-guide.pdf.
  • Add a Ticket Link Links two tickets of a Link Type, either Normal for related tickets or Parent and Child for a hierarchy. The source ticket is given by its ticket number, not its ID.
  • Add a Ticket Mention Subscribes a user to the updates of a ticket. Leave User empty to subscribe yourself.
  • Add a Ticket Tag Applies a Tag to a ticket. A tag that does not exist yet is created, provided you are allowed to.
  • Archive a Knowledge Base Answer Archives a knowledge base answer and returns the updated Answer.
  • Create a Calendar Sets up a business-hours calendar for a Time Zone such as Europe/Berlin. Business Hours give one working window per day, and Holiday Feed URL pulls public holidays from an iCal feed.
  • Create a Checklist Starts a checklist for a ticket. Pick a Template to copy its items, or leave it empty for a blank checklist.
  • Create a Checklist Item Writes a new entry on a checklist from its Text, such as Call the customer back. Turn on Checked to record it as already done.
  • Create a Checklist Template Saves a reusable checklist under a Name such as Onboarding. Fill Items with the item texts in order, and switch Active off to hide it from agents.
  • Create a Data Privacy Task Queues the deletion of a User under data privacy rules. It runs in the background and cannot be undone.
  • Create a Group Registers a group, with :: between names to make a subgroup such as Sales::Europe::South. Use Assignment Timeout to unassign unanswered tickets after some minutes, and Assign Follow-ups to keep the previous owner on reopened ones.
  • Create a Knowledge Base Answer Writes an answer under a Category ID, with the Title readers see and a Locale ID for its language. Add a Body of text, where HTML is allowed.
  • Create a Knowledge Base Category Opens a category with a Title, a Locale ID and a Font Awesome Icon code such as f115. Set Parent Category ID to nest it, or leave it empty for a top-level category.
  • Create a Role Sets up a role such as VIP service by Name. Fill Permission IDs with the permissions it grants, and turn on Default at Signup to give it to every new user who signs up.
  • Create a Shared Draft Saves a Draft Article on a ticket for other agents to pick up and send. An existing draft on that ticket is replaced.
  • Create a Tag Adds a Name to the tag list, such as refund.
  • Create a Ticket Opens a ticket with a Title, a Group, a Customer and a First Article. Map guess:jane@example.com as the customer to find or create them by email, and use Suppress Notifications to skip agent email and in-app notifications.
  • Create a Ticket Article Adds a message to a ticket from its Body, as a note by default. Set Type to email to send it to the To recipients, and mark it Internal to hide it from customers.
  • Create a Ticket Priority Defines a priority named like 4 urgent, which Zammad sorts by Name. Turn on Default for New Tickets to give it to tickets created without one.
  • Create a Ticket State Adds a state from a Name and a State Type ID that decides how it behaves. Turn on Ignore Escalation to pause SLA escalation in it, and use Next State for pending states.
  • Create a Time Accounting Entry Logs Time Unit spent on a ticket, such as 60.0, in the unit your admin has set. Add an Activity Type ID when activity types are in use.
  • Create a User Registers a user from a First Name, Last Name and Email, and Zammad matches incoming email to users by Email. Leave Login empty to default it to the email address, and note that only admins can set Roles.
  • Create an Access Token Generates a personal access token with the Permissions it grants, named after where it is used. Leave Expires On empty for a token that never expires.
  • Create an Object Manager Attribute Defines a custom field on an Object, with a lower-case Name using underscores and a Display Name for agents. Give Data Options as JSON, and mind that a Data Type is final once created.
  • Create an Organization Provisions an organization by Name. Use Domain with Domain Assignment to enroll users of that email domain automatically, and turn on Shared to let members see all of its tickets.
  • Create an SLA Defines an SLA under a Name that uses a business-hours Calendar. Set First Response Time, Response Time, Update Time and Solution Time in minutes, and Condition to choose which tickets it covers.
  • Delete a Calendar Removes a business-hours calendar once the SLAs that use it have been moved to another calendar.
  • Delete a Checklist Removes a checklist from its ticket.
  • Delete a Checklist Item Deletes one entry from the to-do list of a ticket checklist.
  • Delete a Checklist Template Removes a checklist template. Checklists already made from it stay as they are.
  • Delete a Group Deletes a group, which works only while no tickets remain in it.
  • Delete a Knowledge Base Answer Deletes a help-center answer from the knowledge base that holds it.
  • Delete a Knowledge Base Answer Attachment Deletes a file that is attached to an answer of a knowledge base.
  • Delete a Knowledge Base Category Removes a knowledge base category, which must be empty first.
  • Delete a Shared Draft Removes the shared draft stored on a ticket and returns its Shared Draft ID.
  • Delete a Tag Removes a tag from the tag list, which also removes it from every ticket.
  • Delete a Ticket Deletes a ticket by its numeric ID rather than its ticket number. This cannot be undone.
  • Delete a Ticket Mention Removes a mention subscription from a ticket. Only your own mentions can be removed.
  • Delete a Ticket Priority Deletes a priority level that is not in use by any ticket in Zammad.
  • Delete a Ticket State Removes a ticket state that no ticket currently has.
  • Delete a Time Accounting Entry Removes a time entry that was logged on a ticket.
  • Delete a User Deletes a user together with whatever references them, which can include tickets. The deletion sticks.
  • Delete All Online Notifications Clears every online notification of the current user at once.
  • Delete an Access Token Revokes an access token, so integrations that use it stop working.
  • Delete an Object Manager Attribute Deletes a custom field attribute from an object. Its removal takes effect after the migrations are executed.
  • Delete an Online Notification Removes a single entry from your online notifications.
  • Delete an Organization Deletes an organization, which cannot have users or tickets at that point.
  • Delete an SLA Deletes a service-level agreement from Zammad.
  • Execute Object Manager Migrations Applies pending object manager changes, such as added or deleted attributes, in one run.
  • Get a Calendar Fetches a business-hours calendar with its Timezone, Business Hours, Public Holidays and iCal URL.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with SherpaDesk and Zammad integrations. Pick any from the list below if the current combination isn't the one you need.

Automate SherpaDesk and Zammad on WEXTL®

Claim your 3-day trial to build SherpaDesk with Zammad integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting SherpaDesk and Zammad.

How do I connect SherpaDesk and Zammad?

Connect your SherpaDesk and Zammad accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between SherpaDesk and Zammad?

Example: when the "Watch Accounts" trigger in SherpaDesk fires, WEXTL can "Add a Knowledge Base Answer Attachment" in Zammad. SherpaDesk has 2 triggers (including Watch Accounts and Watch Projects). Zammad has 136 actions (including Add a Knowledge Base Answer Attachment, Add a Ticket Link, and Add a Ticket Mention). Add filters and transforms between steps when you need them.[1]

Can SherpaDesk trigger actions in Zammad, and Zammad in SherpaDesk?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate SherpaDesk and Zammad?

No. SherpaDesk-to-Zammad automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does SherpaDesk integrate with Zammad in real time?

Yes. Trigger-based automations start the moment SherpaDesk (or Zammad) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a SherpaDesk + Zammad integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect SherpaDesk with Zammad?

You can build your SherpaDesk + Zammad automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the SherpaDesk and Zammad integration.

  1. SherpaDesk and Zammad integration source code, module specs and credentials implementation.
  2. Our SherpaDesk and Zammad integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for SherpaDesk and Zammad, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. SherpaDesk integration information
  6. Zammad integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted SherpaDesk and Zammad integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore SherpaDesk and Zammad, or get started