Bridge Gmail and iMessage with Blooio and log conversations to Close
Email ↔ iMessage Bridge (via Blooio + Gmail) A 2-branch bidirectional bridge. Email a customer from Close (or any CRM) — they get a blue-bubble iMessage. They reply on iPhone — it lands in your Gmail with the phone nu...
Template notes
Email ↔ iMessage Bridge (via Blooio + Gmail)
A 2-branch bidirectional bridge. Email a customer from Close (or any CRM) — they get a blue-bubble iMessage. They reply on iPhone — it lands in your Gmail with the phone number in the subject. Reply in Gmail — it goes back out as iMessage. No database, no state store. The subject IS the routing table.
How it works
- ⏰ 📬 Gmail Trigger polls a dedicated bridge inbox every minute for new outbound email - 🔍 IF node validates the subject contains a phone number (\+?\d{10,15}) — drops everything else - 🧹 Set node extracts the phone from the subject and strips HTML + quoted reply chains from the body - 💬 Blooio Messaging node sends the cleaned text as iMessage to the extracted phone - 📡 Blooio Webhook fires on message.received — inbound iMessages arrive in real-time - 📧 Set node builds a consistent subject iMessage from +15551234567, Gmail Send delivers to your main inbox with Reply-To set back to the bridge — so your reply re-enters Branch 1 - 🗂️ In parallel, the workflow looks up the lead in Close by phone and logs the inbound iMessage as an email activity — attaches it to the lead timeline AND triggers Close Sequence exit
The 2 branches
| Branch | Trigger | What it does | |--------|---------|--------------| | 🟢 Email → iMessage | Gmail Trigger (1-min poll) | Phone-in-subject → strip quoted chains → send iMessage via Blooio | | 🟣 iMessage → Email | Blooio Webhook (message.received) | Build threaded subject → send to main inbox with Reply-To → log to Close |
Why this matters
| Metric | Manual | This workflow | |--------|--------|---------------| | ⚡ Speed | Switch apps every reply, lose context | Stay in Gmail, customers get blue bubbles | | 🔁 Consistency | Some texts in Messages, some in a 3rd-party app | Every conversation in one Gmail thread | | 📉 CRM gaps | Texts never reach Close — lead timeline is half a story | Every inbound iMessage logged + Sequence exits fire | | 🧠 Staff time | 30–60 sec per reply jumping apps | Zero — reply in the inbox already open |