LoginSign Up
← Back to all sparks
L

Lime Connect

CRM
Velocity5.0

Lime Connect is fusing its AI agent with its workflow engine, one release at a time

conversational-aiworkflow-automationknowledge-basewhatsappagent-observabilityenterprise-sso
◆Current state
Lime Connect ships a bundled changelog every few weeks, and nearly every entry touches the same two systems: Connect AI and Workflows. The recent run is operational maturity — knowledge-base files can be renamed and counted against limits, website sources report crawl failures and next sync time, execution history is filterable by operator and rating, and workflow nodes support delays and timeouts. Enterprise plumbing arrived alongside it with per-role SSO and SCIM in beta.
◆Where it's heading
The two halves of the product are converging. Agents can trigger workflows, workflows can route to an operator chosen from a variable, and the agent can read the page a contact is currently viewing before answering. That combination moves the agent from answering out of a knowledge base toward acting inside defined processes, with the workflow engine as the guardrail. Most of the surrounding work is observability — execution history, activity logs, transcripts showing which AI action fired — which is what a vendor builds when customers are letting the agent act unsupervised.
◆Prediction
Expect the observability layer to turn into evaluation: ratings, execution history, and per-action transcripts are the ingredients for measuring agent quality, and nothing yet reports on them in aggregate. Continued WhatsApp and campaign channel work is likely given how consistently it appears in every bundle.

◆Recent moves

  1. 16d ago

    AI Execution History filters; agent stops leaking its reasoning

    Operator and contact-rating filters land in AI Execution History, plus a fix stopping the agent from surfacing internal reasoning to contacts. Both belong to the observability push: one makes agent behavior reviewable, the other keeps what should stay internal off the customer's screen.

    View source ↗
  2. 1mo ago

    Connect AI and Workflow enhancements (Release on July 2nd, 2026)

    Knowledge sources now show their next sync time, agent conversations record contact navigation events, and workflow nodes accept delays and timeouts. The timeout controls matter most — they let a workflow wait on a human or an external system instead of failing forward.

    View source ↗
  3. 1mo ago

    Simplified template management and other improvements (Release on June 25th, 2026)

    Knowledge-base files can be renamed and counted against the limit, workflows can forward to an operator or group resolved from a variable, and WhatsApp templates store default placeholder values. Dynamic forwarding is the notable one: routing becomes data-driven rather than hardcoded per flow.

    View source ↗
  4. 1mo ago

    Knowledge Base updates and other improvements (Release on June 19th, 2026)

    Dynamically loaded websites became crawlable as knowledge sources, with explicit errors when a URL disappears, and per-role SSO shipped with SCIM in beta. The crawl fixes address the quiet failure mode of retrieval agents — a knowledge base that silently stops matching the site it was built from.

    View source ↗
  5. 2mo ago

    Improved AI and Workflow behavior (Release on May 12th, 2026)

    Streaming responses for Connect AI Agents and the ability to split API response data into separate workflow variables. Streaming is catch-up on perceived latency; the variable splitting is what lets a workflow branch on an external system's answer.

    View source ↗
  6. 3mo ago

    Combine AI and Workflows (Release on April 24th, 2026)

    ⚡ SPARK

    The release that joins the product's two halves: AI Agents can trigger Workflows, and the agent can read the URL a contact is currently viewing to answer questions about it. Everything shipped since — activity logs, execution history, timeouts, dynamic forwarding — is scaffolding around agents that now act rather than answer.

    View source ↗