# Zapier Integration Guide

Zapier lets Pictor talk to the rest of your stack - Google Sheets, Airtable, Slack, your CRM, a webhook, anywhere Zapier connects. If you've ever wanted every event submission, new gallery photo, or signup to flow automatically into another tool without copy-pasting, this is the page for you.

> **Plan note.** Zapier is available on **Premium** ($149/mo) and **Enterprise** plans. If you're on Basic or Pro and want this integration, upgrade to Premium any time from Account Settings → Billing - it takes effect immediately.

---

## What you can do with Pictor + Zapier

A few real examples operators are already running:

- **Push every new gallery photo to a Google Drive folder** for client delivery
- **Log every new event signup to a Google Sheet or Airtable base** for client reporting
- **Send a Slack message to your team's channel** when a new event goes live
- **Add event leads to HubSpot or Mailchimp** for follow-up sequences
- **Trigger a custom webhook** to your own backend when specific events happen

If you can describe it as "when X happens in Pictor, do Y somewhere else," Zapier can almost certainly wire it up.

---

## How to connect

### Step 1 - Generate your Zapier API key in Pictor

1. Sign in to app.pictor.pro
2. Go to **Account Settings → Integrations → Zapier**
3. Click **Generate API Key**
4. Copy the key - you'll paste it into Zapier in the next step

> **Keep this key private.** Anyone with the key can trigger Zaps on your behalf. If you ever suspect it's leaked, return to this screen and click **Revoke & Regenerate**.

### Step 2 - Create a Zap in Zapier

1. Sign in to zapier.com (or create a free account if you're new)
2. Click **Create Zap**
3. Search for the **Pictor** app in the app picker
4. When prompted, paste the API key from Step 1 to connect your account
5. Pick a **trigger** (what happens in Pictor) and an **action** (what happens elsewhere)
6. Test the connection and turn the Zap on

That's it. Once the Zap is on, it runs in the background - no extra clicks needed.

---

## Triggers Pictor offers

A *trigger* is the event in Pictor that starts a Zap. The current set:

| Trigger | What it does |
|---|---|
| **New Event Created** | Fires when you create a new event in Pictor |
| **New Photo Captured** | Fires every time a guest photo or video is captured |
| **New Event Signup** | Fires when a guest signs up for your event (pre-registration, surveys, paywall) |
| **New Gallery Upload** | Fires when a new image lands in an event gallery |
| **New Form Submission** | Fires when a guest submits a survey or data-capture form |

Each trigger comes with a payload of event data - guest email, photo URL, event name, timestamp, and more. You map these fields to whatever tool you're sending data to.

---

## Actions Pictor offers

Right now, Pictor focuses on **outbound** triggers (events *leaving* Pictor to trigger Zaps elsewhere). For most workflows - Sheets, CRMs, Slack, webhooks - this is all you need.

If you need Pictor to receive data *from* another tool, the standard pattern is to have Zapier write to an intermediary (a Google Sheet, Airtable, or your own webhook endpoint) that Pictor polls or reads from. We're exploring richer two-way actions in future releases.

---

## Common workflows

### "Save every gallery photo to Google Drive"

- **Trigger:** New Gallery Upload
- **Action:** Google Drive → Upload File
- **Map:** `photo_url` → file source, `event_name` → folder name

### "Log every event signup to a Google Sheet"

- **Trigger:** New Event Signup
- **Action:** Google Sheets → Create Spreadsheet Row
- **Map:** `guest_email`, `guest_name`, `event_name`, `signup_date`

### "Notify Slack when a new event goes live"

- **Trigger:** New Event Created
- **Action:** Slack → Send Channel Message
- **Map:** `event_name`, `event_url`, `creator_name` → message text

### "Add leads to HubSpot"

- **Trigger:** New Event Signup
- **Action:** HubSpot → Create or Update Contact
- **Map:** `guest_email`, `guest_name`, `event_name` → contact properties

---

## Troubleshooting

**Zapier can't find the Pictor app?**

- Confirm you're on a **Premium** or **Enterprise** plan (the integration is gated there)
- Try searching "Pictor Photo Booth" in the Zapier app picker - exact wording matters sometimes

**API key rejected?**

- Re-copy the key from **Account Settings → Integrations → Zapier** in Pictor
- Make sure there are no trailing spaces when you paste
- Try revoking and regenerating the key

**Trigger fires but no data shows up downstream?**

- Open the Zap's **Zap History** in Zapier to see what data Pictor sent
- Re-test the action step with sample data
- Confirm the receiving tool (Sheet, CRM, Slack channel) is writable

**Trigger never fires?**

- Confirm the Zap is **turned on** (toggle is green in Zapier)
- Confirm the event in Pictor actually matches the trigger - for example, "New Gallery Upload" only fires when a guest uploads, not when you upload manually
- Check Zapier's task history for errors

---

## Tips for getting the most out of Zapier

- **Start with one Zap.** Wire up the most obvious workflow first - Sheets logging, say - then add more as you get comfortable.
- **Filter at the Zap level.** If you only want to log *paid* events, add a Zapier filter step before the action.
- **Use Paths for branching.** Zapier's Paths feature lets you route different events to different actions based on conditions (e.g., weddings vs. corporate events).
- **Watch your Zapier task usage.** Each event triggers one Zap task. If you're running high-volume events, check your Zapier plan limits.
- **Document your Zaps.** Give each Zap a clear name ("Pictor → Sheets - Wedding signups") so your future self knows what it does.

---

## Still stuck?

We're here:

- **Chat:** the chat widget in the bottom-right of app.pictor.pro
- **Email:** hello@pictor.pro
- **Event emergency (Friday 4pm - Sunday 2am ET):** call our 24/7 hotline at **+1 (612) 473-8998**

Can't wait to see what you make with Pictor.
