Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input 

Document

• Min: 0

• Max: 1

• Mapper

• Copy Snap

• JSON Parser

Requires the Email Body Type and the Email Content deliver the message.

Output

Document

• Min: 0

• Max: 1

• Read Email

• Mapper

The output would be a confirmation that the email was sent successfully.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:

• Stop Pipeline Execution: Stops the current Pipeline execution when the Snap encounters an error.

• Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

• Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Message ID is required field for sending an email in thread

You have either not entered a message ID or provided an invalid one.

Enter the Existing Message ID also ensure it to be a valid one.

Check whether the file path is correct.

You have entered an invalid/incorrect URL for the email’s attachment.

Verify and enter a valid URL for attachments.

Chunk Upload interrupted

The Snap could not upload the attachments.

Avoid multiple uploading of attachments and retry the process.

Table Data path is not found.

The Snap could not find a JSON path for the table data.

Provide a valid path for the Table Data.

The Table Data Path field does not reference a map or an array of maps.

The Snap is unable to map the Table Data path to the HTML table row data.

Please verify if the Table Data Path references a map or an array of maps