Authenticate to the Users API using API keys or OAuth tokens to securely access endpoints such as GET /social-media-posting/:locationId/tags, POST /social-media-posting/:locationId/tags/details, and statistics endpoints.
Configure Popl to present credentials to the Users API, using a client ID/secret or API key and redirect URI as required by the integration.
GET /social-media-posting/:locationId/tags; POST /social-media-posting/:locationId/tags/details; socialplanner/statistics.readonly; POST /social-media-posting/statistics
Trigger: a new or updated tag in Popl; Action: fetch tag data from GET /social-media-posting/:locationId/tags and push updates to Popl analytics.
Actions: GET /social-media-posting/:locationId/tags to retrieve tags; POST /social-media-posting/:locationId/tags/details to enrich tag data; store results in your analytics panel.
GET /social-media-posting/:locationId/tags
locationId, tagId, tagName, timestamp
Trigger: a request for posting statistics; Action: POST /social-media-posting/statistics to generate metrics for Popl.
Actions: POST /social-media-posting/statistics to compute metrics; use socialplanner/statistics.readonly for live dashboards.
POST /social-media-posting/statistics
locationId, dateRange, metrics
Trigger: analytics inquiry from Popl; Action: pull data with socialplanner/statistics.readonly for live insights.
Actions: call socialplanner/statistics.readonly; optionally enrich with GET /social-media-posting/:locationId/tags for context.
socialplanner/statistics.readonly
locationId, metric, scope
Drag-and-drop automations to post and analyze data without writing code.
Unified data flows ensure consistency between Popl and your analytics dashboards.
Faster onboarding with reusable templates and triggers for recurring campaigns.
Key elements include endpoints, triggers, actions, authentication methods, and data fields used to connect Popl to the Users API.
A specific URL in the GHL API that performs a defined function, such as retrieving tags or posting statistics.
An event within Popl or GHL that starts a workflow between the systems.
The operation executed in response to a Trigger, such as a GET or POST request.
An identifier for a specific Popl location within the GHL system.
Use tag events in Popl to trigger personalized campaigns via the Users API.
Stream live metrics from social postings into a single dashboard.
Schedule automated reports highlighting engagement trends and tag performance.
Create an API key or OAuth client in GHL and note the credentials for Popl.
Enter the endpoints listed earlier into Popl workflows and set up authentication.
Run tests to ensure data flows correctly and go live once verified.
Core endpoints include GET /social-media-posting/:locationId/tags and POST /social-media-posting/:locationId/tags/details, plus the statistics endpoints (socialplanner/statistics.readonly and POST /social-media-posting/statistics). These enable tag retrieval, enrichment, and posting metrics. You can combine them to drive campaigns from Popl data without custom code. The endpoints are designed for straightforward no-code integration with Popl workflows.
No coding is required for basic setups: configure API keys or OAuth credentials and map data fields in your automation builder. For advanced use, you can extend logic with conditional triggers and multi-step actions. The goal is a smooth, drag-and-drop experience between Popl and the Users API.
Authenticate by supplying your GHL API key or OAuth token to Popl. Use secure storage for credentials, rotate keys periodically, and follow best practices for scopes and permissions to limit access to needed endpoints only.
Yes. Use the socialplanner/statistics.readonly endpoint to pull live metrics and combine them with tag data from the tags endpoints for real-time dashboards and reports.
Data fields include locationId, tagId, tagName, timestamp, dateRange, and metrics. Depending on the endpoint, you may also see additional fields like userId and engagement counts when available.
Absolutely. This integration is designed for no-code workflows. Use the visual automation builder to chain triggers (e.g., tag changes) to actions (e.g., fetch tag details, update analytics).
The endpoints list is shown in the Key Endpoints section. You can also view each endpoint’s path and required parameters in your integration builder when configuring the Popl workflow.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
