SnapAPI + Zapier
Complete Integration Guide

Add screenshot capture, PDF generation, and content extraction to any Zapier workflow in under 5 minutes — no native Zapier app needed. Use "Webhooks by Zapier" to call the SnapAPI REST API directly.

How it Works

Every Zap that calls SnapAPI follows the same pattern:

Prerequisites

• A free SnapAPI account — your API key is on the dashboard.
• A Zapier account (free or paid — Webhooks by Zapier works on all plans).
• A Zap trigger that provides a URL (or you will hardcode one for testing).

Step 1: Create a New Zap

Step 2: Choose Your Trigger

Connect your trigger account, configure it, and test it to get sample data. Zapier will show you what fields are available — you will map these to the SnapAPI request body in Step 4.

Step 3: Add "Webhooks by Zapier" Action

Step 4: Configure the Request

In the Data field, enter the JSON body. Use Zapier's variable syntax {{step.field}} to map fields from your trigger. Replace {{1.url}} with the actual field from your trigger step:

{
  "url": "{{1.url}}",
  "format": "png",
  "width": 1280,
  "height": 800,
  "fullPage": false,
  "responseType": "url"
}

Common request parameters

Step 5: Map the Response and Use the Result

The SnapAPI response (with responseType: "url") looks like this:

{
  "url":     "https://cdn.snapapi.pics/screenshots/xk92mf.png",
  "width":   1280,
  "height":  800,
  "format":  "png",
  "cached":  false,
  "credits": 1
}

Now add a third action to your Zap. In any field that accepts a URL, click inside and select the Webhooks step, then url from the available fields. Examples:

• Google Drive — Upload File: Set "File" to the Webhooks url field. Zapier will download the image and upload it to Drive.
• Dropbox — Upload File: Same pattern as Drive.
• Gmail — Send Email: Paste the URL in the email body or as an attachment link.
• Slack — Send Message: Include the URL in the message text. Slack auto-unfurls images.
• Google Sheets — Update Row: Write the screenshot URL back to a "Screenshot" column in your spreadsheet.
• Airtable — Update Record: Save to an attachment or URL field in your base.

Generate PDFs

Change the endpoint URL and body to generate PDF files instead of screenshots:

// URL field:
https://api.snapapi.pics/v1/screenshot

// Body:
{
  "url": "{{1.url}}",
  "format": "pdf",
  "fullPage": true,
  "pdfOptions": {
    "pageSize": "a4",
    "printBackground": true,
    "marginTop": "1cm",
    "marginBottom": "1cm"
  },
  "responseType": "url"
}

Extract Content for AI Processing

Use SnapAPI's Extract endpoint to turn any web page into clean Markdown, then feed it to OpenAI or another AI step in your Zap:

// URL field:
https://api.snapapi.pics/v1/extract

// Body:
{
  "url": "{{1.url}}",
  "format": "markdown"
}

// Response:
{
  "markdown": "# Article Title\n\nIntroductory paragraph...",
  "title": "Article Title",
  "wordCount": 842
}

Map the markdown field from the SnapAPI response as input to an OpenAI — Send Prompt or ChatGPT Zap action for summarization, classification, or data extraction.

Workflow Recipes

Troubleshooting

401 Unauthorized

Your API key is missing or incorrect. Double-check:

• The header name is exactly X-Api-Key (not Authorization, not api-key).
• The header value is your actual API key — no extra spaces, no "Bearer " prefix.
• You are copying the key from the dashboard, not a code example.

400 Bad Request

The request body has a validation error. Common causes:

• The URL is missing the https:// prefix.
• You forgot to set Content-Type: application/json in headers.
• The "Unflatten" option in Zapier is set to "no" — set it to "yes" for nested JSON.
• A parameter value is the wrong type (e.g., "width": "1280" instead of "width": 1280).

429 Too Many Requests

You have exceeded your plan's rate limit. Add a Zapier Delay for step of 1–2 seconds between requests, or upgrade to a paid plan for higher limits.

The screenshot URL is empty / step fails

Make sure you are using the Custom Request event, not the simpler "POST" event. The response from Custom Request is parsed as JSON, making the url field accessible as a Zapier variable.

Make.com Quick Setup

The pattern for Make.com is identical — use the HTTP → Make a request module instead of Webhooks by Zapier. The full Make.com guide is available at: