This connector enables the transmission of email messages via the SendGrid server. It supports TLS 1.3 for enhanced security.
Configuration
SendGrid Mail Send configuration
Server URL
The URL of SendGrid server.
https://api.sendgrid.com
Authorization Token
Define the authorization token that is used to authenticate the connection to SendGrid server.
Input & Output Schema
Input
E-Mail SendGrid Send (ver. 1.0.1)
Column | Data type | Allow null | Description |
---|---|---|---|
Subject | String | Yes | Subject |
Importance | String | Yes | Importance of email (low, normal, high) |
From | E-Mail Send Person 1.0.1 |
Yes | Sender of email |
To | E-Mail Send Person 1.0.1 |
No | The recipient/s of the email data |
Cc | E-Mail Send Person 1.0.1 |
Yes | Recipients that are copied on the email data object |
Bcc | E-Mail Send Person 1.0.1 |
Yes | Recipients that are blind-copied on the email data object |
BodyType | String | No | Body type of message (text, html) |
Body | String | No | Body |
ClickTracking | Bool | Yes | Enabling Click Tracking causes all the links and URLs in your emails to be overwritten and pointed to either SendGrid’s servers or the domain you branded your link with so that any time a customer clicks a link, SendGrid can track those clicks. SendGrid can track up to 1000 links per email. |
OpenTracking | Bool | Yes | Open Tracking adds an invisible, one pixel image at the end of the email which can track email opens. If the email recipient has images enabled on their email client and a request to SendGrid’s server for the invisible image is executed, then an open event is logged. |
Attachment | E-Mail Attachment 1.0.0 |
Yes | Email attachments |
E-Mail Send Person (ver. 1.0.1)
Column | Data type | Allow null | Description |
---|---|---|---|
Name | String | Yes | Name of person |
Address | String | No | Email address |
E-Mail Attachment (ver. 1.0.0)
Column | Data type | Allow null | Description |
---|---|---|---|
Name | String | No | File name with extension |
Content | Base64 | No | Encoded file content |
Output
Data schema is mandatory
The connector requires mandatory input or output data schema, which must be selected by the user from the existing data schema repository or a new one must be created. The connector will fail without structured data.
Release notes
3.1.0
- Plugin binaries update as a result of included connector change.
3.0.3
- Fixed shared nuget package versions.
3.0.2
- Fixed right processing of nullable properties.