---
title: "Building Zaps"
slug: "using-zapier"
updated: 2025-09-30T10:52:38Z
published: 2025-09-30T10:52:38Z
canonical: "help.nexudus.com/using-zapier"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.nexudus.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Building Zaps

{{variable.Zaps}} are just a set of actions that you define to tell {{variable.Nexudus}} and another platform what to do when a specific event is triggered.


## What You Need to Understand About Zaps

### Trigger 
Most {{variable.Zaps}} have a linear logic, meaning they usually work one way. You can easily achieve a two-way connection by setting up two separate {{variable.Zaps}}.

*For example, one {{variable.Zap}} will add new {{variable.Nexudus}} newsletter subscribers to a Mailchimp audience and a second {{variable.Zap}} will add new {{variable.subscribers}} in the relevant Mailchimp audience to a {{variable.Nexudus}} {{variable.subscriber}} list.*



### Actions 
Once the trigger starts the Zap, you need to define which actions both platforms need to perform. Each step or action equals an action that {{variable.Zapier}} will automatically perform for you.

{{variable.Zaps}} can be as simple as the example below or as complex as you'd like. Remember that more complex {{variable.Zaps}} also have greater error margins. 

We'll take newsletter {{variable.subscribers}} in {{variable.Nexudus}} and Mailchimp as a simple {{variable.Zap}} example to help you see the logic behind a {{variable.Zap}}. 

**Whenever a user signs up to one of your newsletters in {{variable.Nexudus}}, you want to add this user in a specific Mailchimp audience.**

### Step 1. Creating the {{variable.Zap}} 
If you haven't done so already, make sure you've [connected your Zapier account to Nexudus](/v3/docs/integrating-zapier){target="_blank"}. 

Once you've connected both platforms, just go to [zapier.com/app/zaps](https://zapier.com/app/zaps){target="_blank"} and click **Create {{variable.Zap}}**. 
 
###  Step 2. Selecting a {{variable.Zap}} Trigger
Search for {{variable.Nexudus}} and select the latest version currently available. 

![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%28794%29.png){height="" width=""}

Select the action that will trigger the Zap from the **Trigger event** drop-down. In our scenario, when a newsletter subscriber is added to Nexudus. 
 

![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%28797%29.png){height="" width=""}


:::(Info) (We recommend using **INSTANT** triggers over polling ones if both are available for the same trigger. )
:::

Click **Continue**, select your Nexudus account, and click **Continue** again. You can now click **Test Trigger** and move to the next step.

## Step 3. Testing Your Trigger 
Now that you have your trigger, Zapier will test the trigger using a test user's data. This test lets you know what user data can be pulled from Nexudus and communicated to other platforms. 

In our scenario, we want to collect the **email** and **name** of the newsletter {{variable.subscriber}} in Nexudus and populate the corresponding field in Mailchimp. To do that, we just need the test user's email to teach Zapier what information should be pulled from Nexudus and transferred to Mailchimp. 

![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%28798%29.png){height="" width=""}

You can think of this user's data as dummy data that teaches both platforms where to look for the information you're trying to transfer and where to put that information once it's collected. If the field or customer info you're trying to get from Nexudus isn't available within the trigger by default, you can always add a *Search for Members in Nexudus* action before adding your action on another platform. This additional action in Nexudus lets you tap into any field available in a customer's record. 


## Step 4. Defining an Action on Another Platform
Now that you have your test user data, you can define the relevant action on another platform. I
In our scenario, you should select the relevant action in Mailchimp and click **Continue**.

![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%28799%29.png){height="" width=""}

Select your Mailchimp account and click **Continue**. 

![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%28800%29.png){height="" width=""}

Now that you've selected the action, you can match the test user's data in {{variable.Nexudus}} to the matching fields in Mailchimp. 

![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%28808%29.png){height="" width=""}

Once you are done, test your {{variable.Zap}}. If your {{variable.Zap}} test returns an error, {{variable.Zapier}} will help you troubleshoot it. Once your {{variable.Zap}} is fully set up and the test is successful, you can turn it on. 

![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%28809%29.png){height="" width=""}

We recommend you test your live {{variable.Zap}} again by triggering the event you've defined. In this scenario, you would add a test newsletter subscriber in {{variable.Nexudus}} and check if the user has been added to the relevant audience in Mailchimp.
* * *

:::(Info) (You can  {{variable.ContactSupport}} for help if you have issues with your {{variable.Zaps}}.)
:::