Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

systeme.io zaps no longer work (I didn't change the zaps at all)

  • February 13, 2025
  • 6 replies
  • 30 views
P

I went in to edit one particular zap, and when I hit the test button (to test a stage with systeme.io integration), all of my systeme.io zaps turned themselves off with the emailed error messages to me (for each zap), “The app returned "The funnel or funnel step that you want to use is not correct. Please update the Zap or recreate it". 

I did not change the funnel or funnel step or anything else, either in all of those zaps or in systeme.io, since the past many months that they have worked successfully together.

I disconnected and re-authorized my systeme.io account.  It did not change anything.

 

Further, in one specific example zap, I had it set up so when a contact is tagged in systeme.io, an email is sent out.  On the second step (“configure”), it asks me to choose a specific tag for the trigger.  However, in the dropdown menu, it now shows no tags to choose from, with the message,

“No options are available.

Some reasons this could be happening:

  • Confirm if you connected the right account.
  • Confirm that there is data in the partner app.
  • Confirm that you have permission to the data in the partner app.
  • There was an issue retrieving data from the partner app. Please try again later.”

My whole sales pipeline depends on these zaps working.  Help please?  Thank you :) 

Best answer by escalateur.comBest answer by escalateur.com

Ok this confirms your systeme.io - Zapier connexion is somehow broken. But you said you already re-connected it so let’s look for another workaround.

 

Try to replace this trigger by Webhooks by Zapier > Catch Hook. Then copy the provided URL.

 

Go to https://systeme.io/dashboard/profile/webhook-settings and click “create”. Paste the Zapier URL in the corresponding field and put whatever in the “Secret” field. It’s not relevant in our case. Then select “Tag added to contact” in the events list below. Save and exit.

 

Then add the tag to a contact and click “Test trigger” in Zapier. If you receive nothing, that’s the end for this solution. But if it does work, simply add a Filter step after the trigger and insert here the desired tag name or ID.

 

(If you have to share a new screenshot hereafter, please don’t let us see your Zapier Webhook address)

View original
Did this topic help you find an answer to your question?

6 replies

P
  • pyocum
  • Author
  • New
  • 3 replies
  • February 13, 2025

 

escalateur.com

Hi, thanks for sharing the screenshot!

 

A first thing I’d do would be to try forcing the trigger by adding the Tag ID manually. Click on the 3 dots at the right of the Tag field, and choose “custom”.

 

Then, find the Tag ID by going in your systeme.io account in the tags section. Click on the tag name, this should send you to your contacts. Now look at your URL bar, it should look like this:

 

https://systeme.io/dashboard/contacts?filter=%5B%7B%22searchValue%22%3A%221363394%22%2C%22compareOperation%22%3A%22IN_LIST%22%2C%22searchField%22%3A%22tag%22%7D%5D

 

In this example, the Tag ID is 1363394. (Make sure not to include the preceding “%22”)

 

Now paste it in your Zap’s trigger, add the tag to someone in your account, and see if Zapier can catch it.

 

Tell me if this doesn’t work so we can work out another solution :)

Adrien
P
1 person likes this
  • P
    pyocum
P
  • pyocum
  • Author
  • New
  • 3 replies
  • February 13, 2025

That did allow me to publish the zap (which I couldn’t before), however I immediately got this email:

 

 

escalateur.com

Ok this confirms your systeme.io - Zapier connexion is somehow broken. But you said you already re-connected it so let’s look for another workaround.

 

Try to replace this trigger by Webhooks by Zapier > Catch Hook. Then copy the provided URL.

 

Go to https://systeme.io/dashboard/profile/webhook-settings and click “create”. Paste the Zapier URL in the corresponding field and put whatever in the “Secret” field. It’s not relevant in our case. Then select “Tag added to contact” in the events list below. Save and exit.

 

Then add the tag to a contact and click “Test trigger” in Zapier. If you receive nothing, that’s the end for this solution. But if it does work, simply add a Filter step after the trigger and insert here the desired tag name or ID.

 

(If you have to share a new screenshot hereafter, please don’t let us see your Zapier Webhook address)

Adrien
P
1 person likes this
  • P
    pyocum
P
  • pyocum
  • Author
  • New
  • 3 replies
  • February 13, 2025

Thank you, that solution did work for this case of triggering on a tag being added, and I can use it for triggering on a sale as well.  It is a bit cumbersome though, is there any hope of figuring out why the original method is no longer working?

escalateur.com

On my side everything worked normally between Zapier and systeme.io, so it should definitely get fixed on your side as well at some point.

 

My best guess right now is that when you removed the systeme.io connection from Zapier and connected it again, the same access token got stored somewhere in the backend. So the latest connection isn’t really a new one. 

 

The complementary idea to this, is that your Zapier account’s access to systeme.io got deprecated or lost permissions. Which is why it’s no longer able to read the available Tags to choose from.

 

I recommend writing to systeme.io support to ask for help in checking Zapier’s API permissions toward your account. And I recommend writing to Zapier support just to check if you’re the only one with this issue. (If multiple people encountered it, we can generally trust that their tech teams are already working on it)

 

In the meantime, you should:

  • Try to use other systeme.io triggers & actions in a new Zap, just to check how wide the problem is
  • Connect a 2nd account to Zapier to compare if these bugs exactly replicate
Adrien

Reply


Terms & Conditions