To begin, generate an API key in the Social Media API dashboard and securely connect it to Acumbamail using the authentication method configured for your workspace (scope: saas/company.write).
Grant Acumbamail permission to access Social Media API endpoints by approving the OAuth flow and selecting the required scopes.
Key endpoints you can use with this integration include POST /bulk-disable-saas/:companyId, GET /snapshots, GET /social-media-posting/:locationId/accounts, POST /social-media-posting/:locationId/csv, POST /social-media-posting/:locationId/set-accounts, and more. Use locationId, csvId, postId, and accountId as needed for data mapping.
Trigger: when a new post is created in Acumbamail, push content to your connected social accounts and publish through the Social Media API.
Actions: upload or update content via CSV, map fields, and publish using endpoints like POST /social-media-posting/:locationId/csv and POST /social-media-posting/:locationId/posts/bulk-delete.
POST /social-media-posting/:locationId/csv
Required fields include locationId, csvId, and the post data payload; you may also specify accountId for targeting.
Trigger: when accounts are added or updated in Acumbamail, synchronize with GHL to refresh the accounts list in the integration.
Actions: retrieve accounts via GET /social-media-posting/:locationId/accounts and map them; set accounts via POST /social-media-posting/:locationId/set-accounts.
GET /social-media-posting/:locationId/accounts
locationId and accountId
Trigger: when a CSV is uploaded or updated in Acumbamail, drive posting and analytics via the Social Media API.
Actions: manage CSV with POST /social-media-posting/:locationId/csv, update or delete with PATCH or DELETE, and pull data from GET /snapshots and GET /social-media-posting/:locationId/csv/:id for reporting.
POST /social-media-posting/:locationId/csv
locationId, csvId, id
Automate cross-channel posting without writing code.
Centralize scheduling and analytics in one place for faster campaigns.
Reuse templates and workflows to speed up campaigns and reduce manual work.
This glossary defines terms you’ll see in the integration, including locationId, endpoints, CSV, accounts, and posts, and explains how they map to your workflow.
A unique identifier for a specific business location in your GHL account.
Comma-separated values file used to batch upload posts, accounts, or data for scheduling.
Linked social media accounts that post on behalf of your location.
An API URL path used to perform a specific action, as shown in the endpoint list.
Set up a weekly CSV-driven publishing workflow to consistently post across channels without manual steps.
Use a single CSV to publish to multiple networks, coordinating accounts and locations.
Collect performance data from posts via snapshots and endpoints to inform future content.
Request or generate a valid API key in Social Media API and authorize it for Acumbamail with the required scope saas/company.write.
Map the fields your workflow needs and enable the endpoints listed in the integration guide.
Run end-to-end tests, validate data flow, monitor webhooks, and switch to production when ready.
No coding is required if you use the built-in automation features and connectors provided by the Social Media API and Acumbamail. You can map fields, set up triggers, and deploy workflows with a few clicks. For more complex needs, consult the endpoint reference to customize data flows. The saas/company.write scope governs access to account management and posting capabilities.
Essential endpoints typically include account listing (GET /social-media-posting/:locationId/accounts), CSV upload (POST /social-media-posting/:locationId/csv), and post-trigger actions (POST /social-media-posting/:locationId/posts/bulk-delete). These allow you to manage accounts, batch upload content, and schedule posts across locations. Additional endpoints support snapshots, CSV management, and account linking as needed.
Authentication is handled by generating an API key in the Social Media API dashboard and linking it to Acumbamail within your workspace. Use OAuth or token-based methods as configured, ensuring the required scope saas/company.write is granted. Store credentials securely and rotate keys periodically to maintain security.
Yes. You can schedule posts across multiple accounts by mapping each account to its target locationId and using the CSV workflow to drive posting. The accounts endpoint helps you keep the accounts list synchronized across platforms, enabling multi-account publishing from a single workspace.
Absolutely. Use no-code connectors and test modes to validate triggers, mappings, and data flow. Start with a small test location, upload a sample CSV, and verify posts, accounts, and analytics appear correctly in your dashboards before going live.
You can pull data points related to posts, accounts, and CSV status from endpoints such as GET /social-media-posting/:locationId/accounts, GET /social-media-posting/:locationId/csv, and GET /snapshots. These allow reporting, auditing, and optimization based on performance data.
Endpoint usage examples are available in the integration guide and API reference. You can find concrete requests, required parameters, and response schemas for account management, CSV actions, and post publishing to help you implement effective workflows.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
