Resources · Make integration

Trust Make integrationAutomate Trust with Make.

Can Make collect, sort and reuse your Trust testimonials without copy and paste? The Trust Make integration offers 14 modules: 1 trigger, 12 actions and 1 search. This guide connects your account and walks you through a first working scenario.

Try the Trust integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Trust Make integration let you automate?

The Trust Make integration links your Trust account to Make, a no-code tool where you build a scenario (the automation itself, a chain of steps). Each step is a module: one trigger, action or search of one app. Trust brings 14 of them, covering testimonials, contacts and media uploads.

React to every fresh review. Watch New Testimonials hands each new testimonial to the rest of the scenario as a bundle (one item passed from module to module). From there you can alert your team in another app, or fetch the full entry with Get a Testimonial Record.

Keep your contact list in step with your sales tools. When a deal closes elsewhere, Create a Contact adds the buyer to Trust, and Search Contacts checks first that the person is not already there. Update a Contact Record then corrects details instead of creating duplicates.

Feed Trust with media. Upload a Video, Upload a Short Video and Uploads an Image send files into Trust from wherever they land first.

Know the limits before you start. The Make documentation for Trust is short and flags itself as AI-generated, with a warning that it may contain errors, so check anything important directly with Trust. When a listed module falls short, Make an API Call reaches the rest of the Trust API with the same connection. For a wider view of the tool, read the Make review, and if you hesitate between tools, the n8n vs Make comparison lays out the criteria. Plan details sit on the Make pricing page.

Connect

How do you connect your Trust account to Make?

  1. 01

    Generate a key in Trust

    Log in to Trust and open the account settings, where API keys are managed. Generate a new key and copy it somewhere safe. Make needs this key, plus an active Trust account, before anything can run.

  2. 02

    Add a Trust module in Make

    In your scenario, add any Trust module and click Create a connection. A connection is your Trust account linked to Make once; every Trust module of the scenario reuses it afterwards.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name (optional, but handy with several accounts), paste the key you copied, then save. Make now lists what it can read in your Trust account.

First scenario

Your first scenario with Trust and Make

GoalWhen a new customer shows up in another app, Make adds that person as a contact in Trust.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app where your customers first appear, such as your shop or CRM, and choose its trigger.

  2. 02

    Add Create a Contact

    Click the + to the right of the first module, search for Trust and pick Create a Contact. Select the connection you made earlier, or click Create a connection.

  3. 03

    Map the customer details

    Fill the contact fields by mapping values from the first module: click a field, then pick the matching item from the previous step. No typing of fixed values, so each customer lands with their own details.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Open the bubble above each module to read the bundles it received, then check in Trust that the contact really appeared.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default for a new scenario) and switch the scenario on. Each module execution counts as one operation on your Make plan.

Triggers

What can start a Trust scenario?

1 module starts a scenario when something happens in Trust. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Trust as soon as it happens.

Trust1Watch New Testimonials

Watch New Testimonials

triggerIn the docs only

This trigger picks up testimonials that have arrived in Trust since the last check and passes each one down the scenario as its own bundle, ready for the next modules to use.

How it fires
it is listed as a scheduled trigger (a type deduced from its name). Make checks Trust on the scenario's schedule (the clock badge on the module), every 15 minutes by default, and 15 minutes is the shortest interval on the Free plan.
When to use it
any time a new review should set something in motion, like a message to your support team or a follow-up with the customer.
Watch out
the documentation gives no detail on this module, so run it once with a real testimonial and read the bundle before building on it.
Modules

What can Make do in Trust?

Trust gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Trust1

Create a Contact

ActionIn the docs only

Adds a new person to your Trust contacts from data that already lives in another tool, so nobody retypes names coming out of a sale or a signup.

When to use it
right after an order or a signed deal, to have the customer ready in Trust.
Watch out
place Search Contacts in front if the same person can come through twice.
Trust2

Create a Testimonial

ActionIn the docs only

Writes a testimonial into Trust from another source, which saves you pasting reviews collected elsewhere, for example from a survey form or an email reply.

When to use it
when praise reaches you outside Trust and you want it stored with the rest.
Watch out
the docs list no fields, so run it once and confirm how the entry looks in Trust.
Trust3

Delete a Contact

ActionIn the docs only

Removes one contact from Trust, which keeps your list clean when someone asks to be forgotten or leaves your customer base for good.

When to use it
after a deletion request logged in your helpdesk or CRM.
Watch out
a delete cannot be undone from Make, so test on a dummy contact and add a filter before switching it on.
Trust4

Delete a Testimonial

ActionIn the docs only

Takes a single testimonial out of Trust, handy when a customer withdraws consent or a review was posted by mistake and should disappear everywhere.

When to use it
when a removal request reaches your team through a form or a ticket.
Watch out
there is no undo here either; point it at one precise testimonial, never at a broad search result.
Trust5

Get a Contact

ActionIn the docs only

Fetches one known contact from Trust so later modules can use what Trust holds about that person, without you opening the dashboard.

When to use it
when an earlier module already gave you the contact's identifier and you need their details downstream.
Watch out
it reads one record; to find someone without an identifier, go through Search Contacts.
Trust6

Get a Testimonial Record

ActionIn the docs only

Pulls the full record of a single testimonial from Trust, so the next modules work with everything stored on it rather than a partial copy.

When to use it
after Watch New Testimonials, when you want to reread the entry before sharing it with your team.
Watch out
it needs the testimonial's identifier from a previous step, so map it rather than pasting a fixed value.
Trust7

Make an API Call

ActionIn the docs only

Opens the rest of the Trust API from your scenario, using the same connection as the other modules, so a missing module is not a dead end.

When to use it
when none of the other Trust modules covers the request you need.
Watch out
you write the request yourself, so keep Trust's API documentation open and test every call with Run once.
Trust8

Search Contacts

SearchIn the docs only

Looks through your Trust contacts and returns whatever matches: zero, one or several bundles. It answers the question "is this person already here?" before you create anything.

When to use it
in front of Create a Contact or Update a Contact Record, to avoid duplicates.
Watch out
several results mean the following modules run once per match, and each run uses operations.
Trust9

Update a Contact Record

ActionIn the docs only

Changes an existing contact in Trust, so details corrected in your CRM or billing tool also show up on the Trust side without manual edits.

When to use it
when a customer changes company or contact details in the tool you treat as the reference.
Watch out
you need the right contact first, usually from Search Contacts, or you risk editing the wrong person.
Trust10

Update a Testimonial Record

ActionIn the docs only

Edits a testimonial already stored in Trust, which lets a moderation step elsewhere fix or complete the entry without anyone logging in to Trust.

When to use it
when your team reviews testimonials in a shared tool and wants the result pushed back to Trust.
Watch out
map the testimonial's identifier from an earlier module; a fixed value would rewrite the same entry every run.
Trust11

Upload a Short Video

ActionIn the docs only

Sends a short video clip into Trust from a scenario, so a clip recorded or stored elsewhere reaches Trust without a manual download and upload.

When to use it
when your video testimonials are brief clips kept in another app.
Watch out
the documentation does not say where the line between short and regular video sits; test with a real clip, and on the Free plan files stay under 5 MB.
Trust12

Upload a Video

ActionIn the docs only

Moves a full video file into Trust, which spares you juggling downloads when customers send recorded testimonials through another channel.

When to use it
when the file is a complete recording rather than a short clip.
Watch out
the Free plan caps files at 5 MB and data transfer at 512 MB, which videos reach fast; check your plan before you rely on it.
Trust13

Uploads an Image

ActionIn the docs only

Places an image in Trust straight from the scenario, for instance a customer photo or a logo that belongs next to a testimonial.

When to use it
when pictures arrive through a form or a shared folder and belong in Trust.
Watch out
the module name really reads "Uploads an Image" in Make; search for it with that exact wording if it does not show up.
Need help

Need help automating Trust with Make?

A person reads every message.

FAQ

Trust and Make: common questions

01Is the Trust Make integration free?
Yes, on the Make side. Trust is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module execution. Your Trust subscription is a separate matter.
02What do you need to connect Trust to Make?
An active Trust account and an API key generated in it. Log in to Trust, open the account settings or the area where keys are managed, create a key and copy it. In Make, add a Trust module, click Create a connection, optionally name the connection, then paste the key. The connection is saved once and every Trust module in your scenarios can reuse it, so you only go through this when you add a new account.
03Does the Trust trigger in Make fire in real time?
No. Watch New Testimonials is listed as a scheduled trigger: Make checks Trust on the scenario's schedule rather than being alerted by Trust. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans go down to 1 minute. So a fresh testimonial reaches your scenario at the next check, not the second it is posted. The type comes from the module's listing and name, so confirm it by the clock badge on the module in Make.
04What if a Trust module is missing in Make?
Use Make an API Call. It is part of the Trust app in Make and reaches any endpoint of the Trust API with the connection you already set up, so you can cover what the other modules leave out. You write the request yourself, with the Trust API documentation beside you. Keep in mind that the Make documentation for Trust describes itself as AI-generated and may contain errors, so confirm important behavior with Trust before you build on it.
05Should you use Make or n8n for Trust?
It depends on what you need to check, and this page only has facts on the Make side. In Make, Trust comes with 14 modules, including a scheduled trigger, a contact search and Make an API Call for the rest of the API. Many apps also have an n8n node, but nothing here confirms one for Trust, so look it up before comparing. Then weigh the modules each tool offers for your case and how your team likes to build.
Same platform

Other docs you might need on this stack.

Browse all integrations