Skip to main content
Connecting Leap lets your jobs and proposals start postcard campaigns around the job address, and credits the money back to the campaign that earned it. Postcard leads flow the other way into Leap as customers.

​
What you get

  • Triggers — seven Leap events can start a campaign: Job created, Job moves to a stage (stages load live from your workflow), Job won, Job completed, Job lost, Proposal accepted, and Customer created. You choose the event on each automation.
  • Revenue tracking — revenue books when a proposal is accepted. Mailr’s wizard says it plainly: “Revenue books when a proposal is accepted.” Job completion never books revenue.
  • Lead delivery — when someone scans your postcard and fills in the landing page, Mailr creates a customer in Leap tagged “Mailr” through the referral note, matched on an exact email address so a resubmitted form doesn’t make a duplicate.

​
Connect Leap

1

In Mailr, open Automations

Go to Campaigns → Automations in the Mailr app and find Leap under CRM Connection. Clicking a tile only opens its panel — nothing starts connecting until you press the Connect button inside. Only the workspace owner can connect a CRM.
2

Generate an access token in Leap

In Leap, go to Settings → Developer (you need admin access) and generate an access token. Mailr’s dialog links straight to the Developer settings page.
3

Paste the token in Mailr

Press Connect Leap and paste it into the Access token field. Mailr checks it against your account before saving, so a bad token never saves.
The tile switches to Connected and the 3-step setup wizard opens: Leads → Job address → Tracking.

​
How syncing works

Out of the box, Leap runs on the hourly sweep — a campaign can be queued up to an hour after the event, and automated campaigns use a design you’ve already approved and are reviewed by Mailr before anything mails.

​
Turn on instant updates (optional)

After connecting, the connected panel and the wizard’s success screen show a webhook URL with a Copy button:
1

Copy the URL Mailr shows

“Instant sync: paste this webhook URL into Leap under Settings → Webhooks so events reach Mailr the moment they happen (the hourly sweep runs either way).”
2

Paste it into Leap

In Leap, go to Settings → Webhooks and add the URL. Nothing to paste back into Mailr.
If instant updates never arrive, the URL almost certainly didn’t make it into Leap. Everything still runs hourly in the meantime.
The first sync starts the clock the moment you connect. Jobs and proposals that were already won or accepted before you connected will never trigger a campaign. To test, accept a fresh proposal after connecting.

​
Disconnect or reconnect

Disconnecting shows a confirmation titled “Disconnect Leap?”: “Lead sync and campaign triggers through this connection will stop, and the stored credentials are deleted. Your settings are kept, so reconnecting later picks up where you left off.” Your campaign history, leads and results are never deleted. Reconnecting keeps your field mappings and attribution window — and the same webhook URL, so you don’t have to paste it into Leap again.
The webhook URL you pasted into Leap stops working when you disconnect. If you don’t plan to reconnect, remove it in Leap → Settings → Webhooks.

​
Notes & limits

  • Leap requires a phone number on every customer. If a lead didn’t leave one, Mailr writes the placeholder 0000000000 so the record still saves. Tell your office staff, so nobody dials it thinking it’s real.
  • Custom field values are written when the customer is created only. If the customer already existed and was matched by email, custom fields aren’t updated.
  • Custom fields you want to map must be text fields on Customers, created in Leap Settings → Custom Fields. The wizard says the same thing and gives you a Refresh link once you’ve made them.
  • If you import past work to mail older customers, Mailr looks at your recent jobs in the stage you pick, or your recent customers — deep history isn’t reachable.
  • Addresses outside the US and Canada may save without a state.
Still stuck? See Troubleshooting connections or contact support.