To use this integration, you will also need a Zapier account. For sign up and log in, visit Zapier.com. If you have questions regarding Zapier itself, please consult the Zapier help documentation page.

Quick steps

1. Get your API key from Trustmary.
2. In Zapier, select Trustmary and your other app as Trigger and Action, or vice versa.
3. Connect the apps (this is where you'll need the API key), and configure both steps in Zapier so that all necessary data is included.
4. Publish the Zap and start enjoying your integration!

Getting started

In this article, we will take a look at a simple way of integrating Trustmary with other apps by using Zapier. The article will cover the basics of setting up a Zapier automation (Zap), and can be applied to most similar integrations.

This is a general purpose article to give you an approximate idea on how integrations work through Zapier, so some things might appear different in your use case and selected apps. If you need instructions for a particular app, check out our other articles on integrations.

First, we'll connect Trustmary with Zapier, so the two can communicate. Once the connection is good to go, we'll move on to creating the actual automations; first with Trustmary as the receiver of data (action) and second with Trustmary as the sender (trigger).

If you already know what you need to do, go ahead and skip to the part of the guide that is useful to you.

Creating an API key in Trustmary

To get data moving from Trustmary to Zapier and vice versa, you will need to connect the two through our API. This can be done simply by grabbing the API key from Trustmary and inserting it into Zapier.

Start by going to the Settings menu by clicking the profile icon in the lower left corner in Trustmary.

Click on Developers in the menu, and find the API keys section. Click Add new to create another API key.

A window opens up where you can set a name for your API key and copy the API key itself.

You'll only see the key once, so it's best to copy it over somewhere safe for the next steps.

Zapier basics

In Zapier, the automations connecting one app to another are called Zaps. To create a Zap click the Create button on Zapier's dashboard, and select Zaps.

In the Zap editor, find your apps by describing your workflow to the AI, or select the apps manually by clicking the numbered steps in Zapier and searching for the correct apps in the menu.

The "Trigger" and "Action" steps are simply the starting point and the end point of the workflow. The Trigger always works as the start, and triggers the app when certain conditions (set by you) are met. The Action always follows the Trigger, and is the destination of the data that is brought in in the triggering step.

Moving data from other applications to Trustmary

As we're planning on sending data from another app (in this example, Pipedrive) to Trustmary, we'll need to select it as the Trigger, and Trustmary as the Action.

First you'll need to configure your Trigger step (your other app). The configuration varies depending on which app you choose, so we'll not go into it in this article. See the documentation for your trigger app for more information.

Then select Trustmary in the second step in the same way, and you can then move on to configuring Trustmary. This consists of three steps in which you'll select the desired action event, connect your Trustmary account, and determine what data goes where.

For the sake of this tutorial, we'll select Create/Update Contact as the action event, but you can do even more with the integration. See the full list of actions on our Zapier app page.

Once you've selected the action event, you'll need to connect your Trustmary account. This is where the API key from before makes an appearance: click Connect new account (if the account is not already connected) in the Zapier dialogue, and you should see a popup window asking for an API key. Paste it in the text field, and click Yes, continue to Trustmary to finish the connection. It should now show up without errors in the Zap editor.

The most important things in configuring the action is to have a valid email selected in the Contact Email field from the other app, and to which list or survey to add the contact in Trustmary (the Add to list field). You can also select different data, like for example the contact name, company name, or external IDs from other systems. You can also make custom fields for your contacts into which this data can be stored.

Once all data is set, move on to the next phase and test the integration with the data Zapier gives you. If the test returns no errors, you can double check on your contact list or survey to see if the contact has made it there.

Moving data from Trustmary to other applications

When sending data from Trustmary to some other application, the order of the apps is reversed; Trustmary is set as the Trigger, and your other application is set as the Action. Specific conditions in Trustmary trigger the workflow, and the data is then carried over to the other app.

In this tutorial we'll use the New Survey Answer trigger, but you can select whichever trigger suits your use case. See the full list of triggers on our Zapier app page.

Once you've selected the Trigger event, you'll need to connect your Trustmary account. This is where the API key from before makes an appearance: click Connect new account (if the account is not already connected) in the Zapier dialogue, and you should see a popup window asking for an API key. Paste it in the text field, and click Yes, continue to Trustmary to finish the connection. It should now show up without errors in the Zap editor.

After the event is selected, and your account connected, Continue onto the next step. This is where Zapier will fetch test data from your account. You can see the contents of the test data by clicking each answer.

After this configuration you're set on Trustmary's side. The next step is to select an app for the Action and configure it to receive the data brought in from Trustmary. This step is unique to each app, so please check your app's Zapier page for more information.

Updated on: 16/12/2025