We are pleased to introduce Kanvas Ecosystem API v1.100.2!
Following the major milestone release of v1.100.0 (introducing Model Context Protocol support, our dedicated Expenses Agent, and Odoo integration) and v1.100.1's messaging stability updates, v1.100.2 delivers substantial enhancements across lead intelligence, ID verification scoring, standardized connector synchronization, and messaging precision.
Here is everything you need to know about what's new in v1.100.2.
🎯 Richer Lead Intelligence & Trait-Based Discovery
Understanding customer intent is essential for both autonomous agents and sales representatives. In v1.100.2, the Kanvas Lead entity has been upgraded with deep commerce context:
- Product and Variant Interests: Leads can now explicitly track product and variant interests directly within their profile. AI agents and CRM automation flows now have immediate visibility into the specific inventory items or variants a prospect cares about.
- Trait-Based Lead Search: We've introduced trait-based search across leads, allowing agents and sales workflows to query, filter, and segment contacts using rich structured traits.
- Secondary Index Configuration: Added secondary index support and index configuration to boost search speed and expand structured data retrieval for RAG-powered agents.
Customer Interaction ➔ Track Product / Variant Interests ➔ Trait-Based Indexing ➔ Targeted Agent Follow-up
🪪 Smarter ID Verification & Real-Time Document Tracking
Identity verification and compliance workflows receive major upgrades in this release:
- Mismatch-Count Scoring: Rather than relying strictly on binary critical-field rules, verification scoring now evaluates the total number of field mismatches, providing a more nuanced and accurate risk assessment.
- Centralized Verification Reports: Verification reports are automatically structured and archived into standardized directories.
- Lead-Level PDF Tracking: Kanvas now monitors checklist PDF generation directly at the lead level and emits real-time events when generated PDFs are ready for downstream review or customer delivery.
🔄 Standardized Connector Workflows & CRM Matching
Maintaining consistent behavior across diverse CRM connectors is a core focus of Kanvas. In this release:
- Unified Connector Pull Structure: We standardized connector pull result schemas, ensuring external systems pass predictable structures into Kanvas.
- Enhanced Reynolds Matching: Reynolds lead candidate discovery features improved candidate searching algorithms, minimizing false duplicates and discrepancies during synchronization.
💬 Precision Messaging with Channel UUID Targeting
As agent swarms and communication channels scale, routing messages reliably becomes mission-critical:
- Direct Channel UUID Targeting: Messages can now be explicitly attached to conversation channels using their unique UUID, eliminating ambiguity when multiple channels share similar names or slugs.
- Global Channel Routing: Refined channel resolution guarantees seamless message delivery across both conversational agents and automated outreach workflows.
🤖 Agent Stability, Payments & Platform Fixes
- Agent Tool & Calendar Fixes: Resolved edge cases in agent tool execution, fixed calendar tool operations, and improved handling of incomplete agent turns.
- RAG Queue Reliability: Enhanced retry logic for RAG queue workers to ensure background embeddings and indexing tasks recover cleanly from network interruptions.
- WordPress Agent Protections: Built-in safeguards to prevent accidental duplicate content generation in automated publishing workflows.
- Commerce & EchoPay Reversals: Improved EchoPay reversal handling; failed reversal attempts are now automatically retried rather than mistakenly marked as completed.
- Core Upgrades: Updated the Symfony HTTP client, alongside queue and indexing reliability patches.
Upgrading to v1.100.2
Kanvas Ecosystem API v1.100.2 is available now. We encourage all teams to update and take advantage of these new CRM, verification, and agent reliability enhancements.
Check out the Full Changelog (v1.100.1...v1.100.2) for commit-level details.
