Crisp email verification with BillionVerify
Crisp is a customer messaging and CRM platform that helps teams manage conversations, contacts, and outreach in one place. By connecting Crisp to BillionVerify — via the n8n community node, Integrately, or the REST API — teams can verify every email address before it enters the CRM or triggers a message, keeping contact lists clean and deliverability high.
Why verify before the send
CRM tools like Crisp are only as effective as the contact data inside them. Invalid addresses, disposable inboxes, and role-based emails (like info@ or support@) inflate your list, inflate your bounce rate, and quietly damage your sender reputation over time. Verifying each address at the point of capture or before a campaign fires means bad addresses never reach your sending queue — protecting deliverability, reducing costs, and keeping your Crisp workspace free of dead-end contacts.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before Crisp sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in Crisp + 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 Crisp contacts",
"message": "Replace this Gmail send with your Crisp 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 Crisp
Ready-to-use workflows that verify emails before Crisp sends.
How it works
- 1
A trigger fires in your workflow — a new Crisp contact is created, a form is submitted, or a campaign list is queued for sending.
- 2
The email address is sent to BillionVerify via the n8n community node, an Integrately 1-click automation, or a direct REST API call.
- 3
BillionVerify checks the address against SMTP validation, disposable domain lists, role-address patterns, and catch-all detection, then returns a deliverability result.
- 4
An IF/conditional step in your workflow routes the address: deliverable addresses proceed to Crisp for storage or sending; invalid or risky ones are skipped, flagged, or routed to a review list.
- 5
Your Crisp workspace receives only verified contacts, and your campaigns send only to addresses that can actually receive mail.
When to use this
Clean contacts on the way in
When a new contact is added to Crisp — from a form, live chat, or import — pass the email through BillionVerify first. Only deliverable addresses get saved, so your CRM stays clean from day one without any manual review.
Protect outbound campaigns from bounces
Before a Crisp campaign or automated sequence goes out, verify the recipient list with BillionVerify. Addresses flagged as invalid, disposable, or catch-all are filtered out, keeping your bounce rate low and your sender reputation intact.
Flag risky addresses without deleting them
Use BillionVerify's result codes to tag contacts in Crisp by deliverability status — deliverable, risky, or undeliverable. This lets your team make informed decisions about outreach without losing historical context on a contact.
FAQ
Does BillionVerify connect directly to Crisp?
BillionVerify integrates with Crisp through middleware: the n8n community node, Integrately for a no-code 1-click setup, or the BillionVerify REST API for custom builds. No direct native plugin is required.
What types of bad addresses does BillionVerify catch?
BillionVerify detects invalid addresses, disposable or temporary inboxes, role-based emails like info@ or noreply@, catch-all domains, and addresses that fail SMTP-level validation — the main sources of bounces and low engagement.
Will this slow down contact creation in Crisp?
Verification is fast — typically under a second per address. For bulk imports, you can verify the list in batch before uploading to Crisp, so real-time workflows are not affected.
Can I verify existing Crisp contacts, not just new ones?
Yes. Export your existing contact list, run it through BillionVerify in bulk via the API or n8n, then use the results to update or suppress records in Crisp before your next campaign.
Verify emails in Crisp
Create a free account, grab your API key, and stop bounces before they happen.
Get started free