What is your goal?I want to create a new contact or update contact in GHL whenever someone purchase a ticket through lovable.dev
What is the problem & what have you tried?I don’t want duplicate contact. Person1 is already in the contact
Person1 purchased the ticket and used New email and existing Phone number
I will have error I did not turned on the duplication in GHL
Screenshots (scenario flow, module settings, errors)Hi @Macky0002311,
In create OR update situations you indeed 1) search for a record and if it exist a) update it or if it doesn’t exist b) create it. I recommend to use one router for this, as you probably do not need the second Search Contacts module.
This is the generic principle, GHL might behave differently though.
My problem was this specific person used a different email address but she is already in the GHL system’s contact so the search module only looked for email and it went to the create path.
My question is how can I make the search module look for either email or phone number? Sorry I’m new to automation
That might happen, you can never build a 100% airtight deduplication method.
What did you map in the Search Contacts module right now? Is phone number an available field?
Cheers,
Henk
@Macky0002311 Thanks for sharing this, I can see the issue.
Right now, the flow isn’t clearly separating when to update vs when to create. So even if a contact already exists (same phone), it can still try to create a new one, which causes the duplicate error in GHL.
We just need to tighten the logic:
If contact exists → update only
If not → create only
