Escalate overdue and blocked Jira tickets with Gmail and Google Chat
Pull contacts, verify each address with BillionVerify, and continue to Google Chat — only deliverable addresses get through.
Why verify before the send
Sending to invalid, risky, catch-all, or disposable addresses spikes your bounce rate and erodes sender reputation. A verification gate before the Google Chat step removes that risk automatically — only deliverable addresses continue, the rest are flagged.
The workflow
BillionVerify — verification sits right before the send.
Node by node
- 1When clicking ‘Execute workflow’Trigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 2Schedule TriggerTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 3⚙️ CONFIGSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 4GET_JIRA_ISSUESSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 5GET_ISSUES_LISTSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 6Loop Over ItemsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 7END PROCESSSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 8ISSUE_DATE_INSIGHTSSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 9ROUTESLogic· n8n
Routes items based on the workflow logic.
- 10Verify Email (BillionVerify) 4Verify· billionverify
The BillionVerify node verifies the address — status (valid / invalid / risky / catch-all / role / disposable), is_deliverable, and a confidence score — before anything is sent.
- 11IS_OVERDUE_BETWEENLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 12Verify Email (BillionVerify)Verify· billionverify
The BillionVerify node verifies the address — status (valid / invalid / risky / catch-all / role / disposable), is_deliverable, and a confidence score — before anything is sent.
- 13GET_ISSUE_CHANGELOGSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 14DATA_FLOWSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 15CONTINUE_LOOPSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 16IF deliverable 4Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 17Verify Email (BillionVerify) 5Verify· billionverify
The BillionVerify node verifies the address — status (valid / invalid / risky / catch-all / role / disposable), is_deliverable, and a confidence score — before anything is sent.
- 18NOTIFY_TEAMSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 19IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 20AGGREGATE_ITEMSSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 21MERGE_DATASource· n8n
Provides or transforms the contact data flowing through the workflow.
- 22SEND_DUEDATE_REMINDERSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 23IF deliverable 5Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 24Wait - Rate Limit (Warning)Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 25MANAGER_ESCALATIONSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 26GET_BLOCKED_ITEMSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 27Wait - Rate Limit (Reminder)Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 28SEND_DUEDATE_WARNINGSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 29CONTINUE_LOOP_ESCALATIONSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 30Wait - Rate Limit (Escalation)Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 31COMPUTE_BLOCKED_DAYSSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 32CONTINUE_LOOP_OVERDUE_WARNINGSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 33CONTINUE_LOOP_BLOCKED_WARNINGSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 34SwitchLogic· n8n
Routes items based on the workflow logic.
- 35Verify Email (BillionVerify) 3Verify· billionverify
The BillionVerify node verifies the address — status (valid / invalid / risky / catch-all / role / disposable), is_deliverable, and a confidence score — before anything is sent.
- 36NOTIFY_TEAM_BLOCKEDSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 37Verify Email (BillionVerify) 2Verify· billionverify
The BillionVerify node verifies the address — status (valid / invalid / risky / catch-all / role / disposable), is_deliverable, and a confidence score — before anything is sent.
- 38Wait - Rate Limit (Blocked Escalation)Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 39IF deliverable 3Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 40IF deliverable 2Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 41CONTINUE_LOOP_BLOCKED_ESCALATIONSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 42SEND_BLOCKED_WARNINGSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 43MANAGER_ESCALATION_BLOCKEDSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
Workflow JSON
Copy or download this workflow, then import it in n8n (Workflows → Import from File / Paste). Install the BillionVerify community node first, then add your API key credential.
When to use this
- Cleaning a list before a Google Chat send or sync.
- Protecting Google Chat deliverability and sender reputation.
- Keeping bounce rates low so your sending is never throttled.
FAQ
Why verify before sending in Google Chat?
Verifying first keeps your bounce rate low, which protects your sender reputation and your results.
How do I import this workflow?
Download the JSON, then in n8n go to Workflows → Import from File (or paste it). Install the BillionVerify community node and add your API key credential.
What happens to risky or catch-all addresses?
They are routed to the false branch and excluded from the send. You decide whether to retry, review, or drop them.
Add verification to your workflow
Create a free account, grab your API key, and stop bounces before they happen.
Get started free