LeadConnector V2 Custom API 401 Scope Error

[Kri8itDigital]

Hi,

I am trying to use the Custom API action with the LeadConnecter V2.

I am trying to create a conversation via the API as per the documentation here - https://highlevel.stoplight.io/docs/integrations/8d0b19e09176e-create-conversation

Error Received: 401 Error The token is not authorized for this scope.

Do we have the conversations.write scope enabled/passed in the auth request?

 

[ArshilAhmad]

Hi @Kri8itDigital,

Please try setting up the endpoint in this manner and see if that fixes your issue.

 

[Kri8itDigital]

Hi @Kri8itDigital,

Please try setting up the endpoint in this manner and see if that fixes your issue.
View attachment 45878

The token is created by the LeadConnector V2 connection from Pabbly. How can we access this token?

 

[Supreme]

Can you please share the workflow URL once in which you have tried the same so that we can look into it?

Also please refer to the following short recorded video on how you can get the API token from your GHL(LeadConnector) account.

Loading…

www.screenpresso.com

 

[Kri8itDigital]

Can you please share the workflow URL once in which you have tried the same so that we can look into it?

Also please refer to the following short recorded video on how you can get the API token from your GHL(LeadConnector) account.

Loading…

www.screenpresso.com

Thank you for your response.

The workflow link is below:

Pabbly - Online Marketing & Sales Software

Automate your sales and marketing with Pabbly. Unite email marketing, lead capture, WordPress themes, subscription all at one place.

connect.pabbly.com

With regards to the API key - I don't know if that will work as the API has updated to work with the OAuth flow when connecting the action listed under Connections.

The token required would be from that connection and not the standard API key on the account.

When creating the OAuth connection to LeadConnector the URL generated to grant the access contains the scopes that will be enabled. So the url has a parameter called "&scope=" with a space separated list of scopes as below.

The current list of scopes in the Pabbly integration are:

&scope=conversations/message.readonly%20conversations/message.write%20campaigns.readonly%20locations/customFields.readonly%20locations/customFields.write%20contacts.readonly%20contacts.write%20opportunities.readonly%20opportunities.write%20users.readonly%20users.write%20locations.readonly%20locations.write%20locations/tasks.readonly%20workflows.readonly%20businesses.write%20businesses.readonly%20calendars.readonly%20calendars/events.write%20locations/templates.readonly%20locations/customValues.readonly%20locations/customValues.write%20funnels/redirect.write

We are missing "conversations.write%20conversations.readonly%20"

Thanks!

 

[Supreme]

We recommend you run that API request correctly on Postman first and then try the same CURL on API using the Pabbly action step.