Skip to main content
Question

Troubleshooting Mailchimp contact syncing issues with Zapier and Nexudus

  • February 25, 2026
  • 2 replies
  • 11 views

Hi everyone,

I’m running into a strange issue with Nexudus, Zapier and Mailchimp and I’m trying to understand where the logic is breaking.

Setup:

We have one Nexudus account managing multiple cities (Torino, Milano, Firenze).
Each city has its own Mailchimp audience.
Each city also has its own set of Zaps.

The logic is simple:

  • If a contract is created in Torino → contact goes to Torino Mailchimp list

  • If a contract is created in Milano → contact goes to Milano list

  • Same for Firenze

Each Zap includes a filter based on Home Space.

The problem:

When I create a contract in Torino, the contact is correctly added to the Torino Mailchimp list.
But the same contact is also being added to the Milano and Firenze Mailchimp lists.

This should not happen. Cities are supposed to be independent.

Important detail:
The Home Space fields are correctly set for each city, and filters are already in place inside the Zaps. Still, contracts created in one city are triggering Zaps for the others.

It almost looks like Nexudus is sending account-wide customer updates, and all Zaps connected to the same account are picking them up.

Any insight from someone who has handled multi-location setups would be really helpful.

Thanks.

2 replies

drtanvisachar
Forum|alt.badge.img+5
  • Zapier Solution Partner
  • February 25, 2026

Hey ​@IHSB 

What you’re seeing is consistent with the trigger being account wide, not city scoped.

In Nexudus, some Zapier triggers fire when a record is created or updated at the account level, and a contract creation can also update the related customer record. If each city Zap is watching the same Nexudus account and the trigger event is broad enough, all those Zaps can start, even if only one should pass the filter.

A few practical ways to fix it:

  • Check the exact Nexudus trigger event you’re using. If it is a customer or coworker update style trigger, it can fire for changes caused by a contract in any city. If Nexudus offers a contract specific trigger, use that instead so you are not relying on side effects.

  • Move the city filter as early as possible, directly on fields that come in on the trigger. If you are doing a lookup after the trigger to fetch Home Space, you can get surprises if the lookup returns current data that is shared or recently changed.

  • Consider replacing three separate Zaps with one Zap and use Paths for Torino, Milano, Firenze. That way one trigger runs once, then routes cleanly per city, instead of three triggers racing each other. This also reduces accidental duplicate behavior from multiple Zaps using the same trigger.

  • Use Zap History to confirm what field value each Zap saw at trigger time. It will usually reveal whether the trigger payload already contains the “wrong” Home Space, or if the mismatch happens later.

Dr. Tanvi Sachar
Monday Certified Partner, Monday Wizard


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • February 25, 2026

Hi ​@IHSB 

Check your Zap Run history to see the DATA IN/OUT for each step to help you trace the data flow and troubleshoot: https://zapier.com/app/history/

 

Help us have more info by posting screenshots showing:

  • how your Zap steps are outlined
  • how your Zap step filters/paths are configured
  • DATA IN for each filter/path from a Zap Run