Resources · Make integration

Skyvern AI Make integrationAutomate Skyvern AI with Make.

Can Make start a Skyvern AI task for you and bring the result back? Yes: the Skyvern AI Make integration gives you 8 modules, 7 actions and 1 search, with no trigger of their own. This guide connects your account with an API key, then walks you through a first scenario.

Try the Skyvern AI integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Skyvern AI Make integration let you automate?

The Skyvern AI Make integration links your Skyvern AI account to Make, a tool where you chain apps together without code. Inside a scenario (the automation you build in Make), you can launch tasks and workflows in Skyvern AI, then read back their details to pass them on to another app.

Launch work from an event elsewhere. A new row in a sheet or a form submission can start a scenario that calls Run a Task V2 or Run a Workflow. The event comes from another app, because Skyvern AI has no trigger module in Make.

Read a result and route it. Once a task exists, Get a Task V2 or Get a Workflow fetches its details so the next module can file them, post them or store them.

Check which accounts you can reach. List Organizations is the only search module here: it can return zero, one or several organizations, each as its own bundle (one item passed to the next module).

What Make does not do for this app: nothing reacts on its own when something changes in Skyvern AI, so the scenario starts from a schedule or from another app. When the 8 modules fall short, Make an API Call reaches the rest of the Skyvern AI API with the same connection. To see how Make compares with a similar tool, read n8n vs Make, and to check what each plan includes, open Make pricing.

Connect

How do you connect your Skyvern AI account to Make?

  1. 01

    Copy your API key

    In Skyvern AI, open Settings and copy the API key shown on the screen. You need an active Skyvern AI account first; if you do not have one, create it before going further.

  2. 02

    Add a module and open the connection

    In your Make scenario, add any Skyvern AI module, then click Create a connection. A connection is your account linked to Make once and reused by every Skyvern AI module afterwards.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like, it is optional. Paste the API key, or follow the instructions Make shows on screen, and save.

First scenario

Your first scenario with Skyvern AI in Make

GoalWhen a new request lands in another app, Make starts a Skyvern AI task and then fetches its details.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app that holds your requests as the first module, for example a sheet or a form.

  2. 02

    Add Run a Task V2

    Click the + to the right of that first module, search for Skyvern AI and choose Run a Task V2. Select your connection, then map data from the first module into its fields.

  3. 03

    Fetch the task with Get a Task V2

    Add Get a Task V2 right after. Map into it what Run a Task V2 returned to identify the task (the Run once bundle shows it), so Make reads back the task it just launched.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time; open the bubble on each module to read the bundles it received and check that the task was created in Skyvern AI.

  5. 05

    Schedule it and switch it on

    Set the schedule on the first module (every 15 minutes by default, 15 minutes at the shortest on the Free plan) and switch the scenario on. Each module run counts as an operation on your plan.

Modules

The 8 Skyvern AI modules in Make

Skyvern AI gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Skyvern AI1

Get a Task

ActionIn the docs only

Pulls the details of one existing Skyvern AI task into your scenario, so a later module can store or send them.

When to use it
your tasks were launched with Run a Task, the first version, and you want to read one back by its reference.
Watch out
keep the same version on both ends; Make lists this module and Get a Task V2 side by side, and the doc does not explain what separates them.
Skyvern AI2

Get a Task V2

ActionIn the docs only

Reads back a task started through the V2 modules. You then map its details into whatever comes next.

When to use it
right after Run a Task V2, to hand the task details to a sheet, a chat app or your CRM.
Watch out
the Make doc describes neither version. Before you commit to one, run both on a test task and compare what each bundle holds.
Skyvern AI3

Get a Workflow

ActionIn the docs only

Brings a Skyvern AI workflow and its details into Make, so you can check it or pass its information along without opening Skyvern AI.

When to use it
before Run a Workflow, to confirm you are pointing at the right one, or afterwards to log what ran.
Watch out
it reads, it does not start anything; launching is the job of Run a Workflow.
Skyvern AI4

List Organizations

SearchIn the docs only

Returns the organizations your connection can see, each one as a separate bundle, which helps when an account spans several of them.

When to use it
at the start of a scenario, to find out which organization the next modules should work in.
Watch out
as a search it can return zero, one or many results, and every result makes the following modules run once more, each run counting as an operation.
Skyvern AI5

Make an API Call

ActionIn the docs only

Lets you call any endpoint of the Skyvern AI API from your scenario, reusing the connection you already created, with no extra key to paste.

When to use it
the action you need is not among the seven other modules, and the Skyvern AI API offers it.
Watch out
here you write the request yourself, so keep the Skyvern AI API documentation open while you fill it in.
Skyvern AI6

Run a Task

ActionIn the docs only

Starts a new task in your Skyvern AI account from inside a scenario, using data mapped from the modules that come before it.

When to use it
your existing setup already relies on the first version, and you want each new sheet row or form entry to launch a task.
Watch out
read the result back with Get a Task, not the V2 module, so both steps stay on the same version.
Skyvern AI7

Run a Task V2

ActionIn the docs only

Launches a Skyvern AI task through the V2 module. What it returns is not described in the doc; check its bundle after a Run once to find what the next step can reuse.

When to use it
you are building a new scenario and want an event in another app, such as a submitted request, to kick off a task.
Watch out
test it with Run once on a harmless task first, since each run creates real work in your Skyvern AI account.
Skyvern AI8

Run a Workflow

ActionIn the docs only

Triggers one of your saved Skyvern AI workflows from Make, which saves you from rebuilding its steps inside the scenario.

When to use it
the job already exists as a workflow in Skyvern AI and you only need Make to start it when an outside event happens.
Watch out
pair it with Get a Workflow if you need to confirm which workflow the scenario is about to run.
Need help

Need help automating Skyvern AI with Make?

A person reads every message.

FAQ

Skyvern AI and Make: common questions

01Is the Skyvern AI Make integration free?
Yes, on the Make side. Skyvern AI is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, 15 minutes at the shortest between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans go down to a 1 minute interval with unlimited active scenarios. Your Skyvern AI subscription is a separate matter, covered on the Skyvern AI pricing page.
02What do you need to connect Skyvern AI to Make?
An active Skyvern AI account and its API key. You find the key under Settings in Skyvern AI and copy it. In Make, add any Skyvern AI module, click Create a connection, name it if you want, then paste the key or follow the instructions on screen. The connection is created once and every Skyvern AI module in your scenarios reuses it, so you never paste the key twice, even across several scenarios.
03Does the Skyvern AI integration in Make react in real time?
No, not by itself. Skyvern AI has no trigger module in Make, so nothing fires when something changes on its side. You start the scenario in one of two ways: put another app's trigger first, such as a new form entry, or let the scenario run on its schedule, every 15 minutes by default and every minute at the shortest on a paid plan. The Skyvern AI modules then act in that flow.
04What if a Skyvern AI module is missing in Make?
Use Make an API Call. That module can reach any endpoint of the Skyvern AI API with the connection you already set up, so you are not limited to the seven other modules. You write the request yourself, which means keeping the Skyvern AI API documentation nearby. Note also that the Make doc for this app is generated from the vendor documentation and may contain mistakes, so check anything important with Skyvern AI.
05Should you use Make or n8n for Skyvern AI?
It depends on the tool your team already works in. On Make, Skyvern AI brings 8 modules, 7 actions and 1 search, plus Make an API Call for whatever they leave out, and it runs from the Free plan. The same app often has an n8n node as well. Compare the modules each side offers against the tasks and workflows you plan to run, then choose the tool whose editor you already know.
Same platform

Other docs you might need on this stack.

Browse all integrations