Minery: Crear Tarea desde EmailInstall

Summary

Create tasks and/or communications in ECIJA from email data, optionally uploading attachments and sending autoreplies, based on the selected workflow type.

Inputs

• workflowType (required) — Select the process flow: full (create task + upload attachments + create communication), taskOnly (create task with autoreply), or communicationOnly (create communication linked to an existing task).
• taskConfig — Configure task details when creating a task (used in full or taskOnly modes): title (defaults to email subject), description (defaults to email content), autoreply email (defaults to email sender), priority, assigned user IDs, client ID, matter ID, due date, and internal task flag.
• communicationConfig — Configure communication details when creating communications (used in full or communicationOnly modes): existing task ID (required in communicationOnly mode), type of communication (received, sent, draft), channel, from address, to recipients, CC, and BCC addresses, with defaults from the email data.
• attachmentConfig — Configure attachment handling when uploading attachments (only in full mode): specify the input field containing attachments, maximum allowed attachment size per file in MB (up to 20), and option to continue processing if an attachment upload fails.
• additionalOptions — Additional options: include full metadata in the response (default true), enable debug mode for extra debug info, and validate that the input contains required email fields (from, to, subject).

Output shape

a single JSON object indicating success status, created task and/or communication IDs, processing steps completed, any errors encountered, and optionally metadata and debug information.

If attachments are uploaded, the operation tracks processing results including successful and failed uploads. Errors in critical steps throw exceptions unless the node is configured to continue on fail. The shape includes contextual metadata and debug data controlled by additional options. Communication creation requires a task ID in communicationOnly mode; in full mode the task ID is obtained during task creation.

Examples

Example 1: Creating a full workflow: task, attachments, and communication from an email input.

Set 'workflowType' to 'full', configure task details as needed, optionally specify attachment field and max size, and provide communication details if needed. Attachments from the specified field in the input email JSON are uploaded. A task is created with the given or default parameters, attachments uploaded, and a communication record linked to that task is created.

Example 2: Creating only a new task with autoreply from an email.

Set 'workflowType' to 'taskOnly'. Configure task parameters such as title, description, and autoreply email address. No attachments or communications are created or uploaded.

Example 3: Creating only a communication linked to an existing task.

Set 'workflowType' to 'communicationOnly', and provide the existing task ID. Configure communication fields such as fromAddress, to, cc, and bcc. No tasks or attachments are created or uploaded.