⚡ Zapier, Make.com & n8n Guide

Add screenshot capture, PDF generation, and content extraction to your no-code automation workflows. No SDK required — just HTTP modules.

Overview

SnapAPI works with any automation platform that supports HTTP requests. You don't need a dedicated plugin — just configure an HTTP module with the right URL, headers, and body.

💡 Tip: Use "responseType": "url" in all no-code integrations to receive a hosted URL instead of binary data. This makes it easy to pass screenshots to other steps in your workflow.

Zapier Setup

1 Add a Webhooks by Zapier Action

In your Zap, add an action step and choose Webhooks by Zapier → Custom Request.

2 Configure the Request

Zapier HTTP Configuration

Method:  POST
URL:     https://api.snapapi.pics/v1/screenshot

Headers:
  Authorization: Bearer YOUR_API_KEY
  Content-Type:  application/json

Body:
{
  "url": "https://example.com",
  "format": "png",
  "width": 1280,
  "height": 800,
  "responseType": "url"
}

3 Use the Result

The response contains a url field with the hosted screenshot. Use it in subsequent steps — send via email, save to Google Drive, post to Slack, etc.

// Response
{
  "url": "https://cdn.snapapi.pics/screenshots/abc123.png",
  "width": 1280,
  "height": 800,
  "format": "png"
}

Zapier: Generate a PDF

Method:  POST
URL:     https://api.snapapi.pics/v1/pdf

Headers:
  Authorization: Bearer YOUR_API_KEY
  Content-Type:  application/json

Body:
{
  "url": "https://example.com/invoice",
  "format": "A4",
  "printBackground": true,
  "responseType": "url"
}

Make.com Setup

1 Add an HTTP Module

In your scenario, add the HTTP → Make a request module.

2 Configure the Module

Make.com HTTP Configuration

URL:     https://api.snapapi.pics/v1/screenshot
Method:  POST

Headers:
  Authorization: Bearer YOUR_API_KEY
  Content-Type:  application/json

Request content:
{
  "url": "{{1.url}}",
  "format": "png",
  "width": 1280,
  "responseType": "url"
}

Parse response: Yes

💡 Tip: Use Make.com variables like {{1.url}} to dynamically pass URLs from trigger modules.

Make.com: Extract Content for AI

URL:     https://api.snapapi.pics/v1/extract
Method:  POST

Headers:
  Authorization: Bearer YOUR_API_KEY
  Content-Type:  application/json

Request content:
{
  "url": "{{1.url}}",
  "format": "markdown"
}

Feed the extracted markdown into an OpenAI or Claude module for summarization, analysis, or data extraction.

n8n Setup

1 Add an HTTP Request Node

In your n8n workflow, add an HTTP Request node.

2 Configure the Node

n8n HTTP Request Configuration

Method:           POST
URL:              https://api.snapapi.pics/v1/screenshot
Authentication:   Generic Credential Type
  → Header Auth:
      Name:  Authorization
      Value: Bearer YOUR_API_KEY

Body Content Type: JSON
Body Parameters:
  url:            {{ $json.url }}
  format:         png
  width:          1280
  height:         800
  responseType:   url

Options:
  Response Format: JSON

n8n: Batch Screenshots

Use the Split In Batches node to process multiple URLs:

1. Trigger (e.g., Google Sheets with URLs)
   ↓
2. Split In Batches (batch size: 5)
   ↓
3. HTTP Request → SnapAPI screenshot
   ↓
4. Google Drive → Upload screenshot
   ↓
5. Loop back to Split In Batches

Workflow Recipes

🔔 Monitor Website Changes

Take daily screenshots of a page and compare them visually.

Schedule Trigger (daily at 9am)
  → SnapAPI Screenshot (full page)
  → Save to Google Drive (dated folder)
  → Slack notification with screenshot URL

🧾 Auto-Generate PDF Invoices

New Stripe Payment (trigger)
  → Build invoice URL with payment data
  → SnapAPI PDF (A4, print background)
  → Send PDF via email to customer

📰 Content Extraction Pipeline

RSS Feed (new article)
  → SnapAPI Extract (markdown)
  → OpenAI summarize
  → Post summary to Slack/Discord

🛒 E-commerce Product Monitoring

Schedule Trigger (hourly)
  → SnapAPI Extract (structured data: price, title, stock)
  → Compare with previous data
  → Alert on price drop or out-of-stock

Tips & Best Practices

💡 Always use responseType: "url" — No-code platforms handle URLs much better than binary data. The hosted URL is valid for 24 hours.

💡 Add delays for dynamic pages — Use the "delay": 2000 parameter (milliseconds) to wait for JavaScript-heavy pages to fully render.

⚠️ Rate Limits: Free tier allows 200 requests/month. For automation workflows, consider a paid plan. The API returns 429 when limits are exceeded — add error handling in your workflow to retry. View plans.

💡 Block ads & cookie banners — Add "blockAds": true and "blockCookies": true for cleaner screenshots in automated workflows.

Next Steps

Reference Full API Documentation → Raw HTTP cURL Examples → Scale up View Pricing Plans → Try it live API Playground →