Skip to content
English
Go to linqapp.com
  • There are no suggestions because the search field is empty.

GHL: Workflows

GHL Workflows SOP

What is it?

  • Workflows are automations in GHL. Companies use these to automate internal processes and outbound responses to customers.

Screenshot 2025-08-12 at 2.13.54 PM

Why it Matters

Most customers are using Linq Blue to integrate with their workflows

  • A well-optimized Linq Blue workflow should:
    • Increase Response Rate
    • Improve show rate, conversion, etc.
    • Set them apart from competition
    • Illuminate activation moment
    • Grow customer affinity and revenue
    • Correctly follows time settings
  • All with a hands-off, automatic approach

Terms to Know

Triggers

  • The event or condition that starts a workflow. (“When this happens, do this”)
    • A workflow can have one or multiple triggers.
    • Watch for events in real time or based on scheduled conditions.
    • Once the condition is met, the contact (or lead, opportunity, etc.) enters the workflow.

Screenshot 2025-08-13 at 12.36.39 PM

  • Most common
    • Contact Created
      • New contact added to GHL
        • Could be from form fill, Linq App, manual, etc.
    • Contact Tag
      • Categorize contact types
        • Real Estate example
          • Buyer
          • Seller
          • 500k+
          • 300k+
    • Contact Card
      • Helps with identifying the sender
    • Form Submitted
      • Facebook
      • Instagram
      • TikTok

Action

  • What the workflow does once it has been triggered. (“When this happens, do this”)
    • Execute in the order you set them.
    • Unlimited actions in a workflow.
    • Can communicate with the contact, update data, or interact with other systems.

Screenshot 2025-08-13 at 12.38.33 PM

  • Most common
    • Add contact tag
      • Automatically adds tag to contact
        • Ex. Form fill on Facebook ad targeted towards people wanting to sell their home
          • Automatically tags as “Seller”
    • Assign to user
      • Ex. Enters into salesperson’s queue
    • Send SMS
      • Uses LeadConnector number to send SMS
    • Send Internal Notification
      • Ex. Notify salesperson a new lead has entered the pipeline
    • Add contact Card
      • Receiver obtains the contact card of the sender for easy identification when calling/texting.
    • If / Else
      • Ex. “If recipient replies ‘Yes,’ send Message A,” “If recipient replies ‘No,’ send Message B”
    • Wait
      • Ex. wait 30 minutes before Send SMS #2

Use Cases

Default Messaging Provider

  • If Linq Blue is set as the primary provider:
    • All outbound messages with automatically be Linq Blue (even if it says SMS)
    • Don’t have to change workflows or select “iMessage” when sending manual texts
    • Turnkey for Workflows
    • Client doesn’t have to learn new processes or actions
    • Cannot use SMS anymore unless they change Linq Blue back to secondary provider
  • If Linq Blue is set as secondary provider
    • Will have to use our custom actions to send messages with Linq Blue number
    • Will still be able to use SMS number
    • Have to ensure all messages (workflows and manual) follow best practices
    • Can create fringe cases

Our Actions

Screenshot 2025-08-18 at 1.53.10 PM

  • Send iMessage

Screenshot 2025-08-19 at 10.45.45 AM

  • Wait for reply
    • Will not send a new message until a reply is sent from number
    • Helpful for following workflow time settings

Screenshot 2025-08-19 at 10.41.27 AM


Screenshot 2026-01-26 at 12.44.44 PM
  • Send Group iMessage

Screenshot 2025-08-19 at 10.39.47 AM

  • How group message looks in Linq App

Screenshot 2025-08-19 at 10.38.14 AM

  • Share Contact
      • Sends a contact card

      Screenshot 2025-12-10 at 7.58.52 PM
      Screenshot 2025-12-10 at 8.00.39 PM
  • Check iMessage Availability
    • 50+ new conversations per day limit

image (1) (2)

Handling Replies in Workflows with Linq Blue

“Stop on response” and Linq Blue

When you use Linq Blue iMessage actions inside a workflow, the built-in Stop on response setting in the workflow does not apply to those actions.

image (31)

That means:

  • A contact can reply to a Linq Blue message and the workflow will keep running.

  • Any future actions in the cadence (additional Blue messages, emails, tasks, etc.) will still execute unless you explicitly remove the contact from the workflow.

If you want a workflow to stop as soon as a contact replies to a Linq Blue message, you’ll need to add your own stop logic.

Recommended pattern: Remove from workflow on reply

To stop a Linq Blue cadence when someone responds:

  1. Add a reply trigger

    • In your workflow, add a step that triggers when the contact replies
      (e.g. a “Contact replied” / “Customer replied” condition, depending on your CRM).

  2. Use the “Remove From Workflow” action

    • Under Internal actions, select Remove From Workflow.

    • Place this action immediately after your reply condition so that as soon as the contact responds, they are removed from the workflow.

      Screenshot 2026-01-07 at 8.39.45 AM

  3. Confirm behavior

    • Test with a sample contact:

      • Enroll the contact in the workflow.

      • Let the first Linq Blue message send.

      • Reply to that message from the contact’s phone.

      • Verify in the workflow’s Enrollment / Execution logs that the Remove From Workflow action runs and no further steps are executed.

When to use this pattern

Use the reply + Remove From Workflow pattern whenever:

  • You’re running a Linq Blue iMessage cadence (multiple texts in a sequence).

  • You want any reply to stop further automated messages.

  • You previously relied on Stop on response and noticed contacts still receiving follow-up iMessages.

This ensures that once a contact is actively engaging in a conversation, they are no longer pushed through automated Blue messaging in that workflow.