ActionQualtricsUpdated September 2026

How do I distribute a Qualtrics survey via email?

Short answer: You can qualtrics email survey distribution in Qualtrics by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Qualtrics Qualtrics Email Survey Distribution action to a workflow, map its 7 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Qualtrics Email Survey Distribution in Qualtrics — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Survey ID
surveyId
stringRequired
Mailing List ID
mailingListId
stringRequired
From Email
fromEmail
stringRequired
From Name
fromName
stringRequired
Subject
subject
stringRequiredMessage subject line.
Message Library ID
messageId
stringOptional
Send At (ISO 8601)
sendDate
stringRequired
Sample request
{
"surveyId": "{{trigger.surveyId}}",
"mailingListId": "{{trigger.mailingListId}}",
"fromEmail": "{{trigger.fromEmail}}",
"fromName": "{{trigger.fromName}}",
"subject": "e.g. Quick update"
}
Returns
{
"result": {
"id": "EMD_abc"
}
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Qualtrics Email Survey Distribution.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Qualtrics Email Survey Distribution.

What does the Qualtrics Email Survey Distribution action do in Qualtrics?
Sends a survey via email to a contact list with configured template. For "weekly NPS survey to closed tickets" customer-feedback automation.
What inputs does Qualtrics Email Survey Distribution require?
Required: Survey ID, Mailing List ID, From Email, From Name, Subject, Send At (ISO 8601). Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Qualtrics returns an error?
The run history shows the failed step with its input and the error message Qualtrics returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Qualtrics Email Survey Distribution support batch operations?
Run Qualtrics Email Survey Distribution inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Qualtrics's rate limits.
More actions

Other Qualtrics actions.

Qualtrics Email Survey Distribution in Qualtrics — start free