← All integrations

Apify

121 operations0 webhooks

Web scraping and automation platform for running actors and extracting structured data.

Supported operations

  • Abort Actor BuildWrite

    Tool to abort an Actor build that is starting or running. Use when you need to cancel a build in progress. Builds in terminal states (FINISHED, FAILED, ABORTING, TIMED-OUT) are not affected.

  • Delete Actor BuildDestructive

    Tool to delete an Actor build permanently. Use when you need to remove a specific build by its ID. The default build for an Actor cannot be deleted. Only users with build permissions can delete builds.

  • Get Actor BuildRead-only

    Tool to get detailed information about a specific Actor build. Use when you need to retrieve complete build details by build ID. Optionally wait for the build to finish using the waitForFinish parameter to avoid polling.

  • Get Actor Build LogRead-only

    Tool to retrieve the log file for a specific Actor build. Use when you need to inspect logs generated during an Actor build process. Only the trailing 5 million characters of the log are stored.

  • Get User Builds ListRead-only

    Tool to get a paginated list of all builds for a user. Use when you need to retrieve build history across all actors. Supports pagination up to 1000 records.

FAQ

Install corsair and @corsair-dev/apify, add the Apify plugin, and connect with an API key. Then call methods like corsair.apify.api.actorBuilds.abortActorBuild() from your app. Corsair syncs data per tenant.

Yes. Apify requires an API key from your Apify account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Apify, GitHub, Notion, Stripe, and the rest. Trigger Apify from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for web scraping and automation platform for running actors and extracting structured data. Common builds include sync jobs, admin tooling, and agents that call Apify APIs from your backend. Local DB entities let you query synced Apify records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Apify API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/apify in the open repo. When Apify ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Apify data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Apify data on your behalf.