To access the Users API from GHL, generate an API key or use OAuth credentials, then include the access token in your requests. Ensure the requested scope is socialplanner/tag.readonly for read-only tag access.
Qwilr uses the connected GHL credentials to access tag and statistics data. Make sure the APPNAME has the necessary permissions and that the OAuth flow is completed for live data syncing.
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 social post location in Qwilr triggers tag retrieval from the Users API.
Actions: Use GET /social-media-posting/:locationId/tags to fetch tags, then POST /social-media-posting/:locationId/tags/details to attach tag details.
GET /social-media-posting/:locationId/tags
locationId, tagId, tagName
Trigger: On-demand statistics requested from Qwilr or a dashboard.
Actions: POST /social-media-posting/statistics to generate data; retrieve with socialplanner/statistics.readonly.
POST /social-media-posting/statistics; socialplanner/statistics.readonly
locationId, dateRange, metrics
Trigger: Tag details updated in Qwilr.
Actions: POST /social-media-posting/:locationId/tags/details to push updated tag info; then refresh tags with GET /social-media-posting/:locationId/tags.
POST /social-media-posting/:locationId/tags/details; GET /social-media-posting/:locationId/tags
locationId, tagId, details
Fast setup with no coding required, using pre-built connectors that map endpoints and fields.
Automations run in the background, keeping Qwilr tag data and statistics in sync with your GHL account.
Easily share insights with your team through dashboards and automated reports.
This glossary defines the core concepts used in the Qwilr + Users API integration: endpoints, triggers, actions, and fields you will work with.
An interface that allows software applications to communicate and exchange data.
A specific URL path and HTTP method used to perform an operation on an API.
Process of proving identity and permissions before access is granted to API resources.
An event that starts an automated workflow or action.
Automatically generate and distribute weekly stats from the statistics endpoint to a Slack channel or email list.
Refresh and validate tag data to maintain clean Qwilr project tagging.
Provide a dashboard with real-time metrics pulled via the endpoints and displayed for your team.
Authorize the GHL Users API with the required scope socialplanner/tag.readonly to read tag data.
Configure endpoints: GET /social-media-posting/:locationId/tags, POST /social-media-posting/:locationId/tags/details, and the statistics endpoints for generating and reading data.
Run tests, verify data integrity, and switch to live syncing.
To start, set up a connected app in GHL and grant the socialplanner/tag.readonly scope so the app can read tag data. Then configure the endpoints to pull and push tag details between Qwilr and your GHL account. Use the provided examples to validate data flow in a test environment.
For a basic sync, you’ll primarily use GET /social-media-posting/:locationId/tags to fetch tags and POST /social-media-posting/:locationId/tags/details to push tag information. The statistics endpoints (socialplanner/statistics.readonly and POST /social-media-posting/statistics) enable performance reporting.
Authentication is done via OAuth or API keys with the appropriate scopes. Include the access token in request headers and ensure the GHL app or API key is authorized for the socialplanner/tag.readonly scope to read tag data. Re-authenticate if tokens expire.
Yes. You can automate statistics reporting by triggering POST /social-media-posting/statistics on demand or on a schedule, then reading results with socialplanner/statistics.readonly. This creates regular insights without manual steps.
No-code connectors are provided to map endpoints and fields, enabling you to set up workflows without custom code. You configure triggers, actions, and required fields through a UI, then test and deploy.
Common data fields include locationId, tagId, tagName, and metric/dateRange values used in statistics requests. The exact fields depend on the endpoints you call and your Qwilr project structure.
Refer to the integration guide and API reference within your Rankr dashboard. You can also access sample templates, endpoint syntax, and troubleshooting tips in the no-code connectors section.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
