Make
Connect PageFork to Make: start scenarios from new leads and stage changes, or create leads from a scenario.
Make (formerly Integromat) builds automations as visual scenarios. The PageFork app for Make lets your leads start a scenario, and lets a scenario put a lead into PageFork.
The Make app is part of the Pro plan. See Basic and Pro plans.
What the app can do
| Module | What it does | |
|---|---|---|
| Trigger | Watch Form Submissions | Starts a scenario when someone submits a form on your site |
| Trigger | Watch Lead Stage Changes | Starts a scenario when a lead moves to another pipeline stage |
| Action | Create a Lead | Adds a lead (and the person) to a site |
Both triggers are instant. Make is told about the lead the moment it happens.
Before you start
You need:
- A Make account. The free plan is enough to try it.
- 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 Make account
The app is available by invitation while it awaits Make’s public listing.
- Open the PageFork Make invite link.
- Click Install.
PageFork now appears when you search for an app in a scenario.
Step 2: create an API key
- In PageFork, open the Team page.
- Under API keys, click Create key and name it “Make”.
- Copy the key. It starts with
pfk_and is shown only once.
More detail in API keys.
Trigger: Watch Form Submissions
- Create a scenario and add the PageFork module Watch Form Submissions.
- Make asks you to Create a webhook. Give it a name.
- Under Connection, click Add and paste your API key. Make checks it and labels the connection with your team’s name.
- Pick the Site, and optionally a Form. Leave Form empty for every form on the site.
- Click Save.
- Add the modules that should run next, then switch the scenario on.
PageFork starts sending to Make as soon as you save the webhook in step 5. Submissions that arrive while the scenario is off wait in Make’s queue and run when you switch it on.
What the trigger gives you
| Item | Meaning |
|---|---|
| Submission ID | The submission’s id |
| Form | 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” |
| Fields | A collection with one item per input in your form |
To map a form value in a later module, open Fields and pick the item, for example Fields: email. If the items aren’t listed yet, run the scenario once with a real submission so Make learns them.
Trigger: Watch Lead Stage Changes
Set it up the same way with the module Watch Lead Stage Changes. It needs its own webhook.
You get everything above, plus:
| Item | Meaning |
|---|---|
| Stage from (key) | The stage the lead left, such as new |
| Stage to (key) | The stage it moved into, such as won |
The scenario runs on every stage move. To act only on some, add a
filter on the line after the trigger, for example “Stage to (key)
equal to 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.
Action: Create a Lead
- Add the PageFork module Create a Lead to a scenario.
- Choose your connection and pick the Site.
- Map what you have. At least one of Name, Email or Phone is required.
| Field | Notes |
|---|---|
| Site | Required |
| Stage | One of the site’s open stages. Empty means the first stage |
| Custom fields | Every custom field on the site |
| Name, Email, Phone, Company | The person’s details |
| Channel | Phone, Walk-in, Referral, Email, Social or Other |
| Tags | Added to the person |
| Note | Saved as a note on the lead |
Stage and Custom fields appear after you pick the site, since they differ from site to site.
How PageFork avoids duplicates
Create a 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 module’s output says what happened through New person and New lead, either true or false.
Things to know
Only leads from forms start scenarios. A lead added by hand, imported, or made by Create a Lead never fires either trigger, even when you change its stage. This also means a scenario using Create a Lead can’t trigger itself.
Create a Lead doesn’t trigger your other destinations either, and doesn’t count as a conversion in analytics.
Changing many leads at once doesn’t start scenarios. Bulk stage changes from the list are silent.
Switching a scenario off doesn’t disconnect it. The webhook stays subscribed and Make queues what arrives. To stop PageFork sending, delete the webhook in Make under Webhooks. You’ll see each connected webhook in your site’s Settings → Forms → Destinations, marked Managed by Make. Those entries are controlled from Make and can’t be edited in PageFork.
Revoking the API key disconnects every webhook that used it. See API keys.
Limits
- 10 Zapier and Make connections per site in total. Each Make webhook uses one.
- Create a Lead accepts up to 60 leads a minute per key.
Troubleshooting
Saving the webhook shows “[403] pro_required”. The site you picked is on Basic. Upgrade it, or pick a Pro site.
Saving the webhook shows “[401]”. The API key was revoked or mistyped. Create a new key in PageFork and add a new connection.
The Site list is empty. The connection’s key belongs to a different team than the one you expected. Check which team you were in when you created the key.
The scenario doesn’t run. Check it is switched on and that the Form on the webhook is the one people submit. Then open the site’s destinations in PageFork: the Managed by Make entry shows each delivery and what Make answered.
Create a Lead fails with “A new lead must start in an open stage”. The stage you picked is a won or lost stage. Choose an open one or leave Stage empty.