Hi Megan,

I wanted to share a couple of options to help eliminate the redundant Zap activity you're experiencing:

Zap 1

RealGeeks to TLA CRM

Zap 2

Webhook to Real Scout

Zap 3

RealScout to TLA CRM

1. Introduce duplicate checking in Zap 3 (RealScout to TLA CRM):
   Before continuing the workflow, include a step that checks if the contact’s email already exists in GHL. If a match is found, the Zap should be halted to prevent duplication.

2. Implement a custom field in RealScout (e.g., “Synced from GHL”):
   This field can be marked as True/False. At the end of Zap 2 (Webhook to RealScout), update the contact in RealScout to mark “Synced from GHL” as True. Then, in Zap 3, add a filter to exclude any contacts where this field is already marked True, so only unsynced contacts and ones you’ve entered manually to RealScout are pushed back to GHL

Hope that helps!

Hi ​@MeganWilliams 

Feedback from your Reddit post: https://www.reddit.com/r/zapier/comments/1krg8ea/lead_keep_moving_in_between_zaps_without_hault/

You may need to check your GHL Automation logic that fires the Zap webhook.

For GHL, the Zap action "Add/Update Contact" should stop the Zaps from running again since if it is updating an existing contact.

Regardless, you probably want to add a Tag or set the Source for the GHL Contact, so you know where the Contact originated, then use those data points to help you Filter in Zaps to stop the looping.

If you add a Tag or the Source to the GHL Contact (RealGeeks, RealScout), then when the Zap fires for the webhook, you can check which Tag/Source, and only continue under your desired conditions.
e.g. Filter condition with [Tag/Source] ‘does not contain’ “RealScout”.

So that would prevent RealScout leads from being sent to RealScout again.