Laiki Changelog: bilingual language, more stable dashboards and context via MCP

In the last two weeks we published three Laiki updates: versions 2026.08.02.1, 2026.08.05.1, and 2026.08.08.1. Together, they bring the platform to Portuguese and English, make dashboards, leads, and automations more stable, simplify the administration of connections and team, release your company's context to AI assistants via MCP, and make plan changes more transparent. See what changed in each area.

Laiki in the language you choose

Now you can use Laiki in Portuguese or English. The preference follows the interface, validation messages, emails, public documents, and content generated by the platform, such as segment descriptions and dashboard analyses. Dates, numbers, and labels appear in each person's language, even when several people look at the same dashboard. This preference is now kept throughout the navigation, including on mobile, where the side menu also now correctly follows the dark theme preference.

More reliable dashboards, leads, and automations

Widgets that fail because of a temporary interruption now get an automatic retry, and old error messages disappear as soon as the data arrives correctly: fewer times when you need to refresh the page manually.

The last interaction and the source of each lead now always come from the same most recent event, which avoids inconsistent combinations between date, campaign, and source. We also reinforced the handling of suspicious identifiers that could mix records of different leads, preserving each one's history more securely.

Segment rules that check lead events now correctly respect the period defined in the query, without letting events outside the interval influence the result. And automations with repetitions now use more stable references for each processed item, which reduces inconsistencies when configuring and running the flows.

Easier to manage connections and team

The connections area gained shortcuts to the most-used services and a table that can be sorted, which makes it easier to find and track connected accounts. Member management also became simpler: you can sort by name, email, role, or join date, identify the Laiki team in the member list, and quickly copy the organization identifier.

Access keys, the credentials used to connect external systems to Laiki, now appear in a table with status, expiration, last use, and related credentials, which makes it easier to audit who is accessing what.

Your company's context, available to AI assistants

We released Organization documents: a space for administrators to record event definitions, funnel rules, attribution criteria, and particularities of the company's own data. The documents accept formatted content, labels, and search.

Assistants connected to Laiki via MCP can consult these documents before analyzing your organization's numbers. That way, each company provides its own definitions as a reference, instead of depending only on what the assistant already knows in a generic way. It is worth stressing: the documents do not train the artificial intelligence nor automatically go into every answer; the assistant consults only the content needed for each question.

The connection via MCP also became simpler, in three steps: select the organization, locate the available operations, and run the chosen query. Access remains limited to the information allowed for the person connected.

More transparent plan changes

Upgrades and downgrades now show the new monthly amount and the new event limit before you confirm the change. Upgrades apply the new limit immediately; on downgrades, the current limit remains valid until the next cycle. The screen also warns when the plan change removes a coupon or a commercial condition you already had.

Other adjustments

We fixed the alignment of counters without a description on dashboards and a publishing failure that could make pages load without their visual styles. Automation runs opened by direct link, or outside the current list, now remain visible while loading, without disappearing or appearing duplicated.

All of these changes are already available on the platform. If you want to recall what changed in the previous version, see the July 31 changelog.