How do I create a ThriveCart standard action within Zapier if the (beta) Custom Action isn't working?

Question

I have tried creating a two step zap - One that identifies a specific form within Kit, and then the second step uses a custom action which is in Beta mode to grant access to a course when someone joins a specific form.

Unfortunately, that custom action does not appear to be working. When I tested it on myself, it sends the course, but I got someone to test it for me and they did not receive it despite multiple attempts. The testing appears to not be revealing any errors.

In the pic below in step 2, when I select the event, and pick Thrivecart as the app and then go to select the action event from the drop down, it does not have any options of picking a standard event. It forces me into using a custom event (which is in Beta).

I have set up the custom event using AI, and it appeared to work for me, but it wont work for anyone else and I don’t know how to solve it.

So my question first is - should there be an option for a standard event within this field for Thrivecart? Am I just not typing in the correct thing for a standard event to appear?

The second question is, if there isn’t a way to create this standard event, how do I test it, if the testing does not reveal what the issue might be?

Thirdly, is there something wrong with the way I am setting up this zap?

Thanks

Rad · Accepted Answer

Thank you, I decided to create another custom action based on giving each subscriber a separate tag within Kit and then using the custom action builder to provide course access and that worked instead. So perhaps the form level kit to thrivecart zap wasn’t enough. Not sure why, but glad the other way worked. Thank you for your response!

drtanvisachar · Answer

Hey ​@Rad!ThriveCart not showing standard actions is normal, it is mostly trigger based in Zapier, so if you are seeing only a custom action that is expected and not something you are doing wrong.The issue is the custom action itself, if it worked for you but not others then it is almost always a data problem, meaning something in your test matched what the API expects but real users are missing a required field or using a different value. Custom actions do not validate well, so Zapier will say it ran fine even if the external app ignored it.What to do next is simple, go into the Zap history for a failed run with your test user and compare it to your own successful run, look at the exact payload being sent in that custom step, especially email, product ID, course ID, or any required field. Something will be different or missing.Also make sure the trigger from Kit is actually passing the same data for other users, sometimes test entries include more fields than real submissions.For testing, do not rely on the “Test” button, use real submissions and check Zap history every time, that is where you will see what is actually being sent.Nothing is wrong with your overall setup, the weak point is the custom action, so the fix is to compare working vs non working runs and adjust the fields until they match exactly.Ethan Marcellus- Automation Expert at Tuesday Wizard | Top Zapier Solution Partner | Zapier Community Contributor

How do I create a ThriveCart standard action within Zapier if the (beta) Custom Action isn't working?

2 replies

Useful links

Useful links

Sign up

Use your Zapier credentials

Log in to the Community

Use your Zapier credentials

Scanning file for viruses.

This file cannot be downloaded