Next-Gen Zaps help Panoramic Properties catch missing lead field
A leasing company found a missing budget field after Google Ads changed a form question. The case shows how manual checks can catch silent automation failures.

Key takeaways
- Panoramic Properties used Next-Gen Zaps to suggest a city when a required lead field arrived blank.
- A Google Ads wording change stopped the budget field from reaching Freshsales without causing an error.
- The builder caught the missing field when Julien asked for a mapping check.
- Panoramic plans to move more Zaps to Next-Gen Zaps one at a time.
In this article
How the leasing workflow works
Panoramic Properties manages about 50 rental buildings in 11 cities. Most leads arrive from Google Ads lead forms. Each lead needs to reach Freshsales, the company's customer relationship management system.
It needs enough detail for a leasing agent to follow up. Adam Julien, a marketing coordinator at the company, estimated around 2,000 Google Ads leads in a normal month.
The key form question asks renters to choose a city. That answer guides the leasing team on where to route the lead and what information to provide. For some time, the city answer often came through empty even though the form required it.
Next-Gen Zaps are automated workflows that move data between apps. Julien used them to provide a useful default for agents. He linked each campaign to its target city.
For regional campaigns covering several cities, the workflow checks the ad group. An ad group is a set of related ads. This helps find a closer match.
If the city field is empty, the workflow suggests a probable city. An agent can confirm the renter's location during contact.
A form change and a quiet failure
Panoramic later updated its lead form. The new form collected the suite type and budget preferred by the renter to help agents follow up. Julien did not rebuild the automation from scratch.
He duplicated the working Next-Gen Zap. He told the builder what had changed. The automation and job stayed the same. The inputs were slightly different.
The builder created a sample lead and passed it through. The test passed and included the budget field. After real inquiries began arriving, Julien checked the live results.
He asked the builder to review the links between form fields and CRM fields. The builder pointed out that the budget was not arriving in Freshsales, and Julien fixed the mapping soon after launch.
Google altered the wording of a ready-made question. The old wording asked about a monthly budget, while the new wording asked about a monthly rental budget. Because the field names did not match any more, the budget did not arrive in Freshsales.
No failure appeared, and no error was raised. The gap affected fewer than 10 leads before Julien spotted it. If the budget field had stayed missing, agents would still have had most other data collected by the team.
Follow-up would have been less useful in conversation. Julien says he reviews new automations regularly, so he would not have allowed the issue to continue.
What caught the problem

Julien identified the Next-Gen Zaps feature that did the work. The auto-fix feature for running Zaps did not notice the absent field, and Julien does not blame it. It responds to errors, and none occurred. The builder, the AI assistant used during building, made the catch after he asked for a check.
He described it as an unusual case where a problem occurs without an error. He ran the check soon after live leads arrived, so the gap closed quickly. Requesting a second look is part of Julien's normal process. He likes automated AI features but also checks everything manually.
Next-Gen Zaps shows the code behind each Zap. When he needed two fields changed, he edited the code himself rather than asking the builder. This gave him more control over the workflow.
Moving more workflows
Panoramic runs about 50 Zaps, but only five or six are used regularly. Most move lead data from one place to another. Julien plans to migrate them himself so he can inspect each change and test before launch.
The first step takes a single click. Opening a classic Zap offers a switch option. Since then, the main Google lead workflows have run on Next-Gen Zaps.
Other Zaps have not been moved yet. Julien is waiting until Next-Gen Zaps can add extra steps for automations requiring them.
Julien said he likes the new system because it gives the team more control, especially the code section. The Panoramic case shows why field mapping checks matter after a form changes. A small wording change can break a data flow without creating an error. A quick review can prevent missing information from reaching the team.
Sources
Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.


