How to Prevent Pipedream from Sending a Status to Mailerlite or Send "Unconfirmed" Instead of "Active" or "Unsubscribed"?

This topic was automatically generated from Slack. You can find the original thread here.

Mailerlite integration. Hi all. I am struggling with the Mailerlite update_subscriber integration. I am firing this integration seconds after creating the subscriber. When the automation runs, it is updating the subscriber with the status “active”, but this happens before the subscriber has confirmed their email address. Aside from issues around consent, this is causing an problems at Mailerlite’s end that prevent the subscriber from being added correctly to the desired email sequence. Pipedream uses the key “type” for subscriber status, which defaults to “active”. The only other option is “unsubscribed”. Both of these options will prevent the desired behaviour from happening. Does anybody know how to prevent Pipedream from sending a status at all to Mailerlite? Failing that, does anybody know how to send “unconfirmed” instead of active or unsubscribed? TIA

Hi , I can reproduce your issue.

I think this might be a bug, I’ll check with our component dev and get back to you

Here’s the ticket that you can track the progress of our fix: [BUG] Mailerlite - Update Subscriber action always set subscriber type to active · Issue #15899 · PipedreamHQ/pipedream · GitHub

We’ve added this to our prioritized backlog. Our component dev will take a look into it soon

That’s great! Thanks very much !

Hi , the action should be fixed on the new version now. Could you follow the steps to apply the fix to your workflow?

  1. Access your workflow
  2. On your Mailerlite - Update Subscriber, on the top right side, click the “Update” button to apply the new version to your action
  3. Try the action again

Hi . Is this updated connection definitely working with Mailerlite classic? The authentication isn’t working. I’m very reluctant to change the API key as I will need to update several other automations if I do, several of which I have seen working in the past couple of hours

When I click the link in Pipedream to fetch my API key, whilst already logged into Mailerlite classic, I am prompted to created a new account. This makes me suspect that the update is set up for new Mailerlite only

Hey , I believe the new fix is only applied for Mailerlite new. Pipedream no longer support Mailerlite classic.

Oh, that’s a shame. The classic connection had been working up until now