Skip to main content
Clever Ops

Case studyReal job

How we built a Zoho and Pylon sync for a solar installer

We built a service for a solar installer in Australia that takes leads from a website form and two lead suppliers into Zoho CRM, one lead per person, tagged with where it came from.

  • Zoho CRMLeads and deals
  • PylonProjects and designs
  • Microsoft GraphReads the mailbox

Transcript

They're a solar installer in Australia. They got in touch through the form on our website, because every lead and every signed job was being typed in by hand.

Leads arrived in three places: the website form and two lead suppliers. Each was typed into Zoho. To design a system, the customer was typed again into Pylon, their solar design and proposal tool. When the customer signed, the totals and equipment were typed back into Zoho.

Here's what runs now. The website form and one supplier post each lead straight to our system. Both suppliers also send notification emails, which it reads from the business's mailbox. Every lead becomes the same shape, with phone numbers in one international format.

Before writing anything, the system checks its own records, then searches Zoho's leads and contacts for that email or phone. Someone new becomes a lead, tagged with its source and marked new for a day. A repeat enquiry updates their existing lead. An existing customer isn't added again. The team gets a message instead.

When a lead becomes a deal in Zoho, the system looks in Pylon for a project with the same contact and full site address. One match, and it links them. None, and it creates an unconfirmed draft. If two could match, it doesn't guess. It holds the deal and tags it for a person.

When a design is ready, its proposal link is written onto the deal, for the proposal email from Zoho. When the customer signs in Pylon, the deal moves to Contract Completed, and its system size, battery, panel count, prices and equipment fill in.

A person still talks to each lead and decides when it's a deal. They confirm the draft and design the system in Pylon, send the proposal, and sort out whatever the system holds back, like a deal with no street address.

Now the detail. It's one Python service on Render, with a Postgres database. A lead posted in has its signature or key checked, is saved as a job, and gets an answer straight away. Every write to Zoho or Pylon is keyed, so a repeat does nothing. A job that keeps failing is parked, flagged and retried daily.

The emails come through Microsoft Graph with the app's own identity, not a person's. Graph can list every message in a mailbox, not just one folder. That matters, because a mail rule files one supplier's emails into their own folder. Each email is routed by sender, and a plain parser reads the labelled fields. No AI reads them.

Zoho can insert or update a record in one call, matching on a module's duplicate check fields, like email for leads. We needed email or phone, across leads and contacts, with numbers in either format. So the system runs a COQL query first.

Zoho also runs the business's workflow rules on records written through its API, unless the request says not to. The system's deal edits say not to, so a sync doesn't send customer emails by itself. Moving to Contract Completed is the exception, and runs their workflows on purpose.

Pylon's API can create projects that stay uncommitted until someone confirms the location, and Pylon only charges credits then. So every new deal can have a project. Pylon and Zoho both notify the system when records change, so it acts within seconds. It still polls both every few minutes, and the polls are the source of truth.

The hard part was jobs that start on either side. A project can exist in Pylon before there's a deal, so the system pairs them from either direction, one to one, and holds any pairing it can't prove. Equipment is matched by model number against Zoho's own list.

It went live in July 2026, and it's running. There's no before and after measure, so there's no result figure in this film.

If you're typing the same customer into Zoho and a second system, get in touch.

When a lead becomes a deal, the service pairs it with a project in Pylon, the solar design and proposal tool, or creates a draft. When the customer signs, the deal fills in its own design details.

How and why they came

They got in touch through the form on our website. Every lead and every signed job was being typed in by hand, and they wanted that to stop.

The problem

  • Leads arrived in three places: the website form and two lead suppliers. Each one was typed into Zoho.
  • To design a system, the customer was typed again into Pylon.
  • When the customer signed, the totals and equipment were typed back into Zoho.

What we built

  1. 1

    Three ways in

    The website form and one supplier post each lead straight to the service. Both suppliers also send notification emails, which the service reads from the business's mailbox. Each source has its own reader, and every lead becomes the same shape, with phone numbers in one international format and emails in lower case.

  2. 2
    Zoho CRM

    One lead per person

    Before writing anything, the service checks its own records, then searches Zoho's leads and contacts for that email or phone. Someone new becomes a lead, tagged with its source and marked new for a day. A repeat enquiry updates their existing lead. An existing customer isn't added again, and the team gets a message instead.

  3. 3
    Zoho CRM

    A project for each deal

    When a lead becomes a deal in Zoho, the service looks in Pylon for a project with the same contact and full site address. One match, and it links them. None, and it creates an unconfirmed draft. If two could match, it holds the deal and tags it for a person.

  4. 4
    Zoho CRM

    The proposal link

    When a design is ready, its proposal link is written onto the deal, for the proposal email from Zoho.

  5. 5
    Zoho CRM

    The signed job

    When the customer signs in Pylon, the deal moves to Contract Completed, and its system size, battery, panel count, prices and equipment fill in.

Every write to Zoho or Pylon is keyed in Postgres, and the service records what it did in an audit table.

The system's own output on made-up leads

  • The website enquiry, written to Zoho as a new lead tagged Website.

    The system's own output. Sample data.

  • After the same leads were sent again: updates, no second lead.

    The system's own output. Sample data.

  • A new deal gets an uncommitted draft project in Pylon.

    The system's own output. Sample data.

  • On signing, the deal fills in the signed design's details.

    The system's own output. Sample data.

What a person still does

A person talks to each lead and decides when it's a deal. They confirm the draft and design the system in Pylon, send the proposal from Zoho, and sort out whatever the service holds back, such as a deal with no street address or two projects that could both match.

The technical detail

What each system allowed

Zoho CRM

  • Zoho's upsert inserts or updates a record in one call, matching on duplicate check fields in one module, such as Email for leads.1
  • The service needed email or phone, across leads and contacts, with numbers in either format, so it runs a COQL query first.
  • COQL is Zoho's SQL-like query language for fetching records.2
  • When a request doesn't say which automations to run, Zoho runs the related workflows, and an empty trigger list stops them.3
  • Zoho can also notify an app when records change; a channel lasts at most a week, and an hour if no expiry is given.4

Pylon

  • Pylon's API can create projects that stay uncommitted until someone confirms the location.1
  • They wait in an "Awaiting activation" list, and credits are only charged at confirmation.1
  • Webhook destinations are set up in the account's API settings, and each delivery is signed with HMAC SHA-256 over its timestamp and body.2

Microsoft Graph

  • An app can call Graph with its own identity through the client credentials flow, with no signed-in user.1
  • Graph can list every message in a mailbox, or one folder's.2

Vendor links checked 17 November 2026.

Design decisions

  • Polls are the source of truth

    Pylon and Zoho notify the service when records change, so it acts within seconds. It still polls both every few minutes, so a missed notification is picked up on the next pass.

  • Thin front door

    A lead posted in has its signature or key checked, is saved as a job, and gets an answer straight away. The slow work happens off the request.

  • A repeat does nothing

    Each delivery and each write has its own key. The same delivery twice makes one job, and the same enquiry twice makes one lead.

  • Sync edits stay quiet

    The service's edits to deals tell Zoho not to run workflows, so a sync doesn't send customer emails by itself. Moving to Contract Completed is the exception, and runs the business's workflows on purpose.

  • No AI in the email step

    A plain parser reads the labelled fields in each notification email. An email it can't read is flagged for a person instead of guessed at.

The hard parts

  • Jobs that start on either side

    A project can exist in Pylon before there's a deal in Zoho. The service pairs them from either direction, one project to one deal, and holds any pairing it can't prove.

  • A mailbox with folders

    A mail rule files one supplier's emails into their own folder, so the service lists messages across the whole mailbox and routes each one by its sender.

  • Equipment names

    Equipment is matched by model number against the options Zoho already has. A new product is added to that list, and a model that matches more than one option is left blank and flagged.

How exceptions reach a person

An existing customer enquires
A message to the team, and no new lead.
A deal with two possible projects, or no street address
The deal is tagged in Zoho and the team gets a message.
A job that keeps failing
It's parked, the team gets a message, and a daily sweep tries it again.

A deal with two possible projects, tagged and flagged instead of guessed at.

The system's own output. Sample data.

Where it stands

Live since

July 2026

  • It went live in July 2026, and it's running.

There's no before and after measure, so there's no result figure on this page.

Questions

Can Zoho CRM stop duplicate leads coming in from several sources?

Zoho's upsert matches records on duplicate check fields in one module, such as Email for leads. On this job a person could arrive by email or phone, as a lead or an existing contact, so our service searches leads and contacts with a COQL query before it writes.

Can a new deal in Zoho create a project in Pylon?

Yes. Pylon's API can create uncommitted projects, and Pylon only charges credits when someone confirms the location. Our service creates one for a new deal unless it finds a matching project, and holds the deal if two could match.

Will updates made through the Zoho API set off our workflow rules?

Zoho runs the related workflows unless the request says not to. Our service tells Zoho not to on its deal edits, except the move to Contract Completed, which runs the business's workflows on purpose.

Does AI read the lead emails?

No. A plain parser reads the labelled fields. An email it can't read is flagged for a person instead of guessed at.

What happens if Zoho or Pylon is down for a while?

Every lead is a job that retries, and the pollers try again on their next pass. A job that keeps failing is parked, flagged and tried again by a daily sweep, and the regular polls pick up anything a missed notification would have brought.

Typing the same customer into Zoho and a second system?

Book Free Assessment

Product names and logos belong to their owners and are shown to identify the systems connected.