Feedback

Third-Party Integration Request: ChatGPT / OpenAI I would like to request an integration between Inspection Support Network (ISN) and ChatGPT/OpenAI. Ideally, I would like the integration to allow authorized access to: * Inspection orders and scheduled appointments * Property address and property information * Client and agent information * Inspection type and selected services * Appointment date, time, and inspector * Inspection/order notes * Payment and agreement status * Inspection status * Report information, observations, comments, and narratives where supported * Uploaded inspection photos/files where supported * Calendar and scheduling information I would also be interested in allowing authorized write actions, with appropriate permissions and safeguards, such as: * Creating or updating inspection orders * Adding or updating inspection notes * Updating scheduling information * Creating client or agent records * Assisting with inspection report narratives and comments * Adding or updating report information where supported * Creating tasks or follow-up items The goal would be for me to interact with my ISN account conversationally through ChatGPT. For example, I would like to be able to ask: “Show me my inspections scheduled for tomorrow.” “Pull up the information for my 10:00 AM inspection.” “Has the client signed the agreement and paid for tomorrow’s inspection?” “Summarize the property information and services I am performing before I arrive.” “Help me clean up the inspection comments from today’s inspection.” “Show me inspections that still have unsigned agreements or unpaid invoices.” “Add a note to this inspection order.” I understand that certain actions may need to remain read-only or require confirmation before ChatGPT is permitted to make changes. A secure API-based integration using ISN’s existing API and webhook capabilities would be ideal. I would be willing to participate in testing or provide additional information about the workflow if helpful. This integration could significantly reduce administrative work for home inspectors by combining ISN’s scheduling, order management, and reporting capabilities with an AI assistant. Thank you for considering this integration.

We're trying to set up a Zapier integration to pull order data (specifically a custom Order Info field, "Referral Reasons") via the ISN REST API, using our Access Key and Secret Access Key. Endpoint tested: https://goisn.net/sunbeltinspections/rest/order/{id} , and also the simpler https://goisn.net/sunbeltinspections/rest/me Auth method: Basic Auth (Access Key as username, Secret Access Key as password), tested via both Zapier's native Basic Auth field and a manually base64-encoded Authorization header - same result both times. Error received on every attempt, including the simple /rest/me endpoint: "You must login to use this service (username received: '' - password had 0 characters)" This suggests the credentials aren't reaching ISN's auth layer at all when sent via Zapier's Webhooks step, even though the request structure matches your documented example (https://[domain]/[company]/rest/...) exactly. Could your Development team confirm whether ISN's API currently supports authentication from tools like Zapier, or advise on the correct request format? Company key: sunbeltinspections

Currently, we have integrated ISN with our Zoho CRM. Whenever a new agent is created or an existing agent is updated in ISN, we sync the data with our CRM. We are using the ISN ID as the unique key for each agent. Just to give you some additional context, our integration currently calls the ISN API every 2 hours. Our main requirement is to understand how the agent profile merge process works in ISN so that we can replicate the same behavior in our CRM. For example, when two or more agent profiles are merged in ISN: 1.Does ISN create a completely new agent profile with a new ISN ID? Or does ISN retain one of the existing profile/ISN IDs and merge the other profiles into it? What happens to the profiles/IDs that are merged into the retained profile? How can we identify through the API that a merge has occurred and determine which profile/ISN ID should be considered the primary record? Currently, when an agent profile is merged in ISN, the API payload we receive contains the key "Show" = "No". We would like to understand the exact behavior and logic behind this when a merge occurs. This will help us determine how we should handle the same scenario in Zoho CRM and ensure that our CRM records remain properly synchronized with ISN.

Below is the payload I'm getting. I have added a test order #6714, address seems to be selected correctly, it's fully confirmed, so no reason for this to happen. Also I can see other fields like "inspector" are blank as well, but this order has an inspector. Can you pls fix this issue? "payload": { "ck": "robbinshomeinspections", "id": "ad4606b4-050c-4593-98a9-1ca60029950c", "os": false, "fee": 0, "oid": 6714, "red": false, "utc": "2026-08-11T21:31:06+00:00", "zip": null, "city": null, "fees": { "fees": [], "taxes": 0, "total": 0, "coupons": [], "deletedFees": [] }, "type": "Residential Inspection", "user": "015fecc3-0595-43cd-b257-f1cbbcf744f9", "local": "2026-08-11T17:31:06-04:00", "state": "FL", "taxes": 0, "total": 0, "action": "ORDER_CREATED", "domain": " 4isn.com ", "signed": null, "address": ", FL", "coupons": 0, "created": "2026-08-11 17:31:03", "address1": null, "address2": null, "datetime": "2026-08-11 17:00:00", "order_id": "ad4606b4-050c-4593-98a9-1ca60029950c", "completed": null, "inspector": null, "order_dte": "2026-08-11 17:00:00", "order_oid": 6714, "scheduled": null, "amount_due": 0, "created_by": "015fecc3-0595-43cd-b257-f1cbbcf744f9", "client_last": null, "created_utc": "2026-08-11T21:31:06+00:00", "client_email": null, "client_first": null, "completed_by": null, "scheduled_by": null, "client_mobile": null, "created_local": "2026-08-11T17:31:06-04:00", "paid_datetime": "2026-08-11T17:31:05-07:00", "report_number": "0811266712", "buyers_agent_id": null, "created_by_name": "Chris Robbins", "signed_datetime": null, "buyers_agent_red": null, "order_created_by": "015fecc3-0595-43cd-b257-f1cbbcf744f9", "sellers_agent_id": null, "buyers_agent_last": null, "buyers_agent_tags": null, "completed_by_name": null, "scheduled_by_name": null, "sellers_agent_red": null, "buyers_agent_email": null, "buyers_agent_first": null, "order_completed_by": null, "order_scheduled_by": null, "sellers_agent_last": null, "sellers_agent_tags": null, "buyers_agent_agency": null, "buyers_agent_mobile": null, "order_report_number": "0811266712", "sellers_agent_email": null, "sellers_agent_first": null, "sellers_agent_agency": null, "sellers_agent_mobile": null, "buyers_agent_total_fees": null, "sellers_agent_total_fees": null, "buyers_agent_agency_address": null, "sellers_agent_agency_address": null, "buyers_agent_inspection_count": null, "sellers_agent_inspection_count": null },

We use http://Seeb.ai as an AI call and scheduling assistant and need it integrated with ISN. At minimum, it needs real-time, read-only access to our live scheduling calendar so it can accurately communicate appointment availability to callers. Ideally, it would also have access to the appropriate inspection or appointment request form to assist with scheduling.

i want to fetch data of orders through API, from this account , did you provide the api for that, i have to map these data in whatconverts. more over for future support please add these email into your ticket furqan@digilatics.com , aras@digilatics.com , areebah.mazhar@digilatics.com

After speaking with a representative, I have been told syncing only occurs every 6 hours. This time frame is too long. Multiple overlapping bookings can happen in 6 hours. I would like to see this syncing frequency be reduced to either near instantly or at least only a few minutes, not 6 whole hours.

I want to be able to read and write notes to a specific order via API

We really like features of ISN and Housecall Pro. Is there any idea if ISN will be working together with Housecall Pro in the future? We have two businesses so keeping the schedule up to date is a necessity and if someone orders an inspection through ISN before I have the opportunity to block it off in the ISN calander, then I have to make calls to reschedule what they just scheduled. The integration of both applications working together would be amazing.

ISN is auto populating the square footage & age. Particularly since so much is only on the private listing network, we are finding these numbers to be wrong & thus causing confusion. If it's a condo the system pulls the square footage from a unit that is actually publicly listed rather than the unit we are actually inspecting. We've had schedulers quote the wrong price as a result.