Zapier

Zapier connects apps to each other with simple “when this happens, do that” automations called Zaps. The PageFork app for Zapier lets your leads start a Zap, and lets a Zap put a lead into PageFork.

Some things people build with it:

• New form submission → add a contact in HubSpot, Pipedrive or Salesforce.
• New form submission → post a message in Slack or Microsoft Teams.
• Lead moved to Won → create an invoice in your accounting tool.
• New Facebook Lead Ad or Typeform response → create a lead in PageFork.

The Zapier app is part of the Pro plan. See Basic and Pro plans.

What the app can do

	Name	What it does
Trigger	New Form Submission	Starts a Zap when someone submits a form on your site
Trigger	Lead Stage Changed	Starts a Zap when a lead moves to another pipeline stage
Action	Create Lead	Adds a lead (and the person) to a site from any Zap

Both triggers are instant: the Zap starts within a second or two, not on a 15-minute check.

Before you start

You need:

• A Zapier account. The PageFork app works on Zapier’s free plan, within that plan’s own limits.
• To be an owner or admin of your PageFork team, so you can create an API key.
• A site on Pro.

Step 1: add the PageFork app to your Zapier account

The app is available by invitation while it awaits Zapier’s public listing.

1. Open the PageFork Zapier invite link.
2. Click Accept Invite & Build a Zap.

PageFork now appears in the app list whenever you build a Zap.

Step 2: create an API key

1. In PageFork, open the Team page.
2. Under API keys, click Create key and name it “Zapier”.
3. Copy the key. It starts with pfk_ and is shown only once.

More detail in API keys.

Step 3: connect

The first time you use PageFork in a Zap, Zapier asks you to sign in. Paste the API key. Zapier checks it and shows the connection under your team’s name.

Trigger: New Form Submission

1. Create a Zap and choose PageFork as the trigger app.
2. Choose the event New Form Submission.
3. Choose your PageFork connection.
4. Pick the Site, and optionally a Form. Leave Form empty to catch every form on the site.
5. Click Test trigger. Zapier fetches your most recent real submission as sample data.
6. Add your action step, map the fields, and Publish the Zap.

Submit your form once before step 5 if the site has no submissions yet. Zapier needs one real submission to learn your field names.

What the trigger gives you

Field	Meaning
ID	The submission’s id
Form Id	Which form was submitted
Site Id, Site Name	Which site it came from
Submitted At	When it arrived
Preview	A one-line summary, such as “Ada · ada@example.com”
Your form fields	One field per input in your form: Name, Email, Message and so on

Your form’s fields appear at the top level, ready to map, under the names you gave them in the form.

Trigger: Lead Stage Changed

Set it up the same way, choosing the event Lead Stage Changed.

You get everything from the list above, plus:

Field	Meaning
Status From	The stage the lead left, such as new
Status To	The stage it moved into, such as won

The Zap runs on every stage move. To act only on some, add a Filter step right after the trigger, for example “Status To exactly matches won”.

The values are your stages’ keys: short lowercase versions of the stage names, fixed when the stage was created. Renaming a stage later keeps its key, so your filters don’t break. Run the trigger’s test once to see the exact keys for your pipeline.

Action: Create Lead

Use this to bring leads into PageFork from anywhere Zapier can reach.

1. In a Zap, add an action step and choose PageFork → Create Lead.
2. Pick the Site.
3. Map what you have. At least one of Name, Email or Phone is required.

Field	Notes
Site	Required
Name, Email, Phone, Company	The person’s details
Channel	How the lead reached you: phone, walk-in, referral, email, social or other
Tags	Added to the person
Note	Saved as a note on the lead
Stage	One of the site’s open stages. Empty means the first stage
Your custom fields	Every custom field on the site appears here automatically

How PageFork avoids duplicates

Create Lead follows the same rule as a form submission:

• PageFork looks for an existing person with the same email, then the same phone number.
• If that person already has an open lead, the new details are attached to it. No second lead is opened.
• Otherwise a new lead is opened for them.
• A known person keeps their existing details. Empty fields are filled in; nothing is overwritten.

The step’s output tells you what happened through Contact Created and Lead Created, either true or false.

Things to know

Only leads from forms start Zaps. A lead added by hand, imported, or made by Create Lead never fires either trigger, even when you change its stage. This also means a Zap using Create Lead can’t accidentally trigger itself.

Create Lead doesn’t trigger your other destinations either, and doesn’t count as a conversion in analytics. It is a way to get leads in, not a form submission.

Changing many leads at once doesn’t start Zaps. Bulk stage changes from the list are silent.

Turning a Zap off disconnects it. Zapier tells PageFork to stop sending. Turning it back on reconnects. You’ll see each active Zap in your site’s Settings → Forms → Destinations, marked Managed by Zapier. Those entries are controlled from Zapier and can’t be edited in PageFork.

Revoking the API key disconnects every Zap that used it. See API keys.

Limits

• 10 Zapier and Make connections per site in total. Each published Zap with a PageFork trigger uses one.
• Create Lead accepts up to 60 leads a minute per key.

Troubleshooting

“Test trigger” finds nothing. The site, or the form you picked, has no submissions yet. Submit the live form once and test again.

The Zap doesn’t run on new submissions. Check the Zap is published, the Form you picked is the one people submit, and the site is on Pro. Then open the site’s destinations in PageFork: the Managed by Zapier entry shows each delivery and what Zapier answered.

An error mentioning “pro_required”. The site is on Basic. Upgrade the site, or pick a Pro site.

“Invalid API key”. The key was revoked or its creator left the team. Create a new key and reconnect PageFork in Zapier.

A custom field is missing from Create Lead. Pick the Site first. The field list loads for the chosen site. Click Zapier’s Refresh fields after adding a field in PageFork.

Create Lead fails with “A new lead must start in an open stage”. The stage you mapped is a won or lost stage. Choose an open one or leave Stage empty.

Next

• API keys
• Make
• Destinations overview
• Webhooks with n8n and other tools