ghl-workflow-automation
0
总安装量
0
周安装量
安装命令
npx skills add https://github.com/justin322322/ghl-skills --skill 'GHL Workflow Automation'
Skill 文档
GHL Workflow Automation
Overview
GoHighLevel’s Workflow Builder is the automation engine powering all marketing, sales, and operational processes. Workflows replace the legacy “Campaigns” and provide a visual, drag-and-drop interface for building complex multi-step automations.
Core Concepts
| Concept | Description |
|---|---|
| Trigger | The event that starts a workflow (e.g., form submitted, tag added) |
| Action | The task performed after a trigger fires (e.g., send SMS, add tag) |
| Condition (If/Else) | Branching logic based on contact data, tags, or custom fields |
| Wait Step | A timed delay between actions (minutes, hours, days, or specific time) |
| Goal | A target state that, when reached, stops the workflow for that contact |
| Custom Values | System-wide variables for dynamic content (e.g., {{custom_values.company_name}}) |
| Custom Fields | Contact-specific data used in merge fields (e.g., {{contact.first_name}}) |
Triggers Reference
Contact Events
Contact Createdâ New contact added to the systemContact Changedâ Any field on a contact is updatedTag Added/Tag Removedâ Specific tag applied or removedContact DNDâ Do Not Disturb status changedBirthday Reminderâ Based on contact’s birthday fieldNote Added/Note Changedâ Internal notes activity
Communication Events
Customer Repliedâ Contact responds via any channel (email, SMS, etc.)Form Submittedâ A specific GHL form is completedSurvey Submittedâ A specific survey is completedTrigger Link Clickedâ Special tracking link is clickedEmail Eventsâ Email opened, clicked, bounced, complained, unsubscribedFacebook Lead Form Submittedâ Lead ad form captured
Sales & Booking Events
Appointment Statusâ Booking confirmed, cancelled, no-showedPipeline Stage Changedâ Opportunity moves to a new stageOpportunity Status Changedâ Deal won, lost, or abandonedOrder Submitted/Order Form SubmissionInvoiceâ Invoice created, sent, paid, overduePayment Received
Membership Events
Membership New SignupProduct Access Granted/Product Access RemovedOffer Access GrantedCategory Completed/Product Completed
Other Events
Task Added/Task Completed/Task ReminderStale Opportunitiesâ Opportunities inactive for a configured periodInbound Webhookâ External systems trigger the workflow via webhook URLManual / API Triggerâ Workflow started manually or via API call
Best Practice: Always apply filters to triggers. For example, filter a
Form Submittedtrigger to a specific form. Without filters, the workflow fires for ALL forms.
Actions Reference
Communication
- Send Email â HTML or plain text, with merge fields and attachments
- Send SMS / MMS â Text messages with optional media
- Send Voicemail Drop â Ringless voicemail delivery
- Send to Messenger â Facebook Messenger message
- Send Internal Notification â Alert team members via email or SMS
- Send Review Request â Automated review solicitation
Contact Management
- Add / Remove Tag
- Create / Update Contact
- Add to / Remove from Workflow
- Add Internal Note
- Create Task â Assign follow-up tasks to team members
- Assign User â Assign contact to a specific team member
- Update Custom Field â Set or modify any custom field value
- Math Operation â Increment/decrement numeric fields (e.g., lead score)
- Set Contact DND
Pipeline & Sales
- Create / Update Opportunity
- Move Opportunity Stage
- Add to / Remove from Campaign
External & Advanced
- Webhook (Custom) â Send data to external systems (Zapier, Make, custom endpoints)
- HTTP Request â Make API calls to third-party services
- Google Sheets â Add rows, update cells
- If / Else Condition â Branch logic based on data
- Go To Step â Jump to a different action in the workflow
- Wait â Delay for a specified time or until a specific day/time
Custom Values vs. Custom Fields
| Feature | Custom Values | Custom Fields |
|---|---|---|
| Scope | System-wide (same for everyone) | Per-contact (unique to each person) |
| Use Case | Company name, phone, address, branding | Contact name, email, lead score |
| Update | Change once â updates everywhere | Changes per individual contact |
| Merge Syntax | {{custom_values.field_name}} |
{{contact.field_name}} |
| Best For | Snapshots, templates, global branding | Personalization, segmentation |
Custom Values Best Practices
- Group by category â Create folders like “Business Info”, “Branding”, “Social Links”
- Use for snapshots â Store client-specific details that can be easily swapped
- Naming convention â Use
snake_casewith clear prefixes (e.g.,biz_phone,biz_email) - Keep them current â Review and update quarterly
Workflow Design Best Practices
Planning
- Map the journey first â Sketch the trigger â action flow on paper before building
- Start simple â Begin with 3-5 steps, then add complexity
- One trigger per workflow â Avoid multiple triggers causing confusion
- Use descriptive names â Name workflows clearly:
[Niche] - [Purpose] - [Channel](e.g.,Dental - New Lead Follow-Up - SMS)
Building
- Use if/else branches â Personalize paths based on tags, custom fields, or contact behavior
- Add wait steps â Space out messages naturally (don’t send 5 SMS in 1 minute)
- Set time windows â Configure delivery hours (e.g., 9 AMâ6 PM in contact’s timezone)
- Use goals â Stop the workflow when the desired outcome is achieved (e.g., appointment booked)
- Add internal notifications â Alert team members at critical workflow points
Testing
- Test with a real contact â Create a test contact and run through the entire workflow
- Verify all links â Check every URL, tracking link, and redirect
- Check merge fields â Ensure all
{{variables}}resolve correctly - Test edge cases â Verify if/else branches with different contact data
- Monitor after launch â Watch the first 10-20 enrollments for errors
Performance
- Review weekly â Check open rates, click rates, and reply rates
- A/B test messages â Experiment with different copy, subject lines, and timing
- Archive unused workflows â Deactivate and archive workflows no longer in use
- Document your automations â Maintain an internal wiki or spreadsheet listing all active workflows
Common Workflow Templates
Speed-to-Lead (New Lead Response)
Trigger: Form Submitted
â Send SMS (Immediate): "Thanks {{contact.first_name}}! We'll be in touch shortly."
â Send Email: Welcome + value proposition
â Internal Notification: Alert sales rep
â Wait 5 min
â If/Else: Contact replied?
â Yes: End workflow
â No: Send SMS follow-up
â Wait 24 hours
â Send Email: Case study / testimonial
â Wait 48 hours
â If/Else: Appointment booked?
â Yes: End workflow
â No: Send SMS with booking link
Appointment Reminder Sequence
Trigger: Appointment Status â Confirmed
â Send SMS: "Your appointment is confirmed for {{appointment.date}}!"
â Wait until 24hrs before appointment
â Send SMS: "Reminder: Your appointment is tomorrow at {{appointment.time}}"
â Wait until 1hr before appointment
â Send SMS: "See you in 1 hour! Here's the address: {{custom_values.biz_address}}"
Review Request Automation
Trigger: Pipeline Stage Changed â "Completed" / "Delivered"
â Wait 2 days
â Send SMS: "How was your experience? We'd love a review! {{custom_values.review_link}}"
â Wait 3 days
â If/Else: Review received?
â Yes: Send thank you SMS
â No: Send Email: Gentle review reminder
Key Resources
- Official Help: Workflow Actions Reference
- Templates: Available in the GHL Marketplace
- Community: GHL Ideas Board for feature requests