2021.1

To let the plugin know where it can find the attachment, you can either provide a full path
("url"), for example:
[{"url":"file:///C:/Terms-and-Conditions.pdf","disposition":"attachment"}]
or
[{"url":"http://www.example.com/image.png","disposition":"attachment"}]
or a Connect File Store ID ("fileid"), for example:
[{"fileid":100034, "disposition":"attachment"}]
Optionally, you may provide a name ("name") to override the name that the plugin creates for
an extra attachment.
Examples:
[{"fileid":100034,"name":"example.pdf","disposition":"attachment"}]
[{"url":"file:///C:/Terms-and-
Conditions.pdf","name":"terms.pdf","disposition":"attachment"}]
All attachments should be combined in one array:
[{"url":"file:///C:/Terms-and-
Conditions.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
attachments and the plain text version (if available) from the File Store, using the folder ID and
file names specified 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.
Page 710