iMIS Send Howler Email icon

iMIS Send Howler Email

Queue an email to be sent via iMIS Howler

Actions2

Send to Party ID

AI-generated

Summary

Queue a Howler email for each input item’s Party ID by creating an iMIS COMMQUEUE activity with the selected Howler Definition. Optionally pass a JSON object to the template, set a Reply-To contact, and use a deduplication key to flag an already-live matching activity as DUPLICATE so it is not sent.

Inputs

  • Howler Definition (required) — The Howler definition (product code) for the email template.
  • Party ID (required) — The iMIS Party ID (contact ID) that receives the email. The node queues one activity per input item.
  • JSON Data — Optional JSON object passed to the template through the activity NOTE field. Leave empty to omit it; arrays and primitive JSON values are rejected.
  • Deduplication Key — Written to activity UF_3. If a COMMQUEUE activity with this key is in QUEUED, HOWLER, or PROCESSED state, the new activity is marked DUPLICATE and will not be sent. Leave empty to always queue for sending.
  • Sender Contact ID (Reply-To) — Optional iMIS contact ID written to OTHER_ID; Howler resolves it to an email address and uses it for the message Reply-To header.

Output shape

One output item per input item, each containing a success flag and the created activity details.

Includes activityId, partyId, activityType, howlerDefinition, sourceCode, deduplication status and key, transactionDate, effectiveDate, parsed jsonData, and the iMIS response with iMIS metadata removed. A duplicate is still recorded as an activity with sourceCode DUPLICATE. Invalid required values, malformed JSON, or queue errors fail the operation.

Links

Discussion