Change Log

New Features

• Per-endpoint Markdown documentation, designed for use with AI assistants. Each endpoint can now be exported as a clean Markdown snippet containing the cURL and Controller request examples, parameter list, response shape, and object reference.
• "Copy for LLM" and "View as Markdown" buttons added to every endpoint — copy the endpoint's full Markdown to your clipboard, or open the raw Markdown in a new tab to share or paste into your AI tool of choice.
• Resource pages now have a sticky table of contents listing all endpoints, so you can jump between endpoints without scrolling back to the top. Responsive layout on narrower screens.
• Redesigned API documentation layout. Endpoint details on the left, live example request and response on the right — easier to scan, easier to compare an endpoint's parameters against its example output.
• Per-endpoint Markdown now includes the Controller (Liquid) example alongside the cURL example, matching what the HTML docs show.
• Search behaviour for list endpoints is now documented on the API Overview page — which fields are searchable, how search_by / keyword / exact interact, and how search combines with pagination and sort.

Improvements

• Endpoint parameters are now split into clearly-labelled Path Parameters, Body Fields, and Query Parameters sections — no more confusion about which values go in the URL versus the JSON body.
• Every endpoint now has a single canonical URL — /admin/api/<module>/<resource>#<endpoint>. Older URLs redirect there automatically so existing bookmarks and shared links keep working.
• Markdown export's Object section now matches the HTML resource reference — nested fields show with dot notation, object-type parents are typed correctly, and list-only query parameters no longer leak into the response shape.
• Sidebar navigation and dark mode now hold up cleanly across every module.
• Parent-resource path parameters (e.g. event_uuid on event sponsors, cart_uuid on cart items) now show a description instead of rendering blank.
• Body Fields in the Markdown export are cleaner on POST and PATCH endpoints — fixed duplicate rows and broken dot-notation paths on resources with object references.
• Body Fields no longer lists response-only file metadata (.file_name, .extension, .url) under upload fields. The information is still available in the resource's response Object reference where it belongs.
• Test Request panel cleaned up — the API URL preview now uses the same code-block styling as the Example Request, and the payload editor stays in sync with the URL preview.
• Overview and Module Versions pages now share consistent page spacing with the rest of the docs.
• Dark mode polish across the sticky example panel and sidebar.

Security

• Upgraded the axios HTTP client from 0.27.x (end-of-life) to 1.16.0, picking up two years of security patches and bug fixes.
• Removed the bundled jQuery 1.12.4 dependency (end-of-life since 2016, multiple unpatched vulnerabilities).

Bug Fixes

• Controller examples are now valid Liquid out of the box — placeholder values are properly quoted so copy-pasting the example works without manual edits.
• DELETE endpoint cURL examples no longer include an empty request body flag.
• Locale data cached in the browser is no longer wiped when a localisation request fails — previous translations stay loaded until a successful refresh.

Breaking Changes

• Renamed external API v2 routes from /all_assets/api/v2/... to /asset/api/v2/... for a cleaner public API surface. External integrators must update their base path.

New Features

• Added GET /asset/api/v2/credentials so external API consumers can retrieve the S3 presigned-POST credentials required by the Add Asset flow. Listed in the API documentation under a new "Assets Credentials" section.

New Feature

• @insites/logic-engine npm package — new TypeScript library that loads the rule and decision corpus, evaluates when/then decisions, renders scaffold templates, and exposes an MCP-server entry point.
• Versioned rule + decision corpus — markdown rule files plus JSON decision files for module detection, feature-pattern recognition, and scaffolding, used by the engine and by AI tooling.
• API endpoints reference — building inbound JSON endpoints under the V2 surface (api/_external/v2/<resource>/<action>.json.liquid), with auth, method, status-code, error, and pagination conventions.
• CRM controllers reference — controllers conforming to the CRM module's V2 surface using the path: front-matter alias.
• User profile types reference — schema location, GraphQL read via related_record + property accessors, write via record_create/record_update, multi-profile users.
• Payments reference — Stripe integration assembled from api_calls/, constants/, and form callback_actions. Worked Checkout Session example and webhook receiver shape.
• CRM module reference — V2 REST endpoints, custom and system fields, webhook coverage, tasks, activities, attachments, event streams, and a field-by-field schema reference.
• CMS module reference — covers 10 object types (Pages, Layouts, Partials, Web Files, Globals, Collections, Emails, SMS, Authorization Policies), file-based stance, IIA admin paths, and override patterns.
• Data module reference — V2 endpoints for user-defined databases, schema discovery, bulk-loop patterns, and an IIA configuration walkthrough.
• GraphQL profile queries — new section explaining how user_profile_types/ schemas are queried via related_record + property accessors, with multi-profile-type users called out explicitly.

Improvement

• Repository renamed insites-ai-tools → insites-logic-engine to align with the npm package identifier @insites/logic-engine. Install URLs and the GitHub repository updated; the previous URLs remain redirected for a transition period.
• README rewritten around the two deliverables shipped from this repository: skills/insites/ for AI-tool consumption (Claude Code, OpenCode, Cursor) and engine/ + logic-engine/ for programmatic tooling.
• Modules-based project layout documented as the canonical structure: modules/<name>/public/{views,forms,graphql,authorization_policies,api_calls,schema,user_profile_types,emails,migrations,assets}/. New project-structure reference covers per-directory purpose, naming conventions, and module-prefixed render/include/graphql paths.
• State changes via form callback_actions — form definitions at modules/<name>/public/forms/<name>.liquid are documented as the canonical pattern for create/update/delete operations: YAML schema for field declarations and per-field validation, a Liquid callback_actions block for GraphQL mutations and side effects. Worked update_password example covering form_set_error / form_set_field_error / form.errors.
• Pages-as-controllers rule calibrated — small page-specific markup, JSON-page bodies, and short redirect/error pages may live inline; reusable markup belongs in partials, with ~10 lines of HTML as the extract-it threshold.
• Data-fetching boundary — pages own GraphQL calls for new code; partials receive their data through render arguments.
• CLI reference rewritten against the actual insites-cli help output (see also Bug Fix below).

Bug Fix

• Authorization policy output invariant — corrected the truthy/falsy framing. Policies are not Liquid return true/false controllers; the platform compares the file's output as a string against the literal "true". Canonical examples now use single-line {%- ... -%} whitespace-trimmed Liquid that emits exactly true or false. Three concrete failure modes documented: trailing newline, returning a Liquid truthy object, and policy-name typos.
• Logic Engine corpus loading — discriminated-union schema for decision kinds so every module-detection decision is loaded and validated correctly. Added a prepack script that bundles the corpus into the published npm package, plus regex tightening on partial-resolution rules. 23/23 tests passing.
• CLI reference accuracy — the CLI command reference contained 8 inaccurate command signatures, 1 invented command, and 6 missing real commands. Rewritten against the actual insites-cli help output.
• 26 broken markdown links across the skill repaired in a single sweep. Post-fix scan: 0 broken across 812 relative links in 201 files.
• Modules install messaging — replaced misleading 'insites-cli modules install is not yet available' copy with accurate prose: modules are preinstalled per Insites instance and updated through the Insites console; there is no CLI command to install or uninstall modules.
• Install URL branch reference — install scripts pointed at master, but the repository's default branch is main. Corrected to main everywhere so install commands work.

New Features

• Real-Time Instance Creation Status
  • The instance creation process now shows live status updates as each step completes — from setting up the instance to installing each module. The instance card updates in real time (e.g. "Installing CRM / System on My Instance...") so you always know exactly what's happening. The connection automatically recovers if you lose and regain network during the process.
• Custom Date Range for Usage Charts
  • Monthly usage charts (Data Objects, Peak Storage) now include a custom date range picker. Select a specific Start Month and End Month, or use quick presets — This Year, Last Year, Last 12 Months, or Last 6 Months — to filter the chart to the period you need.

Improvements

• Localisation-Aware Date Display
  • Dates across the Console now follow your account's localisation settings, applied consistently across Module Versions, Marketplace items, the Dashboard, and other date displays.
• Relative Dates on Module Versions
  • The Module Version list now shows both the formatted publish date and a relative time label (e.g. "3 months ago", "yesterday", "today") for quicker reference.
• Mobile Filter Layout
  • Filters on the People and Marketplace pages now display as full-width rows on mobile, matching the layout used on the Instances list.
• Usage Charts Default to Last Month
  • Daily usage charts now default to showing the previous month's data instead of the current month, giving you a complete data set to start with.
• CRM / System Breakdown in Data Objects
  • The Data Objects chart now includes a per-table record count breakdown for the CRM / System module, showing exactly where your data objects are being used.
• Retry Mechanism for Module Installation
  • Module installations now automatically retry on transient failures, reducing the chance of a failed install requiring manual intervention.

Bug Fixes

• Fixed an issue where changing the date filter on daily usage charts did not update the chart.
• Fixed "Invalid Date" appearing in the module version list for users with a day-before-month date format (DD/MM/YYYY).

New Features

• External API V2 Endpoints - New v2 API endpoints are now available. Please visit API > Insites API Endpoints for more details.
  • Pipelines
  • Pipeline Stages
  • Opportunities
  • Opportunity Related Contacts
  • System Fields
  • Opportunity Custom Fields

Deploy, manage, and interact with your Insites instances directly from Claude Desktop — no CLI installation or browser login required.

What is CloudShell?

CloudShell is an MCP (Model Context Protocol) server that connects Claude Desktop to your live Insites instances over HTTP. It gives you a direct bridge between your AI assistant and your Insites environment, so you can deploy files, manage environment variables, check logs, and more - all from a single conversational interface.

Why it matters

Traditional Insites development workflows require switching between terminal commands, browser tabs, and deployment tools. CloudShell removes that friction. With a single connection, Claude can read from and write to your instance without you ever leaving the conversation.

This is particularly useful for:

• Rapid prototyping and iteration on pages and templates
• Debugging issues by pulling logs in real time
• Managing environment variables across instances
• Deploying changes without touching the command line

What you can do with CloudShell

Getting started

CloudShell connects via a single endpoint and authenticates using your Insites console credentials passed as HTTP headers. Once configured in Claude Desktop, your AI assistant has direct access to your instance - no additional software to install.

For full setup instructions and tool reference, see the CloudShell documentation.

New Features

• New constants command: set, unset, and list constant variables on an instance.
• New exec command: execute Liquid code or GraphQL queries directly on an instance without deploying files. Supports inline code and --file option.
• --json flag added across 11 commands for structured JSON output (constants list, exec graphql, exec liquid, logsv2 search, logsv2 searchAround, logsv2 alerts list/add/trigger, logsv2 reports, migrations list, modules list).

Bug Fixes

• Fixed data import sending incorrect payload structure.
• Fixed sync error handling for 401 Unauthorized, 404 Not Found, and network connection failures providing unclear or missing error messages.
• Fixed missing authData guard in deploy and sync commands.
• Fixed report module throwing MODULE_NOT_FOUND error.

Improvements

• Expanded logsv2 subcommands: search, searchAround, alerts (list, add, trigger), and reports.
• Various stability and error handling improvements.

Improvement

• Update ins-table Timezone Overlay formatting.

Bug Fix

• Fix ins-sidebar-item icon flickering issue on hover.

New Features

• Event Ticket Purchases - View all tickets purchased by a company directly from their company profile.
• SendGrid Account Management - You can now delete custom SendGrid accounts when they're no longer needed.
• Version Control Activity Stream - Track all version control changes in real time via the Event Stream.
• Admin Action Tracking - Administrator actions are now logged and visible in the Event Stream.

Improvements

• Clearer Company Deletion - When deleting a company, you'll now see exactly what data will be removed and what will be kept.
• Company Profile Tabs - Improved layout and usability for the Opportunities, Event Sponsorships, and Orders tabs.
• Delete Confirmation - A clear warning message now appears before deleting a company.
• API Key Interface - Updated design for managing Instance API Keys.
• Advanced Filter - Boolean Fields - Boolean field type filters now work correctly in Advanced Filter.
• Advanced Filter - Address Fields - You can now filter CRM records by address fields.
• Redirects Interface - Cleaner, updated UI for managing redirects.
• CRM Export Filters - Export filters now apply correctly when exporting CRM data.
• Contact Prefix Options - More prefix choices available when creating or editing CRM contacts.

Bug Fixes

• Fixed an issue where bulk deleting companies could fail.
• Fixed incorrect values showing for event sponsorships on company profiles.
• Fixed column sorting on the Relationships tab of company profiles.
• Fixed contact imports when profiles are included.
• Fixed display issues for archiving and restoring contacts.
• Fixed Event Stream not displaying entries with a log.action value.

New Features

• V2 Get carts endpoint filter by contact_uuid,session_id,company_id

Improvements

• When deleting the cart, all of it’s cart_items must be deleted
• Cart Items V2 API

Bug Fixes

• Using partial modules/insites_ecommerce/seo, the code returns empty canonical which is flagged as an error by w3C
• Adding products with variants sometimes lead to double value
• Opening order details linked from Dashboard->Events Stream shows popup error.
• Order item is not added when adding order via IIA
• Cart Item total displayed is 0
• Updates to products should reflect in cart items (updated cart_item to be linked to product and not use screenshot of the product details)
• The computation for order_total is wrong when the product is_tax_included=true or is_sale_price_tax_included=true (for is_on_sale=true)
• Product variant get controller not working
• Table Data Styles
• Fix local storage for localisationData

Breaking Change

• Update all v2 PUT endpoint to PATCH
• Updated cart_item schema. Removed product snapshot details and now using the product details from product database.

Hotfix

• Fix Loading and editing field type issue on custom fields