Solar AI-Q - Pylon Bi-Directional Integration
By Pipereply | Oct 24, 2025
This integration provides a two-way syncing between Solar AI-Q and Pylon. It ensures that opportunities, projects, and signed proposals flow cleanly between systems while maintaining a single source of truth in Pipereply. Please note that you require at least one CRM seat in Pylon.
🔒 Security
  • All inbound Pylon webhooks are validated by a secure proxy.
  • The proxy uses the Webhook Secret generated in Pylon to verify signatures.
  • Only validated payloads are processed.
Minimum Data Requirements
Before pushing a contact to Pylon for project creation, you MUST have the following in Pipereply.
Contact Name
Address
Email
Pipereply → Pylon (Project Creation)
Trigger
  • Typically initiated when a salesperson updates the opportunity status in Pipereply (e.g., after a sales meeting).
  • This executes the Quote Requested outcome which moves the opportunity to the Create Project stage.
Logic
Matches contact by email:
  • If the contact exists in Pipereply, with a Name, email, and address, then a lead can be created in Pylon.
  • If the contact is missing key information in Pipereply, no lead is created.
Fields pushed into Pylon from Pipereply
  • Contact details: first name, last name, email, phone, address (line1, line2, city, state, postcode, country).
  • Project info: project ID (from Pipereply), source name + ID, notes.
  • Custom property values: customer type, building classification, roof material, number of storeys, power phases, NMI, energy retailer.
  • Tags: pipeline and project status tags.
Pylon → Pipereply (Project Updates)
Triggers
Proposal Sent: When a project is shared from Pylon.
Note: The Opportunity MUST be in Pipeline-3 for this initial sync to occur when sending a proposal, after that the match is made via Project ID.

Proposal Signed: When a customer signs a proposal in Pylon.
Logic
  1. Finds the matching Pipereply contact via email.
  1. Then finds the matching Opportunity via project_id custom field.
  1. If one opportunity is found without a Pylon project ID then that Opportunity is updated and linked.
  1. if two Opportunites are found, one with an ID and one without. If the ID doesn't match, then the Opportunity without the ID is updated. Otherwise the Opportunity with the matching ID is.
  1. if two opportunites are found, both without Pylon project IDs, then the update is ignored as there is no way to know which Opportunity should be updated.
  1. the key is to move one Opportunity at a time to Pipeline-3, create and send that proposal so the link is made before moving another Opportunity for the same contact to Pipeline-3.
Updates at Proposal Sent
Contact custom fields:
  • ai_project_summary → Pretty JSON of up to 3 design options.
  • proposal_link → Direct link to the primary design.
  • proposal_compare_link → Compare link if multiple designs exist.
Opportunity custom fields:
  • project_status → “Project Sent”.
  • date_quoted.
  • project_link (primary design).
  • project_compare_link (if multiple designs).
  • Technical + pricing details:
  • Panel make/model, inverter, battery.
  • PV size, STC values, purchase prices (inc/ex GST).
  • project_options_ai_summary → JSON summary of design options.
  • Per-option summaries (option_1, option_2, option_3) including size, make/models, prices, discounts.
Updates at Proposal Signed
Opportunity custom fields:
  • project_status → “Project Sold”.
  • date_signed.
  • project_link.
  • System details (same as above).
  • Final pricing (inc/ex GST).
  • STC discounts.
  • Links: snapshot, signed PDF, handover pack.
Status/pipeline change:
  • Pipeline = Quote to Sale.
  • Stage = Project Sold.
  • Status = Won.
Document Handling
  • Signed proposal PDF is stored in Pipereply’s Media Library under Signed Proposals.
  • Client handover documentation is attached to the Pipereply opportunity under Project Installation Status.
Mud Maps - Process Overview
Pipereply → Pylon
  1. Sales rep updates the Opportunity via the Status Update Form in Pipereply
  1. The workflow API sends the Contact + Site data to Pylon
  1. Pylon creates a Lead (with tags & custom props) for review
  1. Inside Pylon, a user clicks Create Project on the Lead
  1. Pylon creates the Project (ready for design & sending the proposal)
Pylon → Pipereply
  1. Pylon triggers webhook (proposal sent or signed).
  1. Secure proxy validates payload.
  1. Pipereply finds matching contact by email.
  1. Pipereply finds matching opportunity by project_id.
  1. Updates contact/opportunity fields:
  • At Proposal Sent → push designs, pricing, links.
  • At Proposal Signed → update status to sold, attach signed docs.
❗ Key Rules
Pipereply is the system of record.
Projects are always created from Pipereply first.
If the contact does not exist in Pipereply, and you send a proposal from Pylon, the sync does not run.
Opportunities must include the Pylon Project ID for updates to match correctly. This is added the first time your send a proposal.
All data moves through a secure, validation proxy.
Update One Opportunity at a Time
To ensure the system can find and link the correct opportunity, only have ONE opportunity for a partiqular contact in Pipeline-3 at a time. Once you have sent the proposal the Opportunity will move to Proposal Sent, at this time you can move the next Opportunity for that same contact to Pipeline-3 and repeat the process.
Pylon Integration – Video Summary
This video shows how Pipereply and Pylon work together to streamline your quoting process:
  • Start with a New Lead in Pipereply → this creates a matching lead in Pylon.
  • In Pylon, simply add and design the project (panels, inverter, battery if needed).
  • Once the proposal is sent, Pipereply automatically updates with:
  • Project details
  • Pricing and STCs
  • Proposal links (primary + compare)
  • When the proposal is signed, Pipereply updates again, marking it as Sold, and stores the signed PDF and handover documents.
✅ End result: everything stays synced in Pipereply — your single source of truth — while Pylon handles the project design and proposal generation.