Confluence email verification with BillionVerify
Confluence is a team productivity and knowledge-management workspace where organizations document processes, collaborate on content, and share information. Pairing it with BillionVerify lets you validate email addresses collected through Confluence-connected workflows before they are stored or used for notifications.
Why verify before the send
Knowledge bases and internal tools often collect email addresses through embedded forms, user registrations, or integrations with other systems. Unverified emails lead to failed notifications, bounced invitations, and bloated contact lists. BillionVerify filters out invalid, disposable, and catch-all addresses so your team communications consistently reach real people.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before Confluence sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in Confluence + 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 Confluence contacts",
"message": "Replace this Gmail send with your Confluence 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 Confluence
Ready-to-use workflows that verify emails before Confluence sends.
How it works
- 1
Connect BillionVerify to your automation layer using the n8n community node or Integrately.
- 2
Set a trigger when a new email address enters your Confluence-connected workflow — for example, a form submission or webhook event.
- 3
Send the email address to BillionVerify for real-time verification.
- 4
Evaluate the result: valid addresses proceed; invalid, disposable, or role-based addresses are flagged or removed.
- 5
Write only verified contacts back to Confluence-linked systems such as your CRM or mailing list.
When to use this
Validate emails from embedded intake forms
When a Confluence page or connected form captures a visitor or team member's email, run it through BillionVerify before adding the contact to any mailing list or CRM, ensuring only reachable addresses are stored.
Clean up notification recipient lists
Before triggering automated Confluence space notifications or page-update alerts to a list of stakeholders, verify each address with BillionVerify to prevent bounces and maintain a healthy sender reputation.
FAQ
Does this integration require Confluence admin access?
Not necessarily. The verification step happens in your automation tool (n8n or Integrately), which sits between Confluence and downstream systems, so no Confluence admin changes are typically required.
How does BillionVerify handle catch-all domains?
BillionVerify flags addresses on catch-all domains — servers that accept all incoming mail regardless of whether the mailbox exists — so you can decide whether to include or exclude them based on your risk tolerance.
Is there a limit to how many addresses I can verify?
BillionVerify offers plans for both low-volume real-time checks and high-volume bulk verification, so you can match the plan to however many contacts flow through your Confluence workflows.
Can BillionVerify detect disposable email addresses?
Yes. It maintains an up-to-date list of disposable and temporary email providers and flags any address from those domains, helping you keep low-quality sign-ups out of your workspace communications.
Verify emails in Confluence
Create a free account, grab your API key, and stop bounces before they happen.
Get started free