Integrate n8n with Skyvern
Add browser automation to any n8n workflow, including on websites with no API.
Get the n8n nodeOpens Skyvern's listing on n8n.io.
- Maintained by
- Built by Skyvern, verified by n8n
- Works with
- Skyvern Cloud and self-hosted Skyvern
- You need
- An organization API key
Who calls whom
- n8n workflow
- Skyvern node
- Cloud browser on the website
- Result back in n8n
How it works
n8n connects the apps that have APIs. Skyvern handles the websites that don't. A node in your n8n workflow starts a Skyvern agent or task. Skyvern opens a cloud browser, logs in and does the work on the site. A second node gets the result with the run ID, so the next step in n8n can use it.
Example: a new support ticket starts your n8n workflow. The Skyvern node runs your claim status agent on a payer portal with the member ID from the ticket, and a later node writes the status back to the ticket.
What you can do
Resources and operations of the Skyvern node
Dispatch a Workflow Run
Start an agent you built in Skyvern and fill its inputs from earlier nodes. The node calls an agent a workflow.
Get a Workflow Run
Fetch the status and output of a run with its run ID, which starts with wr_.
Dispatch a Task
Give Skyvern a URL and a prompt for a one-off job, with no saved agent.
Get a Task
Fetch the result of a task with its task ID.
Setup
Before you start
- A Skyvern account (14-day free trial)
- An agent built in Skyvern
- An n8n instance, and its owner or admin for the one-time install
- 01
Install the verified node
An n8n instance owner or admin opens the Nodes panel, finds Skyvern under "More from the community" and selects Install. After that, everyone on the instance can add the node.
n8n Nodes panel - Search:
- Skyvern
- Section:
- More from the community
- Button:
- Install
- 02
Copy your API key
In the Skyvern app, open Settings, then API keys, and copy your organization key.
Skyvern app - Page:
- Settings → API keys
- Header it is sent in:
x-api-key
- 03
Create the Skyvern credential
In n8n, create a Skyvern API credential with the key. Keep the default Base URL for Skyvern Cloud. For self-hosted Skyvern, enter your API origin without
/api/v1.Skyvern API credential - API Key:
- your organization key
- Base URL:
https://api.skyvern.com
- 04
Run your agent
Add the Skyvern node and choose the Workflow resource, which is the node's name for an agent. Then choose the dispatch operation, pick your agent and map its inputs.
Skyvern node - Resource:
- Workflow
- Operation:
- Dispatch a Workflow Run
- Workflow Name or ID:
- your agent
- 05
Get the result
Add a second Skyvern node with the Get operation. Select the same agent and pass the run ID that the first node returned.
Skyvern node - Operation:
- Get a Workflow Run
- Workflow Name or ID:
- the same agent
- Workflow Run ID:
wr_…from the first node
FAQ
Does the website need an API?
No. Skyvern works through the website's normal interface, the same way a person would.
How do I get the result back into n8n?
Use the Get operation with the run ID that the dispatch operation returns. A run can finish after the dispatch node returns, so get the result in a later step, or give the dispatch node a webhook callback URL that Skyvern calls when the run ends.
Does it work with self-hosted Skyvern?
Yes. The credential has a Base URL field. Enter your deployment's API origin, without /api/v1, and make sure your n8n instance can reach it.
Who can install the node?
The verified node needs a one-time install by an n8n instance owner or admin. On n8n Cloud the owner controls verified nodes in the Cloud Admin Panel. On self-hosted n8n the admin controls them with environment variables.
Where can I watch the runs?
Every run started from n8n appears in your Skyvern run history like any other run.
Ready to automate your portal workflows?
14-day free trial. Cancel any time.