Introduction
This Zapier integration derivative work based on an actual user requirements. When his 35+ step zap started to fail because of authentication issues he wanted a solution created for him. He was surprised that no other agencies had the same problem as him. Perhaps, there are no many agencies that had such a comprehensive on board process including creating sub-accounts, user and contact (with tagging) in a single zap. The solution created for him has the ability for the location to use their tokens after it is created.
Use the service desk to request for the invitation link. When you are setting up the Connection in Zapier for your Agency, make sure you take the option to include all sub-accounts and also for future installation. The latter will ensure that your Agency token can be use for the newly created sub-account/location.
Important Notices
This integration includes features that are only available to Agencies with a Agency Pro ($497) plan.
This integration assumes that the data is provided in JSON format and you can API documentation here
Disclaimer :
The token created by this integration does not keep the location token.
Authentication
The authentication used here is Oauth2.0 as described in GoHighLevel(GHL) API 2.0 documentation.
Unknown to many, this implementation by GHL need to start with an app created from their developer marketplace with a clearly defined scope. In this case it is :
contacts.readonly contacts.write locations.write locations.readonly locations/tags.write users.readonly users.write
and other settings.
All these are are automatically handled by Zapier with this integration.
Triggers
There is current no triggers associated with integration
Actions
At the point where your upstream steps, eg trigger from Google sheet through a series of steps to ensure other required data like timezone, had prepared the required data is available you can start to insert the following into your zap.
Create Sub-account
Reference : https://highlevel.stoplight.io/docs/integrations/7cfc7963eda7c-create-sub-account-formerly-location
The mandatory fields includes : name, companyId, and fields in prospectInfo.
If you do not which to hardcode your companyId in the json use Get Sub-accounts where app is installed action (see below).
Create Location Token
The required locationId will be from Create Sub-account step.
Reference : https://highlevel.stoplight.io/docs/integrations/1a30b217da571-get-location-access-token-from-agency-token
Create User
The following mandatory data are available from Create Location Token step :
- Location Access Token
- companyId
- locationId
Reference : https://highlevel.stoplight.io/docs/integrations/cf3f982337757-create-user
Create Contact
The following mandatory data are available from Create Location Token step :
- Location Access Token
- locationId
Reference : https://highlevel.stoplight.io/docs/integrations/4c8362223c17b-create-contact
Delete Location
This is useful when you are developing your app ~~~~zap. The mandatory locationId is required from earlier zap steps.
Reference : https://highlevel.stoplight.io/docs/integrations/54dd4c281f465-delete-sub-account-formerly-location
Get Sub-accounts where app is installed
This action has been modified to return you the companyId if you do not wish to insert it manually.
This action to return a list of all sub-accounts where this app is being used as it was in tended by GHL API 2.0
Reference : https://highlevel.stoplight.io/docs/integrations/aeed19d08490e-get-location-where-app-is-installed