Integrations
PNG Tools with Zapier
PNGmaker can be connected to Zapier workflows to automate image background removal. Because PNGmaker runs in the browser rather than as a REST API, the integration approach is browser automation — which Zapier supports through Code steps or by triggering scripts on your own infrastructure.
How Zapier + PNGmaker works
Zapier is great at connecting apps and triggering actions based on events. PNGmaker handles the image processing locally in a browser. Combining them means: Zapier detects an event (new file in Google Drive, form submission, Shopify product upload), then triggers a browser automation step that runs PNGmaker, and routes the transparent PNG output wherever you need it.
The cleanest integration pattern is to use Zapier to trigger a webhook or script on a server you control, which then runs the Playwright automation. This keeps Zapier lean (trigger + route) while the browser work happens on infrastructure you manage.
Recommended Zapier workflow
- 1Trigger — new file in Google Drive, Dropbox, or a form submission (e.g. Typeform, Jotform with an image upload field).
- 2Webhooks by Zapier (POST) — send the image URL and any metadata to your server's processing endpoint.
- 3Server-side Playwright — your server downloads the image, runs PNGmaker via browser automation, and stores the transparent PNG result.
- 4Return URL to Zapier — your server responds with the output file URL, which Zapier picks up and routes to the next step (upload to Drive, send via email, post to Slack, etc.).
Code reference
This example shows the core browser automation logic for a Zapier Code step or server-side script. It uses PNGmaker's stable data-testid selectors:
// Zapier Code step (Node.js) — requires Playwright available
// Or use in a Zapier-triggered script on your own server
const { chromium } = require('playwright');
const https = require('https');
const fs = require('fs');
const path = require('path');
const os = require('os');
// Download image from Zapier input URL
const imageUrl = inputData.imageUrl;
const tmpInput = path.join(os.tmpdir(), 'input-' + Date.now() + '.jpg');
const tmpOutput = path.join(os.tmpdir(), 'output-' + Date.now() + '.png');
// (download imageUrl to tmpInput — standard https.get code)
const browser = await chromium.launch();
const page = await browser.newPage();
await page.goto('https://pngmaker.com/remove-background/agent');
const fileInput = await page.locator('[data-testid="bg-removal-dropzone"] input[type="file"]');
await fileInput.setInputFiles(tmpInput);
await page.waitForSelector('[data-testid="bg-removal-result"]', { timeout: 30000 });
const downloadPromise = page.waitForEvent('download');
await page.click('[data-testid="bg-removal-download"]');
const download = await downloadPromise;
await download.saveAs(tmpOutput);
await browser.close();
// Return output path for next Zapier step
output = [{ outputPath: tmpOutput }];Good use cases for this integration
- E-commerce product images. Automatically remove backgrounds from product photos when they are uploaded to a shared folder or form.
- Profile photo processing. Remove backgrounds from user-submitted headshots when they fill in a registration or onboarding form.
- Content team asset prep. Designers upload raw images; the Zap processes them overnight and drops transparent PNGs into the right Drive folder.
- Marketplace listing preparation. New product listings trigger automatic background removal before images are published.
Why this is free
PNGmaker runs its AI model entirely in the browser. There are no server-side processing costs passed on to users, no API credits to purchase, and no rate limits tied to subscription tiers. Your Zapier workflow pays nothing for the image processing itself — only for Zapier tasks, which are the same regardless of what the integration does.
Try it with PNGmaker
Use the tool flow directly from this guide. The idea is simple: understand the workflow, then get to the result fast.