Best answer

Acuity & Mailchimp integration

  • 21 September 2020
  • 5 replies

Because there was an issue integrating Mailchimp directily to my Acuity account (GDPR issues), I created a zap so that when new classes get booked, that person automatically gets subscribed to my mailing list in Mailchimp. There were no errors when I created the zap. I had a new member sign up the other day. But she wasn’t added to my Mailchimp. Help!


Best answer by Danvers 2 March 2021, 19:08

View original

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

5 replies

Userlevel 7
Badge +14


  1. Is the Zap ON?
    1. NOTE: Zap only work once turned ON for new data going forward.
  2. Check the Zapier Task History:
    1. Did the Zap trigger?
    2. Did the Zap trigger but error?

The zap was definitely ON and there were no issues. Just looked today and saw this (see screenshot). I looked at my mailing list and the new subscribers haven’t been added, and older subscribers haven’t had their tags updated within Mailchimp.

Userlevel 7
Badge +14

For each triggered Zap in the Zapier Task History you can click in to it to see the Task History Details, which will indicate what Step resulted in an error and the error message which will provide clues to help troubleshoot what may need to be fixed in the Zap step configuration to avoid those errors. (e.g. filter to make sure a data point exists, reformat a data point to a specific format, etc.)

Userlevel 7
Badge +11

Hi @Sarah Moves!

I wanted to check in with you on this one, since I don’t see a response to the last message that our Support team had sent you. Did you still need help here or did their reply to you help you resolve things? Please let us know :)

Userlevel 7
Badge +12

In case someone has a similar issue, here’s what our Support Team said when they looked at our logs:


Taking a look at the errors, it appears that Mailchimp encountered a server error while trying to add this subscriber:

This type of "Internal Server Error" (500) error can happen from time to time when a server is under heavy load, or if the data trying to be passed is too large or for a whole variety of other circumstances.

Since this happens on the other app's end, we can't see exactly what might be the specific problem here, but the good news is that these issues are usually short-lived, and are rarely due to an issue within your Zap. Generally, once they settle back down, failed tasks can be replayed in bulk from the Task History.

To find more info on replaying tasks, I'd recommend this help doc:


If you’re ever unsure about whether an error is temporary (like the one above) or something different, please don’t hesitate to get in touch with our Support Team using the Get Help form: