Send by IQA Query
AI-generatedSummary
Runs an iMIS IQA query and queues a Howler email for each result row with a non-empty party ID. Each email is recorded as a COMMQUEUE activity using the selected Howler definition; an optional deduplication key is scoped to each recipient.
Inputs
- Howler Definition (required) — Howler definition product code for the email template.
- IQA Query Name (required) — Full path of the IQA query to run.
- Party ID Field — Column containing the recipient's party ID; defaults to ID. Rows without a value in this column are skipped.
- Additional Options: Limit — Maximum IQA results to process, from 1 to 10,000; defaults to 500.
- Additional Options: Query Parameters — Positional values passed to the IQA query. Their order must match the query definition; parameter names are for reference.
- Deduplication Key — Campaign key used to check for an existing live Howler activity. The node appends each recipient's party ID to the key; matching recipients are recorded as DUPLICATE and not sent. Leave empty to always queue.
- Sender Contact ID (Reply-To) — Optional iMIS contact ID applied to every queued activity; Howler resolves it to the Reply-To email address.
Output shape
A list of items, one for each IQA row with a non-empty party ID that was queued.
Each item includes success, activityId, partyId, howlerDefinition, sourceCode, deduped status and key, timestamps, the original iqaRow, and the iMIS response. Duplicate rows are included with sourceCode DUPLICATE. Query or queue errors fail the operation.