• Instructions to Ask a Question

    Click on the "Ask a Question" button and select the application for which you would like to ask questions.

    We have 5 different products namely - Pabbly Connect, Pabbly Subscription Billing, Pabbly Email Marketing, Pabbly Form Builder, Pabbly Email Verification.

    The turnaround time is 24 hrs (Business Hours - 10.00 AM to 6.00 PM IST, Except Saturday and Sunday). So your kind patience will be highly appreciated!

    🚀🚀Exclusive Discount Offer

    Just in case you're looking for any ongoing offers on Pabbly, you can check the one-time offers listed below. You just need to pay once and use the application forever -
     

    🔥 Pabbly Connect One Time Plan for $249 (🏆Lifetime Access) -  View offer 

    🔥 Pabbly Subscription Billing One Time Plan for $249 (🏆Lifetime Access) - View offer

[GHL] LeadConnector v1 & v2 contact creation differences

gjpab

Member
Your Task History ID
IjU3NjUwNTZjMDYzNjA0MzQ1MjZmNTUzNjUxM2E1MTZhNTQzNTBmMzAi_pc
Hey, I'm using separate Pabbly workflows for client sub-accounts in GHL and recently started noticing that my workflows in GHL are not firing after contact creation. After investigating I found it to be with how the tags are created. So for example, when using the LeadConnector v1 app in Pabbly, double quotes are not added to the tags but added when using the v2 app.

We'll be using the LeadConnector v2 app going forward as v1 could be phased out soon. I could simply switch my workflows to include the double quotes for tags, but that doesn't solve the purpose as we're deploying sub-accounts using snapshots and would like to maintain consistency in our assets and configuration.

Workflow using LC v1 app:
Task History ID: IjU3NjUwNTZjMDYzNjA0MzQ1MjY4NTUzMzUxMzU1MTY0NTQzNDBmMzUi_pc
Executed at: Nov 03, 2024 23:42:07, (UTC+00:00) Europe/London

Workflow using LC v2 app:
Task History ID: IjU3NjUwNTZjMDYzNjA0MzQ1MjZmNTUzNjUxM2E1MTZhNTQzNTBmMzAi_pc
Executed at: Nov 03, 2024 19:39:12, (UTC+00:00) Europe/London

I've also attached screenshots of contacts created in separate accounts showing the differences when using the LC v1 and v2 apps. Can this be resolved asap since it is impacting live customer orders?
 

Attachments

  • pabbly-v1.png
    pabbly-v1.png
    33.2 KB · Views: 16
  • pabbly-v2.png
    pabbly-v2.png
    33.4 KB · Views: 9

Preeti Paryani

Well-known member
Staff member
Hello @gjpab

Since via both the workflow contact is created, hence the workflow to be triggered at contact creation should get triggered in any case. To check the issue related to that we would need to check that workflow too. Please share the workflow URL of the workflow with contact created as the trigger step.
my workflows in GHL are not firing after contact creation.

Can you please let us know what you refer to by maintaining consistency in your assets? Does it mean by how tags are been added?
would like to maintain consistency in our assets and configuration.

Also, please let us know how you want the tags to be added, as per LC v1 or LC v2, and whether it would maintain the consistency.
 

gjpab

Member
Here's the link to my workflows.

Using LC v2 app:

Using LC v1 app:

I need the contact tagged without double quotes when using the LC v2 app. (i.e. customer, not "customer")
 

Preeti Paryani

Well-known member
Staff member
Hello @gjpab

You have again shared the same workflows. We have asked you to share the workflow which is not getting triggered as contact gets created by the above workflows.

Please share the workflow URL of the workflow with the contact created as the trigger step.
 

gjpab

Member
That's a GHL workflow. It has the trigger 'contact created' with a tag filter that Pabbly adds on every run but doesn't fire since the tag contains double quotes.
 

Preeti Paryani

Well-known member
Staff member
Hello @gjpab

Please try to remove the double quote from the Tag in the Lead Connector v2:Create or Update Contact action step and let us know if it works for you.

1730895715209.png
 

Attachments

  • 1730895636906.png
    1730895636906.png
    79.9 KB · Views: 6
  • 1730895648881.png
    1730895648881.png
    79.8 KB · Views: 6
Top