Skip to main content
Use the Trustpilot destination to send review invitations from your ETL pipeline. The component posts one invitation to Trustpilot’s Invitations API for every input record, using an invitation template you have already defined in the Trustpilot Business portal. Each invitation asks for a service review, and can also ask for a product review of the items on that order.
Every record that succeeds puts an email in a real consumer’s inbox. There is no dry run and no undo. Tasks are not retried on failure, because a retried attempt would re-send every invitation the failed attempt already delivered. Test on a small sample before running against a full dataset.

When to use it

Use this destination to trigger post-purchase or post-interaction review invitations from data already in your pipeline. Typical inputs are order or ticket records with a customer email address and your internal reference number for the transaction. To ask for product reviews as well, add the products for each order and see Requesting product reviews. For reading service reviews and business categories back out of Trustpilot, use the Trustpilot source instead.

Connection

Select an existing Trustpilot connection or create a new one. The destination has two requirements the source does not:
  • API Secret must be set on the connection. The invitations endpoint accepts only OAuth bearer tokens, and Trustpilot mints those through the client_credentials flow, which needs both the API Key and the API Secret.
  • Business User ID must be set on the connection. Trustpilot requires it on every invitation request as the x-business-user-id header.
If either field is missing, the component reports a validation error naming the missing field. Edit the connection, add the value, and re-test the connection. See Connecting to Trustpilot for how to create the connection.

Destination properties

  • Invitation template - the Trustpilot template that will be sent. The dropdown is populated from Trustpilot’s GET /v1/private/business-units/{businessUnitId}/templates endpoint, cached for one hour. Use the refresh control next to the dropdown to bypass the cache after you add or rename a template in Trustpilot.
  • Sender name - default sender display name on the invitation. Overridden per row when a senderName field is mapped.
  • Sender email - default sender address. Overridden per row when a senderEmail field is mapped. Must be a valid email address.
  • Reply-to - default reply-to address. Overridden per row when a replyTo field is mapped. Must be a valid email address.
  • Locale - default locale (for example en-US, de-DE). Overridden per row when a locale field is mapped.

Advanced options

  • Requests per second - throttle applied to the invitations API. Default is 5, matching Trustpilot’s documented application rate limit. Maximum is 100. The component uses a single reducer, so this value is the real request rate against Trustpilot.
  • Maximum failed records - the job fails once cumulative failed invitations exceed this value. Default is 0 (fail on the first failure). Set to -1 for unlimited failures.

Field mapping

The invitation payload is a fixed schema. Map input fields to Trustpilot invitation fields by exact name. Required fields (every invitation needs these): Optional fields (overrides per row): Product review fields (optional, and only for a combined service + product review invitation): These are named separately from templateId / redirectUri / preferredSendTime because Trustpilot nests a set of each under both the service review and the product review, so a single pipeline can drive them independently. The component raises a build-time error if any required field is missing from the mapping, or if a mapped field is not one of the fields listed in the tables above. Catching this up front avoids a run where a missing field fails every record. productReviewTemplateId and productReviewProducts must be mapped together, and mapping any other productReview* field without that pair is also a build-time error: without both, no product review invitation is built at all and the fields you did map would be dropped from every request with nothing to tell you.

Requesting product reviews

Map productReviewProducts to a column holding a JSON array of product objects, for example:
Each product accepts sku, name, mpn, brand, gtin, imageUrl, productUrl and productCategoryGoogleId. Trustpilot treats every one of these as optional and sets no limit on the number of products, so the component checks only that the value parses as a JSON array of objects and leaves the rest to Trustpilot. Supply at least enough to identify the product in your catalogue. Whether a row gets a product review is decided per row, by that row’s productReviewProducts value:
  • A row with products gets a combined invitation: a service review and a product review.
  • A row where the column is empty, or holds an empty array [], gets a service review only. This is the normal case for an order with nothing to review, and it is not an error, so a single pipeline can mix both kinds of row.
  • A row whose value is not valid JSON, or whose array holds an entry that is not an object (for example null), fails, is written to the errors CSV, and counts toward Maximum failed records.
Mapping productReviewProducts but leaving productReviewTemplateId empty for a given row fails that row at run time, because Trustpilot has no template to render the product review against. With the default Maximum failed records of 0, the first such row stops the job, and invitations already sent for earlier rows cannot be recalled.

Success and error tracking

The destination can write two CSVs to a cloud storage connection for reconciliation. Both are optional and configured independently.
  • Track successful records - writes a CSV of records that were accepted by Trustpilot, one row per invitation sent.
  • Track failed records - writes a CSV of records that were rejected, one row per failure, with the Trustpilot error message for each.
Supported storage connections for either output: Amazon S3, Google Cloud Storage, Azure Blob Storage, SFTP, and FTPS. If an invitation batch produces no rows for a given CSV (for example, a successful run with zero failures), the file is not written, so an empty invocation does not leave header-only files in your bucket.

Example: post-purchase invitations from a Snowflake query

A pipeline that reads yesterday’s completed orders from Snowflake and sends one Trustpilot invitation per order:
Map each aliased column to the Trustpilot field of the same name. Set Sender name, Sender email, Reply-to, and Invitation template on the component so every row inherits them. Leave senderName, senderEmail, replyTo, and templateId unmapped. Enable Track failed records to an S3 bucket so you can review rejected addresses after the run.

Trustpilot Source

Salesforce REST API Destination

HubSpot Destination

Destinations Overview

Last modified on October 27, 2026