zapier-platform | The SDK for you to build an integration on Zapier

David here, from the Zapier Platform team.

Your perform function needs to return a JS object (something wrapped in {}). To make the error go away, ensure your promise returns something.

The easiest way is the following:

My problem was solved, Zapier Support helped me. The code is correct, I just was testing it in a wrong way. I was looking for the select drop-down at an early stage of Zap creating page, after I selected the Trigger. Where the drop-down appears after I connect an account to the Zap.

David here, from the Zapier Platform team.

I already answered your support ticket, but I figured I'd reply here in case anyone else has the same issue.

The root problem is made clear when you run zapier logs on the cli:

David here, from the Zapier Platform team.

If your dropdown is totally static, you can use the choices property outlined here. There's a couple of different options (depending if order matters or you need labels) but the end goal is that you'll have a choices key with an array or object attached to it.

For example:

David here, from the Zapier Platform team.

That error comes from here and pops up when we can't find zapier-platform-core in node_modules.

It seems like it should be there given what you posted. with "zapier-platform-core": "7.0.0" in your package.json, run rm -rf node_modules && npm i to make sure everything is fresh.

If that doesn't work, please open an issue at https://github.com/zapier/zapier-platform-cli/issues/new.

Nice, so you're almost there! CLI apps don't have pre_ and post_ poll methods. Instead, you put any manipulation after the response comes in.

David here, from the Zapier Platform team. There's no magic or tricks going on, but it looks like you're making life a little bit harder for yourself. Much of the zapier code doesn't support that event pattern (.on('x', function(){...)). Instead, everything uses promises already. Unhandled rejection refers to a rejected promise that you're not handling with a catch clause. We also provide a z.request function which is going to flow a little better than using the request package itself (though this is allowed if you want to!). Check out the doc section about making HTTP requests. We've also got a z.hash(algo, string) method. and then update your code to be something like the following:

David here, from the Zapier Platform team.

We don't have anything specific to an update action, but since you're in control of what sort of request(s) you make, it's pretty easy to build one.

Separate from the resource, you can write an Update X action (called a "create" in the docs, which I see is a little confusing) which can make whatever request you want.

We've got docs about updates here.

​Let me know if you've got any other questions!

I did suffer from this error a lot. The error is due the test framework which normally doesn't wait beyond 2 seconds. Whatever you do in the tests, timeout occurs if not handled using something like the following. In your app's package.json, please add a timeout to mocha runtime (15 seconds) in this example. Please feel free to set a higher timeout while you are testing.

"scripts": { "test": "node node_modules/mocha/bin/mocha --recursive --timeout 15000" },

As other respondents said, add z.console.log(msg) to your code a lot initially to see what is happening with your requests.