Grant GHL access to your 17hats data by creating an API key or using OAuth and selecting the saas/company.write scope.
Confirm permissions and scopes for 17hats to connect with the GHL Social Media API, then test the connection.
POST /bulk-disable-saas/:companyId; snapshots.readonly; GET /snapshots; socialplanner/account.readonly; GET /social-media-posting/:locationId/accounts; socialplanner/account.write; DELETE /social-media-posting/:locationId/accounts/:id; socialplanner/csv.readonly; GET /social-media-posting/:locationId/csv; GET /social-media-posting/:locationId/csv/:id; socialplanner/csv.write; POST /social-media-posting/:locationId/csv; POST /social-media-posting/:locationId/set-accounts; DELETE /social-media-posting/:locationId/csv/:id; PATCH /social-media-posting/:locationId/csv/:id; POST /social-media-posting/:locationId/posts/bulk-delete; DELETE /social-media-posting/:locationId/csv/:csvId/post/:postId
Trigger: when a 17hats event requires a social update, pull accounts to ensure current connections.
Actions: fetch accounts, map to GHL accounts, enable/disable as needed.
GET /social-media-posting/:locationId/accounts
Key fields: locationId, accountId, status
Trigger: upload or fetch CSV files for scheduling posts.
Actions: create, read, update CSV, link to accounts.
POST /social-media-posting/:locationId/csv
Key fields: locationId, csvId, status
Trigger: post queue ready event or bulk-delete request.
Actions: schedule posts, bulk-delete posts with bulk-delete endpoint.
POST /social-media-posting/:locationId/posts/bulk-delete
Key fields: locationId, postId, status
Automate social workflows without coding.
Centralize control of accounts, CSVs, and posts in one place.
Speed up onboarding and scale collaboration across teams.
Key elements include endpoints, triggers, actions, and field mappings that connect GHL with 17hats.
OAuth is the industry-standard protocol that authorizes apps to access user data without sharing passwords.
CSV (Comma-Separated Values) is a simple format for exchanging tabular data between systems.
An API endpoint is a specific URL and method that enables a request to be made to a service.
A webhook is a callback URL that receives real-time notifications of events from a service.
Trigger social posts when a 17hats milestone occurs (client status, job stage, or invoice).
Populate posts from CSV records to run coordinated campaigns across channels.
Bulk-delete outdated posts and quickly refresh campaigns.
Authenticate the connection by authorizing GHL to access 17hats data using your credentials.
Map the common endpoints to 17hats actions (accounts, CSVs, posts).
Test the integration in a staging environment before going live.
You can connect 17hats to the GHL Social Media API without writing code by using GHL’s built-in connectors and the REST endpoints listed here. In this example, APPNAME is 17hats and GHLAPINAME is Social Media API, letting you manage accounts, CSVs, and posts from a single interface. Start by authenticating, then map endpoints to actions to begin automation.
Available endpoints include account management (GET /social-media-posting/:locationId/accounts and DELETE /social-media-posting/:locationId/accounts/:id), CSV operations (GET/POST /social-media-posting/:locationId/csv and related endpoints), and post bulk actions (POST /social-media-posting/:locationId/posts/bulk-delete and DELETE /social-media-posting/:locationId/csv/:csvId/post/:postId). These endpoints enable syncing accounts, uploading CSVs, and bulk deleting posts.
Authentication involves granting GHL permission to access 17hats data using an API key or OAuth flow, selecting the saas/company.write scope, and then testing the connection. Once approved, you map the endpoints to corresponding 17hats actions and verify data flow.
Yes. The bulk-delete endpoint (POST /social-media-posting/:locationId/posts/bulk-delete) allows removing multiple posts in one operation. You can also prune CSV-based posts with the related endpoints to keep campaigns clean and current.
No-code mapping is supported through the GHL UI, allowing you to connect endpoints to 17hats actions without writing code. You define triggers, actions, and fields, and the system handles the data routing automatically.
The saas/company.write scope controls what the integration can do within your SaaS organization, including creating, updating, and deleting accounts and data. This scope should be granted only to trusted integrations and reviewed regularly.
The endpoint list is shown in the Key Endpoints section; you can reference it here or in the developer docs. You’ll see each endpoint’s path, method, and purpose to guide setup and testing.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
