Obtain API credentials in the GHL developer portal, assign the socialplanner/tag.readonly scope, and securely store keys in Kenect settings to authorize requests.
Link Kenect to the Users API via OAuth 2.0 or API key provisioning in the connection panel, then test the connection.
GET /social-media-posting/:locationId/tags — fetches tags for a location; POST /social-media-posting/:locationId/tags/details — adds or updates tags; socialplanner/statistics.readonly — read-only analytics for dashboards; POST /social-media-posting/statistics — generate engagement statistics; Note: Additional endpoints 5–17 are available but not required for this page.
Trigger: A new social post appears for a location.
Actions: fetch tags (Endpoint1), apply tags to the post, and log results in analytics.
GET /social-media-posting/:locationId/tags
locationId, tags, postId
Trigger: when a report is requested in Kenect dashboard
Actions: POST /social-media-posting/statistics to generate metrics; return results to dashboard
POST /social-media-posting/statistics
dateRange, locationId, metrics
Trigger: end of day or campaign completion
Actions: pull Endpoint3 data via socialplanner/statistics.readonly and assemble a summarized report
GET socialplanner/statistics.readonly
reportDate, locationId, breakdown
Fast setup with a visual, drag-and-drop connector—no coding required.
Automated tagging, statistics, and alerts run automatically from Kenect.
Unified analytics help you see impact across channels and campaigns.
Elements: endpoints, authentication, triggers, actions, and data fields. Processes: trigger to action flow, data mapping, and error handling.
A specific URL in the GHL Users API that performs a defined task when called by Kenect Text Messaging.
The method used to prove Kenect Text Messaging can access the GHL Users API (API keys or OAuth credentials).
An event that starts a workflow, such as a new social post or a request for analytics.
Building automations using a visual interface without writing code.
Automatically tag posts from each location using endpoint1, improving organization and reporting.
Pull statistics to tailor messaging campaigns based on engagement trends.
Generate end-of-day summaries with Endpoint3 data and share with stakeholders.
Create a new connection in Kenect’s admin console and request API credentials from the GHL developer portal.
Enter your API key or OAuth credentials, select the social planner scope, and test the connection.
Choose Endpoint1-4, map their fields, and enable automated workflows in Kenect.
No coding is required—use Kenect’s no-code connector to link to the GHL Users API. Start by creating a new connection, then authenticate and map the endpoints you need.
The core endpoints are GET tags, POST tags/details, and POST statistics (and the readonly statistics for dashboards). Other endpoints are optional depending on your use case.
Use API keys or OAuth credentials; ensure the Kenect app has the socialplanner/tag.readonly scope. Test the connection in the Kenect admin panel.
Yes. Analytics from the Users API are surfaced in Kenect dashboards; you can create reports using Endpoint3 and Endpoint4.
Typical fields include locationId, tags, date ranges, and metrics like counts or engagement.
Yes. Use the test or sandbox mode in the developer portal to validate requests before going live.
API docs are available in the GHL developer portal and Kenect integration docs; support via Rankr resources.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
