Duplicate Run (GHL → Slack)

I’m hoping someone can help me understand why our Zap is producing duplicate Slack notifications when someone books an appointment through our calendar.

We use calendars created in GoHighLevel (GHL), and whenever an appointment is booked, two Slack notifications are triggered across two different Slack channels (each channel represents a separate company). Ideally, only the relevant company’s Slack channel should receive the alert.

Current GHL Workflow Setup

Inside GHL we have the following workflows:

Workflow 1
Trigger: Consultation calendar is filled out
Actions:

• Create / Update Opportunity in GHL

• Send Email Confirmation

• Send SMS Confirmation

• Add Tags

• Send Email / Internal Notification to the company POC

Workflow 2
Trigger: Lead Booked Appointment
Action:

• Send data to Zapier via webhook

Only Workflow 2 sends data to Zapier.

Observed Issue

Despite having only one webhook-triggered workflow, two Zap runs occur for a single booking, which results in two Slack notifications being sent — one to each company’s Slack channel.

Important notes:

• No duplicate leads are created in either GHL or Close CRM

• The duplication occurs only in Slack

• Zapier shows two runs triggered by the webhook

Zap Structure

The Zap is structured as follows:

1. Catch Webhook

2. Determine Lead Type and Lead Owner

3. Lead Type Paths

   • Booking

   • Email Enquiry

   • Social Ads

   • Other sources

4. Booking Path

   • Condition: Source Medium = Calendar

5. Get Database Data (Google Sheets)
   Used to match GHL Opportunity / Pipeline IDs

6. AI Analyzer

7. Determine Company

   • Company A

   • Company B

Each company path then runs the same process:

• Path condition: Company name

• Add / Update Opportunity in LeadConnector

• Utility step for request address

• Send Slack Notification

• Find lead in Close CRM

• Create lead & opportunity if it does not exist

• Update lead & opportunity if it already exists

Question

Since only one GHL workflow sends data to the Zap webhook, could you help identify why two Zap runs are triggered for a single appointment booking?

Is there something in the webhook trigger or Zap configuration that might cause this duplication?

Any insight on what might be causing the duplicate runs would be greatly appreciated.

Thanks so much for your help!