← All updates

CHANGELOG

v1.0.0-beta.74

Log calls, emails, meetings and notes; one timeline per contact. 69 changes in all: 42 new, 7 fixes, 1 changed, 10 docs and 9 behind the scenes.

The Aglyn Team · Sep 2026

Released to production on September 5, 2026 at 19:25 CDT. See every commit in this release on GitHub

New

  • Tooling: the e2e seed carries a CRM — a roaster's wholesale book, leads, an audience
  • CRM: log calls, emails, meetings and notes; one timeline per contact
  • Platform: activity kinds, the contact timeline merge and the CRM read tokens
  • CRM: the Companies section, its record page and docs
  • Cloud functions: indexes for the contact-company mirror and the scoped company filters
  • CRM: the companies model, its link mirror rules and the CRM scope hooks
  • CRM: the Leads section, the lead record and the convert dialog
  • CRM: the lead-convert route turns a lead into a contact, a company and a deal
  • Platform: lead status fields and a contact-upsert facet option
  • Documentation: the CRM reference pages, scopes, conventions and What's New
  • Console: a contact's CRM profile over /v1, the CRM sizes in usage, and the suites
  • Console: /v1 grows companies, pipelines, deals, tasks and activities
  • Forms: a form field picks the contact field it saves into
  • CRM: custom contact fields, from definition to value
  • Console: the global search finds a contact by name, email, phone or company
  • CRM: the contact record page, and a list that links to it
  • CRM: a contact can be added by hand, with a profile on its facet
  • CRM: the deals pipeline — board, table, drawer, detail page and linked cards
  • CRM: the deal pipeline model, the deal-stage route and its events
  • CRM: the contacts table grows bulk actions and an audience door
  • Email: audience rules reach owner, stage, company and custom fields
  • Workflows: the trigger pickers read as words and the editor builds the CRM steps
  • Runtime: the CRM owner and assignee resolve by address via the roster
  • CRM: contact events and five CRM steps for automations
  • CRM: tasks and follow-ups — section, record card, routes and widget
  • CRM: the Reports section, its cards and the CRM at a glance widget
  • Platform: the CRM report helpers — periods, week buckets, funnel, pipeline totals
  • CRM: the Companies section, its record page and docs
  • Cloud functions: indexes for the contact-company mirror and the scoped company filters
  • CRM: the companies model, its link mirror rules and the CRM scope hooks
  • CRM: the Import CSV drawer on the contacts list
  • CRM: the contacts-import route — one chunk of a file through the capture door
  • Site data: upsertHostContact answers a verdict and takes a facet
  • Platform: the contact-file normalizer — mapping, row verdicts, skipped-rows CSV
  • CRM: one edit verdict per list, and the cards link to the activities docs page
  • CRM: log calls, emails, meetings and notes; one timeline per contact
  • Platform: activity kinds, the contact timeline merge and the CRM read tokens
  • CRM: the Contacts plugin becomes the CRM hub, id and all
  • Contacts: the Contacts hub — sections, record routes and a server entry
  • Security rules: the CRM collections answer to the contacts predicate, indexed
  • UI components: the list table grows an opt-in row selection
  • Platform: the CRM model, contact profile facet and scope stamp behind Contacts v2

Fixed

  • CRM: the convert dialog's Stage label no longer sits on its placeholder
  • CRM: a stage moved on the contact page fires its event; the leads' selects are named
  • Console: the docs flag registry reads the CRM's own name on the pages it watches
  • CRM: the consolidated CRM v2 tree clears every guard
  • Console: the GA4 Admin host the funnel alarm reads is in the outbound inventory
  • Tooling: the plugin-id backfill finds settings rows by parent, not by collection group
  • Tooling: the funnel alarm grades hourly off Firebase Auth, not two days late

Changed

  • CRM: the import drawer takes the org as the page prop it is forwarded from

Documentation

  • Documentation: the commerce guide points at the account-page step by its current number
  • Documentation: the CRM overview links the API reference at its real route
  • Documentation: the Contacts folder reads as one CRM manual; v1 language swept
  • Contacts: the Leads page — list, record, convert, unqualify
  • Contacts: the contact record — adding by hand, the fields, owner, stages, the page
  • Automations: the CRM events and steps, with their payload tables
  • Contacts: the CRM Reports page, plus its crmReports plugin help topic
  • Contacts: the contacts page list points at the import page
  • Contacts: import contacts from CSV, with the registries regenerated
  • Contacts: activities and the timeline, registries regenerated

Behind the scenes

  • Releases: the beta.74 notes carry the CRM e2e harness and its two fixes
  • Tooling: the console e2e suite reads the org-scoped routes and sectioned hubs
  • Tooling: five browser-driven e2e specs cover the CRM surfaces the v2 arc left bare
  • Bookings: the runtime mocks stub the capture door
  • Tooling: the Linear ceiling reads AGL-2629 for the CRM v2.1 arc
  • Console: the footer guard counts the Fields settings table as bounded
  • Console: the org contacts bridge links into the CRM hub, not the retired route
  • CRM: task routes, views and scope proven; the wiring spec stubs the admin sdk
  • Tooling: the Linear ceiling reads AGL-2609, the workspace head

Share this article

The Aglyn Team

We're building the open web platform. Follow along as we ship — and tell us what you need.

Start building on Aglyn.

Free to start — design your first page and publish in minutes.