Changelog

2026-06-08

Public documentation and automation guides

GTM Engine now has a dedicated public documentation site covering platform concepts, setup guides, automation tasks, API reference docs, and release notes. The docs are designed to help revenue teams understand what the platform can do, and to help technical teams build against the API without reverse-engineering product behavior from screenshots or internal support threads.

The automation guide also explains how workflows use triggers, inputs, outputs, steps, parallel tasks, Liquid variables, structured CRM writes, and user-facing messages. This makes the automation model easier to reason about before teams build real processes on top of it, reducing trial-and-error when moving from a simple workflow to a full CRM data automation system.

2026-06-03

Smoother workflow authoring

Workflow authors now get a more stable canvas, a clearer Add Task picker, better array variable guidance, source-record writeback controls, and easier workflow deletion from the editor. The goal is to make building and maintaining workflows feel less like configuring a hidden backend process and more like working in a reliable visual editor.

This release solves several common authoring pains: losing context on a crowded canvas, choosing the wrong task from a long list, being unsure which variables represent arrays, and needing extra navigation for routine workflow maintenance. Teams can now move faster while still understanding exactly what each workflow is going to change.

2026-05-29

Scalable workflow operations

Bulk workflow runs now have stronger progress tracking, batch history, cancellation controls, queue visibility, and clearer handling for large record selections. Teams can run automation across real pipeline segments without wondering whether work is still running, stuck, complete, or safe to retry.

This is especially valuable for data cleanup, enrichment, backfill, and scoring jobs that touch hundreds or thousands of records. Instead of treating large automation runs as a black box, operators get visibility and controls that make high-volume GTM operations manageable.

2026-05-22

Unified Automation Library

Workflows, triggers, agents, folders, comments, version history, diagnostics, and runs now live together in an IDE-style Automation workspace. Automation assets are easier to find, organize, inspect, and edit because the related pieces of a process are no longer scattered across separate surfaces.

The pain this solves is coordination. Revenue operations teams often need to understand which trigger starts a workflow, which agent can call it, what changed in the latest draft, and why a past run behaved a certain way. Bringing these pieces together makes automation easier to govern as the library grows.

2026-05-15

Self-serve signup and billing

New teams can sign up, start on a free plan, manage seats, buy credits, and track billing usage through the product without waiting on manual setup. The onboarding and billing surfaces now give teams a clearer path from first login to useful GTM data automation.

This reduces dependency on manual provisioning and support handoffs. Admins can understand what their workspace includes, what usage has been consumed, and what steps remain before the team is fully configured.

2026-05-08

Generate pipeline and outreach content

GTM Engine added target-account generation, propensity-guided account actions, and an outreach content builder that creates structured drafts from CRM context. Teams can move from "which accounts should we work?" to "what should we say?" without exporting records into disconnected spreadsheets or prompt documents.

The release solves the gap between data and action. Account signals, CRM fields, ICP context, and prior activity can now feed directly into prospecting workflows and outbound draft generation, so reps and operators spend less time stitching context together manually.

2026-05-01

Generate, Close, and Grow navigation

The app navigation was reorganized around pipeline generation, deal execution, and customer growth so teams can find core workflows more quickly. Instead of navigating by internal product modules, users can now orient around the GTM motion they are trying to improve.

This makes the platform easier for mixed teams to adopt. Sales leaders, RevOps, account executives, and customer-facing teams can get to the right surface without already knowing where a feature lives under the hood.

2026-04-24

Genie across the workspace

Genie gained broader page context, product help, dashboard and report assistance, workflow-building support, and a public product assistant for demo and setup questions. The assistant can now help across more of the workspace instead of being limited to isolated chat answers.

This solves the "what can I do here?" problem that appears in flexible systems. Users can ask questions in context, get help configuring GTM Engine, and move from an idea to a concrete report, dashboard, workflow, or next step faster.

2026-04-17

Workflow versioning and reusable triggers

Workflows now support publish and draft states, version history, rollback, active/inactive controls, reusable triggers, and recommended automation templates. Teams can make changes to important automations with more confidence because drafts and live behavior are separated.

This release addresses the risk of editing production automation directly. Operators can test changes, compare versions, pause automation when needed, and use recommended starting points rather than rebuilding common processes from scratch.

2026-04-10

CRM hygiene and cleanup

GTM Engine added guided cleanup for duplicate, stale, empty, orphaned, and stray records, with previews, dismissals, merge flows, and CRM-safe preservation of unmapped fields. CRM hygiene is now an active workflow rather than a quarterly spreadsheet project.

This helps teams fix the data quality problems that block forecasting, routing, reporting, and automation. Instead of guessing which records are safe to merge or ignore, operators get focused cleanup queues with enough context to act safely.

2026-04-03

Reporting and dashboards

Reports and dashboards gained folders, tags, visualizations, date grouping, cross-entity filters, saved views, and Genie-powered report creation from natural language. Teams can build more useful views of pipeline, activity, account, and contact data without waiting for custom BI work.

This solves the friction between questions and answers. Users can ask for the view they need, refine it with filters and visualizations, and save it as a reusable operating dashboard.

2026-03-26

Forecast history and sales process intelligence

Forecasting now shows how pipeline and risk changed over time, with movement details, risk flows, methodology scoring, and richer Path to Close context. Sales teams can understand not just where the forecast stands, but why it moved.

This release targets the recurring forecast review pain of arguing over stale snapshots and anecdotal deal updates. GTM Engine connects deal movement, activity evidence, qualification progress, and next-step gaps so managers can coach from actual signals.

2026-03-12

AI auto-fill fields

Admins can create and configure AI-filled fields, map CRM fields, test prompts against real records, provide feedback, and use typed outputs such as picklists, dates, numbers, booleans, and users. AI outputs can become durable CRM fields rather than one-off notes.

This solves one of the biggest gaps in AI-for-sales workflows: useful context gets generated, but it does not become structured data that reports, filters, agents, and other workflows can reuse. AI auto-fill turns unstructured activity into fields the organization can trust and query.

2026-02-26

Built-in call recording and activity intelligence

GTM Engine added built-in meeting recording, transcript ingestion, activity matching, recording playback, meeting prep, and user-level recording preferences. Meetings can now become structured GTM context without relying on reps to manually summarize every call.

This helps teams capture the evidence behind deal health, next steps, objections, competitors, and buying process signals. Calls and meetings become part of the CRM data layer, not just files that someone might search later.

2026-02-12

Account and contact discovery

Teams can find accounts and contacts from criteria, similarity, ICP presets, company context, and existing records, with enrichment, credit tracking, and batch progress. Prospect discovery is connected to the same CRM and ICP model the rest of the platform uses.

This reduces the manual work of building target lists, checking whether records already exist, enriching missing details, and deciding what to run next. Teams can move from market definition to usable records faster and with clearer usage visibility.

2026-01-29

Records workspace and bulk actions

Accounts, contacts, opportunities, and activities gained richer record pages, inline editing, CSV import and export, saved views, bulk updates, and workflow runs from selected records. The records workspace became a place to operate on GTM data, not just inspect it.

This solves day-to-day RevOps friction: cleaning fields one-by-one, exporting lists for basic edits, rebuilding views repeatedly, or jumping elsewhere to trigger automation. Users can now find a cohort, edit it, export it, or run a workflow from the same context.

2026-01-15

Team setup and onboarding

GTM Engine added guided onboarding, team hierarchy management, role-aware access, user invitations, quotas, and view-as controls for managers and executives. The platform now better reflects how revenue organizations are actually structured.

This helps managers and operators see the right data for the right people. Teams can set up hierarchy, access, and targets in a way that supports forecasting, coaching, and day-to-day pipeline review.

2025-12-18

Agents and Genie foundations

GTM Engine introduced configurable agents, workflow tools for agents, prompt libraries, suggested prompts, and page-aware Genie assistance across core workspaces. AI assistance became configurable and connected to real GTM tools instead of being limited to generic chat.

This release laid the foundation for agentic work in GTM Engine. Teams could start turning repeatable expertise into assistants that understand context, use tools, and help users complete tasks inside the product.

2025-11-20

Workflow automation foundation

The workflow builder gained triggers, nested workflows, API execution, reusable system workflows, variables, drafts, task testing, and structured task outputs. This made GTM Engine capable of supporting repeatable automation rather than isolated point actions.

The pain it solves is operational drift. When GTM processes live in ad hoc scripts, manual checklists, and one-off automations, they are hard to inspect or improve. Workflows gave teams a shared model for defining, testing, and reusing process logic.

2025-10-16

CRM sync and pipeline foundation

GTM Engine added CRM sync, field mapping, pipeline and stage configuration, forecast category mapping, user sync, and initial onboarding for connected workspaces. The platform could now sit on top of a team's CRM data while preserving the structure needed for forecasting and automation.

This solved the first integration hurdle: GTM data is only useful if accounts, contacts, opportunities, users, stages, and fields are mapped correctly. With this foundation, GTM Engine could become a reliable operating layer rather than a disconnected sidecar.

2025-09-10

Records and CRM hygiene foundation

The first records and hygiene experiences shipped with accounts, contacts, custom views, filtering, pagination, custom fields, orphaned-record cleanup, and ownership repair. Teams got the early tools needed to inspect and improve their CRM data quality.

This addressed the messy reality most revenue teams inherit: duplicate records, missing owners, incomplete fields, and hard-to-filter lists. GTM Engine began turning the CRM from a passive database into something teams could actively maintain.

2025-08-06

Forecasting and opportunity workspace

Pipeline and forecast views gained opportunity tables, forecast maps, owner filters, quota progress, opportunity notes, activity timelines, and history charts. Sales teams could start reviewing pipeline and forecast health in one place.

This release focused on replacing scattered deal inspection with a shared operating surface. Managers and reps gained more visibility into ownership, timing, stage movement, activity, and quota progress.

2025-07-21

Initial GTM Engine foundation

The first GTM Engine foundation shipped for CRM-connected records, opportunity workflows, team dashboards, activity processing, and early automation primitives. It established the core data model and product direction for a first-class GTM automation platform.

This solved the starting problem: before teams can automate revenue work, the system needs a reliable model for people, companies, opportunities, activities, ownership, and process. The initial release created that base so later CRM sync, workflows, agents, and forecasting features could build on the same foundation.