Aurora Solar
Last updated: November 25, 2025
Overview
The Aurora Solar integration connects your Aurora Solar account to your Coperniq account to automatically sync project data. It reduces manual entry and connects pre-sale to post-sale.
How It Works
The integration uses webhooks from Aurora. When specific events occur in Aurora (e.g., an agreement is signed), Aurora sends a notification. The integration then:
Retrieves the relevant project data from Aurora
Maps it to your project fields
Creates or updates projects in your Coperniq account
Attaches proposals and agreements as files
Adds line items to the Coperniq project
Bidirectional Integration
The integration works in both directions:
Coperniq → Aurora (Pre-Sale Flow)
Create an Aurora project directly from a request in your system
The integration automatically links the two systems
Pre-sale triggers are set up to track proposal engagement
Aurora → Coperniq (Post-Sale Flow)
When an agreement is signed or project status changes in Aurora, a project is automatically created/updated in your system.
All design, pricing, and customer data is synced.
Documents are automatically attached.
Creating Aurora Projects from Requests
How It Works:
From a request in your system, select "Sales" >> "Proposal" >> "Create Project in Aurora Solar"
The integration automatically:
Creates a new project in Aurora with customer and address information
Links the Aurora project to your request
Sets up pre-sale tracking triggers
Note: The request value must be a value greater than 0.
What Gets Sent to Aurora:
Customer information (name, email, phone)
Property address (full address with coordinates)
Project type (residential or commercial)
Request title and basic details
After Creation:
The Aurora project is linked to your request
Pre-sale triggers are automatically configured to track:
When proposals are sent
When customers view proposals
When customers sign agreements
As you work in Aurora (create designs, send proposals, etc.), your request is automatically updated with status changes and documents
What Data Gets Synced
You can find the detailed field mappings here.
Project Information:
Customer details (name, email, phone, address)
Project location (full address, coordinates)
Project status and type (residential/commercial)
Project owner/team assignments
Project tags and metadata
Design & System Details:
System size (AC/DC capacity in kilowatts)
Design specifications (arrays, modules, inverters, batteries)
Energy production estimates (annual/monthly)
Solar access and shading data
Bill of materials (equipment list)
Pricing & Financial Information:
System pricing (flat price, price per watt, or breakdown)
Financing options (Cash, Loan, Lease, PPA)
Incentives and adders
Monthly payment information
Documents:
Proposals (PDFs automatically generated and attached)
Signed agreements (downloaded and attached to projects)
Additional Data:
Utility information and rates
Project milestones and status changes
Triggers & Automation
Pre-Sale Triggers (updates existing projects/requests):
Agreement Sent: when a proposal is sent to a customer
Agreement Viewed: when a customer views the proposal
Agreement Accepted: when a customer signs the agreement
Note: Pre-sale triggers are automatically set up when you create an Aurora project from a request.
Post-Sale Triggers (creates new projects):
Agreement Status Changed: when an agreement is sent, viewed, or signed (default: signed)
Project Status Changed: when a project status changes in Aurora
What You Can Control
1. Trigger Configuration
Choose which events create projects (e.g., only when agreements are signed)
Set up pre-sale triggers to track proposal engagement
2. Workflow Automation
Assign a workflow template to automatically start workflows for new projects
Projects can enter your standard process immediately
3. Data Field Mapping
Map Aurora fields to your custom project fields
Control which data populates which fields (1 to 1 mapping)
4. Duplicate Handling
Choose what happens if a matching project already exists:
Skip: don't create a duplicate
Update: update the existing project with new data
Create: always create a new project
5. Project Matching
Configure how the system identifies existing projects (e.g., by email, project ID, or address)
Set primary and fallback matching fields
6. Integration Logs
View all sync activity and troubleshoot issues
See what data was received and how it was processed
Typical Workflows
Scenario 1: Post-Sale Project Creation
Customer signs an agreement or project status changes in Aurora
Integration automatically creates a project in your system
Project includes all design, pricing, and customer information
Signed agreement PDF is attached
Project enters your assigned workflow
Scenario 2: Pre-Sale Tracking (Request → Aurora)
You create a request in your system
You select "Create Project in Aurora Solar" from the request
A project is created in Aurora with customer and address information
The two systems are linked
As you create designs and send proposals in Aurora, your request is automatically updated with:
Proposal status (sent, viewed, signed)
Proposal PDFs
Design details and pricing
Agreement documents when signed
Benefits
Eliminates manual data entry
Ensures data accuracy
Keeps projects synchronized automatically
Captures documents automatically
Supports your existing workflows
Provides visibility into sync activity
Enables seamless handoff from requests to proposals
Tracks customer engagement with proposals in real time
Setup Requirements
Aurora API token
Aurora tenant ID
Access to configure the integration in your platform
This integration streamlines the flow between Aurora Solar and your platform, reducing manual work and keeping your team focused on customer relationships rather than data entry. Whether you're starting from a request in your system or receiving signed agreements from Aurora, the integration keeps everything in sync automatically.