Use your GHL API credentials to authorize Piggy for read-only access to your contacts data.
Approve Piggy to read your Contacts data with the scope contacts.readonly to keep your information secure.
1) GET /contacts/:contactId; 2) GET /contacts/:contactId/tasks; 3) GET /contacts/:contactId/tasks/:taskId; 4) GET /contacts/:contactId/notes; 5) GET /contacts/:contactId/notes/:id; 6) GET /contacts/:contactId/appointments; 7) GET /contacts/; 8) GET /contacts/business/:businessId; 9) contacts.write; 10) POST /contacts/; 11) PUT /contacts/:contactId; 12) DELETE /contacts/:contactId; 13) POST /contacts/:contactId/tasks; 14) PUT /contacts/:contactId/tasks/:taskId; 15) PUT /contacts/:contactId/tasks/:taskId/completed; 16) DELETE /contacts/:contactId/tasks/:taskId; 17) POST /contacts/:contactId/tags
Trigger on GET /contacts/:contactId to pull data and start tasks or notes.
Actions: POST /contacts/:contactId/tasks to create tasks; GET /contacts/:contactId/notes to pull notes; GET /contacts/:contactId/tasks to retrieve tasks.
Methods used: GET for retrieval, POST for creation, PUT for updates, DELETE for removal.
Key fields: contactId (and for tasks: taskId).
Trigger when notes or appointments are updated to reflect changes in Piggy.
Actions: GET /contacts/:contactId/notes and GET /contacts/:contactId/appointments to pull data.
Methods: GET for notes and appointments.
Key fields: contactId, id (note or appointment).
Trigger on changes to contact data to keep systems in sync.
Methods: PUT and DELETE for updates and state changes.
Key fields: contactId, taskId.
Automate data flow between GHL Contacts and Piggy without writing code.
Fast, endpoint-based triggers and actions for everyday tasks.
A unified view of all contact activities (tasks, notes, appointments) in Piggy.
A quick glossary of the elements and processes used in the Piggy‑GHL Connection.
A URL paired with an HTTP method that accesses or manipulates a resource.
The process of proving identity to grant access to data.
A callback URL that notifies your app when an event happens.
The maximum number of API calls allowed in a given window.
When a new contact is added in GHL, automatically create a starter task in Piggy.
Aggregate notes into a daily digest in Piggy for review.
Tag contacts based on activity to enable segmentation.
In GHL, generate an API key with read access to contacts.
Add your API key to Piggy and set scope to contacts.readonly.
Run a test to fetch a contact and confirm data sync.
Piggy provides a no-code way to connect to the GHL Contacts API. You can pull contact data, read tasks, notes, and appointments. This integration supports typical automation patterns. Please test in a sandbox or staging environment first.
Yes. The setup uses endpoints and authentication flows that do not require custom code. Use the app’s inbuilt mappings and triggers to automate workflows.
Required permissions include at least contacts.readonly. Depending on features enabled, write permissions can be granted, but this page focuses on read-only access.
Authenticate via OAuth or API key as provided by GHL. Keep credentials secure, rotate keys periodically, and use scoped access.
With contacts.readonly, Piggy can fetch contact details, tasks, notes, and appointments without modifying them.
Creating or updating contacts is possible if you upgrade permissions to include write access. In this no-code setup, read-only access is the default.
Respect rate limits. If you hit a limit, implement exponential backoff and retries. The Piggy app will surface retry guidance.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
