I am having trouble with this API. It initializes with no issue. But once I put it into a workflow, it says it’s having trouble reaching the server. Has anyone ever run into a problem like this for an API?
Can you share the api configuration?
Pretty sure your issue is related to bad JSON when you are sending the request. You probably didn’t use :formatted as json-safe as it should. Please share screenshot of API connector and your API call action
Is it possible that one group have empty data? (So you have 1 or 2 group instead of 3?)
Also, your screenshot show that you are using, maybe, the same expression for all three group. So I guess this could be duplicated ID in groups?
Normally, this is not the best way to format an array. But if your data are always the same, always three different groups… this could work.
1 Like
Yes the group id numbers are the same. I tried to only do one and I still get a connection issue. They are the same in the api connector also and I have no problem initializing.
ps. the extra groups are there for when I need to make a change to which group to add them in.
If you format as json-safe, you will need to remove double quotes in API connector because this will be added by this function.
In API connector, you don’t seem to have e+17… this normally mean this number is very long… this could lead to an issue in API. Do you have any API doc link?
So just to double check, I removed the extra groups from the api to double check and still get the connect error. Mailer Lite believe its on my end but I do not think it is.
Ya I noticed the e+17 too but when I tried to make it a text data, I get an error 
.
Here is the api doc: Subscribers | MailerLite developers website
To be honest, because the api isnt working it made me use Zapier for the connection. It seems like I will just have to use them if I cannot figure out why there is a connection issue…even though I am able to initialize the api call 
.
You shouldn’t have to use Zapier
Pretty sur your issue is the group ID formatting.
This is a text, as it’s an ID and should be formatted as it. In your screenshot, this is a number for sure. I don’t know how you set this on your side, but the problem is there.