Obtain your API key, review the required scope conversations.readonly, and authorize requests to securely access the Conversations API.
Set up Act! authentication to securely connect to GHL using an API token or OAuth flow before calling endpoints.
Endpoints include: GET /conversations/:conversationsId, GET /conversations/search, POST /conversations/, PUT /conversations/:conversationsId, DELETE /conversations/:conversationsId, GET conversations/messages/:messageId/locations/:locationId/recording, GET conversations/locations/:locationId/messages/:messageId/transcription, GET conversations/locations/:locationId/messages/:messageId/transcription/download, 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
Trigger: When a conversation is created or updated in Act!, fetch or create the corresponding record in the Conversations API to keep both systems in sync.
Actions: GET /conversations/:conversationsId, POST /conversations/, PUT /conversations/:conversationsId
Paths: GET /conversations/:conversationsId, POST /conversations/
Key fields: conversationsId, status, lastUpdated, participants
Trigger: An inbound message arrives in Act! and is posted to the Conversations API for processing.
Actions: POST /conversations/messages/inbound; POST /conversations/messages
Paths: POST /conversations/messages/inbound, POST /conversations/messages
Key fields: messageId, conversationId, from, text, attachments
Trigger: Transcriptions become available for messages and can be surfaced in Act! workflows.
Actions: GET /conversations/locations/:locationId/messages/:messageId/transcription, GET /conversations/locations/:locationId/messages/:messageId/transcription/download
Paths: GET /conversations/locations/:locationId/messages/:messageId/transcription, GET /conversations/locations/:locationId/messages/:messageId/transcription/download
Key fields: messageId, locationId, transcription, status
Automate common tasks with a visual workflow, no heavy coding required.
Keep conversations in sync across Act! and other channels for a unified customer view.
Access a comprehensive end to end set of endpoints for messaging, inbound, and transcription tasks at scale.
Glossary of API, endpoints, inbound messages, transcriptions, and conversations terms to help you design and troubleshoot your integration.
An interface that exposes Conversations endpoints for your app to call.
Messages sent to your account from a user or channel that can start or continue a conversation.
A text version of audio from a message, returned by the transcription endpoints.
A thread of messages between a user and your system that persists over time.
Automatically push status updates between Act! and Conversations API to keep agents informed.
Capture and attach transcriptions to conversations to improve searchability and context.
Route inbound messages to the right teams in Act! based on content and metadata.
Obtain an API key, set the required scopes, and authorize requests to access the API.
Select endpoints and set up webhooks for inbound messages and events.
Run tests, verify data flows, and deploy to production with monitoring.
You authenticate with an API key or OAuth token and grant the requested scope. Start by generating a key in your developer console, attach the conversations.readonly scope for read access, and rotate credentials regularly. If you use OAuth, ensure your redirect URI is registered and refresh tokens before expiry. The API uses standard REST semantics with clear endpoint paths and error codes to help you diagnose issues quickly.
Use GET for retrieving conversations and search endpoints, and POST for creating, updating, or inbound messages. Map your Act! triggers to the corresponding endpoints and test with sample data. Review the endpoint list above for exact paths and payload structures. Validate responses against the schema in your integration docs.
Inbound messages are posted via the inbound endpoint and can be linked to existing conversations. Transcriptions are available at the transcription endpoints and can be downloaded for storage or review. Build a workflow to surface transcription status in Act! and notify agents when new content is ready.
APIs are subject to rate limits and quotas. Plan retries with exponential backoff and monitor usage in the dashboard. If you expect higher traffic, contact support to discuss a higher limit or alternative batching strategies.
Secure your API key by treating it like a password; rotate keys regularly and use OAuth where possible. Use secure storage and never expose keys in client-side code. Employ scoped tokens and principle of least privilege for each integration area.
Yes, a sandbox or development environment is available to test endpoints safely. Use test keys in the sandbox and switch to production keys when ready. Validate end-to-end flows before going live to prevent data issues.
Logs and errors are available in the developer portal and within the app’s dashboard. Use these to troubleshoot authentication, routing, and data mapping issues. Enable verbose logging temporarily during integration debugging for faster resolution.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
