2022.2

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-Condi-
tions.pdf","name":"terms.pdf","disposition":"attachment"}]
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 Mailjet and sends the emails via the
Mailjet Web API.
Output
This task does not make any changes to the Metadata or the Job File.
Properties
General Tab
l
Mailjet API:
l
API Key and Secret Key: The API Key and Secret Key are both generated automatically
when you create your Mailjet account. The plugin needs to provide them in order to authen-
ticate its request to Mailjet's Email API endpoint.
l
Data Source (see "Input" on the previous page):
l
Custom Campaign: Each e-mail going through Mailjet is attached to a campaign. Specify
the campaign name here. If the campaign doesn't already exist it will be automatically cre-
ated in the Mailjet system. When sending email through Mailjet's Web API it is allowed to
send multiple emails with the same campaign name to the same contacts.
Page 590