Obtain your GHL API credentials and securely authorize DonorDock to access contact data. Use OAuth 2.0 or API keys as provided by your GHL account.
Grant DonorDock permission to read and update contacts via the Contacts API. Keep tokens secure and refresh as needed.
A representative set of endpoints includes: GET /contacts/:contactId, GET /contacts/:contactId/tasks, GET /contacts/:contactId/notes, GET /contacts/:contactId/appointments, GET /contacts/, POST /contacts/, PUT /contacts/:contactId, DELETE /contacts/:contactId, POST /contacts/:contactId/tasks, POST /contacts/:contactId/tags, GET /contacts/business/:businessId, and related read/write operations. Use these to read, create, update, or delete contact data and track tasks, notes, and tags.
Trigger: when a donor profile is created or updated in DonorDock, sync the latest data to the Contacts API.
Actions: fetch contact data, map fields, and push updates to the Contacts API to keep records in sync.
Methods/paths: GET /contacts/:contactId; PUT /contacts/:contactId
Key fields: contactId, donorId, email, fullName
Trigger: when a donation is recorded or updated in DonorDock
Actions: create or update tasks, attach notes, and summarize activity in the donor record
Methods/paths: GET /contacts/:contactId/tasks; POST /contacts/:contactId/tasks
Fields: donorId, lastDonationDate, totalDonations
Trigger: notes added or updated on a donor’s record
Actions: add notes, assign tags, and trigger email or campaign workflows
Methods/paths: POST /contacts/:contactId/notes; PUT /contacts/:contactId/notes/:id; POST /contacts/:contactId/tags
Fields: contactId, noteId, tagIds
Benefit: Quick setup with OAuth and API keys, no custom code required.
Benefit: Real-time data sync across DonorDock and your CRM instantly.
Benefit: Scalable donor management with automation rules and workflows.
This glossary defines terms you’ll see when connecting DonorDock to the Contacts API, including OAuth, API endpoints, data mapping, rate limits, and webhooks.
OAuth is a token-based authorization standard that lets DonorDock access the Contacts API without sharing passwords.
A specific URL that enables a particular operation on the service, such as retrieving or updating a contact.
A donor or constituent stored in the Contacts API with fields like name, email, and contact history.
A label used to categorize contacts for segmentation and targeted campaigns.
Use endpoint mappings to tag and group donors by giving history and interests for smarter campaigns.
Trigger communications automatically when donations occur or notes are added to a donor’s record.
Attach contextual notes and tags to guide onboarding, stewardship, and campaigns.
Register your app in GHL to receive a client_id and client_secret for OAuth.
Run the OAuth flow and test with a sample contact to verify access.
Create mappings between DonorDock fields and Contacts fields to ensure clean data sync.
The Contacts API is a RESTful interface that lets DonorDock read and write contact data stored in the GHL workspace. It enables you to pull donor details, update records, and keep donor journeys in sync across your apps. By using the API you can centralize donor information and automate routine updates.
Authentication uses OAuth 2.0 with a client_id and client_secret to obtain access tokens. Include the Authorization: Bearer token in API requests and securely store tokens. Regularly refresh tokens before expiry and use sandbox/test credentials when validating changes.
You’ll have access to endpoints for reading and writing contacts, tasks, notes, and tags (for example GET /contacts/:contactId, POST /contacts/, PUT /contacts/:contactId, POST /contacts/:contactId/tasks, POST /contacts/:contactId/notes, POST /contacts/:contactId/tags, and more). Review the docs for rate limits and field mappings.
Yes. You can create new contacts with POST /contacts/ and update existing ones with PUT /contacts/:contactId. Ensure your payload includes required fields (name, email) and maps to the destination fields in GHL. Handle conflicts gracefully and confirm successful responses.
There are API rate limits. If you hit them, implement exponential backoff and retries in your DonorDock workflows. Space requests out and monitor response headers for quota information.
If syncing fails, verify credentials, access tokens, and endpoint availability. Check response codes, review error messages, and inspect rate-limit headers. Use retries with backoff and validate field mappings.
Zapier can connect to the Contacts API using standard REST actions and optional webhooks. Map fields between DonorDock and the Contacts API, and configure automation to trigger when records are created or updated. You can also use the Zapier app connector for streamlined setup.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
