From a single shared button to Client Station
ActionLink started as a link you could share that rendered one button — a client clicked it and it fired an automation in monday.com. That was it. This is the release history of how that one button grew into today's client portal builder.
22
releases shipped
14 months
of product history
Apr 2025
first release, as ActionLink
Jun 2026
latest release
The Client Station era
Portal building, item timelines, communication — and the new name.
May 2026 – Jun 2026
V41.4 is a major speed and reliability update for Client Station portals. It adds a dedicated monday.com gateway and cache layer, makes portal data reads much faster when cached data is available, keeps cache repair and sync work in the background, and moves transactional email delivery to Mailjet with better branded sender support.
Full release notes
New
- A dedicated monday.com gateway service for monday API communication, caching, webhooks, sync queues, and complexity-aware request handling.
- Account-scoped board, item, subitem, column, column-value, and relation-link caching for portal reads.
- Live webhook projection so create, delete, and column-change events update the cache quickly.
- Scheduled gateway syncs so cached boards are refreshed periodically even when no one is actively editing the portal.
- Clearer Studio cache visibility for cached boards, active sync jobs, cached items, board errors, and recent sync state.
- Account-slug sender addresses and branded sender names such as "Company Name (Client Station)" for verification and reminder emails.
- Mailjet delivery/open event callbacks for tracked reminder and notification emails.
Improved
- Made portal views use cached monday.com data first, with monday.com fallback and background sync requests when data is missing or stale.
- Connection-view access handling by caching linked-item details with item ID, item name, and source board information.
- Made the Studio monday cache status panel fast by decoupling status reads from cache repair; repair now runs in the background instead of blocking the card.
- Moved transactional email delivery from Brevo to Mailjet.
Why it matters
Portals should feel instant once their boards are cached. V41.4 moves the slow monday.com work out of the client's critical path: cached portal reads can load immediately, fallback reads still work when the cache is incomplete, and sync or repair work continues in the background. Studio also feels faster because the monday cache checker no longer waits on a full audit before showing status.
Reliability & polish
- Added BullMQ-backed sync and webhook queues for more controlled cache work.
- Added idempotent webhook handling so repeated monday.com deliveries do not duplicate cache changes.
- Added queue limits and safer webhook status handling.
- Added periodic sync scheduling for registered cached boards.
- Added subscription and whitelist checks before enqueueing background syncs.
- Kept cache repair fire-and-forget from Studio so repeated refreshes do not start repeated repair work.
- Added metrics-route hardening so webhook routes with multiple Express paths cannot crash the server.
- Hardened Docker npm installs with retry and timeout settings for more reliable production deploys.
V41.1.1 is a focused reliability and polish update for portal builder previews, connection views, portal theming, KPI/stat blocks, and Document Vault file views. It fixes per-client board filtering edge cases, makes clean preview mode clearer, improves dark-mode consistency, improves how KPI tiles calculate and edit metrics, and makes document folders behave correctly when some subitems do not have files.
Full release notes
New
- A connection-column picker directly in connection view settings for explicit per-client filtering.
- A clean preview banner with the active "Viewing as" client picker and a stronger return-to-editor action.
Improved
- Auto-detection for monday.com relation columns, including alternate relation settings formats and dependency columns.
- Prevented duplicate connection columns when a board was already linked to the access board.
- Made KPI tiles editable inline, including metric type, number column, label, color, prefix, suffix, tile count, and layout width.
- Dark-mode surfaces across portal login, KPI blocks, timeline panels, view permission controls, and preview surfaces.
Fixed
- Connection-view filtering so content boards can filter through their own relation column back to the client/access board.
- KPI and stats calculations for monday.com number columns whose raw values arrive as JSON strings.
- Publish validation for portals that include KPI view blocks.
- The extra progress and item-count pills from portal view headers.
- Document Vault folders so subitems without files no longer appear as fake file cards; the folder now shows real files plus a note when some items have no files in the selected column.
- The Document Vault "Open" action so files can navigate from a vault folder into the matching subitem page.
Why it matters
Portal builders can now trust that "viewing as a client" reflects the client's linked items, especially for boards where the relation column lives on the content board. KPI tiles are also more useful during design because teams can configure them directly in the canvas and see real totals instead of misleading zeroes. Document Vault folders now distinguish between missing files and broken folder loading, so clients see available files and a clear note for items still waiting on uploads. Dark-themed portals now keep login, preview, and content-builder surfaces visually consistent.
Reliability & polish
- Kept legacy access-board connection traversal as a fallback for existing portals.
- Added focused tests for relation settings parsing, selected connection columns, and auto-detected connection-view filtering.
- Improved preview cache keys so changing connection mode or column selection refreshes item data.
- Kept editor controls hidden in clean preview mode while still making the preview state obvious.
- Kept portal theming centralized through the shared Mantine portal theme scope.
- Added focused Document Vault coverage for sparse subitem permissions and empty file-column rows.
V41.1 follows the timeline-heavy V41 release with a focused portal-builder and runtime update. It improves how teams edit portal navigation, connect boards and columns, preview client experiences, invite contacts, and track portal activity back into Client Station timelines.
Full release notes
New
- Editable module navigation so portal sections can be organized and renamed from the live editing flow.
- Board and connection-column controls for building portal views from the right monday.com data.
- Runtime view blocks with stronger KPI, card, stats, table, and paged-item handling.
- Client invitation tools and "Test as a client" support in Studio.
- DM Sans as a Studio and portal theme font option.
Improved
- The portal builder top bar and step strip to keep setup, preview, and publish actions clearer.
- Portal home presentation, including the top bar, stat strip, resources row, and view cards.
- Embed and iframe blocks so embedded content can fill the available portal space more reliably.
- Moved portal activity and audit events into timeline activity records with batched socket tracking.
- Timeline scoping across item views, portal views, empty conversations, and Studio status activity.
Why it matters
Portal building is now easier to complete without leaving the preview context. Teams can connect the right board data, shape navigation, test the client experience, invite contacts, and see client activity appear in the same timeline surfaces used for communication and status tracking.
Reliability & polish
- Improved portal runtime definitions, navigation adapters, and live preview behavior.
- Tightened portal socket room handling and activity broadcasting.
- Improved client portal branding, login, logo, and localized activity text.
- Simplified older block-rendering paths as view blocks moved further into the runtime catalog.
- Improved contact and access-group handling used by invite, preview, and timeline workflows.
V41 expands Client Station beyond portal building into a stronger communication and activity workflow. It combines the live editor and portal builder refinement from the previous internal marker with the new item-level Timeline experience, a unified Studio Status Page, realtime timeline updates, read states, mentions, and tracked notification emails.
Full release notes
New
- A monday.com item view for Client Station Timeline, so teams can open the relevant client history directly from a monday item.
- Item-view timeline tabs for each matching portal/access group tied to the current monday item.
- Scoped timeline breadcrumbs so Studio users can move between access, view, item, and subitem context without losing the conversation.
- Brand replies, threaded replies, mentions, attention markers, and read-state controls inside the item timeline view.
- A unified Studio Status Page that replaces the separate activity, reminders, and chats navigation with one engagement hub.
- Portal Timeline surfaces in the client portal, including top-bar access, a timeline panel, timeline rail support, and home-page timeline/inbox updates.
- Realtime timeline event and read-receipt broadcasting between Studio and portal users.
- Timeline unread counts, read-state summaries, and read receipts for Studio and client-facing activity.
- Mentionable-contact lookup, @mentions, all-contact mentions, and mention delivery behavior that can notify clients without duplicating alerts for online contacts.
- Tracked notification email lifecycle events, including sent, delivered, opened, clicked, and failed states.
- Brevo webhook handling so email provider events can be reflected back into the Client Station timeline.
Improved
- Kept the live editor and portal builder improvements from the prior internal marker: portal runtime architecture, definition-store editing, in-canvas controls, presentation grid work, view and item presentation handling, embed view blocks, draggable view column ordering, richer block settings, and safer publish/preview behavior.
Why it matters
Client work now has a shared activity record across monday, Studio, and the portal. Teams can see what happened on a client item, reply from the right context, mention the right people, track whether activity was read, and keep portal communication tied to the underlying monday work.
Reliability & polish
- Fixed client typecheck blockers before marking the release as v41.
- Added database support for timeline coordinates, timeline read state, tracked emails, and main-item names on contact access records.
- Added timeline service read-state handling and portal timeline adapters.
- Expanded portal socket authentication, room handling, timeline broadcasting, and realtime cache updates.
- Improved Studio chat/status data loading, realtime sync, message grouping, and timeline cache merging.
- Improved portal top-bar navigation, module navigation, timeline entry points, and conversation presentation.
- Added tests for mention presence, portal chat behavior, timeline portal adapters, and timeline service behavior.
V40 established the modern Client Station foundation. It moved the app further away from legacy ActionLink UI patterns, added native portal guardrails, introduced contact-list portal data modeling, and began a broad design-system migration.
Full release notes
New
- Native portal guardrails so newer portal flows could be built without breaking legacy portals.
- Contact-list portal data modeling for more scalable client access.
- Dev account impersonation to make support and testing easier.
- Portal webhook repair tooling.
- A free tier and improved portal subscription/access polish.
- Portal branding and localization options.
- Portal-builder and monday API surface work.
Improved
- Migrated large parts of the frontend toward a modern component system.
- Portal navigation and access setup.
- The Studio dashboard and portal activity UI.
Why it matters
V40 created the base needed for a more scalable product. It cleaned up older UI assumptions, improved portal setup, and prepared the app for more structured portal building.
Reliability & polish
- Improved portal verification code handling.
- Rebuilt reminder automation on Brevo.
- Tightened portal home and field presentation layouts.
- Fixed Studio dashboard overflow and improved dashboard polish.
- Added OpenRouter LLM infrastructure and architecture documentation for future assistant-powered workflows.
ActionLink
Client Station
With V39.0 the product took its name. Everything below this point shipped as ActionLink.
V39.0 introduced the Client Station identity while preserving the ActionLink transition language. It also brought a large design and portal polish pass, stronger forms, better notifications, and important compatibility work for existing portals.
Full release notes
New
- Reminder automation through monday webhooks and expanded the Engage tracking surface.
- Forms foundations, including form definitions, signature questions, file preview fields, and structured form chrome.
- Portal view hiding, reordering, and sidebar-from-views behavior.
- Richer portal blocks, including expanded charts, stats, calendar blocks, and live-preview editing foundations.
- Broader portal internationalization and translated more runtime strings.
Improved
- Rebranded the Studio shell and portal-facing language toward Client Station.
- Kept "formerly ActionLink" context in the Studio UI during the transition.
- Connection views with path-aware rendering, connection-linking, and safer fallbacks.
- The portal home experience with stronger editorial styling, improved view cards, better item headers, and clearer empty states.
Why it matters
The product started moving from "a link sharing app" toward a more branded client workspace. Teams got more control over portal presentation, forms, views, reminders, and connection-based access.
Reliability & polish
- Added legacy-portal compatibility work so older portals could continue operating while new portal models evolved.
- Added schema-drift recovery and renovation tracking for older portal definitions.
- Improved contact sync infrastructure and webhook diagnostics.
- Rebuilt chat storage toward a DB-backed model and imported legacy Monday Updates chats.
- Added idempotent migration fixes and safer connection-path synthesis.
- Removed several hardcoded brand colors and moved UI surfaces toward theme-aware tokens.
The ActionLink years
From Agency View to a real Studio, with file sharing, branding, and approvals.
Apr 2025 – Apr 2026
V38.3 strengthened access, connection views, and operational reliability. It fixed important portal access behavior, added direct contact resolution, and improved multi-board connection views.
Full release notes
New
- A review prompt flow inside Studio with sentiment-aware feedback routing.
- Direct contact resolution mode for cases where the current monday item is the client record.
- An "All Boards" option to board selection so teams could bypass workspace search when needed.
Improved
- Multi-board connection views.
- Mobile scaling for portal layouts.
Fixed
- Portal token handling so expired or incomplete links returned a safe portal login state instead of failing with server errors.
- Hook crashes and table overflow issues in portal views.
Why it matters
This release made portals safer and more forgiving for real client access. It also expanded the ways teams could model client data in monday.com without forcing every account into one contact-board pattern.
Reliability & polish
- Added granular health endpoints and a Gatus status page.
- Fixed a portal login crash caused by empty monday search results.
- Adjusted review prompt behavior to use monday marketplace review flows more cleanly.
- Reduced failure modes around connection-view rendering and portal authentication.
V38.0 was a broad portal experience release. It introduced a more polished portal UI, better client-facing interaction patterns, stronger contact resolution foundations, analytics, reminders, and the first major steps toward richer portal blocks.
Full release notes
New
- Improved portal home layouts, inline inbox patterns, and richer view cards.
- New view block capabilities, including callout, text, and task-oriented blocks.
- File gallery, upload, and detail-view polish for client-facing file workflows.
- Dutch language support.
- Reminder UI and task reminder foundations.
- Action usage tracking and email usage tracking.
- Mixpanel analytics with source tagging and portal visitor identification.
Improved
- The Studio version and logo presentation.
- Interactive tables, cards, data fields, and column renderers.
Why it matters
The client portal became more useful as a day-to-day workspace. Clients could see cleaner layouts, use richer data views, interact with files and messages more naturally, and receive better reminders.
Reliability & polish
- Added contact model and contact-sync foundations.
- Added portal-driven contact ports and database adapters.
- Improved privacy filtering when columns were removed or unavailable.
- Improved monday SDK token refresh on Studio bootstrap.
- Added a mobile-first portal pass with cleaner account URLs, responsive chat, and better portal blocks.
- Added an email digest queue for batching notifications into twice-daily digests.
V37.9 focused on making Studio easier to operate and making webhook behavior safer. The release tightened the portal editor flow, improved view management, and reduced duplicate or orphaned webhook records.
Full release notes
New
- Clearer card text wrapping and visual cleanup across Studio and portal views.
- Ensure/reconciliation paths for webhooks so missing board/view hooks could be repaired more predictably.
Improved
- Redesigned important parts of the portal editor so setup steps were easier to follow.
- The Studio home screen and view list presentation.
- Webhook visibility inside Studio so operators could understand whether views were connected correctly.
- Continued portal architecture cleanup by moving portal logic toward shared contracts and cleaner API clients.
Why it matters
Portal setup became easier to trust. Teams could see more clearly what was configured, and the app had better tools to keep monday webhooks aligned with portal views.
Reliability & polish
- Added webhook deduplication and orphan cleanup improvements.
- Removed high-cardinality metric labels that could overload Prometheus.
- Improved routing and modernized portal data fetching through the shared portal API client and TanStack Query.
- Continued server architecture separation for portal controllers, adapters, and application logic.
V37.8 expanded the portal from a simple shared view into a richer client workspace. This release focused on better file handling, stronger portal content blocks, and a cleaner Studio setup experience.
Full release notes
New
- Folder-style file organization so client portals could present files in a more navigable structure.
- Callout and content block improvements for clearer portal presentation.
- Iframe support for embedding outside content directly into portal pages.
- Email-column support and smaller block fixes across the portal experience.
Improved
- File detail loading and caching to make file-heavy portals feel faster.
- Banner and welcome message handling so portals could feel more branded and intentional.
Why it matters
Clients could use the portal as a more complete workspace instead of only a table view. Agencies and teams gained more control over how information was introduced, grouped, and presented.
Reliability & polish
- Continued work on background event processing and scheduler foundations.
- Improved notification behavior with early simple notification support.
- Advanced monday.com API compatibility work, including migration preparation for newer API behavior.
- Cleaned up several early infrastructure experiments so the app stayed more stable while larger backend changes were being tested.
V37.6 added email verification codes for portal entry, improving the security of client access.
Full release notes
New
- An email verification code step when clients enter a portal.
Improved
- Strengthened portal access without requiring a heavier login experience.
Why it matters
Client portals often contain sensitive project and account information. Email verification gave teams a stronger access check while keeping the client experience simple.
Reliability & polish
- Improved portal entry security.
- Helped ensure that the person opening a portal had access to the relevant email address.
- Set the stage for later access-control and contact-identification improvements.
V37.5 expanded ActionLink into approval workflows, richer presentation blocks, and activity visibility. It added tools for teams that need process control and client accountability.
Full release notes
- Highly customizable approval processes and change workflows.
- E-signatures.
- Audit logs for reviewing client activity.
- Customizable presentation blocks.
- Charts for richer portal presentation.
Why it matters
Portals became useful for more serious client workflows, not just visibility. Teams could request approvals, collect signatures, track activity, and present information in more flexible ways.
Reliability & polish
- Added client activity visibility through audit logs.
- Expanded portal content beyond basic data views.
- Created the foundation for later block-based portal building.
V37.2 made Studio more robust and easier to use. It added a setup wizard, redesigned the Studio experience, and improved action feedback inside client portals.
Full release notes
New
- A setup wizard for easier onboarding.
- Stronger client portal behavior with action feedback.
Improved
- Redesigned ActionLink Studio to make portal setup less complicated.
Why it matters
Users could create portals with less uncertainty. The setup wizard and redesigned Studio reduced the number of decisions users had to figure out on their own.
Reliability & polish
- Improved onboarding flow clarity.
- Strengthened portal feedback patterns so clients had clearer confirmation after actions.
- Continued hardening Studio as the main portal configuration surface.
V36.1 focused on speed. Fetching core monday data became much faster, and the Studio dashboard gained tutorial videos to help users learn the product.
Full release notes
New
- Tutorial videos to the Studio dashboard.
Improved
- Made fetching items, subitems, and columns significantly faster.
Direction
- Included minor fixes and improvements.
Why it matters
Faster loading made portals and Studio setup feel more dependable, especially for larger monday boards with more items, subitems, and columns.
Reliability & polish
- Improved perceived and practical performance for board data loading.
- Added learning material directly inside Studio.
- Cleaned up smaller product issues after the V36 management release.
V36 focused on making client-portal management easier at scale. It responded to user feedback around importing clients, special setup templates, link sharing, file uploads, embedded portals, and passwordless access.
Full release notes
New
- A board-based Studio setup direction so users could work from their existing client boards.
- The concept of each client item automatically becoming a portal.
Improved
- Reduced the need to manually import clients and create each portal one by one.
Direction
- Planned a centralized client hub where clients could enter their email and access the correct portal.
- Planned cleaner distribution paths for links and embedded portal access.
- Planned no-password portal access for clients who prefer simpler entry.
Why it matters
V36 moved ActionLink toward a more automatic client portal system. The goal was to reduce manual setup, reduce link-sharing overhead, and make portal access easier for both operators and clients.
Reliability & polish
- Clarified the product direction around board-first portal setup.
- Focused on reducing friction for teams with many clients.
- Established the foundation for central client access and future embed/API workflows.
V33.9 was a larger Studio restructuring release. It introduced client importing, groups, reusable views, and single-item views while beginning the move away from older agency ActionLink behavior.
Full release notes
- A client importer tool.
- The ability to import clients from another board.
- Client groups.
- Reusable views.
- A new ActionLink Studio experience.
- Single-item views.
- Broad behind-the-scenes quality upgrades.
Why it matters
ActionLink became easier to scale for teams managing many clients. Instead of creating each client portal by hand, users could import clients, organize them into groups, and reuse view definitions.
Reliability & polish
- Restructured Studio to make future feature development easier.
- Began deprecating older agency ActionLink behavior while preserving active portals during the transition.
- Improved the product foundation for reusable portal configuration.
V33.1 added connection filters so portals could show only the monday items relevant to a specific client.
Full release notes
New
- Connection filters.
- The ability to disable views.
- The ability to reorder views.
Improved
- Allowed portal views to show only client-relevant items.
Why it matters
Teams could share connected monday data without exposing unrelated work. This made portals safer and more useful for client-specific views.
Reliability & polish
- Improved control over which views appear in the portal.
- Helped portal owners shape client navigation around the most relevant information.
- Established early access-control patterns that later connection-view work expanded.
V33 added file sharing and annotations, making ActionLink more useful for client collaboration around assets, documents, and feedback.
Full release notes
New
- File sharing and annotation workflows.
Fixed
- Loading screen flashing.
- The "Show Password" button.
Direction
- Included minor fixes and usability improvements.
Why it matters
Clients could do more inside the portal without leaving the shared workspace. File sharing and annotations reduced back-and-forth communication and made review workflows easier to manage.
Reliability & polish
- Improved the portal loading experience.
- Fixed password visibility behavior.
- Added small interaction fixes around the client-facing portal flow.
V30 introduced a new Studio experience with a redesigned workflow, a new ActionLink template, and more flexible ways to present monday data.
Full release notes
New
- A new Studio dashboard.
- A new ActionLink template.
- Tabular and card-style views.
- Support for status update notes.
Improved
- The Studio workflow.
Why it matters
Portal building became more structured. Users had clearer setup steps, more presentation options, and better ways to share status context with clients.
Reliability & polish
- Improved the Studio foundation for future setup and editor work.
- Gave users a clearer starting point through a new template.
- Added more flexible view formats so portals could better match the type of client information being shared.
V27 added the first major branding controls, making it possible for teams to present portals with their own company identity.
Full release notes
New
- Branding options for client portals.
- Logo upload support.
- The ability to set the company name shown to clients.
- Client chat support for Agency View.
Improved
- The login dialog visuals.
Why it matters
Portals became more credible and client-ready. Teams could show their own branding instead of sending clients into a generic portal experience.
Reliability & polish
- Improved the first client touchpoint through a cleaner login dialog.
- Expanded Agency View with a direct communication path between team and client.
- Set the foundation for later white-label and theme controls.
V26 focused on making portals and onboarding feel more polished. It improved the visual experience and made it easier for new users to understand how to get started.
Full release notes
- Dashboard visuals.
- The onboarding process.
- Made the portal experience feel more polished for client-facing use.
Why it matters
Client portals are part of a customer's brand experience. This release helped portals feel more presentable and made setup less intimidating for new users.
Reliability & polish
- Tightened early dashboard layout and presentation.
- Improved the first-run path so users could move from setup to a working portal with less friction.
V25 introduced Agency View, an early foundation for building client portals around agency workflows, cross-board work, and reusable ActionLink setups.
Full release notes
New
- Agency ActionLinks for agency-style client portal management.
- Support for pulling items from different areas across monday.com.
- A progress/status bar for tracking project progress inside the portal.
- ActionLink presets to speed up repeat portal setup.
- Item-based views for portals centered around specific monday items.
Improved
- The Studio interface with a refreshed look.
Why it matters
Teams could start using ActionLink for more than one simple board view. Agencies could model client work across monday.com and give clients a clearer portal experience around projects, progress, and relevant items.
Reliability & polish
- Created the first structure for reusable portal patterns.
- Improved the early Studio presentation so portal setup was easier to understand.
- Established item-based portal behavior that later releases expanded.
Want to see Client Station today?
Install it from the monday marketplace or book a setup call.