OtherReal-timeUpdated May 2026

Apify

Apify cloud scraping and actor runs

Apify is the cloud platform for running web scrapers and automation actors — its actor model packages a scraper as a versioned, parameterised, schedulable unit that runs on Apify's managed infrastructure. Tiny Command exposes four actions, no triggers (Apify supports webhooks per-actor in the Apify console; point them at a Tiny Command webhook trigger for "scrape finished" workflows): List Actors (every actor in the connected account, including third-party actors from Apify Store the account has installed), Run Actor (start an actor run with input parameters, returns a run ID immediately), Get Run (poll for run status — RUNNING, SUCCEEDED, FAILED, ABORTED), Get Dataset Items (fetch the dataset Apify wrote during the run — typically the scraped records). The connection uses an Apify API token from Account Settings → Integrations. The typical workflow: Run Actor with the URL/query params → wait for the webhook (or poll Get Run) → Get Dataset Items → write the records to a database or push downstream. Apify Store has thousands of pre-built actors (Google Search Results, Instagram Profile, Amazon Product Details) so most scrape use cases don't need a custom actor.

Connect Apify

0triggers

4actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Apify can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Get Dataset Items	Returns the records the actor wrote to its dataset (typically one record per scraped item — product, profile, search result). Shape depends entirely on the actor; check the actor's README in Apify Store for the schema before parsing downstream.	2 fields	View →
Get Actor Run Status	Returns the current state of a run — RUNNING, SUCCEEDED, FAILED, or ABORTED — plus runtime stats and compute usage. Poll for completion in workflows that need to wait, or pair with the actor's webhook for push-based notification.	1 fields	View →
List Actors	Returns every actor in the account — custom-built actors plus Apify Store actors the account has installed. Useful for inventorying available scrapers at workflow-setup time.	2 fields	View →
Run Apify Actor	Starts an actor with the configured input parameters. Returns the run ID immediately; the actor processes async. For long scrapes, configure the actor's webhook to POST completion to a Tiny Command trigger URL instead of polling.	2 fields	View →

Recipes

Pre-built Apify workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Apify → Slack alerts

AI-triage every Apify event, ping the right channel only when it matters.

Apify → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Apify → Notion database

Turn Apify into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Apify once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Apify field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Apify integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Apify to Tiny Command?

Open the Tiny Command workflow builder, drop in a Apify node, and click Connect. Authorize Apify once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Apify triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Apify today. Use Tiny Command's universal Webhook or Schedule trigger to start Apify workflows, then run any Apify action you need.

What Apify actions can I run from a workflow?

4 Apify actions are available out of the box, covering other operations like "Get Dataset Items". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Apify integration real-time?

Apify actions execute synchronously inside your workflow. Tiny Command waits for Apify's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Apify with Tiny Command?

No. Every Apify trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Apify API endpoint directly.

How much does the Apify integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Apify integration itself has no per-app surcharge.