Planyo Online Booking email verification with BillionVerify
Planyo Online Booking lets businesses accept reservations and appointments online. Pairing it with BillionVerify ensures every customer email collected at booking is real, deliverable, and free of disposable or role-based addresses — so your confirmation emails and reminders actually reach the people who booked.
Why verify before the send
A bad email address at checkout means a guest never receives their booking confirmation, leading to no-shows and support headaches. BillionVerify catches invalid, disposable, and catch-all addresses the moment they are submitted, so your reservation records stay clean and your transactional messages land in real inboxes.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before Planyo Online Booking sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in Planyo Online Booking + 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 Planyo Online Booking contacts",
"message": "Replace this Gmail send with your Planyo Online Booking 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 Planyo Online Booking
Ready-to-use workflows that verify emails before Planyo Online Booking sends.
How it works
- 1
A customer submits their email address during the Planyo booking flow.
- 2
An n8n workflow or Integrately automation sends the email to BillionVerify via the REST API.
- 3
BillionVerify returns a verdict — valid, invalid, disposable, catch-all, or role address — within seconds.
- 4
If the address is invalid or disposable, the workflow flags the booking for review or prompts the customer to re-enter their email.
- 5
Clean, verified addresses proceed through to confirmation emails and are stored in your Planyo customer records.
When to use this
Confirm reservations to real inboxes
When a customer completes a booking on Planyo, BillionVerify verifies their email before the confirmation is sent. Invalid addresses are flagged instantly, preventing failed deliveries and protecting your sender reputation with email providers.
Filter disposable emails from your guest list
Some users enter throwaway addresses to avoid marketing follow-ups. BillionVerify detects disposable and temporary email services at the point of booking, keeping your customer database trustworthy and your remarketing lists accurate.
Keep reminder campaigns deliverable
Pre-booking reminder and follow-up campaigns depend on accurate contact data. Verifying addresses as they enter Planyo means your marketing lists stay clean without manual audits.
FAQ
Will verification slow down the booking process?
No. BillionVerify's API responds in milliseconds, so the verification step is invisible to customers completing a reservation on Planyo.
Can BillionVerify handle catch-all email domains?
Yes. BillionVerify identifies catch-all domains and flags them separately, letting you decide whether to accept or review those bookings based on your risk tolerance.
Do I need to code anything to connect Planyo and BillionVerify?
Not necessarily. You can use Integrately for a one-click connection or build a simple n8n workflow. Developers can also call the BillionVerify REST API directly from a webhook.
What happens to bookings with invalid emails?
Your automation can route them to a review queue, send an in-app prompt to correct the address, or cancel the reservation — the logic is fully configurable in your n8n or Integrately workflow.
Verify emails in Planyo Online Booking
Create a free account, grab your API key, and stop bounces before they happen.
Get started free