Fourteen more apps in Connectors

Portail v2.6.23 shipped on 2026-10-12 as a patch release focused on fourteen more apps in connectors. Portail's chat can now work with fourteen more apps from Settings > Connectors: Trello, Linear, Asana, Todoist, Google Drive, Outlook, Dropbox, HubSpot, Jira, Airtable, Calendly, Zoom, LinkedIn, and ClickUp. Link an account once through the same managed sign-in the other connectors use, then ask in plain words. Add a card to a Trello list, file a Linear issue, find a PDF in Drive, check what is on your Outlook calendar tomorrow, schedule a Zoom call, or move a Jira ticket to Done. Reads run straight away, and anything that sends, posts, or changes something on your account goes through the same flow as Gmail and Slack today. Scheduled tasks can use the new apps too, and their write actions stay behind the same per-task opt-in. The list is sorted so the apps you have linked come first, then the ones you can link now. Portail still never stores your passwords or access tokens; the sign-in lives with our connection provider, and you can disconnect any app from the same screen at any time. The work is recorded here because small releases are still product history. They change how people sign in, read responses, pay for access, share conversations, open files, or trust the system when something goes wrong.

The main changes were direct: trello, linear, asana, todoist, jira, and clickup: find, create, and update tasks and issues from chat, google drive, dropbox, and airtable: search files, make folders and share links, and read or add records, outlook, hubspot, calendly, zoom, and linkedin: read mail and calendar, look up contacts, schedule meetings, and publish posts, and connectors now cover twenty-three apps, with linked apps listed first in settings. That list is intentionally plain. It names what changed without turning the release into theatre. When a release fixes a build, a redirect, a storage path, or a UI edge case, the value is often that users stop noticing the problem. The archive keeps that invisible work visible enough for future debugging and for anyone checking whether Portail has cared about the details over time.

This version also fits into the wider Portail contract. One account, one chat history, and one model picker only work if the smaller pieces keep their promises. Authentication has to fail clearly. Billing has to count honestly. Uploads have to arrive in a form models can read. Admin tools have to show the operator what happened instead of hiding it behind a blank screen. v2.6.23 moved that contract forward in its own narrow lane.

The screenshots attached to this entry show the public release record as it now appears on portail.cc. For older releases, this archive was rebuilt from the git history, package version changes, release modal text, and commit subjects. That means the page is honest about its source: it documents the shipped change and preserves the record going forward, even when the exact old production screen cannot be recreated from a single saved image.

The practical result is simple. Someone landing on this page can see the version number, date, release tier, headline, highlights, and a real rendered screenshot of the archive page. Search engines can index the post through the canonical URL, sitemap entry, and structured data. Future releases now have a standard to meet before deploy, so the history should get cleaner from here instead of fuzzier.