Navigation: Catalog: Brevo > Schemas > Schema: Conversations > Tables

ConversationMessageBccsByConversationId

Get a messageRetrieve a single message by its ID.

Catalog: Brevo

Schema: Conversations

This is a read-only table function. The Sendinblue API may not support changing the data or the Invantive UniversalSQL driver for Sendinblue does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Sendinblue API.

Parameters of Table Function

The following parameters can be used to control the behaviour of the table function ConversationMessageBccsByConversationId. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values.

Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three.

Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third.

Name	Data Type	Required	Default Value	Documentation
id		☑		ID of the message

Columns of Table Function

The columns of the table function ConversationMessageBccsByConversationId are shown below. Each column has an SQL data type.

Name	Data Type	Label	Required	Documentation
agentId	varchar2		☐	ID of the agent on whose behalf the message was sent (only in messages sent by an agent).
agentName	varchar2		☐	Agent’s name as displayed to the visitor. Only in the messages sent by an agent.
agentUserpic	varchar2		☐	Only set if the agent has uploaded a profile picture.
createdAt	int64	Creation Date	☐	Timestamp in milliseconds.
email	varchar2	Email Address	☐
file_imageInfo_height	int64		☐	Height of the image in pixels.
file_imageInfo_previewLink	varchar2		☐	URL of the image preview.
file_imageInfo_width	int64		☐	Width of the image in pixels.
file_inlineId	varchar2		☐	The ID of the inline file.
file_isAllowedFileType	char		☐	Whether the file extension is allowed for download.
file_isImage	char		☐	Whether the file is an image.
file_isInline	char		☐	Whether the file is inline.
file_isSticker	char		☐	Whether the file is a sticker.
file_link	varchar2		☐	URL of the file.
file_mimeType	varchar2		☐	MIME type of the file.
file_name	varchar2		☐	Name of the file.
file_size	int64		☐	Size in bytes.
forwardedToSourceStatus_error	varchar2		☐
forwardedToSourceStatus_isSuccess	char		☐
from_email	varchar2		☐
from_name	varchar2		☐
html	varchar2		☐	The HTML content of the message.
id	varchar2	ID	☐	Message ID. It can be used for further manipulations with the message.
integrations	varchar2		☐	Integration details.
isBot	char		☐	`true` for automated messages generated by an AI bot.
isForward	char		☐	‘`true` if the message is a forwarded message.’
isMissed	char		☐	`true` for missed and offline messages.
isMissedByVisitor	char		☐	`true` for unread agent’s messages in finished chats.
isPushed	char		☐	`true` for pushed messages
isSentViaJsApi	char		☐	‘`true` if the message was sent via JavaScript API.’
isTrigger	char		☐	`true` for automatic messages from “Targeted chats & triggers” and API (https://developers.brevo.com/docs/javascript-api-reference#sendautomessage)
messageType	varchar2		☐	The type of message content (e.g. for integration-specific message types).
name	varchar2	Name	☐
rawUnsafeHtml	varchar2		☐	Unescaped HTML content of the message (may include unsafe HTML).
receivedFrom	varchar2		☐	In two-way integrations, messages sent via REST API can be marked with receivedFrom property and then filtered out when received in a webhook to avoid infinite loop.
replyTo_email	varchar2		☐
replyTo_name	varchar2		☐
source	varchar2		☐	Source information for the message.
sourceMessageId	varchar2		☐	The ID of the message assigned by the integration source.
subject	varchar2	Subject	☐	The subject line of the email message (only for messages sent to email threads).
text	varchar2	Text	☐	Message text or name of the attached file
type	varchar2	Type	☐	`"agent"` for agents’ messages, `"visitor"` for visitors’ messages.
visitorId	varchar2		☐	visitor’s ID

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Sendinblue API Data Model

ConversationMessageBccsByConversationId

Parameters of Table Function

Columns of Table Function

Important Safety and Usage Information