OtherReal-timeUpdated May 2026

Zammad

Zammad open-source helpdesk

Zammad is the open-source self-hosted helpdesk platform — modern UI, multi-channel (email, phone, chat, Twitter, Facebook), used by teams that want a Zendesk-class helpdesk with full data control. Tiny Command exposes two actions, no triggers (Zammad emits ticket events via webhooks configured in admin; point at a Tiny Command webhook trigger URL): Create Group (org structure — Groups are Zammad's team/department primitive), Create Organization (a customer organisation record). The connection takes the Zammad instance URL plus a user API token. For non-profit, healthcare, government, and other privacy-sensitive orgs that need helpdesk without sending customer data to SaaS, Zammad is a frequent choice. The German-origin codebase is particularly popular in DACH/Europe. For "self-hosted Zendesk", Zammad and OTRS are the main options.

Connect Zammad

0triggers

2actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Zammad can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Create Group	Creates a ticket group in Zammad (the open-source helpdesk). Groups are the routing primitive that ties agents, signature, and shared mailbox together.	1 fields	View →
Create Organization	Creates an organization (B2B customer account) in Zammad. Used to mirror your CRM accounts into the helpdesk before contacts arrive.	1 fields	View →

Recipes

Pre-built Zammad workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Zammad → Slack alerts

AI-triage every Zammad event, ping the right channel only when it matters.

Zammad → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Zammad → Notion database

Turn Zammad into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Zammad once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Zammad field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Zammad integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Zammad to Tiny Command?

Open the Tiny Command workflow builder, drop in a Zammad node, and click Connect. Authorize Zammad once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Zammad triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Zammad today. Use Tiny Command's universal Webhook or Schedule trigger to start Zammad workflows, then run any Zammad action you need.

What Zammad actions can I run from a workflow?

2 Zammad actions are available out of the box, covering other operations like "Create Group". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Zammad integration real-time?

Zammad actions execute synchronously inside your workflow. Tiny Command waits for Zammad's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Zammad with Tiny Command?

No. Every Zammad trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Zammad API endpoint directly.

How much does the Zammad integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Zammad integration itself has no per-app surcharge.