Use OAuth or API keys to securely authenticate requests to the Conversations API within your GHL account.
Grant permissions and set scopes so Act-On can read and manage conversations via the API.
Overview of endpoints used in the Act-On integration: – GET /conversations/:conversationsId – GET /conversations/search – conversations.write – POST /conversations/ – PUT /conversations/:conversationsId – DELETE /conversations/:conversationsId – conversations/message.readonly – GET conversations/messages/:messageId/locations/:locationId/recording – GET conversations/locations/:locationId/messages/:messageId/transcription – GET conversations/locations/:locationId/messages/:messageId/transcription/download – conversations/message.write – POST /conversations/messages – POST /conversations/messages/inbound – POST /conversations/messages/upload – PUT /conversations/messages/:messageId/status – DELETE /conversations/messages/:messageId/schedule – DELETE /conversations/messages/email/:emailMessageId/schedule
Triggered when a specific conversation is requested by ID
Fetch and return conversation details for downstream workflows
GET /conversations/:conversationsId
conversationsId
Triggered by a search query from Act-On contact data
Query conversations and return matching results
GET /conversations/search
query, page, limit
Triggered when initiating a new conversation from Act-On
Create and store a new conversation, optionally set initial status
POST /conversations/
body (conversation object)
Faster automation with ready-made endpoints
Easier maintenance with centralized API references
Enhanced data sync between Conversations and Act-On workflows
This section defines the core elements and how they interact when connecting the GHL Conversations API to Act-On, including endpoints, triggers, and data fields.
Application Programming Interface: a set of rules that enables applications to communicate with one another.
A specific URL path that performs a defined action in the API.
The process of verifying identity before allowing access to API resources.
A callback URL that receives real-time data updates.
Trigger a welcome message when a new contact is added in Act-On and route to a conversation in GHL.
Analyze transcription sentiment from message and route to the appropriate agent or workflow.
Archive or tag conversations based on status updates from Act-On.
Set up OAuth or API keys for both apps and grant necessary scopes.
Define how GHL endpoints align with Act-On data objects and triggers.
Run end-to-end tests and monitor for errors before going live.
For Conversations API, use OAuth 2.0 or API keys to authenticate requests. OAuth provides token-based access with scopes that you can tailor for read or write operations. API keys can be used for server-to-server scenarios with strict access controls. Always store credentials securely and rotate keys regularly.
Yes. You can emit events from Conversations API to Act-On using webhooks or polling, then trigger Act-On workflows based on conversation state or message events. Map payload fields to Act-On contact properties to drive automation. Ensure your event schema is consistent to avoid data drift.
Common endpoints include getting a conversation by ID, searching conversations, and creating or updating conversations. For Act-On integrations, POST /conversations/ and GET /conversations/search are frequently used, along with message endpoints for sending or updating content. Review endpoint descriptions to determine exact needs.
No heavy coding is required for basic integrations; many tasks can be accomplished with configurable triggers, mappings, and single-step actions. More advanced flows may require small scripts or Zapier workflows to transform data. Start with the no-code endpoints you need and iterate.
Implement retries with exponential backoff and monitor error responses from the API. Log failed requests, alert on critical failures, and implement idempotent operations where possible to avoid duplicates. Use rate-limit-aware requests to prevent throttling.
When creating a new conversation, you typically need at least a participant or contact reference and an initial message payload. Depending on your workflow, include fields like subject, status, and any custom properties that Act-On uses for routing.
Endpoint details are documented in the API reference and include method, path, required parameters, and sample responses. Rate limits vary by plan; check your account settings and the API docs for current quotas and retry guidance.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
