Ellipse Gradient for Header

Trustpilot Integration Guide

Connect Trustpilot business profiles, reviews, invitations, and consumer data with enterprise applications through REST APIs, selected webhook events, and Martini workflows.

Trustpilot integration options at a glance

Trustpilot provides REST APIs for Business Units, Service Reviews, Product Reviews, Review Invitations, Consumers, and related business data. Applications authenticate with API keys or OAuth 2.0 bearer access tokens, subject to the relevant API product and account permissions. Trustpilot also supports webhook-style notifications for selected events, although coverage is limited and should be confirmed for each account. Martini can consume these APIs, receive supported callbacks, schedule incremental synchronization, paginate through review data, and expose normalized REST endpoints to downstream applications. Where webhook coverage is insufficient, Martini workflows can poll Trustpilot, checkpoint progress, apply transformations, and handle throttling and retries.

Integration pointSupported by Trustpilot?Common use casesHow Martini supports it
REST APIsYesRetrieve Business Units, Service Reviews, Product Reviews, Consumers, and related business data; create or manage Review Invitations where the account has access. API responses can be filtered and paginated.Martini can consume Trustpilot REST endpoints in workflows, map responses, apply business rules, expose normalized APIs, and write results to downstream applications or databases.
Webhooks and outbound callbacksLimitedReceive webhook-style notifications for selected Trustpilot events or API products. Coverage is not universal across all review and business-object changes.Martini can expose a webhook-facing API or workflow trigger, validate the callback, retrieve the current Trustpilot object, and process it asynchronously. Polling can cover unsupported events.
AuthenticationYesAuthenticate API requests with API keys or OAuth 2.0 bearer access tokens, subject to Trustpilot API product, account, and permission requirements.Martini can store credentials in protected environment configuration or secrets and use authenticated HTTP requests in workflows without embedding credentials in mappings.
Scheduled synchronizationYesPoll paginated Trustpilot endpoints when webhook coverage is insufficient, using incremental filters, timestamps, cursors, or other documented mechanisms where available.Martini scheduler-triggered workflows can maintain checkpoints, process overlap windows, handle throttling, and reconcile downstream records.
Pagination and incremental retrievalYesRetrieve review and business-data result sets across multiple pages and synchronize new or updated objects without restarting the full dataset.Martini can persist page, cursor, timestamp, or identifier checkpoints after successful processing and use stable Trustpilot identifiers for upserts.
Bulk or asynchronous APIsNot confirmedA generally available bulk or asynchronous API covering all Trustpilot objects was not confirmed. Large jobs should use paginated REST requests and controlled processing.Martini can orchestrate batches over REST endpoints, but the workflow should not assume a Trustpilot bulk API or asynchronous job interface.
File and attachment APIsNot confirmedReviews may contain review-related media or content, but a general-purpose Trustpilot file or attachment API was not confirmed.Martini can process fields returned by confirmed endpoints, but attachment retrieval should be implemented only after verifying the applicable Trustpilot API.
Database or analytics accessNoNo direct Trustpilot database, JDBC interface, or general-purpose analytics database access was confirmed.Martini can consume Trustpilot APIs and write normalized data to a supported SQL database or reporting platform on the target side.

How Trustpilot exposes data and business events

Trustpilot REST APIs

Trustpilot documents REST APIs for Business Units, Service Reviews, Product Reviews, Review Invitations, Consumers, and related business data. Operations and fields depend on the API product, account plan, and granted permissions; list responses may require pagination.

Martini implementation pattern

Martini implementation pattern: Martini workflows authenticate to Trustpilot with an API key or OAuth 2.0 bearer token, retrieve the required resources, apply pagination and incremental checkpoints, map the response into a canonical model, and write or expose the result to downstream systems.

Implementation sequence

Authenticate the Trustpilot API request
Retrieve the required Business Units, reviews, invitations, or Consumers
Follow pagination and apply an incremental checkpoint
Map Trustpilot fields to the target model
Apply validation, routing, and privacy rules
Upsert the result and persist processing status

Trustpilot Webhooks

Trustpilot supports webhook-style notifications for selected events or API products. Coverage is limited, so integrations must confirm which events are enabled for the account and should not treat callbacks as a complete notification stream for every object.

Martini implementation pattern

Martini implementation pattern: Martini exposes a webhook-facing API or workflow endpoint, validates the callback according to the configured Trustpilot mechanism, acknowledges promptly, and retrieves the current object through the REST API before applying business processing. Scheduled reconciliation covers unsupported or missed events.

Implementation sequence

Receive the Trustpilot callback
Validate the callback and configured security requirements
Acknowledge the notification promptly
Retrieve the current Trustpilot object
Apply rating, status, and content-based routing
Create or update the downstream record with duplicate protection

Scheduled Trustpilot Synchronization

Scheduled polling is appropriate when webhook coverage is unavailable or when completeness requires periodic reconciliation. Trustpilot review and business-data endpoints can be processed through paginated REST requests, although a general bulk API was not confirmed.

Martini implementation pattern

Martini implementation pattern: A scheduler-triggered workflow uses a stored timestamp, cursor, page, or identifier checkpoint, retrieves an overlap window of changed data, processes each page, and advances the checkpoint only after downstream writes succeed.

Implementation sequence

Start the scheduled synchronization workflow
Load the last successful checkpoint
Retrieve the next Trustpilot result page
Transform and upsert each object
Handle throttling and transient failures
Advance the checkpoint after successful processing

Common Trustpilot integration patterns

Pattern 1: Synchronize Trustpilot reviews to customer systems

When to use this pattern

Use this pattern when customer-service, account, or lifecycle teams need Service Reviews and Product Reviews in Salesforce, HubSpot, Microsoft Dynamics 365, or another customer application. It supports scheduled retrieval and can also begin from a supported Trustpilot notification.

Integration direction
Trustpilot
Martini
Salesforce
Example Mapping
Trustpilot FieldCanonical FieldTarget Field
reviewIdexternalReviewIdTrustpilot_Review_ID__c
starsratingRating__c
contentreviewTextReview_Body__c
createdAtreviewCreatedAtReview_Created_At__c
Martini implementation pattern

A Martini workflow retrieves the current review, resolves the related Business Unit or Consumer when permitted, normalizes text and timestamps, and applies rules such as routing ratings below a threshold to a customer-success queue. It upserts by the Trustpilot review identifier and records failures for controlled retry rather than creating duplicates.

Martini capabilities used
  • workflows
  • API consumption
  • scheduling
  • data mapping
  • business rules
  • error handling

Pattern 2: Send review invitations after completed orders

When to use this pattern

Use this pattern when an order, fulfillment, or service-completion event in Shopify, Adobe Commerce, NetSuite, Salesforce, or another source should initiate a Trustpilot Review Invitation. The flow must prevent duplicate invitations during retries.

Integration direction
Shopify
Martini
Trustpilot
Example Mapping
Trustpilot FieldCanonical FieldTarget Field
customer.emailconsumerEmailTrustpilot consumer email
order.idtransactionReferenceTrustpilot reference
items[].skuproductReferenceTrustpilot product data
order.completedAtqualificationTimeInvitation eligibility rule
Martini implementation pattern

Martini exposes an API or receives a source event, validates the customer and transaction, checks an internal idempotency key based on order and invitation purpose, and calls the Trustpilot invitation API using the required authentication. The workflow stores the invitation result and retries transient failures without resubmitting completed invitations.

Martini capabilities used
  • APIs
  • workflows
  • data mapping
  • validation
  • business rules
  • secrets management
  • error handling

Pattern 3: Route low-rating reviews to service management

When to use this pattern

Use this pattern when negative Trustpilot feedback should create or update work in Zendesk or ServiceNow. A supported webhook can reduce latency, while scheduled reconciliation provides completeness for events that are not covered.

Integration direction
Trustpilot
Martini
ServiceNow
Example Mapping
Trustpilot FieldCanonical FieldTarget Field
reviewIdexternalCaseKeyu_trustpilot_review_id
starsseverityInputpriority
contentcustomerFeedbackdescription
businessUnitNamebusinessContextaccount
Martini implementation pattern

Martini receives a selected Trustpilot callback or discovers the review during polling, retrieves the complete review from Trustpilot, evaluates rating and content-routing rules, and creates or updates the target ticket. The workflow uses the review identifier for idempotency, records correlation details, and retries transient target-system failures.

Martini capabilities used
  • webhook receiving
  • API consumption
  • workflow orchestration
  • conditional routing
  • data mapping
  • retry handling

Pattern 4: Synchronize Trustpilot reviews to a reporting database

When to use this pattern

Use this pattern when reporting teams need a durable, normalized history of reviews, invitations, Business Units, or reconciliation metrics. It is suitable for incremental synchronization where the relevant Trustpilot endpoint exposes timestamps, cursors, or other change indicators.

Integration direction
Trustpilot
Martini
PostgreSQL
Example Mapping
Trustpilot FieldCanonical FieldTarget Field
reviewIdtrustpilotReviewIdtrustpilot_review_id
updatedAtsourceUpdatedAtsource_updated_at
statusreviewStatusstatus
starsratingrating
Martini implementation pattern

A scheduled Martini workflow loads the last checkpoint, pages through Trustpilot results with a small overlap window, transforms each response into a stable relational model, and performs idempotent upserts. It applies rate-limit backoff, persists progress only after successful database writes, and runs periodic reconciliation for edits or state changes exposed by the API.

Martini capabilities used
  • scheduling
  • API consumption
  • pagination orchestration
  • data mapping
  • SQL database integration
  • checkpointing
  • error handling

Applications commonly integrated with Trustpilot

Trustpilot data can be connected to customer, commerce, service-management, and enterprise-system workflows. The following are realistic architecture patterns; exact implementation depends on API access, permissions, and the capabilities of each application.

Application Scenario Direction Martini Pattern
Salesforce Attach Service Reviews to Accounts and Contacts, route low-rating reviews to account teams, and initiate invitations after qualifying customer events. Trustpilot → Martini → Salesforce Use a scheduled or event-driven workflow to retrieve reviews, resolve customer identifiers, map ratings and review content to Salesforce objects, and upsert using the Trustpilot review identifier. A separate Martini API can accept invitation requests from Salesforce and call Trustpilot.
HubSpot Relate review activity to contact and lifecycle data and trigger review invitations after completed customer interactions. Trustpilot → Martini → HubSpot Consume Trustpilot REST responses and HubSpot APIs in a workflow, normalize consumer and review fields, apply invitation eligibility rules, and maintain external identifiers to prevent duplicate contacts or invitations.
Zendesk Create or update support tickets when reviews indicate dissatisfaction or require customer-service follow-up. Trustpilot → Martini → Zendesk Receive a supported Trustpilot callback or poll for new reviews, retrieve the complete review, evaluate rating and content-routing rules, and create or update a Zendesk ticket with retry and duplicate-detection logic.
ServiceNow Route negative reviews into customer-service or incident-management processes with ownership, escalation, and auditability. Trustpilot → Martini → ServiceNow Use a Martini webhook API or scheduled workflow to obtain the current Trustpilot object, transform review and Business Unit data into ServiceNow fields, and upsert cases or tasks using a stable external key.
Shopify Use order or customer events to request Review Invitations and associate Product Reviews with catalog items where the available APIs and permissions support it. Shopify → Martini → Trustpilot Expose a Martini API for qualifying Shopify order events, validate customer and transaction data, apply invitation idempotency, and invoke Trustpilot. A separate synchronization workflow can map Product Reviews to Shopify catalog references where supported.
Adobe Commerce Request reviews after completed orders and connect Product Reviews to catalog or order data. Adobe Commerce → Martini → Trustpilot Consume Adobe Commerce order events or API data, transform customer, order, and product information, and call the Trustpilot invitation API. Store invitation identifiers and process review updates through a separate paginated workflow.
Microsoft Dynamics 365 Enrich customer and case records with review information and send invitations after sales or service events. Trustpilot → Martini → Microsoft Dynamics 365 Orchestrate Trustpilot and Dynamics 365 API calls, match Consumers to contacts using controlled identifiers, map review status and ratings, and route low scores according to configurable business rules.
NetSuite Use fulfilled orders or customer records to initiate Review Invitations and export review metrics for operational reporting. NetSuite → Martini → Trustpilot Schedule or trigger a Martini workflow from NetSuite data, validate invitation eligibility, call Trustpilot with OAuth or API-key authentication as applicable, and write normalized review metrics to a reporting destination.

How to build a Trustpilot integration in Martini

Objective

Configure Trustpilot authentication and the target-system credentials without embedding secrets in workflows.

Instructions in Martini

  • Choose API-key or OAuth 2.0 authentication according to the Trustpilot API product and account permissions.
  • Store API keys, OAuth client secrets, and tokens in protected Martini environment configuration or secrets management.
  • Confirm HTTPS endpoints, granted permissions, and the minimum required data access.

Objective

Select an event-driven or scheduled entry point based on Trustpilot webhook coverage and synchronization requirements.

Instructions in Martini

  • Use a webhook-facing Martini API or workflow trigger for supported Trustpilot events.
  • Use a scheduler for polling, incremental synchronization, and reconciliation where event coverage is limited.
  • Define the initial scope, overlap window, and checkpoint strategy.

Objective

Obtain the complete Trustpilot object rather than relying only on a notification payload.

Instructions in Martini

  • Call the appropriate Trustpilot REST endpoint for Business Units, reviews, invitations, Consumers, or Locations.
  • Follow pagination and apply documented filters or incremental parameters where available.
  • Persist progress only after the downstream processing for the page succeeds.

Objective

Coordinate validation, enrichment, routing, target calls, and persistence in a maintainable Martini workflow.

Instructions in Martini

  • Validate required identifiers, rating values, timestamps, and customer fields.
  • Resolve related Business Units, Consumers, or product references where the API and permissions allow.
  • Separate notification handling from longer-running processing when callbacks need rapid acknowledgement.

Objective

Convert Trustpilot responses into the canonical and target-system models.

Instructions in Martini

  • Map stable Trustpilot identifiers, ratings, review content, statuses, and timestamps.
  • Preserve Unicode and user-generated content while applying target-specific escaping and field limits.
  • Normalize optional and localized fields without assuming every account returns the same schema.

Objective

Implement invitation eligibility, rating-based routing, privacy, and duplicate-prevention rules.

Instructions in Martini

  • Use an idempotency key for Review Invitations based on the order, Consumer, and invitation purpose.
  • Route low-rating reviews according to configurable customer-service rules.
  • Limit stored personal data to the integration need and define retention behavior.

Common Trustpilot data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
Business UnitsRepresent the company or business profile reviewed on Trustpilot and provide business-level identity and profile data.Salesforce, HubSpot, ServiceNow, Microsoft Dynamics 365, reporting databasesMartini retrieves Business Units through REST APIs, maps profile and identifier fields, and upserts them using stable external identifiers.
Service ReviewsCapture customer feedback about the overall experience with a business, including rating, text, status, and timestamps where available.Salesforce, Zendesk, ServiceNow, Microsoft Dynamics 365, analytics platformsMartini polls or retrieves reviews after notifications, normalizes user-generated content, applies rating-based routing, and upserts by Trustpilot review identifier.
Product ReviewsAssociate customer feedback with a specific product or catalog item.Shopify, Adobe Commerce, product catalogs, reporting databasesMartini maps product and review identifiers, preserves rating and content fields, and sends records to commerce or reporting systems where the relevant APIs support the association.
Review InvitationsRequest that a customer submit a service or product review after a qualifying transaction or service event.Shopify, Adobe Commerce, NetSuite, Salesforce, HubSpotMartini receives order or service-completion data, validates eligibility, applies idempotency controls, and calls the Trustpilot invitation API when permissions allow.
ConsumersRepresent customer or reviewer information associated with invitations and reviews.Salesforce, HubSpot, Microsoft Dynamics 365, customer-service applicationsMartini maps only the required consumer fields, protects personal data, matches contacts using controlled identifiers, and applies retention and privacy rules.
LocationsRepresent business locations or location-related Business Unit data where supported by the applicable Trustpilot API.Salesforce, ServiceNow, Microsoft Dynamics 365, reporting systemsMartini retrieves supported location fields, transforms them into the target location model, and handles optional or account-specific fields conservatively.

Authentication and security considerations

Authentication options

Trustpilot documents API-key authentication and OAuth 2.0 bearer access tokens, depending on the API product, account, and granted permissions. Exact scopes should be confirmed before implementation.

Credential protection

Store Trustpilot API keys, OAuth client secrets, and access tokens in Martini environment configuration or secrets management. Do not embed credentials in workflows, mappings, or source payloads.

Data protection

Consumer names, email addresses, transaction references, and review content may be personal or sensitive data. Use HTTPS, least-privilege permissions, limited field storage, and defined retention and deletion policies.

Operational considerations for Trustpilot integrations

Rate limits and pagination

Confirm limits for the applicable Trustpilot API and account. Process paginated responses with controlled concurrency, exponential backoff for throttling, and checkpoints that advance only after successful downstream processing.

Idempotency and reconciliation

Use stable Trustpilot review and invitation identifiers for upserts. Invitation workflows should use an internal idempotency key. Periodic reconciliation is recommended because webhook coverage is limited and callbacks may be retried or delivered more than once.

Schema and content handling

Review content can contain Unicode, links, HTML-like text, localized fields, and optional properties. Preserve identifiers, ratings, timestamps, and status values while applying safe target-system escaping and validation.

Testing and operations

Test authentication, permissions, pagination, throttling, duplicate callbacks, edited or hidden reviews, and downstream failures. Monitor workflow logs and define retry, dead-letter, and manual-reconciliation procedures.

Why use Martini instead of scripts or point-to-point integrations?

Orchestration instead of isolated scripts

Martini coordinates Trustpilot API calls, webhook handling, scheduled polling, target-system writes, validation, and business rules in reusable workflows rather than distributing logic across one-off scripts.

Maintainable data transformation

Mappings and transformations can normalize reviews, invitations, Consumers, and Business Units for different applications while preserving source identifiers and audit fields.

Reliable enterprise processing

Martini supports controlled retries, checkpointing, idempotent upserts, secure environment configuration, and operational monitoring. This helps integrations remain dependable as destinations, rules, and Trustpilot API requirements evolve.

Reusable APIs

Martini can expose an internal REST API façade for invitation requests or normalized Trustpilot data, allowing enterprise applications to use a controlled contract without each application implementing Trustpilot authentication and pagination independently.

Frequently asked questions

How can Trustpilot be integrated with enterprise systems?

Trustpilot can be integrated through its REST APIs for Business Units, Service Reviews, Product Reviews, Review Invitations, Consumers, and related business data. Applications can authenticate with API keys or OAuth 2.0, use selected webhook-style notifications where available, and use scheduled REST polling with pagination and checkpoints when event coverage is insufficient.

Can Martini integrate with Trustpilot?

Yes. Martini can consume Trustpilot REST APIs, receive supported webhook callbacks, run scheduled synchronization workflows, map and transform Trustpilot data, and expose normalized APIs for downstream applications. A dedicated native Martini Trustpilot connector is not documented in the supplied context.

Do I need a connector to integrate Trustpilot with Martini?

No. A dedicated Trustpilot connector is not required. Martini can integrate using Trustpilot's confirmed native mechanisms, including REST APIs, API-key or OAuth 2.0 authentication, selected webhook callbacks, and scheduled workflows for polling and reconciliation.

Is there any extra Lonti cost to integrate Trustpilot with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Trustpilot. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Trustpilot, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.

Which Trustpilot integration methods should enterprises use?

REST APIs are the primary method for retrieving reviews, Business Units, invitations, Consumers, and related data. Selected Trustpilot webhook-style notifications can support event-driven processing, but coverage must be confirmed for the account and API product. Scheduled REST synchronization remains important for polling and reconciliation.

Can Martini receive Trustpilot events or webhooks?

Martini can receive Trustpilot webhook-style callbacks through a webhook-facing API or workflow trigger when the relevant event is supported and enabled. Coverage is limited rather than universal, so the callback should be treated as a notification and followed by a REST retrieval of the current object. Scheduled polling can cover unsupported events.

How does Trustpilot data synchronization work with Martini?

A Martini workflow can retrieve paginated Trustpilot data, apply an incremental timestamp, cursor, page, or identifier checkpoint where supported, and upsert downstream records using stable Trustpilot identifiers. Overlap windows, periodic reconciliation, and controlled retries help account for late updates, duplicate callbacks, and changes to review status.

How are Trustpilot errors, retries, and duplicate invitations handled?

Martini workflows can validate inputs, detect throttling such as HTTP 429 responses, apply bounded exponential backoff, and persist progress after successful writes. Review and invitation identifiers should be used as external keys, while invitation requests should use an internal idempotency key to prevent duplicate customer requests during retries.

Related Martini documentation

API Workflows

Data Processing

Security Operations

API Exposure

Connect Trustpilot with your enterprise systems

Use Martini to integrate Trustpilot reviews, invitations, business data, and selected event notifications with the applications and databases that run your customer experience processes.

EXPLORE MARTINI
BOOK A DEMO