STEP 1
Connect Apify and TinyFish
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Apify and TinyFish Integration
Connect Apify and TinyFish to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Apify and TinyFish
Detailed info you need to know about Apify and TinyFish integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Apify to TinyFish
Set up your Apify and TinyFish integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Apify and TinyFish nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Apify and TinyFish. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Apify and TinyFish work in WEXTL?
WEXTL exposes actions and triggers for Apify and TinyFish that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Apify triggersTinyFish actions
Apify modules
- Add Request to QueueCreates request to queue.
- Batch Add RequestsPerforms batch add requests.
- Build ActorBuilds actor.
- Charge Events in RunCharges events in run.
- Create ActorCreates actor.
- Create DatasetCreates dataset.
- Create Environment VariableCreates environment variable.
- Create Key-Value StoreCreates key-value store.
- Create Request QueueCreates request queue.
- Create ScheduleCreates schedule.
- Create TaskCreates task.
- Create VersionCreates version.
- Decode and Verify DataRetrieves decode and verify data.
- Delete ActorDeletes actor.
- Delete Build (Abort)Aborts build.
- Delete Build (Abort, Cross-Actor)Aborts build (cross-actor).
- Delete DatasetDeletes dataset.
- Delete Environment VariableDeletes environment variable.
- Delete Key-Value StoreDeletes key-value store.
- Delete RecordDeletes record.
- Delete RequestDeletes request.
- Delete Request QueueDeletes request queue.
- Delete Run (Abort)Aborts an Actor run (DELETE semantics).
- Delete Run (Abort, Cross-Actor)Aborts run (cross-actor).
- Delete ScheduleDeletes schedule.
- Delete TaskDeletes task.
- Delete VersionDeletes version.
- Delete WebhookDeletes webhook.
- Download Records (Batch Export)Retrieves download records (batch export).
- Encode and Sign DataEncodes and sign data.
- Get ActorReturns actor.
- Get Browser InfoReturns browser info.
- Get Browser Info (POST Variant)Returns browser info (post variant).
- Get BuildReturns build.
- Get Build (Cross-Actor)Returns build (cross-actor).
- Get Build LogReturns build log.
- Get Build Log (Cross-Actor)Returns build log (cross-actor).
- Get DatasetReturns dataset.
- Get Dataset ItemsReturns dataset items.
- Get Dataset StatisticsReturns dataset statistics.
- Get Default BuildReturns default build.
- Get Environment VariableReturns environment variable.
- Get Environment VariablesReturns environment variables.
- Get Key-Value StoreReturns key-value store.
- Get Last Task RunReturns last task run.
- Get List of ActorsReturns list of actors.
- Get List of BuildsReturns list of builds.
- Get List of DatasetsReturns list of datasets.
- Get List of Key-Value StoresReturns list of key-value stores.
- Get List of KeysReturns list of keys.
TinyFish modules
- Cancel RunCancel a running automation that was started asynchronously.
- Create a Browser SessionCreate a remote browser session and retrieve a CDP connection URL.
- Create a Vault ConnectionConnect a password manager and sync available credential items.
- Delete a Browser SessionTerminate an active browser session.
- Delete Vault ProviderDisconnect a vault provider and remove cached credential items.
- Fetch ContentFetch and extract clean content from one or more URLs.
- Get a RunRetrieve the current or final state of an automation run.
- List Fetch UsageSearch and filter fetch operation history.
- List RunsSearch and filter automation runs.
- List Vault ConnectionSearch and filter vault provider connections linked to the account.
- List Vault ItemsRetrieve available credential items for automation runs.
- Make an API CallExecutes a custom authenticated request to any TinyFish API endpoint.
- Run AutomationRun an AI-powered browser automation workflow on a website and wait for the final result.
- Run Automation AsyncStart an AI-powered browser automation workflow and return the run ID immediately.
- Search WebSearch the web and retrieve structured search results.
- Sync Vault ItemsSync the latest credential items from connected vault providers.
- Watch Fetch UsageTriggers when new fetch usage records are created.
- Watch RunsTriggers when automation runs are created or their status changes.
Frequently asked questions
Common questions about connecting Apify and TinyFish.
Connect your Apify and TinyFish accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Apify's "Watch Run Aborted" fires, WEXTL can "Cancel Run" in TinyFish. Apify has 4 triggers (including Watch Run Aborted, Watch Run Failed, and Watch Run Succeeded); TinyFish has 16 actions (including Cancel Run, Create a Browser Session, and Create a Vault Connection). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Apify-to-TinyFish automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Apify (or TinyFish) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Apify + TinyFish automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Apify and TinyFish integration.
- Apify and TinyFish integration source code, module specs and credentials implementation.
- Our Apify and TinyFish integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Apify and TinyFish — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Apify integration information
- TinyFish integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library