Skip to content
  • Home

  • Automation with Zapier

  • Customer stories

Customer stories

3 min read

How Panoramic Properties caught a missing field in its leasing workflow

Adam Julien used Next-Gen Zaps to route Google Ads leads into Freshsales—and caught a silent budget mapping miss before it spread.

By Rob Ayre · November 25, 2026

Adam Julien has a rule about Fridays. "I never want to put anything live on a Friday and then be gone for the weekend," he says. He is a marketing coordinator at Panoramic Properties, with some programming experience and a background in game development.

Panoramic Properties is a multifamily leasing company with about 50 buildings across 11 cities. Most of its leads come through Google Ads lead forms, and each one needs to land in Freshsales, the company's CRM, with enough detail for a leasing agent to follow up. Adam estimates roughly 2,000 Google Ads leads in a typical month.

The question that tells the leasing team where to go

The most important question on the form asks which city a renter is interested in. The answer tells Panoramic where to send the lead and how its leasing agents should follow up with accurate information.

For an extended period, that city field often arrived blank even though it is required on the form. Submissions still reached Freshsales without an answer, so Adam used Next-Gen Zaps to give the team a starting point for follow-up.

He used the builder to set up the workflow, then mapped each campaign to the city it served. For regional campaigns that cover multiple cities, the Zap looks at the ad group for a more specific match. When the city field is blank, the Zap uses that information to suggest a likely city. A leasing agent can confirm where the renter is looking when they get in touch.

A test that passed and a field that didn't send

Panoramic later changed its lead form. The updated form captures the renter's preferred suite type and budget to help the leasing team follow up.

Adam did not rebuild from scratch. He copied his working Next-Gen Zap and told the builder what was different: same automation, same job, slightly different inputs. The builder generated its own test lead and sent it through. The test passed with the budget field intact.

Once real inquiries started coming in, Adam reviewed the live results and asked the builder to verify the field mappings. The builder flagged that the budget was not reaching Freshsales, and Adam corrected the mapping shortly after launch.

Google had changed the wording of its prebuilt question from "What is your monthly budget?" to "What is your monthly rental budget?" The field names no longer matched, so the budget never reached Freshsales. Nothing failed, and nothing threw an error.

"It was a really easy fix," Adam says. "It wasn't going into Freshsales, but it also wasn't causing an error."

In this case, fewer than 10 leads arrived before he caught it. Even if the builder had not flagged the field, Adam says he would not have let it run long: he checks new automations regularly. If a budget field had stayed missing, agents would still have had most of the other attributes the team collects; follow-up would just have been a little less useful in conversation.

What caught it, and what didn't

Adam is clear about which part of Next-Gen Zaps did the work. The auto-fix that watches running Zaps did not flag the missing field, and he does not fault it. That feature responds to errors, and there was not one. The catch came from the builder, the AI he talks to while building, when he asked it to look.

"It is a bit of a weird edge case where something goes wrong but it doesn't throw an error," he says. He ran the check almost as soon as live leads came in, so the gap closed fast.

Asking for a second look is how Adam works anyway. "I like to do a lot of things on the agentic side, but then I like to check everything manually 100% of the time," he says. Next-Gen Zaps shows him the code behind each Zap, so when he wanted a couple of fields changed, he adjusted the code himself instead of explaining the change to the builder.

Moving the rest over, one Zap at a time

Panoramic has about 50 Zaps, but only five or six see regular use. Most of them move lead data from point A to point B. Adam plans to bring those over to Next-Gen Zaps himself so he can see each change and run a few tests before anything goes live.

The first step takes one click. When he opens a classic Zap, it offers to switch it over. "One button. Perfect. I like that," he says.

Since the call, all main Google lead workflows have been running on Next-Gen Zaps. He has not moved other Zaps yet. He is waiting until he can add additional steps inside Next-Gen Zaps for the automations that need them.

"I like the new system," Adam says. "It gives us a lot more control, especially the code section."

Special thanks to Adam Julien from Panoramic Properties for sitting down with us and sharing his experience. To learn more about Panoramic Properties and their rentals, visit panoramicproperties.ca.

Learn more about Next-Gen Zaps.

Get AI and automation tips, delivered straight to your inbox

We’ll email you 1-2 times per week—and never share your information.

Related articles

Your agent builds it. Zapier keeps it running. Build automations across 10,000+ apps.

Sign up
A Zap with the trigger 'When I get a new lead from Facebook,' and the action 'Notify my team in Slack'