The Conversations API supports secure authentication via OAuth2 and API keys. Choose the method that best fits your security posture and workflow needs.
In the Zapier App Connector, configure OAuth2 credentials or an API key with the proper scopes to access Conversations data from GHL.
GET /conversations/:conversationsId (retrieve a conversation); GET /conversations/search (search conversations); conversations.write (update permissions); POST /conversations/ (create a conversation); PUT /conversations/:conversationsId (update a conversation); DELETE /conversations/:conversationsId (delete a conversation); conversations/message.readonly (read messages); GET conversations/messages/:messageId/locations/:locationId/recording (retrieve recording); GET conversations/locations/:locationId/messages/:messageId/transcription (retrieve transcription); GET conversations/locations/:locationId/messages/:messageId/transcription/download (download transcription); conversations/message.write (write a message); POST /conversations/messages (create a message); POST /conversations/messages/inbound (ingest inbound message); POST /conversations/messages/upload (upload attachment); PUT /conversations/messages/:messageId/status (update message status); DELETE /conversations/messages/:messageId/schedule (cancel scheduled message); DELETE /conversations/messages/email/:emailMessageId/schedule (cancel scheduled email).
Trigger: When a new inquiry arrives, create a conversation or update existing.
Actions: POST /conversations/ to create; PUT /conversations/:conversationsId to update; GET /conversations/:conversationsId to fetch.
Key endpoint paths: POST /conversations/, PUT /conversations/:conversationsId, GET /conversations/:conversationsId
Fields: conversationsId, subject, participants, status, lastMessage
Trigger: new or updated messages
Actions: POST /conversations/messages; POST /conversations/messages/inbound; POST /conversations/messages/upload; PUT /conversations/messages/:messageId/status
Key endpoint paths: POST /conversations/messages, POST /conversations/messages/inbound, POST /conversations/messages/upload, PUT /conversations/messages/:messageId/status
Fields: messageId, conversationsId, content, status, attachments
Trigger: new transcription or recording available
Actions: GET /conversations/messages/:messageId/locations/:locationId/recording; GET /conversations/locations/:locationId/messages/:messageId/transcription; GET /conversations/locations/:locationId/messages/:messageId/transcription/download
Key endpoints: GET /conversations/messages/:messageId/locations/:locationId/recording; GET /conversations/locations/:locationId/messages/:messageId/transcription; GET /conversations/locations/:locationId/messages/:messageId/transcription/download
Fields: messageId, locationId, transcription, recordingUrl
Build end-to-end conversation workflows without writing code.
Synchronize messages and transcripts in real-time across apps.
Easily test, iterate, and deploy automations with clicks.
Elements: Endpoints, triggers, actions, mappings, authentication, scopes, rate limits.
A set of rules and endpoints that let apps communicate.
A callback URL that notifies your app of events.
A specific URL that represents a function in the API.
Textual representation of spoken content from a recording.
Create or update conversations based on inbound inquiries and route to the right agent.
Transcribe voice messages and route to appropriate teams.
Aggregate metrics from conversations into dashboards and alerts.
Configure OAuth2 credentials or API keys in both sides.
Choose conversation, message, and transcription triggers and map to actions.
Run tests, verify data accuracy, and go live.
The Conversations API exposes endpoints for reading, searching, creating, updating, and deleting conversations, as well as comprehensive message operations and transcription access. You can mix and match these endpoints to fit your workflow. Use the ENDPOINTLIST as a quick reference to pick the endpoints you need for a given automation.
No extensive coding is required when you connect the Conversations API with the Zapier App Connector. Zapier provides no-code triggers, actions, and searches that map directly to the API endpoints, enabling you to automate without writing code. You can customize flows using visual builders and data mappings.
Authentication is supported via OAuth2 or API keys. In most cases, you will configure OAuth2 credentials or issue an API key with the necessary scopes (for example, conversations.readonly) to access resources. Always secure tokens and rotate credentials regularly.
Yes. You can access transcripts using endpoints like GET /conversations/locations/:locationId/messages/:messageId/transcription and the download endpoint. Transcripts can be used in workflows, reports, or routed to agents.
Yes. Conversations can be created via POST /conversations/. Include the subject, participants, and initial messages as part of the payload. This allows you to start new conversations from automations or other apps.
Yes. Scheduling and updating message delivery is supported via endpoints such as PUT /conversations/messages/:messageId/status and DELETE /conversations/messages/:messageId/schedule. This enables flexible delivery and rescheduling within your automations.
Use Zapier’s built-in test feature and sample data to validate connections and mappings. Review endpoint responses and adjust field mappings to ensure data accuracy before going live.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
