Authenticate requests using your GHL API credentials. Use OAuth2 or API tokens as provided in your GHL developer dashboard and securely store them in Clinicminds.
Clinicminds authenticates with the Social Media API by exchanging credentials for access tokens and scoping permissions (saas/company.write). Rotate tokens regularly and store them securely.
Endpoints used include: POST /bulk-disable-saas/:companyId; GET /snapshots; GET /social-media-posting/:locationId/accounts; DELETE /social-media-posting/:locationId/accounts/:id; GET /social-media-posting/:locationId/csv; GET /social-media-posting/:locationId/csv/:id; POST /social-media-posting/:locationId/csv; PATCH /social-media-posting/:locationId/csv/:id; DELETE /social-media-posting/:locationId/csv/:id; POST /social-media-posting/:locationId/set-accounts; POST /social-media-posting/:locationId/posts/bulk-delete; DELETE /social-media-posting/:locationId/csv/:csvId/post/:postId; snapshots.readonly; socialplanner/account.readonly; socialplanner/account.write; socialplanner/csv.readonly; socialplanner/csv.write
Trigger: when new clinics or locations need to be added or removed across your portfolio.
Actions: map accounts to locations, update account lists, and keep accounts in sync across Clinicminds and GHL.
Key methods: POST /social-media-posting/:locationId/set-accounts; GET /social-media-posting/:locationId/accounts; DELETE /social-media-posting/:locationId/accounts/:id
Key fields: locationId, accountId, status
Trigger: when CSVs are prepared for regional campaigns.
Actions: upload CSVs, assign accounts, schedule publishing, and monitor results.
Endpoints involved: POST /social-media-posting/:locationId/csv; GET /social-media-posting/:locationId/csv; GET /social-media-posting/:locationId/csv/:id; POST /social-media-posting/:locationId/set-accounts
CSV id, locationId, accounts
Trigger: post publication events and snapshot updates.
Actions: fetch snapshots, review posting status, pull CSV/account states, and visualize performance in Clinicminds.
Methods: GET /snapshots; GET /social-media-posting/:locationId/csv; GET /social-media-posting/:locationId/accounts
locationId, postId, snapshotId
Automate social workflows without writing code. Use built-in connectors to map fields and trigger actions.
Centralized control of accounts, posts, and CSVs across locations from a single dashboard.
Faster onboarding and scalable campaigns with real-time insights and dashboards.
A quick glossary of API terms and data flows to help you navigate endpoints and data structures.
A defined interface that allows two applications to communicate and exchange data securely.
Comma-separated values file used for bulk data import/export.
A URL that receives real-time event notifications from an API.
An item published to a social feed as part of a campaign.
Create a recurring Zap that pulls approved content from CSVs and publishes across all Clinicminds locations at set times.
Upload regional CSVs to tailor content per location and track performance in one dashboard.
Use set-accounts and account endpoints to onboard new clinics quickly with mapped accounts.
Obtain your GHL API key and secret, grant the saas/company.write scope, and save in Clinicminds secure vault.
Configure endpoints such as /snapshots, /social-media-posting, and /csv in Clinicminds.
Run test calls, verify data sync, and monitor dashboards for accuracy.
No coding is required. Clinicminds provides built-in connectors that map GHL API endpoints to your workflows. You can configure triggers, actions, and data mappings through a simple UI. If you’re comfortable with APIs, you can also customize endpoints for advanced use cases. This makes it easy for clinics to start posting quickly without a developer.
Key endpoints include account management (GET /social-media-posting/:locationId/accounts, POST /social-media-posting/:locationId/set-accounts, DELETE /social-media-posting/:locationId/accounts/:id) and CSV handling (POST /social-media-posting/:locationId/csv, GET /social-media-posting/:locationId/csv, GET /social-media-posting/:locationId/csv/:id, DELETE /social-media-posting/:locationId/csv/:id, PATCH /social-media-posting/:locationId/csv/:id).
Upload a CSV via the CSV endpoint to batch-create or update posts. The system will parse the file, map to accounts, and queue posts for publishing. Make sure your CSV uses the required columns and adheres to the location mapping.
Yes. Use the bulk delete endpoints to remove posts or CSV data. For example, POST /social-media-posting/:locationId/posts/bulk-delete clears posts, and DELETE /social-media-posting/:locationId/csv/:id removes a CSV asset. Always back up data before bulk actions.
You can view snapshots and posting status via GET /snapshots and the related endpoints. Clinicminds dashboards display success, errors, and scheduling timelines so you can optimize campaigns in real time.
The integration uses secure OAuth tokens and scoped permissions (saas/company.write). Data in transit is protected via HTTPS. Rotate credentials regularly and follow best practices for secret storage.
If you need help, contact support via Rankr or your account manager. You can also consult the product documentation and community forums for tips and troubleshooting steps.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
