Skip to main content
Connect Skyvern with 7,000+ apps using Zapier to automate browser-based tasks in your workflows.

​
Overview

The Skyvern Zapier integration allows you to trigger browser automation tasks from any Zapier-connected app. Common use cases include:
  • Automatically fill forms when new leads arrive in your CRM
  • Extract data from websites when triggered by schedule or events
  • Complete repetitive web-based workflows based on spreadsheet updates
  • Download files from web portals when new entries are detected

​
Prerequisites

​
Setup

1

Get your Skyvern API key

  1. Log in to app.skyvern.com
  2. Navigate to Settings
  3. Copy your API key
2

Create a Zap

  1. Go to Zapier and click Create Zap
  2. Choose your trigger app (e.g., Google Sheets, Webhook, Schedule)
  3. Configure the trigger event and test it
3

Add Skyvern action

  1. Click + to add an action
  2. Search for Skyvern and select it
  3. Choose Run a Task as the action event
  4. Connect your Skyvern account using your API key
4

Configure the task

Map your trigger data to Skyvern task parameters:
  • URL: The starting URL for the task
  • Navigation Goal: Natural language description of what to do
  • Data Extraction Schema (optional): JSON schema for extracting data
  • Navigation Payload (optional): Form data to submit
5

Test and activate

Test your Zap to ensure it works correctly, then turn it on.

​
Example Zap: Form Filling from Google Sheets

This example automatically fills contact forms when new rows are added to a Google Sheet.

​
Trigger: New Row in Google Sheets

  • App: Google Sheets
  • Trigger: New Spreadsheet Row
  • Spreadsheet: Your contact form data sheet

​
Action: Run Skyvern Task

  • URL: Map from sheet column (e.g., “Contact Form URL”)
  • Navigation Goal: “Fill out the contact form and submit it”
  • Navigation Payload:
{
  "name": "{{Name}}",
  "email": "{{Email}}",
  "company": "{{Company}}",
  "message": "{{Message}}"
}

​
Available Actions

​
Run a Task

Executes a Skyvern automation task. Input Fields:
  • URL (required): Starting URL for the task
  • Navigation Goal (required): What the task should accomplish
  • Navigation Payload (optional): JSON object with form data
  • Data Extraction Schema (optional): JSON schema for data extraction
  • Webhook Callback URL (optional): URL to receive completion notification
Output Fields:
  • Task ID: Unique identifier for the task
  • Status: Current task status
  • Recording URL: Link to view the task execution
  • Extracted Data: Any data extracted during the task

​
Get Task Status

Retrieves the status and results of a previously run task. Input Fields:
  • Task ID (required): The ID from a previous task run
Output Fields:
  • Status: completed, failed, running, queued
  • Extracted Data: Results from the task
  • Failure Reason: Error message if task failed
  • Recording URL: Link to execution recording

​
Tips and Best Practices

Use delays for long-running tasks: If your task takes more than 30 seconds, use Zapier’s delay action before checking task status.
API rate limits: Zapier free plans have task limits. Check your plan’s limits to avoid interruptions.
  • Keep navigation goals clear: Write specific, actionable instructions
  • Test with real data: Use Zapier’s test feature with actual data before going live
  • Handle failures gracefully: Add error handling paths in your Zaps
  • Monitor task status: Set up notifications for failed tasks

​
Common Issues

​
Task times out

Increase the timeout setting or break complex tasks into multiple steps.

​
Authentication fails

Verify your API key is correct and hasn’t expired. Generate a new one if needed.

​
Data extraction returns empty

Check that your extraction schema matches the website’s structure. Test the task manually first.

​
Support

For Zapier integration issues:

​
Next Steps

Task Parameters

Learn about all available task configuration options

Data Extraction

Extract structured data from websites

Webhooks

Get notified when tasks complete

API Reference

Full API documentation

Build docs developers (and LLMs) love

Get started for freeTalk to us