RFC822 Parser

the rfc822 parser connector facilitates the extraction and analysis of data from emails formatted according to the rfc822 standard the rfc822 email parser connector is designed to seamlessly integrate with swimlane turbine, providing users with the ability to automatically extract and analyze data from rfc822 formatted email attachments this connector simplifies the process of parsing email content for threat detection and incident response, enhancing the capabilities of security teams to respond to potential threats quickly and efficiently by leveraging this connector, users can automate the extraction of valuable information from email attachments, which can then be used in playbooks for further analysis and action within the swimlane ecosystem actions parse attachment extracts data from rfc822 formatted email attachments for enhanced analysis and processing endpoint method get input argument name type required description attachment object optional file to be uploaded attachment file string optional parameter for parse attachment attachment file name string optional name of the resource attachment description string optional parameter for parse attachment input example {"attachment" {"file" "string","file name" "example name","description" "string"}} output parameter type description from string output field from to array output field to cc array output field cc bcc array output field bcc subject string output field subject message id string unique identifier date string date value headers array http headers for the request headers key string http headers for the request headers value string http headers for the request size number size in bytes raw string unformatted email parts array output field parts parts content type string type of the resource parts content disposition string response content parts content id string unique identifier parts is attachment boolean output field parts is attachment parts filename string name of the resource parts creation date string date value parts modification date string date value parts read date string date value parts mime type string type of the resource parts charset string output field parts charset parts content text string response content parts content array response content output example {"from" "string","to" \[],"cc" \[],"bcc" \[],"subject" "string","message id" "string","date" "string","headers" \[],"size" 123,"raw" "string","parts" \[],"status" "string","status details" "string"} response headers header description example content type the media type of the resource application/json date the date and time at which the message was originated thu, 01 jan 2024 00 00 00 gmt