Destinations overview
Send every lead to the tools you already use: a spreadsheet, an inbox, your email list, Zapier, Make, or your own server.
A destination is a place PageFork sends a lead to, automatically, the moment something happens to it. Your leads always live in PageFork first. Destinations copy them outward so the rest of your business hears about them without anyone retyping anything.
Destinations, API keys and the Zapier and Make apps are part of the Pro plan. See Basic and Pro plans.
What you can send leads to
| Destination | What it does | Best for |
|---|---|---|
| Google Sheets | Adds a row to a spreadsheet for every submission | A shared list the whole team can read |
| Emails a verified address on a new submission or a stage change | Routing a form to a person, alerts when a deal is won | |
| Kit | Subscribes the person to a Kit form or tag | Newsletters and email sequences |
| Mailchimp | Adds the person to a Mailchimp audience, with tags | Newsletters and customer lists |
| Zapier | Starts a Zap, or creates a lead from a Zap | Connecting thousands of other apps without code |
| Make | Starts a scenario, or creates a lead from one | The same, in Make |
| Webhook | Sends signed JSON to a URL you control | Your own server, n8n, anything custom |
You can mix them freely. One form can feed a spreadsheet, email your sales inbox and add the person to your newsletter, all at once.
Where destinations live
Destinations belong to a site.
- Open the site in the editor.
- Open Settings and go to the Forms tab.
- Find Destinations and click Add.
- Pick a type and follow its form.
Only team owners and admins can add, change or delete destinations. See Team and roles.
Zapier and Make are the exception to the steps above: you set those up inside Zapier or Make, and the destination appears here by itself, marked Managed by Zapier or Managed by Make.
The three choices every destination has
Name. Anything that helps you recognise it later, such as “Sales inbox” or “Newsletter signups”.
Form scope. One specific form, or All forms on the site. A destination scoped to a form ignores submissions from the others.
Triggers. When it fires. See the next section.
Triggers: when a destination fires
Every destination has a row of trigger chips. Click one to turn it on or off.
- New submission fires when someone submits a form.
- → Stage chips, one per stage in your pipeline (for example → Contacted or → Won), fire when a lead moves into that stage.
They combine. A destination with New submission off and → Won on ignores raw leads and only speaks up when a deal closes.
A destination with every trigger off never fires. The panel tells you so, rather than leaving you to work it out from an empty log.
Google Sheets only offers New submission. A spreadsheet is a flat list of submissions, and a second row for the same person each time their stage changed would only confuse it.
What fires a destination, and what doesn’t
This is the rule that surprises people most, so it’s worth reading once.
Destinations fire for leads that have a form submission. A lead you added by hand, imported from a CSV file, or created from Zapier or Make does not trigger any destination, not when it’s created and not when its stage changes later.
The reason is safety. A destination often does something outward and hard to undo, such as subscribing a person to a mailing list. PageFork only does that for people who filled in your form themselves.
One consequence: if a person you added by hand later submits a form, that submission joins their lead, and from then on the lead behaves like any other form lead. Stage changes on it start firing.
A few more details:
- If a known person submits a form again, the submission joins their existing open lead. New submission destinations still fire, since there is a new submission.
- Stage triggers fire on the move itself, whether you used the stage bar on the lead or dragged a card on the board.
- The one exception is a bulk change. Moving many leads at once from the list never triggers destinations, so changing fifty leads doesn’t send fifty emails.
- Moving a lead through three stages quickly sends three deliveries. Nothing is merged or delayed.
Testing a destination
Google Sheets, email and webhook destinations have a Send test button. It sends a sample built from your form’s real field names, with placeholder values.
Kit and Mailchimp have no test button, on purpose: a test would subscribe a made-up person to your real list. To check those, submit your live form once with your own address.
For any destination, a real submission is the most complete test. It proves the whole path: the form, spam checks, the lead, and the delivery.
The delivery log
Open a destination to see Recent deliveries. Each line is one attempt to deliver one lead.
| Status | Meaning |
|---|---|
pending | Waiting in the queue or being sent right now |
success | The other side accepted it |
skipped | Nothing to send, and that’s fine. For example, the form had no email address to subscribe |
failed | This attempt failed. PageFork will try again |
dead | PageFork has given up on this one |
A delivery that ended badly can be sent again with Retry.
Delivery records are kept for 30 days. They are a debugging window, not an archive. Your leads themselves are never affected by a delivery failing.
Retries and automatic disabling
- PageFork tries each delivery up to 5 times, waiting longer between each try, starting at 5 seconds.
- Temporary problems (the other service is down, busy, or rate limiting you) are retried. Permanent ones (a wrong address, a rejected key) stop straight away, since trying again can’t fix them.
- After 50 failures in a row, a destination is disabled automatically and the team’s owners and admins get an email. Fix the cause, then click Enable.
- Some failures disable a destination at once, because nothing can succeed until you act: a Google account that was disconnected, a spreadsheet that was deleted, or an API key that Kit or Mailchimp rejects.
Pausing and deleting
Disable pauses a destination without losing its settings. Enable switches it back on. Leads that arrived while it was paused are not sent afterwards.
Delete removes it and its delivery log. Nothing is deleted in the other tool: rows already in your spreadsheet and people already on your mailing list stay there.
Limits
Per site:
- 10 destinations in total that you create yourself.
- Enabled at the same time: 5 webhooks, 5 email destinations, 3 Google Sheets, 3 Kit and 3 Mailchimp.
- 10 Zapier or Make connections, counted separately from the above.
If your site moves to Basic
Destinations stop firing while a site is on Basic, for example when its 14-day Pro trial ends without a Pro plan. That includes the Zapier and Make apps. Nothing is deleted and nothing is switched off: your destinations keep their settings and start firing again, for new activity only, as soon as the site is back on Pro. Leads that arrived in between are not sent retroactively.
Troubleshooting
Nothing is being sent. Check, in this order: the site is on Pro; the destination says Enabled; at least one trigger chip is on; its form scope matches the form people are actually submitting; and the lead came from a form rather than being added by hand or imported.
It worked, then stopped. Open the destination. If it was disabled automatically, the reason is shown at the top. Fix it and click Enable.
The log says skipped. PageFork had nothing to send. For Kit and
Mailchimp this almost always means the mapped email field was empty on
that submission.
I see the lead in PageFork but not in the other tool. Open the destination and read the newest delivery. The status and the message next to it say exactly what the other service answered.