Community

Add Qualtrics File Transfer Support to Activations

Answered

Chaitanya Makashir User

September 22, 2026 18:18

Hi team,

Background

Hightouch currently supports two protocols for syncing data to Qualtrics:

API
File Transfer

We are currently using the File Transfer option due to challenges encountered with the API-based approach.

Feature Request

As part of our migration to Activations, we would like to continue using the existing File Transfer workflow and retain our current field mappings, including ACCOUNT_OWNER_NAME, CRM_*, and other custom fields.

However, the Qualtrics destination in Activations currently offers only the Contact API sync. The available fields are limited to:

Email
First name
Last name
External reference
Phone
Language
Unsubscribed

Could you please consider adding File Transfer support for the Qualtrics Activations destination? This would allow us to maintain our existing integration and field mappings while migrating from Hightouch to Activations.

Given our migration timelines and dependency on this functionality, could you please consider treating this request as a high priority? Additionally, could you provide an estimated timeline or ETA for when this feature might be available?

Please sign in to leave a comment.

Comments

1 comment

Official comment

Jeremy Wan Fivetranner
- September 23, 2026 19:17
Hi Chaitanya,

Thanks for the detailed writeup. Before we scope file transfer support, we want to make sure we're solving the right problem, so a couple of questions:

1. Custom fields
Our Qualtrics connector already supports custom fields like ACCOUNT_OWNER_NAME and CRM_* today, via Qualtrics' embedded data. It's not limited to the 7 fields listed on our destination page. Have you tried mapping these fields directly in your sync? If so, what happened?

2. The API-based issues you mentioned
You noted you moved to File Transfer in Hightouch due to "challenges" with their API-based approach. Could you share specifics: errors, rate limits, timeouts, or something else? Knowing the actual blocker helps us figure out whether it's specific to Hightouch's implementation, or a real limitation we'd hit too.

3. On file transfer itself
We don't have an ETA for file-based import support. That said, if what you're actually running into is a fixable gap in our existing API-based sync rather than something only file transfer can solve, that's work we're more likely to be able to prioritize than building a new delivery mode from scratch. The answers above will help us find the fastest path to unblocking you.

Best,
Jeremy

Official comment

Jeremy Wan Fivetranner

September 23, 2026 19:17

Hi Chaitanya,

Thanks for the detailed writeup. Before we scope file transfer support, we want to make sure we're solving the right problem, so a couple of questions:

1. Custom fields
Our Qualtrics connector already supports custom fields like ACCOUNT_OWNER_NAME and CRM_* today, via Qualtrics' embedded data. It's not limited to the 7 fields listed on our destination page. Have you tried mapping these fields directly in your sync? If so, what happened?

2. The API-based issues you mentioned
You noted you moved to File Transfer in Hightouch due to "challenges" with their API-based approach. Could you share specifics: errors, rate limits, timeouts, or something else? Knowing the actual blocker helps us figure out whether it's specific to Hightouch's implementation, or a real limitation we'd hit too.

3. On file transfer itself
We don't have an ETA for file-based import support. That said, if what you're actually running into is a fixable gap in our existing API-based sync rather than something only file transfer can solve, that's work we're more likely to be able to prioritize than building a new delivery mode from scratch. The answers above will help us find the fastest path to unblocking you.

Best,
Jeremy