Short answer: Drop the "Qualtrics → Qualtrics Email Survey Distribution" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Survey ID surveyId | string | Required | — |
Mailing List ID mailingListId | string | Required | — |
From Email fromEmail | string | Required | — |
From Name fromName | string | Required | — |
Subject subject | string | Required | Message subject line. |
Message Library ID messageId | string | Optional | — |
Send At (ISO 8601) sendDate | string | Required | — |
{"surveyId": "{{trigger.surveyId}}","mailingListId": "{{trigger.mailingListId}}","fromEmail": "{{trigger.fromEmail}}","fromName": "{{trigger.fromName}}","subject": "e.g. Quick update"}
{"result": {"id": "EMD_abc"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.