Bridge iMessage and Slack threads with Blooio for two-way messaging

Workflow preview

100%

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

Turn any Slack channel into your team's iMessage inbox. How it works → Customer texts your business number → Blooio pushes the webhook into n8n → n8n posts a new thread in Slack → Your ...

Best for

Support Chatbot automation workflows
intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.webhook, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.slacktrigger, n8n-nodes-base.filter, n8n-nodes-base.set, n8n-nodes-base.httprequest, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by David Schreiber.

Original n8n.io source

1.1 Workflow description

Title: Bridge iMessage and Slack threads with Blooio for two-way messaging
Workflow name: Bridge iMessage and Slack threads with Blooio for two-way messaging

Turn any Slack channel into your team's iMessage inbox.

How it works

📱 → Customer texts your business number 🔵 → Blooio pushes the webhook into n8n 💬 → n8n posts a new thread in Slack 🧵 → Your team replies in the thread 🔵 → n8n sends the reply through Blooio 📱 → Customer gets a blue-bubble iMessage

Why this matters

What you get	Why it matters
💙 Blue bubbles, not green	iMessage open rates blow past SMS. People read texts from friends — not from 10DLC short codes.
🧰 One tech stack, not five	No separate texting app, no SMS gateway, no CRM seat for a receptionist. Just Slack + Blooio. Your team already knows Slack.
💼 Turn Slack into a mini iMessage CRM	Every contact = one thread. Scroll the channel, see every active conversation. Search by phone, name, or keyword. Your history lives where your team already works.
📱 iMessage from any device	Desktop, phone, tablet, browser — anywhere Slack runs, your team can text customers. No shared iPhone sitting on a desk. No "let me check when I'm at my computer."
👥 Team inbox + personal reach	Your whole team sees inbound messages and can jump in. But replies still come from your business number — not from whoever happens to be on shift. Customer experience stays consistent; coverage doesn't.

More opens = more leads = more deals.

What you need

Tool	Cost	Why
Blooio	~$39/mo starting	Send + receive iMessages via REST API
Slack	Any plan	Dedicated bridge channel (private recommended)
n8n	Cloud or self-hosted	Run the workflow

⚠️ Blooio P2P notice: Blooio requires all outreach to be opt-in and actively enforces this.

The two branches

Branch	Trigger	What it does
🟥 Inbound iMessage → Slack	Blooio webhook (message.received)	Post new iMessage to Slack as a threaded parent
🟩 Slack Reply → Outbound iMessage	Any new message in bridge channel	Filter → get parent → extract phone → send via Blooio

Set up steps

Takes about 15 minutes
Sign up at blooio.com, grab your API token and webhook
Create a dedicated Slack channel
Connect Slack credentials
Create an HTTP Bearer Auth credential with your Blooio API token
Copy the Production URL to "Blooio Webhook"
Text yourself to confirm it posts threaded in Slack, reply in the thread, confirm blue bubble arrived.

Learn more at SMB Excel

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Blooio Webhook

Type / Role: n8n-nodes-base.webhook - webhook
Config choices: Version 2.1

Block 2 - Is Incoming Message

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.3

Block 3 - Post iMessage to Slack

Type / Role: n8n-nodes-base.slack - slack
Config choices: Version 2.4

Block 4 - Slack Thread Reply

Type / Role: n8n-nodes-base.slackTrigger - slackTrigger
Config choices: Version 1

Block 5 - Human Reply in Thread?

Type / Role: n8n-nodes-base.filter - filter
Config choices: Version 2.3

Block 6 - Get Thread Parent

Type / Role: n8n-nodes-base.slack - slack
Config choices: Version 2.4

Block 7 - Extract Phone + Reply

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 8 - Send iMessage via Blooio

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.4

Block 9 - Sticky Note 9a6d6867

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 10 - Sticky Note d18f2fad

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 11 - Sticky Note 483a7fcb

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

3. Summary Table

Workflow	Bridge iMessage and Slack threads with Blooio for two-way messaging
Complexity	intermediate
Nodes	11
Categories	Support Chatbot
Author	David Schreiber
Published	24 Apr 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/15264/15264.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Support Chatbot workflows

Frequently asked questions

What does Bridge iMessage and Slack threads with Blooio for two-way messaging do?

Turn any Slack channel into your team's iMessage inbox. How it works → Customer texts your business number → Blooio pushes the webhook into n8n → n8n posts a new thread in Slack → Your ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Support Chatbot use case.

David Schreiber

4 workflows

Nodes

n8n-nodes-base.webhook n8n-nodes-base.if n8n-nodes-base.slack n8n-nodes-base.slacktrigger n8n-nodes-base.filter n8n-nodes-base.set n8n-nodes-base.httprequest n8n-nodes-base.stickynote

Complexity

intermediate

Published 24 Apr 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/15264/15264.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Route RAG customer support across WhatsApp and Outlook with Pinecone and OpenRouter

## Quick overview A production-ready 3-workflow system that handles customer support across WhatsApp and Email using RAG-powered AI. Automatically routes queries, detects escalation intent, logs handoffs to Google Sheets, alerts your team via Slack, and lets agents resolve cases with a single slash command. ## How it works 1. A form trigger accepts PDF, DOCX, and TXT documents, chunks them with a token splitter, embeds them using Google Gemini, and stores them in your Pinecone vector store to build the AI knowledge base. 2. Incoming messages from WhatsApp Business Cloud API and Microsoft Outlook are each normalized into a unified contact format — capturing channel, contact ID, name, and message text — before merging into a single pipeline. 3. Every message is checked against a Google Sheets handoff tracker. If the contact is currently assigned to a human agent, the message is forwarded directly to Slack without any AI involvement. 4. For active (non-handoff) contacts, the AI Support Agent queries Pinecone via RAG, pulls context from a sliding conversation memory window, and returns a structured JSON output containing a reply and a handoff_requested flag. 5. If the AI detects escalation intent or has no answer, it sets handoff_requested: true — the contact is logged to Google Sheets, AI goes silent for that contact, and a detailed alert is posted to your Slack support channel. 6. Answers are routed back through the originating channel — WhatsApp replies via Business Cloud API, email replies via Microsoft Outlook — keeping every conversation native to its platform. 7. Support agents run /resolve [contact_id] in Slack to close a handoff. The workflow validates the input, updates the Google Sheets row with agent name and timestamp, re-enables AI for that contact, and confirms resolution in the Slack channel. ## Setup 1. Pinecone + Embeddings: Create a Pinecone index and add your Pinecone credential to the "Insert into Vector Store" and "Knowledge Base" nodes. Set your Google Gemini API credential on both Embeddings nodes (one in Workflow 1, one in Workflow 2). 2. WhatsApp: Connect your WhatsApp Business Cloud API credential to the WhatsApp Trigger node. Replace YOUR_WHATSAPP_PHONE_NUMBER_ID in both Send WhatsApp Message nodes. 3. Email: Add your Microsoft Outlook OAuth2 credential to the Outlook Trigger and the Send Email Answer node. 4. Handoff Sheet: Create a Google Sheet with a tab named Handoffs and these column headers exactly: contact_id | channel | contact_name | status | handoff_since | resolved_by | resolved_at. Set your Google Sheets credential and paste your Sheet ID into all four Google Sheets nodes across Workflows 2 and 3. 5. Slack: Create a Slack bot app, add it to your support channel, and set the credential in all three Slack nodes. Update the channel name if yours differs from #support-handoff. 6. AI Model: Add your OpenRouter (or OpenAI) API key to the Chat Model node. Swap the model slug in node settings as needed. 7. Slash Command: Activate Workflow 3 first to generate its production webhook URL. Then in your Slack app settings go to Slash Commands → Create New → set command to /resolve → paste the webhook URL → reinstall app to workspace. 8. Activate order: Workflow 1 (KB ingestion) → Workflow 3 (resolve handler) → Workflow 2 (main support flow). ## Requirements - n8n (self-hosted or cloud) - WhatsApp Business Cloud API account (Meta Developer App) - Microsoft 365 / Outlook account - Pinecone account - Google Gemini API key - OpenRouter or OpenAI API key or Any other LLM - Google Sheets - Slack workspace with a custom bot app ## Customization - Edit the system prompt in the AI Support Agent node to match your brand voice, support scope, and escalation rules - Swap Google Gemini Embeddings for OpenAI Embeddings — just replace the Embeddings node and ensure your Pinecone index dimensions match - dd more channels (Telegram, Instagram DM, etc.) by normalizing their payloads into the same contact format and feeding them into the Merge node - Adjust conversation memory window (default: 8 messages) in the Conversation Memory node - Trigger the resolve webhook from your CRM or helpdesk instead of Slack if preferred ## Additional info All three workflows must be active simultaneously for the system to function Handoff state is persisted in Google Sheets and survives n8n restarts or server reboots Once a contact enters handoff, the AI is completely silent for that contact — no accidental double-responses Document metadata (filename, uploader name, timestamp) is stored alongside vectors in Pinecone for full traceability Default chunk settings: 500 tokens / 100 overlap — tune in the Token Splitter node based on your document style Contact / Support 🔗 n8n Templates: n8n.io/creators/salmanmehboob 💼 LinkedIn: linkedin.com/in/salman-mehboob-pro 📧 Email: [email protected] 💬 WhatsApp: +92 306 746 6499

View

Answer hotel guest messages with GPT-4o mini, Slack, and Google Sheets

## Quick Overview This workflow receives guest messages via a webhook, uses OpenAI (GPT-4o-mini) to generate multilingual hotel support replies with an escalation flag, notifies the front desk in Slack when needed, logs the interaction to Google Sheets, and returns a JSON acknowledgement to the messaging gateway. ## How it works 1. Receives an inbound guest message through a webhook from a WhatsApp/Viber gateway. 2. Normalizes the incoming payload into a consistent structure (guest ID, channel, guest name, and message text). 3. Uses OpenAI (GPT-4o-mini) to generate a short reply in the guest’s language based on the built-in hotel information and outputs structured JSON with language, reply, category, and an escalate flag. 4. If the message needs human attention, posts the guest details and message to a Slack front-desk channel. 5. Routes the reply based on the reported channel and sends the generated reply text to Slack. 6. Appends the conversation data to Google Sheets and responds to the gateway with a JSON status including the detected language and whether it was escalated. ## Setup 1. Configure the inbound webhook URL in your WhatsApp/Viber gateway so it sends a payload containing at least channel, from, and text/message fields. 2. Add OpenAI API credentials for the GPT-4o-mini model. 3. Add Slack OAuth2 credentials and set the target channels for front-desk notifications and reply delivery. 4. Add Google Sheets OAuth2 credentials and update the spreadsheet/document ID and sheet tab used for logging.

View

Answer support questions from a knowledge base with OpenAI GPT-4o-mini

## Quick Overview This workflow powers a support chat experience that uses an OpenAI RAG agent with in-memory vector search to answer questions from a knowledge base, and includes a manual ingestion flow that fetches an external FAQ document, splits it into chunks, embeds it with OpenAI, and stores it for retrieval. ## How it works 1. Triggers when a new chat message is received. 2. Uses an OpenAI chat model with conversation memory to generate a support reply while following the system support guidelines. 3. Creates OpenAI embeddings for the user’s query and searches an in-memory vector knowledge base for the top matching snippets. 4. Uses the retrieved knowledge base content as a tool to ground the final answer and returns the response to the chat. 5. When run manually, fetches FAQ content from a specified URL via HTTP. 6. Splits the fetched text into chunks, converts it into documents, generates OpenAI embeddings, and inserts the vectors into the in-memory knowledge base for future queries. ## Setup 1. Add OpenAI credentials for both chat completions (GPT-4o-mini) and embeddings. 2. Update the source URL in the HTTP Request step (currently https://example.com/help-center/faq.txt) to point to your real FAQ/knowledge base content. 3. Run the manual ingestion flow once to populate the in-memory knowledge base before testing the chat trigger.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Bridge iMessage and Slack threads with Blooio for two-way messaging

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

How it works

Why this matters

What you need

The two branches

Set up steps

Learn more at SMB Excel

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Blooio Webhook

Block 2 - Is Incoming Message

Block 3 - Post iMessage to Slack

Block 4 - Slack Thread Reply

Block 5 - Human Reply in Thread?

Block 6 - Get Thread Parent

Block 7 - Extract Phone + Reply

Block 8 - Send iMessage via Blooio

Block 9 - Sticky Note 9a6d6867

Block 10 - Sticky Note d18f2fad

Block 11 - Sticky Note 483a7fcb

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions