How to Use the Check iMessage Action in Your GHL Workflow

Overview
Project Blue can detect whether a contact is an iPhone user before you send them a message. The Check iMessage action in GoHighLevel lets you automatically route iPhone users and non-iPhone users down different paths in your workflow — so you can send iMessages to those who support it and fall back to SMS for everyone else.

How It Works
Setting this up takes two steps inside your GHL workflow: adding the Check iMessage action, then adding a branch to split contacts based on the result.

Step 1: Add the Check iMessage Action Inside your workflow, add a new action. Go to Apps, scroll down until you find Project Blue, and select Check iMessage. In the phone number field, enter the contact's phone number using the raw format variable (not a formatted version). This is important — Project Blue needs the number in raw format to detect correctly whether the contact is on an iPhone.

Step 2: Add an If/Else Branch After the Check iMessage action, add a new action and choose If/Else from GHL's native actions. Set up the branch with these settings: - Branch type: Project Blue - Action: Check iMessage - Condition: Available - Value: True

Once saved, your workflow will split into two paths — iPhone users go left, and non-iPhone users go right. You can then tailor the messaging in each branch accordingly.

🎥 Want to see it in action?
https://www.loom.com/share/15fe79a360b240a0bffd5eba282918c6

Key Things to Know
- Always use raw format for the phone number field. Formatted numbers can cause the detection to fail or return incorrect results.
- The If/Else branch must be configured with all three settings (Project Blue → Check iMessage → Available → True) for the split to work correctly.
- Contacts detected as iPhone users are routed to the left branch; everyone else goes to the right branch.
- This action works at the workflow level, so it runs each time a contact enters that workflow — great for automations where you don't know in advance what device a contact is using.

Related Features
This way you can keep using your A2P line for massive actions and Project Blue only for specific ones, it depends on your use case.