My Zap isn't sending subscribers from my bot to Mailerlite.
I have created a Zap to connect my Bot (Aminos) submission to Mailer Lite. Zapier connects to my bot without a glitch and properly identifies the name and email I want to capture.
Same result with MailerLite, I am able to identify and select the subscriber group and the email field. When completing the test I get the following message:
“A Subscriber was sent to MailerLite about 1 second ago”
I proceed to publish
But I don’t get any subscriber information on MailerLite…
Any ideas why the subscriber data is not populating if zapier test is successful ?
Thank you,
Page 1 / 1
Hi @ScottJ
The returned data shows the ID of the Subscriber that was created or updated in MailerLite, which you can use to check.
That was the record I selected when designating the fields. Email Field, Name field, etc. Maybe I should start over with a new zap and select the sample as a real email and name.
After it said, the subscriber had been sent, I assumed that it did and then went to my bot to try it with a real name and email
@ScottJ
Post screenshots with how your Zap steps are configured.
Zap trigger step
MailerLite action step
I just updated the email to a real email. I will report back with the results.
Okay, so here is what is happening. When I “Test” it does send the information to Mailerlite. YEAH!!! BUT… If I do it from the bot, it never arrives.
@ScottJ
We would need to see screenshots with how your Zap trigger step is configured to have context.
Some Zap triggers are scheduled.
So, when retesting, the email does get into my mailerlite.
However, not when I use the bot. My thoughts are that settings are correct in this Zap. It is the bot that is malfunctioning.
posting video in a moment
Here is what I did, I started over as you can see, the zap reached over and I selected a subscriber:
The Loom video shows that the test worked. The email was delivered in test mode.
I then published it and tested again from the bot side and, it did not work.
At the end, I was looking in Mailerlite and was frustrated that the email did not show up and then, to my surprise I received an email notification.
Close to solving this, just need it to work in published mode from the bot side. www.GraceonFire.net is where the Jamie the bot lives.
@ScottJ
Some Zap triggers are scheduled which means those can take from 1-15 minutes to fire depending on your Zapier plan.
You can try reaching out to AminosSupport for guidance about troubleshooting their Zap app integration.
I appreciate all of your help on this. But, I guess.. this is not going to work. Tried and tried. Aminos doesn’t answer my support tickets, Mailerlite tells me to contact support at Zapier (can’t do that unless I am paying $29 a month).
According to the information below, everything is working. Problem is, it never reached my Mailerlite account. The list name is: Grace Empowered Living
DATA OUT:
data:
id:
58101231756772731
email:
questworx@gmail.com
status:
active
source:
manual
sent:
0
opens_count:
0
clicks_count:
0
open_rate:
0
click_rate:
0
ip_address:
71.229.129.248
subscribed_at:
2019-05-24 19:13:57
unsubscribed_at:
null
created_at:
2022-06-16 20:00:52
updated_at:
2023-12-17 17:49:51
fields:name:
scott
last_name:
Johnson
company:
Mr.
country:
US
city:
Littleton
phone:
null
state:
CO
z_i_p:
null
zip:
80128
woo_orders_count:
null
woo_total_spent:
null
woo_last_order:
null
groups:0:id:
103491816661190289
name:
Grace Empowered Living
active_count:
500
sent_count:
5
opens_count:
3
open_rate:float:
0.6
string:
60%
clicks_count:
1
click_rate:float:
0.2
string:
20%
unsubscribed_count:
0
unconfirmed_count:
0
bounced_count:
53
junk_count:
0
created_at:
2023-10-30 20:24:47
1
103491816675870359
@ScottJ
Make sure the email being used to test isn’t unsubscribed in MailerLite.
Can you show the DATA OUT from Step 2 in the Zap Run?
I’ve deleted that email inside of Mailerlite from previous use.
You should be able to use this ID to find the matching Subscriber in MailerLite.
id: 58101231756772731
The email never lands in MailerLite.
Hi there @ScottJ,
I did some digging into this, and it seems like this is a known bug with the MailerLite app where subscribers are not created despite successful run when using the “Create or Update Subscriber” action step.
I've added your email address as another affected member. That does a few things:
Bring this to the attention of the integration developers
Help track and prioritize fixes
Allows us to notify you via email if/when this is fixed
Unfortunately, I do not have an ETA, but I’ve added you to the list of users affected by this issue so we can let you know as soon as we have any updates.
Thank you for your patience and understanding.
Wow… Thank you so much Ken for resolving this and saving me from spending days on this. Now, I need to find a temporary solution. Just want to send out a single email response with a link to their requested download link.
Just to be upfront, Webhooks by Zapier is considered an advanced feature, so our support for it may be more limited. Not because we don't want to help, but because APIs can be so different and each request can be so unique. This makes it hard for us to know why the request may be receiving errors or not working as expected.
If you’d like help setting up Webhooks by Zapier. I’d recommend consulting with one of our certified Zapier Experts. You can reach them here: https://zapier.com/experts
Hopefully, this helps!
Hey @ScottJ
Marina here, reaching out as I've been in touch with the team at Mailerlite about the issue you were having with the Create/Update Subscriber action, where it appeared successful in your Zap history but the subscriber didn't actually get created/updated in Mailerlite.
They are currently troubleshooting the issue and having some trouble recreating this. Can you please confirm if this is still happening for you?
Hey folks,
I just wanted to pop by here to share that we’ve worked with MailerLite’s developers on this issue and it’s been resolved.
That said, if you’re still experiencing issues with subscribers not being created or updated despite them showing as successful in the Zap run, please do reach out to our Support team and they’ll be happy to investigate further.
