Building Zaps

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

What You Need to Understand About Zaps

Trigger

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

For example, one Zap to add new Nexudus newsletter subscribers to a Mailchimp audience and a second Zap to add new susbcribers in the relevant Mailchimp audience to a Nexudus newsletter 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 Zapier will automatically perform for you.

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

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

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

Step 1. Creating the Zap

If you haven't done so already, make sure you've connected your Zapier account to Nexudus.

Once you have just go to zapier.com/app/zaps and click Create Zap.

Step 2. Selecting a Zap Trigger

Search for Nexudus and select the latest version currently available.

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

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 it trigger through a test user's data. This test trigger lets you know what user data can be pulled from Nexudus and communicated to another platform.

In our scenario, we want to collect the email and name of the newsletter susbcriber 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.

You can think of this user's data as dummy data that teaches both platform 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.

Select your Mailchimp account and click Continue.

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

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

We recommend you test your live Zap again by triggering the event you've defined. In this scenario, you would add a dummy newsletter subscriber in Nexudus and check the user is added to the relevant audience in Mailchimp.