Authenticate securely using OAuth 2.0 or an API key. The required scope is saas/company.write to manage accounts and posting settings.
Grant ActiveDEMAND permission to access GHL data within your workspace and configure user roles to control what can be read or written.
– POST /bulk-disable-saas/:companyId — disable SaaS access for a specific company – snapshots.readonly — read only snapshots data – GET /snapshots — fetch available snapshots – socialplanner/account.readonly — read accounts data – GET /social-media-posting/:locationId/accounts — list accounts for a location – socialplanner/account.write — write accounts data – DELETE /social-media-posting/:locationId/accounts/:id — delete an account – socialplanner/csv.readonly — read CSV imports – GET /social-media-posting/:locationId/csv — list CSVs for a location – GET /social-media-posting/:locationId/csv/:id — read a specific CSV – socialplanner/csv.write — write CSV data – POST /social-media-posting/:locationId/csv — upload a CSV – POST /social-media-posting/:locationId/set-accounts — map accounts to a location – DELETE /social-media-posting/:locationId/csv/:id — delete a CSV – PATCH /social-media-posting/:locationId/csv/:id — update a CSV – POST /social-media-posting/:locationId/posts/bulk-delete — bulk delete posts – DELETE /social-media-posting/:locationId/csv/:csvId/post/:postId — delete a specific post from CSV
Trigger: when a new campaign or queue is created in ActiveDEMAND, initiate a batch of posts for a selected location.
Actions: create accounts, map accounts to locations, upload CSVs, and publish posts across multiple locations.
POST /social-media-posting/:locationId/csv
locationId, csvId, accountId, postId
Trigger: a daily or weekly schedule to fetch snapshots and refresh reports.
Actions: read-only access to snapshots, export CSV data, and populate analytics dashboards.
GET /snapshots
locationId, snapshotId
Trigger: new accounts added via CSV trigger a posting queue setup.
Actions: upload CSV, set accounts, map locations, and schedule batch posts.
POST /social-media-posting/:locationId/set-accounts
locationId, csvId, accountId
Launch campaigns faster with a visual workflow and no coding required.
Automate publishing and reporting directly from ActiveDEMAND to your social channels.
Centralize control of social accounts with a single, scalable integration.
Key elements include API endpoints, authentication methods, data models, and permission scopes that govern access.
A specific URL and HTTP method used to perform an action via the GHL Social Media API.
An authorization framework that enables secure access to GHL data without sharing credentials.
Comma-separated values used for bulk account imports and data exchange between systems.
A callback URL used to notify your app when events occur in the API.
Centralize publishing for all connected social accounts and push to each account via the API.
Automatically export performance data from the Social Media API into ActiveDEMAND dashboards.
Use CSV imports to onboard new accounts and quickly set up initial post queues.
Collect your GHL API credentials and activate ActiveDEMAND access tokens.
Set endpoint paths in ActiveDEMAND, run test calls, and verify responses.
Publish a test post to a selected location and confirm data flow to reporting.
You will need write permissions for the SaaS company in GHL plus access to the relevant ActiveDEMAND resources. Ensure the OAuth scope includes saas/company.write so ActiveDEMAND can manage accounts and posting settings. After granting permissions, test a few API calls to confirm access. If you run into restricted scopes, adjust the authorization grant to include the necessary permissions and re-authenticate to apply changes.
Yes. ActiveDEMAND can trigger posts across multiple social accounts by linking each account via the CSV upload and account mapping endpoints. Use location scoping to control where posts go and batch schedule for efficiency. Monitor per-location dashboards to ensure each account receives the correct content and timing.
Check API responses and status codes from each call. Use the endpoints that expose snapshots and post queues to verify activity. ActiveDEMAND dashboards can display success rates and error details for quick triage. Enable webhook notifications if available to receive real-time error alerts.
Yes, there are rate limits on API requests. Plan your posting cadence to stay within limits and stagger calls across endpoints. If you anticipate high volume, use batch endpoints like bulk CSV uploads to minimize individual requests. Contact support if you expect sustained high-throughput to discuss rate limit accommodations.
No heavy coding is required. The integration is designed for no-code or low-code setups using the provided endpoints and CSV workflows. You can configure connections, map accounts, and schedule posts entirely within ActiveDEMAND and the GHL API interface.
Yes. CSV is a core part of the workflow for onboarding accounts and bulk posting. You can upload CSV files to create accounts, map them to locations, and drive batch posting. CSV exports are also available for reporting purposes.
Start with a small pilot test using a single location and a limited set of accounts. Validate each endpoint response, verify post visibility, and check reporting data. Gradually expand scope as you confirm stability and accuracy.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
