Trustmary

Collect reviews and testimonials with Trustmary, importing contacts, pushing reviews, and reading surveys and lists. Agents ask for a review at the moment the customer is happiest and route the answers.

1 trigger 12 actions API key available

Trustmary website ↗ Platform Documentation ↗ Capability data verified 2026-08-02

On Survey Answer fires the moment a customer finishes a review survey

Agent calls Get Survey to map the answer keys in the payload back to the readable questions

Agent reads the score and checks whether the customer left a usable written testimonial

Agent looks up the account in the CRM to confirm the customer is cleared as a public reference

Agent calls Create Or Update Review with the published flag left off, so the testimonial exists as a draft nobody can see yet

Agent posts the draft quote, the score and the customer name into the customer marketing channel

A person confirms the wording and the consent before the testimonial goes live on the site

What This Integration Enables

Trustmary is the only service in this category where the customer is asked to say something in public with their name on it. Everything else here moves points, credits and prizes inside your own systems. A testimonial leaves your systems entirely: it carries a real person's words, often their photo and sometimes a hosted video, onto a page anyone can read. That asymmetry should drive how you build with it, because the cost of asking the wrong customer at the wrong moment is not a wasted API call, it is a public one-star review and an awkward conversation.

The connector handles both directions. Agents can create contacts with an external ID that keeps them linked to the matching CRM or ERP row, drop them onto contact lists so surveys reach whole groups, retrieve and delete contacts, and push reviews collected anywhere into Trustmary's store with an external ID that makes the call idempotent. They can read survey definitions to map answer keys back to questions, list contact lists including smart lists that Trustmary populates from survey answers, and manage the connections that import third-party reviews from services like Google, Capterra or Airbnb. The On Survey Answer trigger delivers the answer, the matched contact and the created review in real time.

Without FlowRunner

Review requests sent on a schedule Everyone gets asked at the same point in the month regardless of how their week went

Low scores discovered in a report An unhappy answer sits in a dashboard until someone runs the weekly export

Testimonials published from a queue A named quote goes onto the site without a second read for wording or consent

With FlowRunner

Requests timed to the relationship The ask goes out when the customer has just had a good outcome, not on the calendar

Low scores routed immediately A poor answer opens a support follow-up the same minute it arrives

Publication is a decision Reviews land as unpublished drafts and a person chooses what goes public

Use Case Scenarios

Answers routed by what they actually say

On Survey Answer fires. The agent calls Get Survey once to translate the answer keys into readable questions, then branches on the content. A high score with a substantive written comment becomes an unpublished review through Create Or Update Review and goes to the customer marketing channel for a publication decision. A low score does not become a review at all: it opens a support follow-up in Slack with the answer text and the account attached, so the person who owns that relationship hears about it while it is still fixable. The same trigger, two completely different paths, decided on what the customer said rather than on a schedule.

Asking at the moment the customer is happiest

Review requests work best right after a good outcome, and your product knows when those happen far better than a calendar does. When a renewal completes, an onboarding milestone is hit, or a support ticket closes with a positive resolution, the agent calls Create Contact with the customer's external ID and drops them straight onto the contact list tied to the right survey. The ask arrives while the experience is fresh. Customers whose accounts are flagged as unhappy or in escalation are never added to that list in the first place.

Reviews collected on your own site, pushed into one store

Plenty of teams collect testimonials through their own forms, in interviews, or in a shared document. Create Or Update Review takes those and puts them in Trustmary so they can appear in the same widgets and walls of love as survey-collected reviews. Supplying an external ID makes the call idempotent: the first run creates the review, later runs update it, and the response tells you which happened. That means a nightly sync from your own database is safe to re-run without producing duplicates.

Human-in-Loop Highlight

Publication is the gate. Create Or Update Review leaves a review unpublished until the published flag is set, and that design choice is the one worth building your flow around, because setting that flag puts a named human being's words, picture and hosted video onto a public page. It is not the kind of thing you quietly roll back if the customer's legal team objects, if the quote was pulled out of context, or if the person who gave it left the company last week. So the agent never sets the flag. It prepares the review as a draft, and asks: "Dana Reyes at Northwind scored 9 and wrote: 'The onboarding was the smoothest we have run in four years.' Draft saved unpublished. Northwind is cleared as a public reference in the CRM. Publish this quote as written, edit it, or hold for their approval first?" A person answers in the channel and the agent acts on the answer. Delete Contact deserves the same treatment, since it removes a contact by exact email address with no recovery. The agent does everything up to the point where a decision reaches the public, and then it stops and asks. That is what human-in-the-loop means when the next step has your customer's name on it.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

12 actions

Connection

Verify Connection Calls the Trustmary key test endpoint to confirm the configured API key is valid and reachable. Used as the first step of a flow, or when troubleshooting authorization failures, before running any operation that writes data.

Contacts and Lists

Create Contact Adds a contact so it can be invited to answer review and feedback surveys, optionally dropping it straight onto one or more contact lists. A valid email address is required. An external ID keeps the record linked to the matching row in your CRM or ERP, and custom fields carry over any extra attributes already configured in Trustmary.
Get Contacts Retrieves contacts, returning an array of contact objects, or a single contact when an email address is supplied. Returns at most 1000 per call, so larger sets are paged by increasing the offset in steps of 1000.
Delete Contact Deletes a contact by email address. Used to honour erasure requests or clean up records imported by mistake. The contact is identified solely by its address, so the address must match exactly.
List Contact Lists Returns the contact lists used to organise contacts and to send surveys to whole groups at once, each with its ID, type, contact count and source. A smart list is populated automatically by Trustmary from survey answers rather than by manual import.

Reviews

Create Or Update Review Pushes a review or testimonial into Trustmary so it can appear in widgets and walls of love. An external ID makes the call idempotent, creating the review the first time and updating it on later calls, with the response action field reporting which happened. Reviews stay unpublished until the published flag is set, and both a picture URL and a hosted video URL can be attached.

Surveys

List Surveys Returns the review and feedback surveys in the account, each with its ID, type, name, total answer count and timestamps, filterable by survey type to separate customer surveys from employee surveys and embedded widget forms. Up to 1000 are returned per call.
Get Survey Fetches one survey by ID with its full definition, including the question fields that make up the form. Used to map the answer keys arriving from the survey answer trigger back to readable questions.

Third-Party Review Connections

List Review Connections Returns every configured connection that imports third-party reviews, such as Google, Capterra or Airbnb listings, each reporting the source service, the review language, and the target ID and URL being tracked.
Create Review Connection Connects a third-party review page so its reviews are imported. The page is identified either by the same URL you would use to browse the reviews, or by the review service name together with its listing ID where that service requires it. The response contains the connection ID.
Update Review Connection Renames a review connection or changes its slug. Only the slug and title can be changed, and any property left blank is kept as it is, so a single field can be edited on its own. Addressed by either ID or current slug.
Delete Review Connection Removes a review connection so Trustmary stops importing reviews from that third-party listing. Addressed by either ID or slug.

Triggers

1 triggers

Event Triggers

On Survey Answer Fires in real time when a customer completes a review or feedback survey, and can be scoped to a single survey. The payload carries the answer, the matched contact and the created review, which is enough for an agent to branch immediately on what the customer said: draft a testimonial for review, or open a support follow-up on a poor score before it hardens into a public complaint. Trustmary documents no webhook signature, so deliveries are not cryptographically verified and downstream steps should treat the payload accordingly.

Frequently Asked Questions

What can FlowRunner do with Trustmary?

FlowRunner agents can run Verify Connection, Create Contact, and Get Contacts in Trustmary, plus 9 more actions.

Does connecting Trustmary to FlowRunner require OAuth?

No. Trustmary connects to FlowRunner with an API key, no OAuth flow required.

Can Trustmary trigger a FlowRunner workflow automatically?

Yes. Trustmary supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Trustmary

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us