Skip to content

Laiki Changelog: leads with more context and easier-to-connect agents

Each event's URL on the lead timeline, the lead source preserved, AI agents connected in fewer steps and automations that recover on their own.

Published on

2 min read

Icon of stacked dashboards with a sync indicator, the default cover for Laiki release notes

Laiki's release of the week, November 8, 2026: we released improvements to investigate leads with more context, connect AI agents in fewer steps and keep automations running when another system has a hiccup. The focus was on making day-to-day work more predictable: the right information in the right place, with no manual work to fix what should resolve itself.

The page where each event happened

In a lead's Events tab, each event now shows the event URL: the address of the page where it happened, such as a form that was filled in or a page that was visited.

The link opens in a new tab and has a button to copy the address. When the recorded URL is incomplete, it shows as text instead of leading to the wrong address. The information appears everywhere the lead panel opens: lead and event lists, segments and dashboards.

When you switch leads or events in the side panel, the list goes back to the top. You no longer land in the middle of the next lead's timeline.

A lead's source stays with whoever created it

When another system records an event about a lead that already exists, the lead's source is no longer replaced. It stays the source of the system that created the lead.

This keeps filters and automations that depend on this information stable, even when several systems send events about the same person.

Connecting an AI agent got simpler

The Connect agent button now asks which agent you use. In Claude, the connection screen opens already filled in with Laiki. In ChatGPT and other agents, you copy a starter text with that agent's installation steps.

A brief instability in access verification also no longer disconnects agents that are already connected.

Automations that recover on their own

When an automation cannot reach another system because of a temporary connection failure, the run ends quickly and is retried automatically, instead of getting stuck repeating the same failure.

We also adjusted the runs screen:

  • when rerunning in bulk, an indicator shows the progress;
  • rerunning a run no longer changes which one you are viewing;
  • the publish window closes correctly when the version has already been published.

The updates are already available in Laiki. To see the previous release, check the November 2 changelog.

Share

Related content

Never make another decision in the dark

We set up your data operation alongside you and get your team ready to decide. Book a conversation and try it with your own data.