Apify and Supadata Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep Apify and Supadata matched by integrating their events and actions. When developer tools events happen in Apify, update the Supadata automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Apify and Supadata

Detailed info you need to know about Apify and Supadata integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Apify

    • Developer Tools
    • 4 triggers
    • 55 searches
    • 60 actions

    Run Apify Actors and tasks, manage datasets and stores, and watch for Actor run completion events.[5]

  • Supadata

    • Developer Tools
    • 15 searches
    • 5 actions

    Video transcripts, social media data and web page content as clean text.[6]

How to connect Apify to Supadata

Set up your Apify and Supadata integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Apify and Supadata work in WEXTL?

WEXTL exposes actions and triggers for Apify and Supadata that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Apify triggersSupadata actions

Apify modules

  • Abort a Build Aborts a build while it is still running and ends its work early.
  • Abort a Build (Cross-Actor) Ends a build directly through its Build, without first naming the Actor that owns it.
  • Abort a Run Cancels a run that has not finished yet and halts whatever the Actor was doing.
  • Abort a Run (Cross-Actor) Terminates a run directly through its Run, with no Actor needed.
  • Add a Request to a Queue Puts a single new request into a request queue, where it waits to be processed.
  • Batch Add Requests Adds up to 25 requests to a request queue in one call, each with a Unique key, URL, Method and Payload. Turn on Add to the front to place them at the head of the queue.
  • Build an Actor Kicks off a new build for an Actor, producing a build record with a Status and Data.
  • Charge Events in a Run Applies charges for events to an Actor run, identified by its Actor and Run.
  • Create a Dataset Sets up a dataset in Apify storage and returns its Created at time.
  • Create a Key-Value Store Opens a new key-value store, a place that keeps records under keys.
  • Create a Request Queue Opens a new request queue that holds requests waiting to be processed.
  • Create a Schedule Registers a schedule through Apify and returns its Name.
  • Create a Task Saves a task with Apify and returns its Updated at time.
  • Create a Version Attaches another version to an Actor, alongside the ones it already has.
  • Create an Actor Creates an Actor in Apify and returns its ID and Name.
  • Create an Environment Variable Defines a new environment variable on a particular Version of an Actor.
  • Decode and Verify Data Decodes an encoded value and verifies it, the reverse of Encode and Sign Data.
  • Delete a Dataset Removes a dataset from your Apify storage.
  • Delete a Key-Value Store Deletes a key-value store held in your Apify storage.
  • Delete a Record Removes the record kept under a given Recordkey in a key-value store.
  • Delete a Request Removes the request with a given Requestid from a request queue.
  • Delete a Request Queue Deletes a request queue from your Apify storage.
  • Delete a Schedule Removes a schedule that exists in your Apify account.
  • Delete a Task Deletes a stored task from your account.
  • Delete a Version Removes a version that was attached to an Actor.
  • Delete a Webhook Deletes a webhook configured on your Apify account.
  • Delete an Actor Deletes an Actor from your Apify account.
  • Delete an Environment Variable Removes an environment variable from the chosen Actor Version.
  • Download Records (Batch Export) Downloads every record kept in a key-value store as one batch export.
  • Encode and Sign Data Encodes and signs data, producing a value that Decode and Verify Data can check.
  • Get a Build Reads a build of an Actor and reports its Status and last update.
  • Get a Build (Cross-Actor) Reads a build straight from its Build, even when the owning Actor is not known.
  • Get a Build Log Returns the log text that was produced while a build ran.
  • Get a Build Log (Cross-Actor) Returns the log text of a build addressed by Build alone, whichever Actor it belongs to.
  • Get a Dataset Reads the details of a dataset, including its Name and creation time.
  • Get a Key-Value Store Reads the details of a key-value store such as its Name and timestamps.
  • Get a Record by Key Reads the record kept under a given Recordkey in a key-value store.
  • Get a Request Reads a single request from a request queue by its Requestid, including its Status and Data.
  • Get a Request Queue Returns a request queue with its Name and creation time.
  • Get a Run Fetches a single Actor run together with its Status and Updated at.
  • Get a Run (by ID, Cross-Actor) Reads a run straight from its Run, regardless of the Actor behind it.
  • Get a Schedule Returns a schedule with its Name, Status and Created at.
  • Get a Schedule Log Returns the log describing what a schedule has done so far.
  • Get a Task Reads the stored configuration of a task, along with its timestamps.
  • Get a Task Input Reads the input values that are stored with a task and used when it runs.
  • Get a Version Reads a version of an Actor together with its Name and timestamps.
  • Get a Webhook Returns a webhook configuration with its Name and timestamps.
  • Get a Webhook Dispatch Reads a single webhook dispatch by its Dispatchid, including its Status.
  • Get an Actor Looks up an Actor and returns its ID, Name, Status and Data.
  • Get an Environment Variable Reads a single environment variable defined for an Actor Version, with its Name.

Supadata modules

  • Create a Website Crawl Starts a crawl across a whole site beginning at its URL and returns a Job ID for Get a Website Crawl. Use Limit to cap the number of pages visited, since each page costs a credit.
  • Create a YouTube Transcript Batch Queues transcripts for many videos at once. Name a Playlist or a Channel, or list the Video IDs yourself. Use Language to request one language and Limit to cap the count. Returns the Job ID.
  • Create a YouTube Video Batch Queues a metadata lookup for a group of videos. Give Video IDs, or name a Playlist or Channel to cover its videos, and use Limit to cap the group size. Returns the Job ID.
  • Create an Extract Job Starts an AI extraction on a video or direct media file at its URL, up to 3 hours long. Use Prompt to say in plain language what to pull out and Schema to shape the result, then read it with Get an Extract Job.
  • Get a Transcript Fetches the written text of a video at its URL. Use Mode to choose native or generated captions and Chunk Size to split long text. Large videos return a Job ID.
  • Get a Transcript Job Follows a long transcript request by its Job ID. Reports the Status and, once finished, the Content with its Lang.
  • Get a Website Crawl Reads a crawl made with Create a Website Crawl, using its Job ID. Reports the Status and lists the Pages found. Use Skip to jump past pages already read.
  • Get a YouTube Batch Reads a batch started earlier by its Job ID, with Status, Results, Stats and Completed At. Use Offset and Limit to page through the results.
  • Get a YouTube Channel Looks up a channel by Channel link or handle and reports its Name, Handle, Subscriber Count, Video Count and View Count.
  • Get a YouTube Playlist Fetches playlist details for a Playlist link or ID, including its Title, Video Count, View Count, Last Updated date and Channel.
  • Get a YouTube Translated Transcript Translates the transcript of a YouTube video. Use Language to set the target language, give the video as URL or Video ID, and turn on Text to get one plain text instead of timed chunks.
  • Get an Extract Job Checks an extraction started with Create an Extract Job, using its Job ID. Reports the Status and, when done, the Data and Schema.
  • Get Post Metadata Reads the details of a social media post from its URL, such as Platform, Type, Title, Description and Author.
  • Get the Account Shows your Supadata plan with the Organization ID, Max Credits and Used Credits.
  • Get Web Page Content Scrapes a page at its URL into readable text, with Name, Description and Count Characters. Turn on No Links to leave the links out of the Markdown.
  • List Website Links Crawls a site map starting at its URL and lists the Urls it contains.
  • List YouTube Channel Videos Collects what a channel has published, split into regular videos, Short IDs and Live IDs. Use Type to keep one kind and Limit to stop early.
  • List YouTube Playlist Videos Lists the videos in a playlist as Video IDs. Use Limit to stop after a set number of IDs.
  • Make an API Call Calls the Supadata REST API directly with a free-form request under your saved credential.
  • Search YouTube Searches YouTube for a Query and returns Results with the Total Results. Narrow it with Type, Upload Date, Duration or Features, order it with Sort By, and continue with Next Page Token.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Apify and Supadata integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Apify and Supadata on WEXTL®

Claim your 3-day trial to build Apify with Supadata integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Apify and Supadata.

How do I connect Apify and Supadata?

Connect your Apify and Supadata 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]

What can I automate between Apify and Supadata?

Example: when the "Watch Aborted Runs" trigger in Apify fires, WEXTL can "Create a Website Crawl" in Supadata. Apify has 4 triggers (including Watch Aborted Runs, Watch Failed Runs, and Watch Succeeded Runs). Supadata has 20 actions (including Create a Website Crawl, Create a YouTube Transcript Batch, and Create a YouTube Video Batch). Add filters and transforms between steps when you need them.[1]

Can Apify trigger actions in Supadata, and Supadata in Apify?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Apify and Supadata?

No. Apify-to-Supadata automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Apify integrate with Supadata in real time?

Yes. Trigger-based automations start the moment Apify (or Supadata) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Apify + Supadata integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Apify with Supadata?

You can build your Apify + Supadata automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Apify and Supadata integration.

  1. Apify and Supadata integration source code, module specs and credentials implementation.
  2. Our Apify and Supadata integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Apify and Supadata, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Apify integration information
  6. Supadata integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Apify and Supadata integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Apify and Supadata, or get started