Zammad email verification with BillionVerify
Zammad is an open-source helpdesk and customer support platform that centralises tickets, chat, and email communication. Integrating BillionVerify with Zammad ensures that customer email addresses collected during ticket creation or contact import are valid and reachable, reducing bounce-related delivery failures and keeping your support queue clean.
Why verify before the send
Support teams rely on accurate email addresses to follow up with customers and send ticket updates. Invalid addresses cause delivery failures, disposable addresses come from users who will never engage, and role-based aliases can land in unmonitored inboxes. BillionVerify filters all three before they enter Zammad, so your agents spend time on real customers.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before Zammad sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in Zammad + BillionVerify",
"nodes": [
{
"parameters": {},
"type": "n8n-nodes-base.manualTrigger",
"typeVersion": 1,
"position": [
240,
300
],
"name": "When clicking ‘Test workflow’"
},
{
"parameters": {
"assignments": {
"assignments": [
{
"id": "email-field",
"name": "email",
"value": "jane@example.com",
"type": "string"
}
]
},
"options": {}
},
"type": "n8n-nodes-base.set",
"typeVersion": 3.4,
"position": [
460,
300
],
"name": "Get contacts"
},
{
"parameters": {
"sendTo": "={{ $json.email }}",
"subject": "Message for Zammad contacts",
"message": "Replace this Gmail send with your Zammad node — only deliverable, verified contacts reach it.",
"options": {}
},
"type": "n8n-nodes-base.gmail",
"typeVersion": 2.1,
"position": [
900,
300
],
"name": "Send email",
"webhookId": "",
"credentials": {
"gmailOAuth2": {
"id": "",
"name": "Gmail account"
}
}
},
{
"parameters": {
"operation": "verify",
"email": "={{ $json.email }}",
"additionalOptions": {}
},
"type": "n8n-nodes-billionverify.billionVerify",
"typeVersion": 1,
"position": [
540,
300
],
"name": "Verify Email (BillionVerify)",
"credentials": {
"billionVerifyApi": {
"id": "",
"name": "BillionVerify account"
}
}
},
{
"parameters": {
"conditions": {
"options": {
"caseSensitive": true,
"leftValue": "",
"typeValidation": "loose"
},
"combinator": "and",
"conditions": [
{
"id": "is-deliverable",
"leftValue": "={{ $json.is_deliverable }}",
"rightValue": "",
"operator": {
"type": "boolean",
"operation": "true",
"singleValue": true
}
}
]
}
},
"type": "n8n-nodes-base.if",
"typeVersion": 2,
"position": [
720,
300
],
"name": "IF deliverable"
}
],
"connections": {
"When clicking ‘Test workflow’": {
"main": [
[
{
"node": "Get contacts",
"type": "main",
"index": 0
}
]
]
},
"Get contacts": {
"main": [
[
{
"node": "Verify Email (BillionVerify)",
"type": "main",
"index": 0
}
]
]
},
"Verify Email (BillionVerify)": {
"main": [
[
{
"node": "IF deliverable",
"type": "main",
"index": 0
}
]
]
},
"IF deliverable": {
"main": [
[
{
"node": "Send email",
"type": "main",
"index": 0
}
],
[]
]
}
},
"settings": {
"executionOrder": "v1"
}
}Workflow templates with Zammad
Ready-to-use workflows that verify emails before Zammad sends.
How it works
- 1
Connect Zammad to n8n using its REST API or the Integrately integration.
- 2
Trigger the workflow when a new ticket is created or a contact is added.
- 3
Pass the customer's email address to BillionVerify for verification.
- 4
Route contacts with valid addresses into the normal Zammad workflow; flag or reject invalid and disposable addresses.
- 5
Optionally notify the customer or agent when an address fails verification so it can be corrected promptly.
When to use this
New ticket email validation
When a customer submits a ticket and provides an email address, trigger a BillionVerify check via n8n before the ticket is confirmed, preventing invalid or throwaway addresses from creating orphaned support records.
Contact list import hygiene
Before bulk-importing customer contacts into Zammad from a CSV or external CRM, verify the email list with BillionVerify to remove invalid and disposable addresses, protecting deliverability for all future outreach.
Automated contact auditing
Schedule a recurring workflow that queries Zammad for recently added contacts, verifies their email addresses, and flags any that have become invalid — keeping your helpdesk contact database accurate over time.
FAQ
Can BillionVerify prevent fake emails from creating Zammad tickets?
Yes. By adding a BillionVerify verification step before a ticket is finalised, you can reject submissions from disposable or clearly invalid email addresses.
What does BillionVerify check beyond basic syntax?
Beyond syntax, BillionVerify checks domain validity, MX record existence, mailbox reachability via SMTP, and whether the address belongs to a disposable or catch-all domain.
Does this require changes to Zammad itself?
No. The integration runs in n8n or Integrately as a middleware layer, so Zammad requires no modifications or plugins.
How do I handle customers who provide a catch-all address?
BillionVerify flags catch-all addresses separately so you can decide whether to accept them with a warning or require an alternative address — giving you fine-grained control over your acceptance policy.
Verify emails in Zammad
Create a free account, grab your API key, and stop bounces before they happen.
Get started free