I’m using the “Subscribe Member with Custom Merge Tags” call to add new subscribers to a Mailchimp list. When the person is already subscribed I receive the following error message:
Hey @philip.ehl, I updated the plugin so that this call uses PUT instead of POST. Now you can subscribe or update a member with custom tags with this single call. Keep in mind that this update is non-backward compatible, so you’ll need to back to anywhere you’re using the action and update the settings.
It now requires the MD5 hash of the email address and body has different requirements. If the member doesn’t exist, you’d still need to provide email_address and status_if_new. If the member already exists, you can leave those out and use whatever parameters you need like you did before. The default body has a sample body for new subscriber.
Unfortunately, I cannot figure out why the “Subscribe or Update Member with Custom Merge Tags” function does not work for me. Sometimes I receive error messages, sometimes not, but it never updates the corresponding member.
Here is, how I set up the workflow when a user signs up to our website (he can potentially be in our mailing list beforehand):
First, I subscribe the member to the mailing list:
I have a similar situation. I want to check to see if my set-up is correct.
User signs up
User could already be on our list
So the plugin action will be:
“ Mailchimp Extended: Subscribe or Update Member ”
I add my data center# and list id
I add the Input’s email address is :lowercase :formatted as MD5 hash
Is this set up accurate?
So I ran a few tests with different users/emails. I got errors for the users/emails that were already on the list. The error message says “email@domain.com is already a list member. Use PUT to insert or update list members”.
You need to replace “email@domain.com” with the actual email (aka “input -email’s value”). And also replace all the merge field data. The “tag X” should be the name of your custom field and “tag x value” should be the actual values for that user.
See @kontakt.youare’s screenshot from earlier with their same setup filled in with their own values.
I have tried to set up the system beforehand as you suggested, but it didn’t work, why I was testing on some adjustments. After your message I tried to set it up like this again, but it just does not adjust the given merge fields. If I do not use the “Mailchimp Extended - Subscribe Member” workflow before using the “Mailchimp Extended - Subscribe or Update Member with Custom Merge Tags” one, the new user would not be added to my list at all. Here I receive the following message (if that might help to resolve the problem in general):
That specific error message is saying that the email value “should not be blank” which indicates you’re not sending an email address. If you’re positive that you’re inserting the dynamic email address properly in the action settings, run the action in preview mode with the debugger in step by step mode and see if you can find the disconnect there. Maybe you’re referencing a different input, or the input is getting cleared before getting to this action?
For example, I have some users who are subscribing to a newsletter (and so get tag “Newsletter”), others who are just signing up for the app and emails associated with the app (tag “App Signup”), and others who are agreeing to both Newsletter and App Signup.
Can you advise how to include this in the JSON code?
I’m having trouble using the “Mailchimp Extended - Subscribe or Update Member with Custom Merge Fields” function from the Mailchimp Extended plugin.
Here are 2 screenshots: one from my workflow and one is the error message I’m getting : “Unable to resolve DNS for…”… I’m not sure I to fix this… I feel like I’ve set up everything correctly…