All code and tests need to be rewritten into apify-client-js v1 client.

We need to fetch input schema and prefill input regarding that. But we need to have input schema in build detail API. Now we use just defaultRunOptions, exampleRunInput.

From reported issue in Zapier:

Hi there, Apify Team!

JC here, reaching out from Zapier Support. One or more of our mutual customers has requested a new feature in your app.

Specifically, they'd like to see the Finished Actor Run trigger to GET more than 100 records, and not be limited to just 100.

An example use case for this is when a user has a "paid player" on Apify i.e. Tiktok Scraper that allows them to retrieve data from Tiktok but the scaper returns more than 100 records. All exceeding records are lost and are not sent to their downstream app, so removing this limit will allow them to do this.

Here's a GIST where we can see the endpoint query has a 100 record limit:

https://cdn.zapier.com/storage/files/c5c95c85dd8b0e9c548bd36a603a96ea_2.txt

Thanks, and please let us know if you have any questions!

cc https://developer.zapier.com/app/15018/issues/11

The issue was reposted on https://developer.zapier.com/app/15018/issues/12

The user set the testMode to false, but the input from Zapier was called with true.

There is Actor when it happened
https://console.apify.com/admin/users/ihinbAhWkLMJFW9bD/actors/tasks/bJEGS07jSlo36ulHr/console

Zapier UI doesn't provide multi-select field yet. We have to think about workaround or wait for it.

This will give us better discoverability in Zapier search, right now we don't show up under "scrape" or "crawl" keywords at all.

TBD:

• should we include Web Scraper as well?
• Zapier has max 30 seconds wait time for actions, that might be painful

The issue was reported by Zapier user, for the full zapier report go to issue on Zapier platform.

Loads featured actor from Apify Store to actor run dropdown.

It is useful for Zapier users, who want to test Apify and don't have any actor yet.

Shouldn't we support also text types or possibly other types (images, ...)?

Originally posted by @mtrunkat in #5

Creating Zaps for actor runs with status Failed for example requires setting the Trigger Event to Finished Actor Run then adding Filter Action to filter the actor run's status and test it to be equal to Failed. Zapier only allows users on paid plans to turn on Zaps with Actions steps (see attached image). Instead we could have a Trigger Event for such case for example Failed Actor Run.

https://help.apify.com/en/collections/1778384-zapier-integration

and

Zapier missing in https://docs.apify.com/platform/integrations
we need to create an article here we should move https://help.apify.com/en/articles/3034235-getting-started-with-apify-integration-for-zapier her once is updated.

Steps TBD

The new version 3.0.4 was released, which was breaking.

Let's give some time to test users this new version (week or two) and then we need to deprecate the old version so the users will be forced to migrate into new one.

There is a feature request from the Zapier team:

Hi there, Apify Team!

Breetel here, reaching out from Zapier Support. One or more of our mutual customers has been having trouble setting up Zaps using the "Run Actor" action because they're not sure what to put in the field for Input Body. Many Zapier users are not familiar with json and would do not know how to format their data in this way.

We'd love to see any action steps that require json to be reconfigured so that the user would just need to input values, then your code could format those values as your API expects to receive them.

Would this be possible? Please let us know your thoughts and how we can help!

The problem can be solved by fetching input schema in process of Zap creation and generate fields based on it.
The Zapier allow dynamic fields, which is feature we can use.

Automate workflow, which we have now in readme.md under Deploy title.