- 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?
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?
