Misleading content please update said in free but not in free

Hi @gtarafdarr ,

Thanks for the feedback.

As with most of our integrations, some triggers and actions are available in the free version and some are in Pro. Have a look at https://automatorplugin.com/integration/affiliatewp/. As you’ll see there, these 4 triggers are available, unrestricted, in the free version:

A new affiliate is approved
A new affiliate is awaiting approval
A user becomes an affiliate
An affiliate makes a referral of a specific type

Your second screenshot shows the integration as “Pro” because you selected an “Everyone” recipe. “Everyone” recipes that can either create or map to an existing user do unfortunately require Pro. If you choose Logged In as the type instead you will see the triggers available to free users. Your screenshot of the readme is correct, elements of the integration are completely unlocked for free plugin users, it’s the recipe type selection that means you have restrictions here.

Credits only apply to a handful of non-WordPress integrations that require you to connect an account, like Google Sheets, Slack and Facebook. See https://automatorplugin.com/knowledge-base/what-are-credits/ for more information.

The credit system was just added to the last release to give free plugin users a way to try some of the non-WordPress API integrations (not all Pro triggers, actions and features–the code for all of those is still in the Pro plugin). We tried to make this clear in our Knowledge Base and inside the plugin, but I’ll see what we can do to make this more obvious in the readme as well (we can better identify that what’s available in free is for logged in recipes only). If you have other suggestions about how we can make this more obvious we’re definitely open to feedback.

Thanks for your prompt reply with proper detailing. I love the way how you have explained that. If possible, add a section to show what is available for free in the logged-in user group or for everyone.

BTW, after your proper guideline, I’ve tried it. But the Action is not working properly. Every time it’s caught by API error. Can you please help me?
https://ibb.co/ZNDB5t2

Thanks again.

Hi @gtarafdarr ,

For the first point (about not being clear enough with Everything recipes), we’ll update the readme this week and we’re thinking about adding a notice above Everyone trigger recipes that says something like, “Missing a trigger or integration you expected? Try a Logged In recipe type instead.” What do you think?

As for the error you reported, there could be a few causes (we assume this is Mailchimp, but a screenshot of the recipe would REALLY help); our developers suggested the following:
– Data may be missing from the trigger that Mailchimp requires; adding a Send Email action that outputs token data might help confirm this.
– Confirm the audience/tag still exist in Mailchimp, removing either that the recipe has a dependency on would cause this error
– Try again, yesterday afternoon we made a small change on our side for Mailchimp, there’s a slim chance you could have been affected.

The recipe screenshot would definitely help; we can see if we can reproduce your issue.

Hello There, sorry for the late reply, I’m getting the same issue, I’ve updated the plugin too,
SS: https://ibb.co/YWd8Vhw

Sorry @gtarafdarr , I ran it by our team but it could be a number of things causing it. Were you able to review our previous suggestions to confirm that on the Mailchimp side there’s no tag missing, list missing, user missing? Without signing in to your Mailchimp account our ability to check what is failing is limited, the error is returned by MailChimp and indicates that something is unavailable that’s in your recipe. Maybe you could also send us a screenshot of the recipe with as much expanded as possible?

I’m using a free account, I’ve only one list SS: https://ibb.co/Cvp2LLx
One tag: https://ibb.co/gVyvJWP
Here is an audience to that list: https://ibb.co/vdm9Cs7
Unfortunately, I can’t give you access to that account, as I’ve another confidential profile is connected.
Looking forward to solving the issue.

Hi @gtarafdarr , sorry about the delay. We did a fair bit of testing to understand why you were seeing this.

One of our testers was able to recreate what you describe when the associated user was not part of the Mailchimp audience. Once the user was added to an audience, everything worked as expected.

Can you confirm that your test user is also a member of the Mailchimp audience? Our tester noted that the email address in your action log didn’t match the user in the Mailchimp audience.

Let us know if this doesn’t explain your issue.

Thanks for replying back to me. Umm, wait a min. Maybe I’m missing something. Let me explain again.

I want to send the activated affiliate’s email to MailChimp by using your recipe.

Maybe it’s not possible, right?

As you have mentioned I need the same user on that list.

Hi @gtarafdarr , our team was just validating that you could just use a recipe with 2 actions: add a user to an audience, wait a minute, add a tag to a user, which should work around the problem you experienced. Certainly we expect that Automator can add new contacts to Mailchimp.

During follow-up testing we hit an issue on our side, a developer is investigating, but I didn’t want to hold up a reply before the weekend. You could try the above for now.

Thanks a lot, your solution works great.
https://ibb.co/vkMHLFN
I got the desired result.

Love your support.

I got my solution. Thanks.

That’s great, and thanks so much for the review! Enjoy your weekend.

Thank you.

BTW please update your documentation according to your solution. I follow the guideline like your knowledge. https://automatorplugin.com/knowledge-base/mailchimp/

You have mentioned that we can add a new audience to the list. But your SS is showing the option of adding Tag only, https://ibb.co/5FmqCJ4. I think that’s why I repeat my mistakes. I was not sure enough about having the multiple actions set up process.

If possible, add the 1000 credits expiry process broadly too to the Mailchimp section as well.

Thanks again, take care of yourself too. Happy Weekend

Thanks! At the top of the page I changed the reference to “This integration requires Uncanny Automator Pro” (outdated as of 3.1) to it requiring Pro for unlimited use and that free users can use credits.

I also added a note later in the article about the audience limitations, but I may have someone from the team review it again next week as well.

Thanks for the feedback!

Thanks for the quick action. I will try to create a tutorial video on it. I think many of us looking for a solution as this is not available in the core plugin. And sorry to say, they are paid one, and that essential option is missing from their plugin. It’s absurd. BTW thanks a lot, for your support to the community. Only for that having zero knowledge of coding I’m able to handle the whole thing. Great work. And sorry for my previous threads.