;}%20.st6{fill:url(%23SVGID_00000021089067129159788970000008246765442136188072_);}%20.st7{fill:url(%23SVGID_00000117639240116366130650000015074833605515028638_);}%20.st8{opacity:0.4;fill:url(%23SVGID_00000101781798616409025840000016567063639337360777_);}%20.st9{opacity:0.4;fill:url(%23SVGID_00000052086836598721292040000002033117744178971046_);}%20.st10{opacity:0.4;fill:url(%23SVGID_00000159460939004760751800000002448009281983951536_);}%20.st11{opacity:0.4;fill:url(%23SVGID_00000013177830667419993080000017721442101626521532_);}%20.st12{opacity:0.4;fill:url(%23SVGID_00000152235521444854938490000006526001119318383285_);}%20.st13{opacity:0.4;fill:url(%23SVGID_00000119823135212293698520000012774889010992664993_);}%20%3c/style%3e%3cg%3e%3cpolygon%20class='st2'%20points='134.78,14.22%20114.31,48.21%20101.33,69.75%20158.22,69.75%20177.97,36.95%20191.67,14.22%20'/%3e%3cpolygon%20class='st3'%20points='227.55,69.75%20186.61,69.75%20101.33,69.75%20129.78,119.02%20158.16,119.02%20228.61,119.02%20256,119.02%20'/%3e%3cpolygon%20class='st3'%20points='136.93,132.47%20116.46,167.93%2073.82,241.78%20130.71,241.78%20144.9,217.2%20180.13,156.18%20193.82,132.46%20'/%3e%3cpolygon%20class='st3'%20points='121.7,131.95%20101.23,96.49%2058.59,22.63%2030.15,71.91%2044.34,96.49%2079.57,157.5%2093.26,181.22%20'/%3e%3cpolygon%20class='st2'%20points='64.81,131.95%2025.15,131.21%200,130.74%2028.44,180.01%2066.73,180.72%2093.26,181.21%20'/%3e%3cpolygon%20class='st2'%20points='165.38,181.74%20184.58,216.46%20196.75,238.47%20225.19,189.2%20206.66,155.69%20193.83,132.46%20'/%3e%3c/g%3e%3c/svg%3e)
Windmill HubApify
Data OAuth, or a personal API keyRun Apify actors and tasks, read their datasets and key-value stores, and have a finished run call a Windmill flow back.
Set up in 2 steps
Connect from the Resources page
Open Resources, click Add a resource/API and pick apify from the OAuth APIs list. Click Connect, allow access, then name the resource and save it.
Run your first script
Fork the run actor script below. The actor and task pickers are live dropdowns — they list what your account can reach, so there is no id to look up.
Scripts
Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.
Create Actor Webhook
Create Task Webhook
Delete Webhook
Get dataset items
Get key value store record
Run Actor
Run Task
Scrape Single URL
Task Run Trigger (for polling)
Actor Run Trigger (for polling)
Flows
Multi-step workflows that already wire Apify to something else.
Trigger flows from Apify
Apify is not only a destination. These inbound paths are supported today.
Actor and task webhooks
The create webhook scripts register a Windmill flow's URL with Apify, so a finished run starts it. They take an apify_webhook_config resource, which pairs that URL with the token Apify should send back.
Resource type
apify — the shape of the credential every script on this page expects.
| Field | Type | Required | What it is |
|---|---|---|---|
| token | string | Yes | Apify OAuth token. Available only on Windmill Cloud. |
All resource types
Questions
Which resource type do I need?
apify from the OAuth flow, or apify_api_key if you paste a token yourself — both authorize the API. apify_webhook_config is a different thing: it holds the Windmill URL and token an actor should call back, not a credential for Apify.
There is no Connect button on my instance
Self-hosted instances need an Apify OAuth client configured once by an admin before the tile appears.
Are my credentials stored on the hub?
Never. They live only in your own Windmill workspace, encrypted at rest.