Apify and Vercel Integration

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

Build developer tools workflows between Apify and Vercel on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

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

Learn about Apify and Vercel

Detailed info you need to know about Apify and Vercel 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]

  • Vercel

    • Developer Tools
    • 2 triggers
    • 53 searches
    • 69 actions

    Frontend cloud for deploying and hosting web projects.[6]

How to connect Apify to Vercel

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

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

WEXTL exposes actions and triggers for Apify and Vercel 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 triggersVercel 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.

Vercel modules

  • Add a Domain Adds a domain to your Vercel account from its Domain Name. Use Method to add one you own or move one in from elsewhere, Create DNS Zone to create its zone as well, and Enable CDN to switch on the Vercel CDN.
  • Add a Firewall Bypass Rule Adds a rule that lets traffic from a Source IP, an address or CIDR range, skip the project firewall. Use Domain to limit it to one domain and Duration for the minutes it lasts.
  • Add a Project Domain Connects a hostname to a Vercel project. Use Git Branch to serve it from a branch instead of production, Custom Environment for a custom environment, and Redirect To to forward it to another domain or URL.
  • Add a Project Member Grants a person one of the roles Admin, Developer or Viewer on a project via Project Role. Use Team Member for someone on the team, or Email when no team member is picked.
  • Approve a Rolling Release Stage Advances a rolling release to a later stage for its Canary Deployment, and reports the Active Stage and Current Canary Percentage.
  • Assign an Alias to a Deployment Makes a deployment answer on a hostname such as staging.example.com. Use Redirect To to send the Alias to another hostname instead. You receive the Alias and the Old Deployment ID.
  • Cancel a Deployment Halts a deployment while it is building or queued. You receive the deployment with its Ready State and URL.
  • Complete a Rolling Release Finishes a rolling release by sending all traffic to the Canary Deployment. You receive the Active Stage and Current Deployment.
  • Create a Custom Environment Builds a custom environment for a project under a Slug of up to 32 characters. Use Branch Match to send matching branches to it, and Copy Variables From or Copy From Custom Environment to start from existing variables.
  • Create a Deployment Starts a deployment of a project from a connected Git repository or from uploaded files, set through Source. Leave Target blank for a preview, and turn on Force New Deployment to build again even when nothing changed.
  • Create a DNS Record Adds a DNS record of a chosen Type to a domain. Use Name for a subdomain such as www, or leave it blank for the domain itself. Use TTL for a lifetime in seconds, at least 60.
  • Create a Project Sets up a Vercel project. Leave Framework blank to let Vercel detect it, use Git Provider to connect a repository so pushes deploy, and Root Directory for the folder of the project inside the repository.
  • Create a Project Environment Variable Defines a variable on a project with a Name, Value and Type of Encrypted, Plain Text or Sensitive. Choose Targets for the environments it covers, and turn on Replace If It Exists to overwrite a variable with the same name and target instead of failing.
  • Create a Team Creates a Vercel team from a Slug of up to 48 characters, with an optional Name. You receive the team ID and Slug.
  • Create an Access Group Creates an access group with a Name of up to 50 characters. Use Project Roles to give the group a role on specific projects and Members To Add to put team members in it. You receive the Access Group ID.
  • Create an Edge Config Makes an Edge Config from a Slug of lowercase letters, digits, hyphens and underscores. Use Items to start it with values, which stay masked in run logs.
  • Create Shared Environment Variables Sets up to 50 shared Variables in one call, each stored with a Type of Encrypted or Sensitive for the chosen Targets. Link them to projects through Projects.
  • Delete a Certificate Deletes a certificate. This cannot be undone, so turn on Confirm to proceed.
  • Delete a Custom Environment Removes a custom environment. Turn on Also Delete Unassigned Variables to delete variables that belong to no other environment.
  • Delete a Deployment Removes a deployment. Switch on Confirm to go ahead, since there is no undo.
  • Delete a DNS Record Deletes a DNS record on a domain. Turn on Confirm to proceed, since deletion cannot be undone.
  • Delete a Domain Deletes a domain. Turn on Confirm to proceed, as there is no undo.
  • Delete a Drain Removes a log drain once Confirm is switched on. Deletion cannot be undone.
  • Delete a Feature Flag Deletes a feature flag from its project. Switch on Confirm to continue, as undoing is not possible.
  • Delete a Project Removes a project from Vercel. Turn on Confirm to proceed, because this cannot be undone.
  • Delete a Project Check Deletes a check defined on a project. Turn on Confirm to proceed.
  • Delete a Project Environment Variable Removes a project variable, either everywhere or only from one custom environment through Custom Environment. Turn on Confirm to proceed.
  • Delete a Team Deletes a team, which cannot be undone once Confirm is on. Set New Default Team to the team that should become your default afterwards.
  • Delete a Webhook Deletes a webhook. If a workflow trigger relies on it, turn that trigger off instead. Turn on Confirm to proceed.
  • Delete an Access Group Deletes an access group from the team. Turn on Confirm to go ahead, as this cannot be undone.
  • Delete an Access Token Revokes an access token. Turn on Confirm to proceed, and note that deleting the token this credential uses breaks the credential.
  • Delete an Alias Removes a hostname alias pointing at a deployment. Turn on Confirm to proceed.
  • Delete an Edge Config Turn on Confirm to delete an Edge Config. There is no way to undo it.
  • Delete an Edge Config Item Removes the item stored under a Key inside a config store.
  • Delete Multiple Project Environment Variables Deletes up to 1000 variables of one project in a single call, reporting the Deleted count and the Ids. Turn on Confirm to proceed.
  • Delete Shared Environment Variables Removes up to 50 shared variables at once, reporting any Failed deletions. Turn on Confirm first.
  • Get a Certificate Shows a certificate with its Cns, Auto Renew setting and Expires At date.
  • Get a Custom Environment Returns a custom environment with its Slug, Branch Matcher and Domains.
  • Get a Deployment Retrieves a deployment with its Ready State, URL, Target and Inspector URL. Turn on Include Git Info to add the Git repository details.
  • Get a Domain Gets a domain on your account with its Verified flag, Nameservers, Intended Nameservers and Expires At date.
  • Get a Domain Configuration Reviews how a domain is set up in DNS, flagging a Misconfigured domain and showing Configured By. Add Project to look at one project.
  • Get a Domain Price Looks up the Purchase Price, Renewal Price and Transfer Price of a Domain Name. Use Years to price a longer term, or leave it blank for the shortest term the domain allows.
  • Get a Drain Reads a log drain with its Name, Project Ids and Disabled Reason. Turn on Include Delivery Stats to add its delivery health.
  • Get a Feature Flag Fetches a feature flag with its Kind, State, Environments and Maintainer Ids.
  • Get a Project Retrieves a project with its Framework, Node Version, Build Command and Root Directory.
  • Get a Project Check Reads a project check with its Name, Source, Requires and whether it Is Rerequestable.
  • Get a Project Domain Looks up a domain attached to a project, showing its Verified flag, Redirect and Git Branch.
  • Get a Project Environment Variable Reads a project variable with its Key, Type, Target and Value. The real Value enters the run history, and sensitive variables return no value.
  • Get a Rolling Release Reads rolling release progress on a project, with its Active Stage, Current Canary Percentage and Stages. Use State to filter by whether it is Active, Complete or Aborted.
  • Get a Rolling Release Configuration Returns how rolling releases are set up for a project: the Target, the Gate, the Stages and the Canary Response Header.

Explore alternative integrations

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

Automate Apify and Vercel on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Apify and Vercel.

How do I connect Apify and Vercel?

Connect your Apify and Vercel 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 Vercel?

Example: when the "Watch Aborted Runs" trigger in Apify fires, WEXTL can "Add a Domain" in Vercel. Apify has 4 triggers (including Watch Aborted Runs, Watch Failed Runs, and Watch Succeeded Runs). Vercel has 122 actions (including Add a Domain, Add a Firewall Bypass Rule, and Add a Project Domain). Add filters and transforms between steps when you need them.[1]

Can Apify trigger actions in Vercel, and Vercel 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 Vercel?

No. Apify-to-Vercel 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 Vercel in real time?

Yes. Trigger-based automations start the moment Apify (or Vercel) 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 + Vercel 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 Vercel?

You can build your Apify + Vercel 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 Vercel integration.

  1. Apify and Vercel integration source code, module specs and credentials implementation.
  2. Our Apify and Vercel integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Apify and Vercel, 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. Vercel 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 Vercel integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Apify and Vercel, or get started