Skip to content

HighLevel: Add an inbound message

HighLevel conversations.addAnInboundMessage: arguments, response, policy and SDK examples.

← Conversations operations · Get started

Operation gohighlevel.add_an_inbound_message

Provider route: POST /conversations/messages/inbound. Alter supplies the connection’s credentials and routing.

Install @alter-ai/sdk @alter-ai/gohighlevel with npm, or alter-sdk-gohighlevel with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { HighLevelIntegration } from "@alter-ai/gohighlevel";
async function execute(input: Parameters<HighLevelIntegration["conversations"]["addAnInboundMessage"]>[0]) {
const app = new App({ apiKey: process.env.ALTER_API_KEY! });
try {
const provider = new HighLevelIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
const call = await provider.conversations.addAnInboundMessage(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from alter_sdk_gohighlevel import HighLevelIntegration
async def execute(arguments):
async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
provider = HighLevelIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
call = await provider.conversations.add_an_inbound_message(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
bodyModelRequired within parentExpand Add an inbound message — request body — body

Referenced models: Add an inbound message — request body — body

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$ModelRootExpand Add an inbound message — response body

Referenced models: Add an inbound message — response body

Add an inbound message — response body
FieldTypePresenceDescription and constraints
$objectRoot
contactIdstringOptionalContact ID associated with the processed message
conversationIdstringRequired within parentConversation ID.
dateAddedstringOptionalTimestamp when the processed message was created
Format: date-time
emailMessageIdstringOptionalEmail message ID created for email conversations
messagestringRequired within parentResult message returned after processing
messageIdstringRequired within parentThis is the main Message ID
successbooleanRequired within parentWhether the message processing succeeded
Add an inbound message — request body — body
FieldTypePresenceDescription and constraints
$objectRoot
altIdstringOptionalexternal mail provider's message id
attachmentsarrayOptionalArray of attachments
attachments[]stringEach item
callJSONOptionalPhone call dialer and receiver information
call (allOf 1)ModelAll variants applyExpand Add an inbound message — request body — body call from, status, to
contactIdstringRequired within parentContact Id
conversationIdstringRequired within parentConversation Id
conversationProviderIdstringRequired within parentConversation Provider Id
datestringOptionalDate of the inbound message
Format: date-time
directionobjectOptionalMessage direction, if required can be set manually, default is outbound
Default: outbound
emailBccarrayOptionalList of email address to BCC
emailBcc[]stringEach item
emailCcarrayOptionalList of email address to CC
emailCc[]stringEach item
emailFromstringOptionalEmail address to send from. This field is associated with the contact record and cannot be dynamically changed.
emailMessageIdstringOptionalSend the email message id for which this email should be threaded. This is for replying to a specific email
emailTostringOptionalRecipient email address. This field is associated with the contact record and cannot be dynamically changed.
htmlstringOptionalHTML Body of Email
messagestringOptionalMessage Body
subjectstringOptionalSubject of the Email
typestringRequired within parentMessage Type
One of: SMS, RCS, Email, WhatsApp, GMB, IG, FB, Custom, WebChat, Live_Chat, Call, IVR_Call, Campaign_Call, Campaign_VoiceMail, TIKTOK, ALL_IN_ONE_CHAT, FORM_SUBMISSION

Referenced models: Add an inbound message — request body — body call from, status, to

Add an inbound message — request body — body call from, status, to
FieldTypePresenceDescription and constraints
$objectRoot
fromstringOptionalPhone number of the dialer
statusstringOptionalCall status
One of: pending, completed, answered, busy, no-answer, failed, canceled, voicemail
tostringOptionalPhone number of the receiver

SDK function policy ID: gohighlevel.add_an_inbound_message. Catalog operation: add-an-inbound-message. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Required provider scopes: ["conversations/message.write"]

Pinned headers: {"Version": "v3"}

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.