Question

Update contact in Lead connector not updating


I am using the Ai message router to interpret the text from a chatbot in LeadConnector via Webhook, then route the customer into 3 separate routes, sales, tech support, or billing.

After the Zi message router determines the route, I want it to add a tag to the contact in Go High Level (LeadConnector).  I have 3 paths set up.  If the message rute is billing, it will add the “billing” tag to the customer.  When I test the action, the tag is not added.


10 replies

Userlevel 7
Badge +14

Hi @StephAXC 

Good question.

To help us have enough context, please post detailed screenshots with how your Zap steps are configured, thanks.

 Sure… everythign works until that last step… the tag never appears in leadconnector.

I have not upgraded my account to support paths, but it should work during testing regardless, right?

 

Userlevel 7
Badge +14

@StephAXC

With your Zap ON, test live, and check the Zap Runs history data to see the DATA IN/OUT for each Zap step to help you troubleshoot.

https://zapier.com/app/history/

 

You should be able to see the GHL Contact ID to reference in GHL.

Make sure to refresh the data before viewing in GHL.

Ok, I upgraded Zapier, turned the zap on. It says it was successful and yet no tag is inside of GHL.

Step 1
steps 2 and 3.  It picked the right path
Data In
Data Out


Inside GHL after waiting and refreshing :
 


I have another zap running to add a tag in GHL that worked just fine.  Not sure why this one isn’t working.​​​​​

AHHHH!!!!  @Troy Tessalone 

I am a moron.  I was connected to the wrong GHL subaccount.  I’m tagged all over the place in a different GHL account. sigh.  thank you for your help!

 Sure… everythign works until that last step… the tag never appears in leadconnector.
Pinterest video downloader
I have not upgraded my account to support paths, but it should work during testing regardless, right?

 

I'm using the Zi message router to guide customers into different paths: sales, tech support, or billing. I've hit a roadblock when it comes to adding tags to contacts in Go High Level (LeadConnector). My setup includes three distinct paths, and I've configured it so that if a customer is routed to the "billing" path, a corresponding "billing" tag should be added to their contact. Unfortunately, during testing, it seems that the tagging action isn't functioning as expected.

I am using the Ai message router to interpret the text from a chatbot in LeadConnector via Webhook, then route the customer into 4 separate routes, thecapcutpro, sales, tech support, or billing.

After the Zi message router determines the route, I want it to add a tag to the contact in Go High Level (LeadConnector).  I have 3 paths set up.  If the message rute is billing, it will add the “billing” tag to the customer.  When I test the action, the tag is not added.

Hey, Ensure that the Ai message router is correctly configured to recognize the "billing" keyword and route the message accordingly.

Check if the message router is properly parsing the chatbot's text input and identifying the relevant keywords. I hope you understand it.

I am using the Ai message router to interpret the text from a chatbot in LeadConnector via Webhook, then route the customer into 3 separate routes, sales, tech support, or billing.
woven labels
After the Zi message router determines the route, I want it to add a tag to the contact in Go High Level (LeadConnector).  I have 3 paths set up.  If the message rute is billing, it will add the “billing” tag to the customer.  When I test the action, the tag is not added.

This is particularly concerning when dealing with critical automation processes, as it disrupts the seamless flow I rely on. I've checked the trigger conditions, verified data sources, and even tested with different input scenarios, but the problem persists. It's essential for me to ensure the reliability of my Zaps, especially when they involve complex workflows and integrations across various apps.

 

Hey Everyone, Test each path (sales, tech support, billing) independently to see capcut for ios if the tagging works for each scenario. This can help identify if the issue is specific to the "billing" route or if it's a broader problem.

Regard,

 

I am using the Ai message router to interpret the text from a chatbot in LeadConnector via Webhook, then route the customer into 3 separate routes, sales, tech support, or billing.
Rent a jet ski
After the Zi message router determines the route, I want it to add a tag to the contact in Go High Level (LeadConnector).  I have 3 paths set up.  If the message rute is billing, it will add the “billing” tag to the customer.  When I test the action, the tag is not added.

The Zap I created is designed to route incoming messages to different paths based on their content and then add corresponding tags in the CRM. However, despite rigorous testing and configuration adjustments, the tags are not being added as expected. I've meticulously checked the Zap setup, scrutinized the webhook payloads, and ensured that the authentication details are accurate. 

Reply