Authenticate requests to the Users API using your API credentials and OAuth tokens. Keep keys secure and rotate them regularly.
In Zapier, connect the Zapier app for the Users API and authorize using your API credentials for a secure connection.
GET /social-media-posting/:locationId/tags; POST /social-media-posting/:locationId/tags/details; socialplanner/statistics.readonly; POST /social-media-posting/statistics
Trigger when a contact score changes or crosses a defined threshold
Actions include updating the lead in your system, tagging the contact in GHL, or sending a notification to your team
Method path: use the GET and POST endpoints to fetch score data or submit new scores
Key fields: contact_id, score, threshold, timestamp
Trigger on a schedule to sync scores in batches from GHL to Zapier
Actions: push batch results to a spreadsheet, CRM, or analytics tool
Method path: bulk endpoints or a Zap that processes multiple items
Fields: batch_id, total_items, success_count
Trigger when a new lead is created or enrichment data becomes available
Actions: enrich CRM records, add notes, or create tasks with score context
Method path: call endpoints to fetch lead details and enrichment fields
Fields: lead_id, enrichment_fields, score
Fast setup with a drag and drop Zapier editor
Real time data flow with webhooks and polling options
Centralized lead scoring across your apps
A quick glossary of terms used in this guide including lead score, endpoint, trigger, action, and authentication
A numeric indicator of lead quality used to prioritize outreach
A URL path and HTTP method used to access data or perform an action in the API
A mechanism for real time data delivery between apps
The process used to verify identity and authorize API requests
Capture form submissions, compute a lead score, and route to CRM in minutes
When contact data changes, recalc score and sync back to your tools
Add score related notes and enrichment fields to lead records
In GHL, generate an API key and note the client id and secret for Zapier
In Zapier, add the GHL Users API app and authorize the connection using your API key
Create a Zap with a trigger for score changes and actions to update records and notify teams
The Users API supports API key based auth and OAuth tokens. Keep keys secure and rotate them regularly.\nUse OAuth when possible for user specific permissions.
The endpoints cover tags and statistics. GET /social-media-posting/:locationId/tags retrieves tags. POST /social-media-posting/:locationId/tags/details returns tag details.\nsocialplanner/statistics.readonly returns stats. POST /social-media-posting/statistics updates statistics.
Yes, batch processing is possible via bulk endpoints or by iterating items in a single Zap.\nBuild a Zap that loops or uses a bulk action.
Poll frequency varies by Zapier plan. Typical ranges are every 5 to 15 minutes.\nFor near real-time updates, consider using webhooks where available.
Lead score data typically includes the score value, scoring signals, timestamp, and lead identifier.\nYou can enrich with additional fields as needed.
Yes. Webhooks can push lead score changes to Zapier in real time.\nSet up a webhook trigger or use a polling alternative if needed.
Rate limits and best practices vary by API plan.\nCheck the GHL docs for current limits and implement retry logic and pagination where appropriate.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
