--- title: "Check Solar Installation Readiness Across Salesforce and NetSuite" description: "Check Solar Installation Readiness Across Salesforce and NetSuite. Follow the evidence, approvals, and completion checks with a copyable Genie job description." canonical: https://www.stacksync.com/blog/check-solar-installation-readiness-across-salesforce-and-netsuite last_modified: 2026-09-18 --- # Check Solar Installation Readiness Across Salesforce and NetSuite > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md An installation readiness check compares the Salesforce schedule with equipment, permit, and crew evidence. Author Ignacio Malpartida · GTM Engineer Published September 15, 2026 Updated September 18, 2026 Read time 8 min read APP TIPS ## Review the next two weeks as a set of dependencies An installation readiness check compares the Salesforce schedule with equipment, permit, and crew evidence. Every morning, review projects scheduled within the next two weeks and create tasks for anything that could block the planned installation. Readiness depends on the combination of required conditions, not the presence of a date on a calendar. Use the project’s approved scope and required equipment list. Link Salesforce projects to NetSuite demand or allocation records and the corresponding permit and crew records in Postgres. Missing relationships should be surfaced as evidence gaps, because the wrong project’s inventory or permit can make an unready installation appear ready. ![Select the schedule: Every morning, review Salesforce installations scheduled in the next two weeks.; Check permits and crews: Read project-specific permit status and crew availability from Postgres.; Re-evaluate readiness: Refresh the dependency evidence when tasks or source records change.](https://www.stacksync.com/images/blog-highlights/genies-installation-readiness-guide.webp) *Select the schedule: Every morning, review Salesforce installations scheduled in the next two weeks.; Check permits and crews: Read project-specific permit status and crew availability from Postgres.; Re-evaluate readiness: Refresh the dependency evidence when tasks or source records change.* ## Systems and prerequisites This is a workflow design to configure with Stacksync Genies and your existing systems. Connecting an application does not by itself establish the permissions, record mappings, approval routing, or operational process described here. Before enabling the job, confirm which records the Genie can read, which actions it can take, and who receives clarification or approval requests. | System or owner | Evidence and responsibility | | --- | --- | | Salesforce | Installations scheduled in the next two weeks, project scope, dates, and responsible owners. | | NetSuite | Equipment stock, existing allocations, and incoming purchase orders. | | Postgres | Project-linked permit status and crew availability records. | Required context for this workflow design. ## Check equipment that is actually available to the project Inspect the exact equipment, required quantities, location, current allocation, and incoming purchase orders. On-hand stock committed to another installation does not cover this project. For inbound equipment, compare expected receipt with the scheduled work and the organization’s receiving and transport allowances. An open purchase order does not prove the equipment will be on site in time. Read required permit status and crew availability from the operational records. Do not infer a permit from an uploaded filename or a previous project at the same location. Do not infer crew capacity from a roster that lacks the relevant scheduled assignment. The review should identify what the authoritative record confirms and what still requires an owner’s action. ## Create specific tasks and refresh them each morning For each blocker, identify the project, requirement, evidence, responsible owner, and action needed. Equipment gaps belong with the supply or project owner, permit gaps with the responsible permitting owner, and crew conflicts with scheduling. Use the organization’s assignment and due-date rules rather than inventing staff responsibilities. Update existing unresolved tasks on repeat runs and close or resolve them only when the evidence supports that change. Never mark a project ready when required equipment is allocated elsewhere or a required permit is missing. This administrative check supports project coordination; it does not replace technical, safety, or authority decisions for the installation. ## A five-step operating sequence 1. 01 Select the schedule Every morning, review Salesforce installations scheduled in the next two weeks. Match project identifiers to the operational equipment, permit, and crew records. Missing links should be visible evidence gaps rather than silently skipped prerequisites. 2. 02 Check supply and allocation Compare required equipment with usable NetSuite stock, existing allocations, and incoming purchase orders. Account for receiving and transport timing under the operation’s planning rules. Equipment committed elsewhere does not make the current project ready. 3. 03 Check permits and crews Read project-specific permit status and crew availability from Postgres. Use the authoritative definitions for required approvals and scheduled capacity. A submitted permit or a general crew roster does not necessarily satisfy the actual installation prerequisite. 4. 04 Assign blockers Create or refresh tasks for the responsible equipment, permitting, and scheduling owners. State the project, missing condition, source evidence, and needed action. Use existing tasks on repeated reviews so owners receive updated evidence instead of duplicate work. 5. 05 Re-evaluate readiness Refresh the dependency evidence when tasks or source records change. Never mark ready while equipment is allocated elsewhere or a required permit is missing. The administrative result supports coordination and does not replace technical or safety release authority. ![Check Solar Installation Readiness Across Salesforce and NetSuite — select the schedule, then check supply and allocation, then check permits and crews, then assign blockers, then re-evaluate readiness.](https://www.stacksync.com/images/blog-diagrams/genies-installation-readiness.webp) *Check Solar Installation Readiness Across Salesforce and NetSuite — select the schedule, then check supply and allocation, then check permits and crews, then assign blockers, then re-evaluate readiness.* ## Illustrative workflow example A project scheduled next Tuesday needs six units. NetSuite holds six, but all are allocated to another project. The check creates an equipment-allocation task and keeps readiness blocked despite the positive on-hand quantity. This example uses fictional records to show the decision logic. It is not a customer case study or a claim of measured results. In a live case, retain the actual record IDs and evidence behind each statement, and replace all illustrative quantities or timing assumptions with the approved operational inputs. ## What the handoff should contain A project readiness matrix for the next two weeks with equipment, allocation, inbound timing, permit, and crew evidence plus one owned task per unresolved blocker. Keep the evidence reference, observation time, current owner, and outstanding decision with the case. A colleague taking over should be able to distinguish a proposal from a confirmed result without reading every previous message. If a source value changes while the case is waiting, recheck the affected decision before proceeding. ![Required systems feed case verification; missing evidence or decisions return to clarification before the workflow proceeds.](https://www.stacksync.com/images/blog-diagrams-mermaid/genies-installation-readiness.webp) *Required systems feed case verification; missing evidence or decisions return to clarification before the workflow proceeds.* ## Approval and completion checklist - Review Salesforce installations scheduled within the next two weeks every morning. - Check equipment allocations and incoming supply, not only gross stock. - Check required permits and crew availability in project-linked Postgres records. - Create owner tasks; never mark ready with equipment allocated elsewhere or a missing required permit. ## Validate the job before enabling it Start with a small reviewed set of cases from the systems above. Include a complete case, an ambiguous match, a missing source record, and an interrupted action where the result is uncertain. Use a draft or test environment for validation and compare the output with the source records before allowing the configured production actions. For this job, the most important checks are review Salesforce installations scheduled within the next two weeks every morning. Create owner tasks; never mark ready with equipment allocated elsewhere or a missing required permit. Record the expected result before the trial, then compare both the proposed action and the final evidence. A fluent message is not a passing result if it skips one of these conditions. - Scheduled projects with all required evidence checked - Blockers with a responsible owner and current task - Ready statuses invalidated by missing permits or conflicting allocations Use these as operating measures, not promised performance improvements. Establish the current baseline and review exceptions with the team that owns the process. Investigate an increase in incorrect matches, unauthorized actions, or premature closure before expanding the job’s scope. ## Give your Genie a job description Copy the job description below. It preserves the scope and decision boundaries of this use case. Configure the referenced systems, record relationships, policies, and approval owners in your workspace before enabling the job. Installation readiness · Medium Every morning, review installations scheduled in Salesforce for the next two weeks. Check equipment availability, existing allocations, and incoming purchase orders in NetSuite, plus permit and crew availability recorded in Postgres. Identify anything that could block installation and create tasks for the responsible owners. Do not mark a project ready when equipment is allocated elsewhere or a required permit is missing. Paste this into “Give your Genie a job description.” [Explore Stacksync Genies](https://www.stacksync.com/ai-agents). ## Apply this in solar installation and O&M services: proposed equipment swap and technical review Equipment changes can invalidate an earlier solar-readiness decision, while project closeout requires evidence from the completed installation. The linked guides handle those adjacent transitions: reapprove the changed scope and assemble the final serial-number and handover packet. | Record to reconcile | Responsible owner | Rule to preserve | | --- | --- | --- | | Proposed equipment swap | Procurement or project manager | Identify original requirement, alternative and reason for the change. | | Technical review | Qualified technical owner | Record the accepted specification decision and any conditions. | | Commercial revision | Account and project owners | Capture price, schedule and scope effects for customer review. | An exception to plan for: **Technical approval includes conditions**. Keep those conditions attached to the handoff and verify the responsible team accepts them. Acceptance check for the pilot: original and proposed equipment remain distinguishable. The [solar installation and O&M services hub](https://www.stacksync.com/industry/construction/solar-installation-service) connects the broader operating context. These guides develop the specific record mappings and decisions for this application: - [Solar Project Change Orders: Route Equipment Swaps Through Approval and Revised Billing](https://www.stacksync.com/blog/solar-project-change-orders-route-equipment-swaps-through-approval-and-revised-billing) - [Genies for Solar Project Closeout: Assemble Serial Numbers, Completion Evidence, and Handover Records](https://www.stacksync.com/blog/genies-for-solar-project-closeout-assemble-serial-numbers-completion-evidence-and-handover-records) - [Solar Equipment Change-Order Workflows](https://www.stacksync.com/use-case/solar-equipment-change-order-workflows) - [AI Project Closeout for Solar Installers](https://www.stacksync.com/use-case/genies-solar-project-closeout) ## Related workflow and integration guides - [Identify Equipment Allocation, Permit, and Crew Blockers](https://www.stacksync.com/blog/identify-equipment-allocation-permit-and-crew-blockers) - [All Genies workflow examples](https://www.stacksync.com/ai-agents#genies-use-cases) - [When a workflow should escalate to a person](https://www.stacksync.com/blog/human-in-the-loop-automation-when-to-escalate) - [Qualify and Route Commercial Solar Inquiries in HubSpot](https://www.stacksync.com/blog/qualify-and-route-commercial-solar-inquiries-in-hubspot) - [Coordinate Equipment Repairs Across Service, Inventory, and Scheduling](https://www.stacksync.com/blog/coordinate-equipment-repairs-across-service-inventory-and-scheduling) - [Aurora PostgreSQL and Salesforce in Both Directions, Step by Step](https://www.stacksync.com/blog/sync-aurora-postgresql-with-salesforce) - [Netsuite integrations](https://www.stacksync.com/connectors/netsuite) - [Salesforce integrations](https://www.stacksync.com/connectors/salesforce) ## Implementation references These first-party references document the underlying records and interfaces. The cross-system sequence, approvals, and completion rules in this article are a proposed operational configuration; validate them against your connected workspace before enabling it. - [NetSuite: inventory availability and allocation](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_157236254323.html) - [NetSuite: inbound supply and partial quantities](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_159171354002.html) FAQ ## Frequently asked questions What does the installation readiness workflow produce? A project readiness matrix for the next two weeks with equipment, allocation, inbound timing, permit, and crew evidence plus one owned task per unresolved blocker. What should the team verify before the job can proceed? Review Salesforce installations scheduled within the next two weeks every morning. Check equipment allocations and incoming supply, not only gross stock. About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector PostgreSQL integrations](https://www.stacksync.com/connectors/postgresql) - [platform AI agent operations](https://www.stacksync.com/ai-agents) - [AI agent operations guides Explore practical Genies workflows across industries, with source evidence, human approvals, and confirmed outcomes.](https://www.stacksync.com/blog#topic-ai-agent-operations) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Identify Equipment Allocation, Permit, and Crew Blockers 7 min read read](https://www.stacksync.com/blog/identify-equipment-allocation-permit-and-crew-blockers) [App tips Solar Service Visits: Route Confirmed Repair Completion Into O&M Billing 5 min read read](https://www.stacksync.com/blog/solar-service-visits-route-confirmed-repair-completion-into-o-m-billing) [Data engineering Solar Fleet Ownership Changes: Align Salesforce Asset Owners With NetSuite Billing Customers 5 min read read](https://www.stacksync.com/blog/solar-fleet-ownership-changes-align-salesforce-asset-owners-with-netsuite-billing-customers) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)