# sib_transactional_emails.sendtransacemail: Sendinblue Package for Transactional emails operations that could not be mapped to a table. sib_transactional_emails.sendtransacemail: Sendinblue Package for Transactional emails operations that could not be mapped to a table. Send a transactional email to one or more recipients, either using inline HTML content or a pre-built template via `templateId`. You can schedule emails for future delivery using `scheduledAt` (UTC, up to 5-minute delay), send multiple personalized versions with `messageVersions` (max 2000 total recipients, 99 per version), and attach files via URL or base64-encoded content. A `sender` and `subject` are required when no `templateId` is provided; when a `templateId` is used, the template''s sender and subject are applied unless overridden.Parameters of Procedure The following parameters can be used to control the behaviour of the procedure `sib_transactional_emails.sendtransacemail`. 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 `begin package.procedure(value1, value2, value3); end` on a procedure 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 `begin package.procedure(name1 => value1, name3 => value3); end` on the same procedure 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 | |---|:---:|:---:|:---:|---| | `batchId` | `string` | ☐ | | UUIDv4 identifier for the scheduled batch of transactional emails. If omitted, a valid UUIDv4 batch identifier is automatically generated. | | `htmlContent` | `string` | ☐ | | HTML body content of the email. Required when `templateId` is not provided. Ignored when `templateId` is provided. | | `email` | `string` | ☐ | | Email address in reply to | | `name` | `string` | ☐ | | Display name for the reply-to address. Maximum length is 70 characters. | | `scheduledAt` | `datetime` | ☐ | | UTC date-time when the email should be sent (format: YYYY-MM-DDTHH:mm:ss.SSSZ). Include timezone information in the date-time value. Scheduled emails may be delayed by up to 5 minutes. | | `email_2` | `string` | ☐ | | Sender email address. Required when `id` is not provided. | | `id` | `int64` | ☐ | | Sender identifier. Required when `email` is not provided. Use this field to select a sender with a specific IP pool (dedicated IP users only). | | `name_2` | `string` | ☐ | | Display name of the sender. Maximum length is 70 characters. Only applicable when `email` is provided. | | `subject` | `string` | ☐ | | Email subject line. Required when `templateId` is not provided. | | `templateId` | `int64` | ☐ | | Template identifier | | `textContent` | `string` | ☐ | | Plain text body content of the email. Ignored when `templateId` is provided. |