Testing

Hello, I’ve been working on an issue a user has been dealing with, that I believed I had solved based on my testing with the CLI tests and before promoting the version on the zapier UI. The fix is supposed to take errors like we see (due to deleted objects) and filter them out in the returned results. However now that it is promoted (1.14.4), the error shows up when trying out “Find new records” while it does not happen for the version being pushed again without promotion (1.14.5). I guess I just want to understand what exactly that “Find new records” button is doing/ what bundle it sends so I can repeat it exactly from the CLI for debugging?  

I am creating a new app, and I have added a trigger and an action to get started. The steps for creating an action (https://developer.zapier.com/app/210627/version/1.0.0/triggers/update_contact/api) indicate that I should test it by creating a Zap. So I created a Zap but when I try to configure the "Catch Hook" step and change it from "Webhooks by Zapier" to my app, I can't find my app, it isn't listed. I expect it isn’t listed because it hasn’t been published, but don’t I need to test it before I submit/publish it? How do I test my new action? Similarly, when I try to test my new trigger I don't see my app listed there either, so how do I test my trigger?

Hello I’m just wondering if you or anyone on here has had an issue converting Zapier to your PayPal . I do have a Business Account and I did Copy the URL, I tried to test it but it never showed. Could anyone help or know what I should do. Thanks 

I’m triyng to export a deal on plooms, but i had some issues. I can't select the final destination, in this case for this automation it would be a specific funnel. I already talked to ploomes and they said that this is where the problem is, but I don't think so. Any ideas that could be wrong ?

Hello and Welcome Forum MembersHey Guys, this is my first blog post. I look forward to good discussions and a good exchange of information with you

We have an app but we don't support login via email + password. We only support login via Google, GitHub, and Magic Link. Does this work for the review team to test the integration?  

Hi We have app which calls our backend api for asynchronous task and pass the callback url. This works fine. In this case Test step is not working because we test step does not have callback url. Can we pass callback url in sample data or how do we make the test step working for test step. Best regardsChandra  

I used the template in Zapier, where I am taking a new customer or payment (I’ve tried it both ways) from Stripe and trying to add them to a Hubspot workflow. When I test it from the Hubspot portion of the Zap set up, it asks for a contact (it’s required) so I pull in one of the existing emails from the Stripe dropdown and the data does come over to Hubspot. However, when I add a new customer to Stripe, they are not coming over automatically, I have to go into Zap and add them?  How do I get Zap to recognize all of the future emails that come into Stripe and move them to the Hubspot workflow?  they are not making it over, only the original one that I tested in Zap before I published the Zap?? 

Hey Zapier team, I can see the “Test” step in API polling based triggers basically tries to poll for recent records from the endpoint defined in `perform` step. Its easy and simple when the API returns the records matching the output fields as defined. As it gives the user a confidence in how the data might look like. Consider this case: The user selects an input choice from dynamic dropdown. Say ‘UserID’ : ‘123’.  My perform setup is an API call to say GET  ‘booksRead/user?UserID=123’. Query parameter populated from bundle data. The API returns a response like {currentlyReading: {}, userDetails: {id: 123,isLoggedIn: true, isAdmin: false} }, currentlyReading this value gets updated whenever the user picks up a book to read.  So, zapier polls for change in the response and hence a change in currentlyReading every certain interval, and whenever there is a change, say userID:123 picked up ‘ZapierGuide’ to read, I make the perform return a composite object something like this: { user: {

Hi, After submit the app to review, We received the mail like from zapier "The provided credentials are not valid. Please provide valid credentials for a user registered with integration-testing@zapier.com to allow us to log into the app's user interface."Where will we create this login? Create a login in our own application to access or create demo zapier account?

I have converted a number of integration projects to CLI projects, using zapier convert.  I’ve noticed that they use mocha for their testing framework:{ "name": "dummy", "version": "1.0.1", "description": "lorem ipsum.", "main": "index.js", "scripts": { "test": "mocha --recursive -t 10000" }, "engines": { "node": ">=v14", "npm": ">=5.6.0" }, "dependencies": { "zapier-platform-core": "^7.3.0" }, "devDependencies": { "mocha": "^10.2.0", "should": "^13.2.0" }, "private": true, "zapier": { "convertedByCLIVersion": "12.2.0" }}If I start a new CLI project, using zapier init, it uses jest as its testing framework:{ "name": ".", "version": "1.0.0", "description": "", "main": "index.js", "scripts": { "test": "jest --testTimeout 10000" }, "dependencies": { "zapier-platform-core": "14.1.1" }, "devDependencies": { "jest": "^26.6.3" }, "private": true}Before I created the CLI project (using zapier init), I updated my version of zapier:$

Hi How do I test the Partner API without Zapier users being able to see my Integration?I would like to be able to create Zaps (and maybe more) through the API and test it, before everyone can find/see my integration…Is this possible? I need to be able to “embed” the possibility of i.e. creating Zaps from the webpage of the company I work for. Thank you

As a developer, what approaches do y'all favour for testing an upcoming Zapier App version?Some options come to mind: Release a new private version, make the changes and point URLs to a testing backend server. Check everything works. Once happy, point URLs to live server again and promote version. Create a Zapier App which is essentially a copy of the Production one. This app is permanently pointing to a testing backend server. Drawback: it's hard to ensure they are in sync. Updating settings is a manual error-prone process. Use Zapier CLI instead of the Web Builder and rely on unit tests (From Zapier CLI i just know what i read from the docs, haven't tried it yet). Anyways, i am curious about other people's recommendations. Floor is open for discussion :)