Leadconnector v1 and v2

[J.B. Murdock]

GoHighLevel announced API v1 is deprecated, and it will be sunset by June 1, 2024.

GoHighLevel API V1.1.20

> API v1 is deprecated, and it will be sunset by June 1, 2024. Please use the v2 API - [https://highlevel.stoplight.io/docs/integrations/0443d7d1a4bd0-overview](https://highlevel.stoplight.io/docs/integrations/0443d7d1a4bd0-overview) For any queries email us at...

public-api.gohighlevel.com

Does this affect all instances of Leadconnector v1?

I also noticed that most of the v2 actions are not as detailed as some on v1 and that more actions need to be added to get the same result.

Can I get some clarification on this so I can start migrating from v1 to v2 if I have to?

Thanks.

 

[Pabblymember11]

Hey @J.B. Murdock

The deprecation of GoHighLevel API v1 will affect all instances of Leadconnector v1. As you consider migrating to v2, please note that some v2 actions may require additional steps compared to v1 to achieve the same level of detail.

Could you also inform us of any additional fields or action steps you require in V2 so that we can investigate and assist you accordingly?

 

[J.B. Murdock]

One issue we are running into right now is assigning a user/owner to the contact record (we can assign an owner to the opportunity).

They recently added the ability to separate assigning a user/owner to the contact and the opportunity, so you can have a different owner for both.

In V1 we were able to assign the user/owner in the create/update opportunity step.

In V2 we can assign a user/owner to the opportunity, but there is no longer an owner attached to the contact record.

We have workflows that trigger based on the user/owner of the contact record, not the opportunity.

Is there a way in the create/update action to assign a user/owner in the contact record?

 

[Pabblymember11]

In V2 we can assign a user/owner to the opportunity, but there is no longer an owner attached to the contact record.

We have workflows that trigger based on the user/owner of the contact record, not the opportunity.

Is there a way in the create/update action to assign a user/owner in the contact record?

As per the V2 API documentation of LeadConnector, they haven't mentioned the Owners field in the Create or Update Opportunity action step.

Upsert Opportunity | Integrations API

Upsert Opportunity Powered by Stoplight.

highlevel.stoplight.io

Upsert Contact | Integrations API

Please find the list of acceptable values for the `country` field <a href="https://highlevel.stoplight.io/docs/integrations/ZG9jOjI4MzUzNDIy-country-list" target="_blank">here</a><br><br>If `Allow Duplicate Contact` is disabled under Settings, th... Powered by Stoplight.

highlevel.stoplight.io

 

[J.B. Murdock]

As per the V2 API documentation of LeadConnector, they haven't mentioned the Owners field in the Create or Update Opportunity action step.

Upsert Opportunity | Integrations API

Upsert Opportunity Powered by Stoplight.

highlevel.stoplight.io

Upsert Contact | Integrations API

Please find the list of acceptable values for the `country` field <a href="https://highlevel.stoplight.io/docs/integrations/ZG9jOjI4MzUzNDIy-country-list" target="_blank">here</a><br><br>If `Allow Duplicate Contact` is disabled under Settings, th... Powered by Stoplight.

highlevel.stoplight.io

Thanks, Supreme.

Can this be escalated to the High Level or someone in your organization?

To be clear, the missing field is (Assigned to Owner/User) Create or Update Contact—Action Step.

Not

(Assigned to Owner/User) Create or Update Opportunity—Action Step. This field is available and functioning well.

High Level recently separated the Assignments so that you could assign one user to the Contact and another to the Opportunity.

This is why the field (Assigned to Owner/User) Create or Update Contact—Action Step in Pabbly API is critical and needs to be added ASAP.

 

[Pabblymember11]

Please make sure to review the LeadConnector API documentation carefully. They have not mentioned the "Assigned to/Owner's" field.

Once they add support for the "Assigned to/Owner" field in their API documentation, we will definitely update it on our end.

We recommend that you contact the LeadConnector support team to request them to add this information to their API documentation.

Upsert Contact | Integrations API

Please find the list of acceptable values for the `country` field <a href="https://highlevel.stoplight.io/docs/integrations/ZG9jOjI4MzUzNDIy-country-list" target="_blank">here</a><br><br>If `Allow Duplicate Contact` is disabled under Settings, th... Powered by Stoplight.

highlevel.stoplight.io

 

[Pabblymember11]

Hey @J.B. Murdock

Can this be escalated to the High Level or someone in your organization?

To be clear, the missing field is (Assigned to Owner/User) Create or Update Contact—Action Step.

Not

(Assigned to Owner/User) Create or Update Opportunity—Action Step. This field is available and functioning well.

High Level recently separated the Assignments so that you could assign one user to the Contact and another to the Opportunity.

This is why the field (Assigned to Owner/User) Create or Update Contact—Action Step in Pabbly API is critical and needs to be added ASAP.

In response to your concern, our team has included the 'assigned to' field in the 'Create or Update' action steps of the LeadConnector, following the API documentation. Please check this on your end and inform us of any issues.

 

[J.B. Murdock]

Thanks for your reply.

I did see that we could get the user ID by using the "Search User" action.

The issue is that the "Search User" action is for agency level users only and not subaccount (location level).

We need the same functionality that the "Assign to" under the Create user.

In this instance it is only assigning the user to the opportunity and not the contact record.

---

Sidenote: When I search for the leadconnector app v2, the search does not auto filter and I cannot find the app in the list.

 

[Pabblymember11]

Hey @J.B. Murdock

We are currently checking on it, please allow us some time.

 

[Pabblymember11]

Hey @J.B. Murdock

We have cross-checked your requirements with the LeadConnector team, and according to their reference, they currently do not support the "Assign To" field for users.

 

[J.B. Murdock]

I am confused because the field was added to the API Action step in Pabbly in Version 2.

This field was in and functioned in Version 1.

Also, as previously stated, you can add a user in the Assign to Field in the Add or Update Opportunities, but not the Contacts.

 

[Pabblymember11]

Yes, we have reviewed your query on my end with the LeadConnector support team and after consulting with the team, they confirmed that it is currently not possible to create an "Assign to" field for contacts.

 

[J.B. Murdock]

The Assign User Exists in the Action Step, but there is no User Drop-Down List to select like in the Opportunities. This is not that complicated to resolve.

 

[Pabblymember11]

Please note that if the desired fields and options you are looking for are available in the LeadConnector API documentation, we will add them. However, if the Assign option is not available on their end, we are unable to do so.

We have already consulted with them, and they currently do not support this in the V2 API of LeadConnector. For more clarity on your specific requirements, we recommend contacting the LeadConnector support team.

 

[J.B. Murdock]

I understand that nothing can be changed without the API Documentation from HL.

I did put in a ticket with HL, and then I was told the API Documentation was updated.

I don't understand why the Field was added in your Pabbly Action Step when it was not previously there in the same Action Step.

Why add the Field if it cannot be mapped to the User from the API Documentation from HL?

Can you understand my confusion and frustration with something so simple?

 

[Pabblymember11]

Please allow us some time, we are checking on it, and shall notify you with an update soon.

 

[J.B. Murdock]

I spoke to the High-Level (Lead Connector) Developers today, and they will update the API Documentation very soon.

 

[Pabblymember11]

Ok, thanks for the update, let us know if you get any further updates on the LeadConnector team.

 

[J.B. Murdock]

Please check and see if the Lead Connector documentation has been updated.

They told me it would be completed by today, Friday.

 

[Pabblymember11]

Please check and see if the Lead Connector documentation has been updated.

They told me it would be completed by today, Friday.

We have already updated the integration team, and they will update the action steps here once it's reflected in the API reference.