Authenticate every request with your GHL credentials (OAuth 2.0). Use the proper access token and ensure the app has read permissions for contacts data.
Referral Rock relies on the GHL authorization flow to grant read access to contacts. After approval, use the issued access token to call the Contacts API endpoints for data retrieval.
Available endpoints include: GET /contacts/:contactId, GET /contacts/:contactId/tasks, GET /contacts/:contactId/tasks/:taskId, GET /contacts/:contactId/notes, GET /contacts/:contactId/notes/:id, GET /contacts/:contactId/appointments, GET /contacts/, GET /contacts/business/:businessId, and more (see full list for read-only access).
Trigger: when a contact is accessed or updated, pull the latest details from Contacts API into Referral Rock.
Actions: fetch contact data, pull related tasks and notes, and keep the record in sync.
GET /contacts/:contactId
Key fields: id, name, email, phone, status
Trigger: a new task is created or updated for a contact in Referral Rock, then update the corresponding task in GHL.
Actions: create or update tasks in /contacts/:contactId/tasks, set due dates, and mark completion when appropriate.
POST /contacts/:contactId/tasks
Fields: taskId, title, dueDate, status
Trigger: notes updated or tags added on a contact to push updates to Referral Rock
Actions: create or update notes, attach tags, and ensure references link back to the contact
POST /contacts/:contactId/notes | POST /contacts/:contactId/tags
Fields: noteId, content, tags, timestamp
No-code setup to connect data sources quickly using visual builders
Real-time data sync without custom code
Unified customer view across Apps with centralized data
In this guide you’ll find definitions for endpoints, triggers, actions, methods, fields, and glossary terms used to connect the GHL Contacts API with Referral Rock.
An Application Programming Interface that allows different software to communicate.
A specific URL path in an API used to access a resource.
Open standard for token-based authentication that authorizes API access.
A real-time push message from an app to another app when data changes.
Automatically apply tags in Contacts API based on Referral Rock source fields to improve segmentation in your CRM.
Create targeted tasks in the Contacts API when new referrals enter Referral Rock to guide new customers through onboarding.
Automatically store notes and conversation highlights in Contacts API as referrals are engaged in Referral Rock.
Request or generate an OAuth token and ensure the app has read permissions for contacts.
Authorize the Referral Rock app to access Contacts API data within your GHL account.
Map contact, task, notes, and tag fields between GHL and Referral Rock and run end-to-end tests.
OAuth 2.0 tokens are issued by GHL and should be requested with the contacts.readonly scope. Keep tokens secure and rotate them regularly; test in a sandbox environment before going live.
All endpoints labeled with read-only access begin with GET and do not modify data. For example, you can retrieve contacts and their related tasks, notes, and appointments. If you need to write or update data, you must request write permissions and use the corresponding POST, PUT, or DELETE endpoints after obtaining approval.
Data sync frequency depends on your setup and polling strategy; you can schedule regular pulls or use webhooks if supported. Consider a cadence that matches your business needs and the rate limits of your plan.
Yes, you can write updates for endpoints that support write operations if your token includes the write scope. Use POST, PUT, or DELETE calls for appropriate resources and handle errors gracefully. Always validate changes in a staging environment before going live.
Common errors include 401 unauthorized, 403 forbidden, 429 rate limits, and 404 not found. Check token validity, scopes, endpoint paths, and ensure the app is authorized. Review API responses and retry with backoff where appropriate.
Rate limits vary by plan and endpoint. Monitor the API response headers for remaining quota and reset times, then implement exponential backoff and retries. If you frequently hit limits, consider a higher plan or batching requests.
Field mappings are documented in the glossary of this guide. Map core contact fields (id, name, email, phone), tasks fields, notes fields, and tags to ensure data aligns between systems. Test mappings thoroughly during integration testing.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
