2022.2

All attachments should be combined in one array:
[{"url":"file:///C:/Terms-and-Condi-
tions.pdf","disposition":"attachment","name":"Terms.pdf"},{"name":"Take
action Mandie.pdf","disposition":"attachment"}]
The order of the key/value pairs is not important.
Processing
The plugin communicates with the Connect Server to retrieve each email message's body, any attach-
ments and the plain text version (if available) from the File Store, using the folder ID and file names spe-
cified in the output of the Render Email Content task.
It then transforms the files into email messages as specified by SendGrid and sends the emails via the
SendGrid v3 Web API.
Output
This task does not make any changes to the Metadata or the Job File.
Properties
General Tab
l
SendGrid API:
l
API Key: Enter your API key, retrieved from SendGrid. It will be used for authentication
with the SendGrid v3 Web API. A valid key is required to send email messages.
l
Data Source (see "Input" on the previous page):
l
Categories (optional): Enter a single category name (e.g. invoice) or an array of category
names (e.g. ["invoice","brand1"]) for the messages. The maximum length of each category
name is 255 characters. You can specify up to 10 categories per request. See About cat-
egories.
l
Send At (optional): Enter a UNIX timestamp specifying when you want your email to be
sent from SendGrid. This can be left empty if you want the email to be sent at the time of
your API request.
l
Headers (optional): A JSON object containing key/value pairs of header names and the
value to substitute for them. Example: {"x-my-header":"my-value"}.
If they contain Unicode characters, you must ensure that these are properly encoded.
Custom header names normally start with "x-".
The following headers are reserved and cannot be used as custom header: x-sg-id, x-
sg-eid, received, dkim-signature, Content-Type, Content-Transfer-Encod-
ing, To, From, Subject, Reply-To, CC, BCC.
Page 591