Automate Apify

What Apify is

Apify is a platform for collecting public web data: its API runs any actor from the Apify Store (scrapers for Google Maps, social platforms, job boards and thousands more) and returns the collected records as datasets.

API host: api.apify.com

What HumDay can do in Apify

131 documented operations change something in Apify. The 60 most useful are listed here.

• POSTCreate task/v2/actor-tasks
• POSTCreate webhook/v2/webhooks
• POSTCreate schedule/v2/schedules
• POSTRun task synchronously and get dataset items/v2/actor-tasks/{actorTaskId}/run-sync-get-dataset-items
• DELETEDelete task/v2/actor-tasks/{actorTaskId}
• PUTUpdate task/v2/actor-tasks/{actorTaskId}
• POSTCreate Actor/v2/actors
• POSTCreate dataset/v2/datasets
• POSTCreate request queue/v2/request-queues
• POSTCreate key-value store/v2/key-value-stores
• POSTStore record (POST)/v2/key-value-stores/{storeId}/records/{recordKey}
• POSTCharge events in run/v2/actor-runs/{runId}/charge
• POSTRun task/v2/actor-tasks/{actorTaskId}/runs
• PUTUpdate task input/v2/actor-tasks/{actorTaskId}/input
• POSTRun task synchronously/v2/actor-tasks/{actorTaskId}/run-sync
• DELETEDelete last task run's default store's record/v2/actor-tasks/{actorTaskId}/runs/last/key-value-store/records/{recordKey}
• POSTStore record in last task run's default store (POST)/v2/actor-tasks/{actorTaskId}/runs/last/key-value-store/records/{recordKey}
• PUTStore record in last task run's default store/v2/actor-tasks/{actorTaskId}/runs/last/key-value-store/records/{recordKey}
• POSTStore record in default store (POST)/v2/actor-runs/{runId}/key-value-store/records/{recordKey}
• POSTStore items in last task run's dataset/v2/actor-tasks/{actorTaskId}/runs/last/dataset/items
• POSTAdd request to last task run's default request queue/v2/actor-tasks/{actorTaskId}/runs/last/request-queue/requests
• PUTUpdate limits/v2/users/me/limits
• DELETEDelete webhook/v2/webhooks/{webhookId}
• PUTUpdate webhook/v2/webhooks/{webhookId}
• DELETEDelete schedule/v2/schedules/{scheduleId}
• PUTUpdate schedule/v2/schedules/{scheduleId}
• DELETEGet browser info/v2/browser-info
• POSTGet browser info/v2/browser-info
• PUTGet browser info/v2/browser-info
• POSTAbort Actor task's last run/v2/actor-tasks/{actorTaskId}/runs/last/abort
• DELETEDelete record/v2/key-value-stores/{storeId}/records/{recordKey}
• PUTStore record/v2/key-value-stores/{storeId}/records/{recordKey}
• POSTReboot Actor task's last run/v2/actor-tasks/{actorTaskId}/runs/last/reboot
• DELETEDelete last task run's default dataset/v2/actor-tasks/{actorTaskId}/runs/last/dataset
• PUTUpdate last task run's default dataset/v2/actor-tasks/{actorTaskId}/runs/last/dataset
• POSTBatch add requests to last task run's default request queue/v2/actor-tasks/{actorTaskId}/runs/last/request-queue/requests/batch
• POSTMetamorph Actor task's last run/v2/actor-tasks/{actorTaskId}/runs/last/metamorph
• POSTRun Actor synchronously and return key-value store record/v2/actors/{actorId}/run-sync
• POSTCreate version/v2/actors/{actorId}/versions
• POSTTest webhook/v2/webhooks/{webhookId}/test
• POSTStore items/v2/datasets/{datasetId}/items
• DELETEDelete last task run's default request queue/v2/actor-tasks/{actorTaskId}/runs/last/request-queue
• PUTUpdate last task run's default request queue/v2/actor-tasks/{actorTaskId}/runs/last/request-queue
• DELETEDelete last task run's default store/v2/actor-tasks/{actorTaskId}/runs/last/key-value-store
• PUTUpdate last task run's default store/v2/actor-tasks/{actorTaskId}/runs/last/key-value-store
• POSTAdd request/v2/request-queues/{queueId}/requests
• POSTStore record in last run's default store (POST)/v2/actors/{actorId}/runs/last/key-value-store/records/{recordKey}
• POSTRun Actor synchronously and get dataset items/v2/actors/{actorId}/run-sync-get-dataset-items
• POSTEncode and sign object/v2/tools/encode-and-sign
• POSTDecode and verify object/v2/tools/decode-and-verify
• DELETEDelete default store's record/v2/actor-runs/{runId}/key-value-store/records/{recordKey}
• PUTStore record in default store/v2/actor-runs/{runId}/key-value-store/records/{recordKey}
• POSTStore items/v2/actor-runs/{runId}/dataset/items
• DELETEDelete Actor/v2/actors/{actorId}
• PUTUpdate Actor/v2/actors/{actorId}
• DELETEDelete run/v2/actor-runs/{runId}
• PUTUpdate run/v2/actor-runs/{runId}
• POSTAdd requests/v2/request-queues/{queueId}/requests/batch
• DELETEDelete dataset/v2/datasets/{datasetId}
• PUTUpdate dataset/v2/datasets/{datasetId}

What HumDay can read from Apify

These are the operations a schedule or a trigger can watch.

• GETGet user runs list/v2/actor-runs
• GETGet list of tasks/v2/actor-tasks
• GETGet user builds list/v2/actor-builds
• GETGet list of webhook dispatches/v2/webhook-dispatches
• GETGet list of task runs/v2/actor-tasks/{actorTaskId}/runs
• GETGet private user data/v2/users/me
• GETRun task synchronously and get dataset items/v2/actor-tasks/{actorTaskId}/run-sync-get-dataset-items
• GETGet public user data/v2/users/{userId}
• GETGet task/v2/actor-tasks/{actorTaskId}
• GETGet list of Actors in Store/v2/store
• GETGet list of Actors/v2/actors
• GETGet list of datasets/v2/datasets
• GETGet list of webhooks/v2/webhooks
• GETGet list of schedules/v2/schedules
• GETGet list of request queues/v2/request-queues
• GETGet list of key-value stores/v2/key-value-stores
• GETGet list of webhooks/v2/actors/{actorId}/webhooks
• GETGet task input/v2/actor-tasks/{actorTaskId}/input
• GETRun task synchronously/v2/actor-tasks/{actorTaskId}/run-sync
• GETGet list of webhooks/v2/actor-tasks/{actorTaskId}/webhooks
• GETGet last task run's default store's record/v2/actor-tasks/{actorTaskId}/runs/last/key-value-store/records/{recordKey}
• GETGet last task run's dataset items/v2/actor-tasks/{actorTaskId}/runs/last/dataset/items
• GETGet last task run's default store's list of keys/v2/actor-tasks/{actorTaskId}/runs/last/key-value-store/keys
• GETList last task run's default request queue's requests/v2/actor-tasks/{actorTaskId}/runs/last/request-queue/requests
• GETDownload last task run's default store's records/v2/actor-tasks/{actorTaskId}/runs/last/key-value-store/records
• GETGet limits/v2/users/me/limits
• GETGet webhook/v2/webhooks/{webhookId}
• GETGet schedule/v2/schedules/{scheduleId}
• GETGet webhook dispatch/v2/webhook-dispatches/{dispatchId}
• GETGet browser info/v2/browser-info
• GETGet last Actor task run's log/v2/actor-tasks/{actorTaskId}/runs/last/log
• GETGet list of runs/v2/actors/{actorId}/runs
• GETGet record/v2/key-value-stores/{storeId}/records/{recordKey}
• GETGet last task run's default dataset/v2/actor-tasks/{actorTaskId}/runs/last/dataset
• GETGet list of builds/v2/actors/{actorId}/builds
• GETGet list of versions/v2/actors/{actorId}/versions
• GETGet dataset items/v2/datasets/{datasetId}/items
• GETGet schedule log/v2/schedules/{scheduleId}/log
• GETGet monthly usage/v2/users/me/usage/monthly
• GETGet last task run's default request queue/v2/actor-tasks/{actorTaskId}/runs/last/request-queue

How automating Apify works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Apify account.
4. Grant access, then go live. You approve the specific Apify operations it may use — and only those.

Popular Apify integrations

Connect Apify to the tools people pair it with most.

• Apify and OData for namespace microsoft.graphintegration
• Apify and Cloudflareintegration
• Apify and NetBoxintegration
• Apify and GitHubintegration
• Apify and Mistintegration
• Apify and Loket.nlintegration
• Apify and Atlassian The Jira Cloud platformintegration
• Apify and Magento B2Bintegration
• Apify and Stripeintegration
• Apify and Zuora Reference Billingintegration
• Apify and bunqintegration
• Apify and DocuSignintegration

Automate Apify with these

• Datto Autotask PSA2958 operations
• DocuSign414 operations
• Figma50 operations
• Peoplegeneratorapi OpenAPI definition46 operations
• Botify26 operations
• Browshot17 operations
• Voodoomfg Voodoo Manufacturing 3D Print11 operations
• Swagger Generator7 operations
• Chompthis Chomp Food Database Documentation4 operations
• Scrapewebsite Scrape Website Email3 operations
• import.io2 operations
• PasswordUtility.2 operations

Categories

• Tools
• Data

Questions about Apify automation

Can HumDay connect to Apify?

Yes. HumDay reads Apify's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 224 operations are documented.

Do I need to write code to automate Apify?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Apify account.

What can HumDay do in Apify?

131 of the 224 documented operations change something in Apify, and 93 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Apify account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Apify is held behind that approval.

Where this came from

The operations above are read from the API description Apify publishes themselves at api.apify.com/v2/openapi.json. Descriptions are the provider’s own words, not ours.