// CHANGELOG

What's new

Every release, improvement, and fix — in one place. Subscribe via RSS to get notified the moment something ships.

  1. NEW

    Call Intelligence: AI-extracted buying signals from call notes

    Log a call and ZeroPipeline automatically extracts structured buying signals — sentiment, objections, next steps, and more — from the transcript. Extraction runs as a background job with a configurable model fallback chain, and the prompt path is hardened against injection from call content.

    • Call notes now carry an extraction_status and structured signals object
    • Transcript extraction runs as a background job instead of blocking the request
    • Configurable model fallback chain keeps extraction running if a provider is degraded
    • Hardened against prompt injection and silent transcript truncation
  2. NEW

    Enterprise SSO (OIDC) and SCIM 2.0 provisioning

    Enterprise-tier orgs can now configure Single Sign-On with any OIDC-compatible identity provider (Okta, Azure AD, Google Workspace) from a new Security tab in Settings, plus SCIM 2.0 for automated user provisioning and deprovisioning from the company directory.

    • OIDC-based SSO configurable per org from Settings > Security
    • SCIM 2.0 endpoints for directory-synced user provisioning and deprovisioning
    • A deactivated user loses access on their very next request
    • Gated to the Enterprise plan via the existing subscription guard
  3. NEW

    Natural-language workflow authoring for automations

    Describe an automation in plain English and the AI agent builds the trigger, conditions, and actions for you. Saved Views also landed on the Records page, and Reports and Outreach are now reachable from the main sidebar nav.

    • Describe-to-build automation authoring, powered by the chat agent
    • Saved Views: save a filtered/sorted segment of Records and return to it later
    • Reports and Outreach added to the primary sidebar navigation
    • Chat orchestrator can now answer questions about agent activity directly
  4. FIXED

    AI chat tool calling restored after a silent regression

    A chain of issues had left the AI chat agent unable to call any of its 25+ CRM tools, and in some cases fabricating that destructive actions had completed when nothing had actually run. Tool selection, argument recovery, and token budgeting were all fixed, and the chat agent now grounds its final answer instead of guessing.

    • Restored client-side tool selection for AI chat — all CRM tools reachable again
    • Chat agent no longer fabricates completed actions when no tool call ran
    • Fixed token budget and context isolation bugs causing silent tool-selection failures
    • Chat no longer presents soft-deleted deals/customers as current data
  5. FIXED

    Checkout, billing, and team invitations fixes

    A cluster of checkout and account-management bugs were fixed: trial checkout was charging full price immediately instead of honoring the 14-day trial, new-visitor checkout could 401 or crash outright, and team invitations were broken end to end.

    • Checkout now correctly honors the advertised 14-day free trial
    • Fixed checkout session creation crashing for every new customer (Stripe)
    • Fixed checkout 401ing for logged-in users due to a wrong localStorage key
    • Fixed team invitations sending the wrong URL and role format
  6. FIXED

    Security: dependency upgrades closing critical CVEs

    Next.js was upgraded to 15.5.29, closing 3 critical RCE advisories. 24 of 27 known backend dependency vulnerabilities were resolved, and @sentry/nextjs was upgraded to resolve transitive audit findings.

    • Next.js 14.2.35 -> 15.5.29, closing 3 critical RCE advisories
    • 24 of 27 pip-audit vulnerabilities resolved in the backend dependency tree
    • @sentry/nextjs upgraded 8.33.0 -> 11.10.0
    • FastAPI, python-multipart, sentry-sdk, and python-dotenv patched to current versions
  7. IMPROVED

    Performance: shared DB pool, GZip, analytics fixes, N+1 elimination

    A batch of four performance improvements shipped together: a shared Postgres connection pool across request handlers, GZip response compression, fixed analytics query limits, and N+1 query elimination across customer list endpoints.

    • Shared DB pool across request handlers — connection overhead cut by 70%
    • GZip compression on all JSON responses — payload sizes down 60%+
    • Analytics endpoints now respect per-query limits, preventing runaway queries
    • N+1 query patterns eliminated from customer and deal list endpoints
  8. NEW

    source_is_null and untagged filters for customers and bulk-tag endpoints

    Two new filter parameters let you find exactly the leads that need attention: contacts imported without a source, and contacts with no tags applied. Both filters are available on the list endpoint and the bulk-tag endpoint.

    • filter_source_is_null=true returns contacts with no import source
    • filter_untagged=true returns contacts with an empty tags array
    • Both filters work in combination with existing tag and search filters
    • MCP tools list_customers and bulk_tag_customers updated to support both flags
  9. NEW

    Instant org provisioning with zero-human onboarding

    First-time users are now auto-provisioned into a full org the moment they sign in via AINative auth. No manual setup, no waiting — your pipeline is ready before you finish the first tab switch.

    • Auto-provision org, pipeline, and default ICP profile on first login
    • Zero-human provisioning path: 100% agent-driven org bootstrap
    • MCP server ships with instant_provision tool for programmatic setup
    • Health probe aligned to direct Postgres for sub-50ms cold checks
  10. IMPROVED

    MCP server bumped to v0.2.0 — PyPI release + tag coverage tool

    zeropipeline-mcp v0.2.0 ships to PyPI. The package now includes get_tag_coverage for auditing how well leads are segmented, and a confirmation gate blocks bulk imports of more than 50 records without explicit approval.

    • zeropipeline-mcp v0.2.0 released to PyPI
    • New get_tag_coverage MCP tool returns tag distribution across your CRM
    • Confirmation gate added to bulk_create_customers for imports > 50 records
    • Audit logging added to all bulk_create_customers calls
  11. NEW

    JSONB tag filter and mandatory source/tags on import

    Tag filtering now uses Postgres JSONB operators instead of application-level filtering, cutting response times on large datasets from seconds to milliseconds. Bulk imports now require a source field and default_tags to enforce clean data hygiene.

    • JSONB @> operator replaces application-level tag filtering
    • Bulk import requires source field — rejected at validation if missing
    • default_tags applied to every record in a bulk import run
    • POST /customers/bulk-tag endpoint for mass tag operations
  12. IMPROVED

    Writes routed through direct Postgres, eliminating ZeroDB REST latency

    All mutating operations (create, update, delete) now bypass the ZeroDB REST layer and talk directly to the Postgres instance. Read operations still use ZeroDB for compatibility. P95 write latency dropped by 68%.

    • Direct Postgres adapter for all write paths
    • ZeroDB REST retained for reads and vector operations
    • Database adapter auto-selects path based on operation type
    • Connection pooling tuned for Railway's shared Postgres tier
  13. NEW

    MCP server for native agent integration

    ZeroPipeline now ships an MCP (Model Context Protocol) server, letting any Claude, GPT-4o, or Gemini agent call pipeline tools directly. Plug in your agent and it can create deals, move stages, and run outreach — no custom API wrapper needed.

    • 40+ MCP tools covering the full CRM surface
    • Published to npm as @ainative/zeropipeline-mcp
    • Works with Claude Desktop, claude-code, and any MCP-compatible host
    • SEO-optimized package metadata for registry discovery
  14. FIXED

    Password reset proxy and auth route alignment

    Password reset emails were failing silently when the user account was managed by AINative auth (SSO flow). Requests are now correctly proxied to the AINative auth service, and the /forgot-password route handles both local and SSO accounts.

    • Proxy password-reset requests to AINative auth for SSO accounts
    • Unified /forgot-password flow for local and SSO users
    • Fixed token expiry edge case on reset link click
    • Added E2E test coverage for the full reset flow