Apify Actor Automation: Approve from Your Phone
Run Apify on autopilot. Keep the veto.
113 actions
Apify manages Actors, datasets, and crawl queues. Rills gates destructive and configuration-changing operations, including dataset deletion and Actor version changes, before they run.
Interactive. No signup. 14 days free · approvals always free.
Most automation fires first, asks later. Rills shows you the change before it ships.
Every consequential ai action from Apify arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue (3)
Retry 3 actors with updated input parameters?
3 actors · last run failed
Target URLs returned 404
Same pattern as Tuesday's outage
Free to wait. Free to think.
Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.
Approve from your phone in five seconds.
Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, and no surprise send you find out about after it's already out the door.
Clear runs stop waiting on you.
Every run is scored against your review step. The ones that clearly match your judgment run above your threshold without a tap; the borderline ones still come to the queue. Autonomy is earned run by run, never switched on for good.
About Apify automation
Apify actors run tasks that scrape thousands of pages, fire webhooks to your communication tools, and update datasets that feed your dashboards. When one of those runs ships the wrong data or a webhook fires a payload you haven't checked, you're cleaning up bad leads and broken integrations for hours.
When Apify runs unsupervised
Unsupervised Apify automation doesn't just waste resources. It sends bad data downstream before you know it's wrong.
- Delete Webhook: You delete a webhook that was routing enrichment data to your CRM, and new leads stop flowing.
- Run Actor Asynchronously: You trigger a large scrape with the wrong input, and it pulls thousands of irrelevant pages before you can stop it.
- Add Request to Queue: A misconfigured queue floods your workflow with duplicate requests, and your dataset fills with garbage.
- Update Dataset: You overwrite a dataset that your dashboard relies on, and your reports go blank.
What Rills does inside Apify
Instead of letting those actions happen immediately, Rills intercepts them. When you configure a trigger that would delete a webhook, run an actor, or update a dataset, the AI proposes the change and waits for you to approve Apify changes from your phone.
The data still flows. You just stop the bad data before it ships.
Why Apify has no triggers and how Rills fills the gap
Apify doesn't natively support event-driven triggers for many of its operations, so you can't set up automatic checks before actions run. Rills fills that gap by monitoring your Apify account on a schedule or by reacting to upstream signals from your other tools.
- Scheduled actor checks: Rills polls the last actor run status and proposes a retry with corrected input if the run failed.
- Upstream webhook triggers: When a webhook fires from a monitored source, Rills can review the payload and decide whether to add it to the queue or delete the webhook.
- Dataset hygiene sweeps: Rills periodically checks for stale datasets and proposes deletions or updates to keep your data fresh.
What Rills can do in Apify
6 of 113 actions across reads, writes, and updates.
- 01
Abort Actor Build
Tool to abort an Actor build that is starting or running.
- 02
Abort Actor Run
Tool to abort a running or starting Actor run.
- 03
Add Request to Queue
Adds a web page URL to a crawling queue, enabling systematic data extraction from websites without accidentally duplicating work. Useful for managing multiple URLs to scrape in a controlled, batch-oriented way.
- 04
Batch Add Requests to Queue
Tool to batch-add up to 25 requests to a request queue.
- 05
Batch Delete Requests from Queue
Tool to batch-delete up to 25 requests from a queue.
- 06
Build Actor
Compiles an Actor's source code into a deployable Docker image, allowing you to create a new version of your automation or scraping tool with specific configuration.
Common questions about Apify automation
How do I approve Apify actor runs before they start?
When you schedule an Apify actor run, Rills doesn't let it fire immediately. It proposes the action, showing you which actor, what input, and the estimated cost. You review the proposal on your phone and swipe to approve. Only then does the run execute. That way, no scraping job starts without your say-so, and you don't burn credits on a script you forgot to pause.
Can I get mobile approval before deleting an Apify webhook?
Yes. When a workflow proposes deleting an Apify webhook, Rills sends the proposal to your phone as an approval card. You can review which webhook is targeted and why, then swipe to confirm or reject. No webhook is severed without your explicit permission. This prevents accidental disconnection of critical integrations you'd only notice after data stops flowing.
How do I automate Apify queue management without AI overloading my queues?
You set up conditions for when to add requests to an Apify queue. Rills' AI proposes the 'Add Request to Queue' action along with the specific data, then waits for you. You approve from your phone before the request hits the queue. The same for deletes: nothing gets removed unless you say so. This prevents AI from flooding your scrapers with junk or deleting critical pending tasks.
How do I run Apify tasks on a schedule with a human check?
Rills can watch your calendar or time triggers, but instead of auto-running the task, it proposes the 'Run Task Sync' action. You get a notification on your phone with the task name and input parameters. You approve the run only if conditions are right. This stops scheduled tasks from churning through data during a holiday or outage, saving you from wasted compute and bad data.
How is Rills different from Zapier for Apify automation?
Zapier automates Apify actions instantly: a trigger fires, and the action executes without a pause. Rills inserts a mandatory approval step. Every proposed Apify action, like running an actor or deleting a task, lands in your phone as a swipeable card. You decide what actually ships. This means you don't wake up to a scraper that ran wild because a condition you forgot about was met overnight.
Why use Rills instead of Make for Apify workflows?
Make's scenarios run automatically once triggered. Rills puts a gate between trigger and action. For Apify, that means a proposed 'Run Actor' or 'Delete Actor Version' waits for your approval before executing. You get a mobile notification with the details, and you swipe to confirm. This gives you a safety net for actions that could cost money or data, without having to monitor a dashboard.
Does Rills support Apify webhooks?
Rills can't trigger on Apify webhooks directly, but it can manage them. You can set up workflows that propose deleting a webhook when certain conditions are met, and you approve that deletion from your phone. For inbound webhook events, you'd need another trigger. Rills focuses on actions you control, not passive events, ensuring no changes happen without your nod.
How much does Rills cost for Apify automation?
Rills charges only for real actions: AI calls and external API work. All approvals, workflow logic, and the mobile approval queue are free. You can build as many Apify automation sequences as you need, with as many approval steps, without paying for the logic. You only pay when Rills actually executes something like running an actor or adding a request to a queue.