Create or Update Contact - Lead Connector V2 Tagging

[DYL Admin]

Your Task History ID

IjU3NjUwNTZkMDYzNDA0M2Q1MjZjNTUzNDUxMzM1MTYxNTQzMDBmMzAi_pc

When creating or updating a contact using lead connector v2, all tags are being deleted in the GHL contact when placing the new tags. I want to just add tags to the contact where tags already exist.

 

[DYL Admin]

I found this previous thread right after I posted this. I added a step to add tags instead of adding tags in the create/update contact step. Although, "create/update" tells me that it should do just that.. if contact exists, update.

Leadconnector V2 -> add tag -> replace all tags ???

Hello it seems that when a "leadconnector V2" action is performed with a tag added , it actually removes all the tags from the contact in GHL + adds the tag ... instead of adding the tag on top of the other tags that are already associated to the contact ??? It should not remove all the tags ...

forum.pabbly.com

 

[ArshilAhmad]

Hi @DYL Admin,

Thank you for the update. I hope the issue is now resolved, and that you are able to add tags instead of replacing the older ones.

 

[Fagun Shah]

I found this previous thread right after I posted this. I added a step to add tags instead of adding tags in the create/update contact step. Although, "create/update" tells me that it should do just that.. if contact exists, update.

Leadconnector V2 -> add tag -> replace all tags ???

Hello it seems that when a "leadconnector V2" action is performed with a tag added , it actually removes all the tags from the contact in GHL + adds the tag ... instead of adding the tag on top of the other tags that are already associated to the contact ??? It should not remove all the tags ...

forum.pabbly.com

It is a GHL api issue, not a pabbly connect issue.

 

[Contactiger]

It is a GHL api issue, not a pabbly connect issue.

I don't think that we can just blame this on the GHL API, because this workaround works ...

If the Tags section of the "LeadConnector V2 : Create or Update a Contact" action is left Blank, and then a "LeadConnector V2 : Add Tags to Contact" action is used to add Tags. Then, everything works.

The current Tags are maintained, and the new tags are added.

So, Pabbly can do it!

The question is, why doesn't the Tags section of Pabbly's "LeadConnector V2 : Create or Update a Contact" action work correctly? It just needs to work the same way at the "LeadConnector V2 : Add Tags to Contact" action.

 

[ArshilAhmad]

I don't think that we can just blame this on the GHL API, because this workaround works ...

If the Tags section of the "LeadConnector V2 : Create or Update a Contact" action is left Blank, and then a "LeadConnector V2 : Add Tags to Contact" action is used to add Tags. Then, everything works.

The current Tags are maintained, and the new tags are added.

So, Pabbly can do it!

The question is, why doesn't the Tags section of Pabbly's "LeadConnector V2 : Create or Update a Contact" action work correctly? It just needs to work the same way at the "LeadConnector V2 : Add Tags to Contact" action.

That’s how the Tag field is handled in the 'Create or Update a Contact' endpoint of GHL’s API; we don’t have any control over it.

 

[Contactiger]

That’s how the Tag field is handled in the 'Create or Update a Contact' endpoint of GHL’s API; we don’t have any control over it.

OK.
Seems crazy, but thanks for explaining.