Use OAuth2 tokens scoped for socialplanner/tag.readonly and the statistics endpoints to securely access tag data and analytics.
Authorize Lark in the App Connector and grant the required scopes so data can flow between Lark and the Users API.
GET /social-media-posting/:locationId/tags; POST /social-media-posting/:locationId/tags/details; socialplanner/statistics.readonly; POST /social-media-posting/statistics
Trigger: when Lark publishes a post, pull content and tag details from the Users API.
Actions: create or update tags in GHL via the endpoints, then log for analytics.
GET /social-media-posting/:locationId/tags
locationId, tagId, tagName
Trigger: daily or hourly stats checks from the Users API.
Actions: request socialplanner/statistics.readonly and POST /social-media-posting/statistics to push updates.
POST /social-media-posting/statistics
startDate, endDate, locationId
Actions: update tags and stats concurrently using endpoints 1 and 4.
GET /social-media-posting/:locationId/tags; POST /social-media-posting/statistics
locationId, tagId, statsId
Automate workflows without writing code.
Get real-time insights and accurate tagging without manual steps.
Enjoy seamless data sync between Lark and GHL with auditable activity.
A quick glossary of API terms used in this guide and how they apply to Lark and the Users API integration.
Application Programming Interface — a set of rules that lets two applications talk to each other.
The process of verifying identity and permissions before accessing data.
A specific URL path exposed by an API for a particular function.
A callback mechanism that notifies your app of events in real time.
Leverage content signals from Lark to auto-assign tags via the Users API, then feed those tags into analytics.
Show live tagging stats from GHL in a Lark dashboard, with drill-downs for campaigns and locations.
Publish a tagged campaign from Lark to GHL, triggering tag creation and statistics updates automatically.
Create or copy OAuth2 API keys and configure scopes for tags and statistics access.
Select endpoints 1–4 (tags and statistics) and map required fields.
Run tests in a staging environment, review logs, and deploy to production with monitoring.
The GHL Users API provides programmatic access to your data, including tags and statistics, so you can automate workflows. It enables you to read tag details and pull analytics to inform content decisions.
Supported endpoints include GET /social-media-posting/:locationId/tags, POST /social-media-posting/:locationId/tags/details, socialplanner/statistics.readonly, and POST /social-media-posting/statistics. These cover tag retrieval, tag updates, and statistics retrieval/posting.
Authentication uses OAuth2 tokens scoped to the required endpoints. You’ll authorize Lark in the App Connector and grant access to the needed tag and statistics endpoints.
Yes. You can set up triggers to run actions in Lark when data changes in GHL, such as updating tags or triggering analytics updates.
Connections use token-based authentication over encrypted channels. Scopes limit what each token can do, reducing exposure.
Data synced includes tags, tag details, and statistics across defined date ranges. You can control what is synced via scopes and field mappings in the App Connector.
If a sync fails, review the App Connector error logs, verify credentials and scopes, and confirm endpoint availability.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
