Make.com Integration

​

Overview

• Automated form submissions from multiple data sources
• Web scraping triggered by schedules or events
• Multi-step workflows combining web automation with other services
• Batch processing of web-based tasks

​

Prerequisites

• Make.com account (free or paid)
• Skyvern API key from app.skyvern.com
• Understanding of Make scenarios

​

Setup

​

Blueprint Template: Contact Form Automation

​

Import the Blueprint

1. Download the blueprint: contact_form_make.com_blueprint.json
2. In Make.com, click Scenarios > Import Blueprint
3. Upload the JSON file
4. Configure your connections:
   • Google Sheets connection
   • Skyvern connection (use your API key)

​

Blueprint Structure

1. Watch Rows (Google Sheets): Monitors for new rows with contact form data
2. Filter: Only processes rows marked “Send to Skyvern = TRUE”
3. Run a Task (Skyvern): Executes the form filling task
4. Sleep Modules: Waits for task completion (5 minutes total)
5. Get Task (Skyvern): Retrieves final task status
6. Update Row (Google Sheets): Writes back task ID, status, and results

​

Customizing the Blueprint

{
  "full_name": "{{Name}}",
  "email_address": "{{Email}}",
  "phone": "{{Phone}}",
  "company_name": "{{Company}}",
  "message": "{{Message}}"
}

​

Available Modules

​

Run a Task V1

• URL (required): Starting URL
• Navigation Goal (required): Task instructions in natural language
• Navigation Payload (optional): Form data as JSON
• Data Extraction Schema (optional): Schema for extracting structured data
• Max Steps Overrides (optional): Maximum steps before timeout
• Webhook Callback URL (optional): Endpoint to notify on completion

• task_id: Unique task identifier
• status: Current status (created, running, completed, failed)
• request: Original request parameters

​

Get Task

• Task ID (required): ID from a previous “Run a Task” module

• task_id: Task identifier
• status: completed, failed, running, queued
• extracted_information: Data extracted from the website
• failure_reason: Error details if failed
• recording_url: Link to watch task execution

​

Example Scenarios

​

Scenario 1: Scheduled Data Extraction

1. Schedule: Trigger every day at 9 AM
2. Skyvern - Run Task: Extract product prices from competitor website
3. Google Sheets - Add Row: Save extracted data
4. Gmail - Send Email: Send summary to team

​

Scenario 2: Lead Processing Pipeline

1. Webhook: Receive new lead from website
2. Skyvern - Run Task: Submit lead to partner portal
3. Sleep: Wait 2 minutes
4. Skyvern - Get Task: Check completion status
5. Router:
   • If success → Update CRM
   • If failed → Send alert to team

​

Scenario 3: Bulk Form Submissions

1. Google Sheets - Watch Rows: Monitor spreadsheet for new entries
2. Filter: Only process rows with “Status = Pending”
3. Skyvern - Run Task: Fill and submit form
4. Sleep: Wait for completion
5. Skyvern - Get Task: Get results
6. Google Sheets - Update Row: Mark as completed with task details

​

Tips and Best Practices

• Test with one item first: Use the “Run once” feature to test before processing batches
• Add error handling: Use error handler routes for robust scenarios
• Set appropriate timeouts: Add enough sleep time for complex tasks
• Store task IDs: Keep track of task IDs for debugging and status checks
• Use Make’s scheduling: Space out high-volume automations to avoid rate limits

​

Common Issues

​

Connection fails

• Verify your API key is correct
• Ensure you’re using the API key from app.skyvern.com
• Try creating a new connection

​

Task doesn’t complete

• Check if the wait time (sleep modules) is sufficient
• Increase max steps override if the task is complex
• Test the task manually in the Skyvern dashboard first

​

Extracted data is empty

• Verify your extraction schema matches the website structure
• Check the recording URL to see what the browser saw
• Simplify the extraction schema and test incrementally

​

Advanced Features

​

Data Stores

• Track task status across multiple runs
• Implement retry logic with counters
• Store extracted data temporarily

​

Webhooks

1. Add a webhook module to your scenario
2. Copy the webhook URL
3. Pass it as webhook_callback_url in Run Task
4. Skyvern will POST results when complete

​

Error Handling

• Ignore: Continue scenario if module fails
• Retry: Attempt the module again
• Commit: Save partial results before failure
• Break: Stop scenario execution

​

Support

• Review the Skyvern API documentation
• Check Make’s documentation
• Email [email protected]

​

Next Steps