Capability reference

Find supported capabilities, their business purpose and the setup or review each needs.

Updated September 27, 2026 1 min read

Use this reference when you know the kind of work you need to do and want to find the supporting capability. Each entry explains its business purpose and current behavior. The catalog is generated from the same content as the product page.

Entries marked Review workflow use an approval process. Other entries may still have permission, provider or policy requirements, so check Setup and Integrations for your workspace’s availability.

For a complete task combining several capabilities, choose an industry workflow recipe. For the exact operations an assistant can call, use the AI tool reference.

Capture

It captures what happens.

Meeting transcript context: Bring supported transcript content from a configured Drive source into the workspace. Connected Drive indexing retains extracted text from supported files. Review extracted information against the source; processing depends on the configured sync, supported file type and available AI workflow.
Pasted contact lists and context: Turn a pasted contact list into a review batch, or supply context for a specific AI request. Contact import lets you inspect proposed records before confirming them. Other requests use the assistant’s available tools and may need a separately reviewed proposal.
Connected email history: Read supported email threads alongside the customer and work they belong to. Connect and verify the mailbox, then inspect sync results and identity matches. Unfamiliar senders can be reviewed before their conversations are linked to a contact.
Calendar context: Keep available meeting records and attendees connected to the workspace. A configured calendar connection provides meeting context. Meeting preparation identifies upcoming appointments; Meeting commitments turns an explicitly entered checklist into assigned tasks.
Bring in available history: Use configured sync and backfill to make earlier email and calendar records available. Review the provider permissions, job limits and sync results to understand the history imported. A connected account does not guarantee that its entire archive has been read.
Contact import: Bring in a CSV or a pasted list, check it against the people you already know, and review the proposed records before anything saves. An import is a review step rather than a blind write. The system flags rows that look like someone you already have, which is how an unfamiliar sender ends up attached to the right person instead of becoming a duplicate.

Organize

It keeps records connected.

Customer records: Find the available conversations, notes and commitments linked to a person. Open a contact to see its next step, recent open work, linked conversations, opportunities and timeline together. Ask AI opens a draft question about that record; the person decides when to send it. Missing sources or unresolved identities remain visible work for the team to check.
Companies: Who works where, which deals belong to whom, and how the accounts connect. Company records tie people, deals, and history together, so an account is one place to look instead of a set of names you have to join up yourself.
Opportunities and pipeline: See current stages, values and next actions in board, list or calendar form. Open the opportunity to inspect its customer, activity and next step. Calendar shows dated next actions on the viewer's local day and keeps unscheduled opportunities visible. Individual and bulk status changes from Leads use the same Pipeline rules, with named recovery details for incomplete updates. Retrying the same change preserves its existing follow-up or client engagement. Use the evidence you have before changing the record, then confirm the saved result.
Tasks and commitments: Give work a title, date and source context so the team can follow it through. Work starts with your open tasks and can show team work when needed. Use the same tasks as a list, status board or date calendar; filter and save a personal or workspace view; then edit, snooze or complete work through its existing task service. The list supports keyboard triage. Ask AI can prepare task reopening and description edits for review, with stale-change checks before execution. Onboarding and meeting workflows can create assigned checklists linked to their source records.
Customer notes: Keep useful customer details attached to a shared record. Save notes where the team can find them alongside the relationship history. Inspect the original source when a note affects a decision or commitment.
Business-specific records: Adapt the platform to track the information your process needs. Use supported settings where available. New fields, record types or lifecycles may require a source extension that reuses the existing identity and permission services.
A connected relationship graph: People, companies, deals, and documents link through the same records, so the connections between them are visible. Suggested relationships from Opportunity Radar arrive with their sources and wait for your review. An introduction offer is an offer, and it does not mean the other person has agreed to be contacted.
Customer activity history: Follow available messages, notes and recorded work in the context of a customer. Open the linked source to inspect a timeline entry. The activity record helps distinguish human decisions, proposed work and executed results.
Review contact matches: Check suggested identities before linking an unfamiliar sender to a customer. Identity matching lets you match a sender, create a contact when appropriate or leave the item for later. Imports also surface possible matches for review.
Opportunity RadarReview workflow: Keep supplied sources, reviewed opportunities, relationship context, and saved drafts in one workspace, and approve anything before it sends. Source briefing runs on a budget you set and stays off until you turn it on. Reviewed outreach uses the sender you configured only after an exact human approval, with contact checks and cooldowns. Automatic discovery and outcome measurement are still being built.

Act

It prepares work and, once you approve, does it.

Website pages: Draft and edit pages with AI help, preview them at phone and desktop widths, and publish only a revision you have reviewed. New forks start with an editable, neutral product homepage and a fictional demo that needs no credentials. Guided setup connects your own workspace; save a contact and task before adding optional providers. Create your own pages, connect published forms to reviewed intake, and choose an AI model by provider and price or edit manually. Drafts stay private until published, with revision history and optional owner-only ChatGPT access through the same editor services.
Social marketingReview workflow: Prepare LinkedIn posts from your own sources, approve the exact wording and schedule, and follow the result through to a verified publication. Each workspace connects its own organization account. An uncertain submission keeps its receipt for review instead of being reported as published.
CollectionsReview workflow: Group verified invoices by account and currency, record promises and disputes, and approve an exact reminder when you are ready to send. With Stripe invoicing enabled, open Invoices from the sidebar to create customer invoices, then use Collections to manage overdue balances. Ask AI to propose a pause, promise, dispute, owner or next action, then review the exact change. Fresh invoice and contact checks guard approvals; reminders require a separate review and send receipt.
Subscriptions: Sell monthly or annual plans through Stripe Checkout and give each customer a branded account for renewals, invoices, and card changes. Stripe stays the payment authority, and the workspace shows a checkout or webhook delay as pending rather than guessing an outcome.
Context-aware reply draftsReview workflow: Ask AI to prepare a reply using the available conversation and business records. An explicit outreach request can stage a reviewable email proposal in the same conversation. Check the wording, recipient and commitments in Work before approving a send, then inspect its recorded result.
Follow-up commitmentsReview workflow: Turn an agreed next step into visible work with a date and an owner. Enter the commitment directly or use a supported task proposal. Meeting commitments takes an explicit checklist; automatic transcript extraction is a separate workflow.
Assigned task checklistsReview workflow: Break an onboarding or meeting follow-up into tasks the team can complete. The bundled workflow plugins prepare one to ten tasks with descriptions, dates and assignees. Review the plan and confirm the created tasks after execution.
Reviewed pipeline changesReview workflow: Ask AI to propose a stage change for a specific opportunity. Inspect the record, proposed stage and supporting context in the approval flow. Confirm the saved stage and activity after the action runs.
Campaign follow-upReview workflow: Prepare multi-step outreach with recipient checks, stop rules and reviewed activation. Inspect the audience, sender, content, timing and limits before activation. Reply and suppression handling stop eligible future work through the shared campaign services.
Bulk contact changes: Tag up to two hundred contacts, stage them into a draft campaign, or suppress campaign email, with a result for each one. Successful rows stay saved if another row fails, so a partial run is visible and the unfinished part can be retried.
Configured recurring work: Use supported jobs and workflow triggers to keep repeated work visible. Configure the required capabilities and schedules, then inspect job and action results. A new business rule may require a source extension rather than a setting.
Shared approvalsReview workflow: Review AI proposals and workflow plans in one place, with their source context. Approval records the decision; execution records the result. Autonomous proposals are checked before they reach the queue, and each one explains why it earned your attention. Anything you asked for directly is never held back, and a background check that finds nothing finishes quietly instead of reporting it. Eligible autonomy changes need a separate human decision, and restricted external actions keep their approval requirements.

Learn

It turns your decisions into rules.

Reusable corrections: Propose guidance your team wants future work to follow. Learning Inbox keeps the proposed rule, scope and source available for review. Approved independent rules stay active together, and edited replies can propose reusable corrections. Cited references and later context receipts make their use inspectable.
Recorded decisions: Keep the reason for declining a proposal available with the work. A recorded rejection helps the team understand the decision. Propose reusable guidance through Learning Inbox when the correction should apply beyond that one action.
Results you can inspect: Compare recorded replies, stage changes and provider results with the work you requested. Activity and action receipts retain evidence of execution. Use those records to assess the result; a completed action alone does not establish a business outcome.
Autonomy you raise on purpose: Every kind of action carries its own trust level, and standing permission takes a human decision to grant. Changing a level, a constraint, or the source clears the previous approval, so a shift in policy always comes back to a person. Revoking a permission keeps its audit history.
A view of today’s work: Start with decisions, follow-up and business changes drawn from available records. Today provides source-linked attention and supporting context. Open a finding to inspect its record before acting.
Prepare for upcoming meetings: Find upcoming meetings and use their linked context to plan your preparation. The Meeting preparation plugin provides a time-ordered report. A configured Meeting Intelligence Coworker can support richer briefs; its sources and execution must be set up separately.
Find overdue follow-up: Use stale opportunity and overdue-task reports to decide what needs another look. Pipeline follow-up and Overdue commitments apply defined rules to available records. Inspect the source and report coverage before drawing conclusions about the customer.
Advance a debate production: Track each participant commitment and the first step still missing. The Bookings module keeps topic interest, pairing, question, format, date and the verified Google invitation separate. Today links to the production. Review two inbound participant acceptances before approving an invitation, then recheck the provider event and responses.
Keep open questions with the work: Record an unanswered question as a note or next action linked to the customer. The team can return to that context before the next conversation. Use an assigned task when the question needs a specific owner and due date.

Connect

You reach it from any device or assistant.

The web workspace: Today leads with sourced decisions and follow-up; the same tasks and approvals stay editable in Work. Eight primary destinations group the workspace around Today, Work, Records, Conversations, Knowledge, Coworkers, Apps and Settings. Personal and shared Today arrangements keep view tools under More, wide desktop layouts keep independent columns, and Search and Ask AI stay available while you scroll. The mobile dock keeps the three daily destinations within reach.
Run work through conversation: Ask for the result you need, review exact changes in chat and follow the saved work. Ask AI reads records, prepares replies and tasks, and previews ordered jobs. Configured background work retains progress after the browser closes. You can approve exact proposals inside chat and grant bounded permission for named internal operations. Messages, publishing, billing and permission changes keep human review. Available tools depend on modules, providers and current access.
Your own assistant, connected: Use a connected agent to read records, prepare changes and manage saved work. Compatible clients use the same registered tools, record services and approval rules. An authenticated member connection can delegate ordered work and read or control its progress. Tenant bearer keys retain integration scope. Pending proposals link to the exact human review, and unsupported operations are reported plainly. A separate owner-only Site Studio connection handles website editing.
A mobile-ready workspace: Today, Intake review, Pipeline, Records, and Setup all work from a phone browser, including the pipeline board. The board scrolls freely, keeps its column controls at every screen size, and supports dragging, touch, and a stage control for moving a card without dragging. Deployments with a dedicated app address also support installation, connection status and local drafts that you can read and reuse after reconnecting.
Shared service interfaces: Build integrations against the platform’s supported operations. Use the documented tool, adapter and service contracts. A custom integration needs implementation and permission checks for the particular records and actions it exposes.
Decision-ready analytics: Source, owner, campaign, stage, communication, forecast, attribution, and data-quality signals sit together. Metric definitions are documented, so a forecast is labelled as a forecast and does not read as a recorded fact.
Apps built around your process: Extend the platform with custom records, lifecycles, workflows, integrations, AI tools, and screens that reuse your existing customer context. Configuration covers the supported settings today, and broader changes use source development. A general-purpose in-app App builder is planned.
Make the workspace your own: Choose one of nine appearances or preview a custom palette, typography, and corner style, then save it for the workspace. Text contrast is checked before a theme saves, density is adjustable independently, and a theme follows the same permissions and revision checks as other branding. Demo choices stay separate from the live workspace.

Govern

You keep control, and every action is logged.

Choose optional capabilities: Enable the optional parts of the workspace your business needs. Core capabilities remain available. Disabling an optional module removes its navigation and gates its routes and tools, while preserving existing records.
Point a coding agent at the backlog: A plain-language request is enough for a coding agent to pick up a task, prepare an isolated workspace, and carry it through verification and commit. The agent does not need a ticket key or a provider-specific command, and it never asks you to paste credentials. With recovery enabled, a replacement agent can resume an interrupted task from its saved state. Verification renews the active claim, and checkpoints include safe unfinished source while excluding credentials and generated output.
Trace recorded actions: Inspect who initiated a change and the result recorded for it. Activity and receipts link actions to source records. Sensitive content stays in authorized records rather than being copied into every audit entry.
Disable optional automation: Turn off a supported module or capability when your team needs to stop its work. Use the relevant configuration control and inspect any pending work. Historical records remain available according to the feature’s retention and access rules.
Workspace data boundaries: Keep business records separated by workspace access, or run a self-hosted installation on infrastructure you control. Managed workspaces use tenant-scoped records, active membership, and row-level policy. A self-hosted installation uses your own database and provider accounts; agree on export and handoff responsibilities before a managed implementation.
Workspace and record access: Keep business data behind active membership, roles and record permissions. The runtime rechecks access for supported operations. An installation can offer Google sign-in alongside email, while active membership still controls workspace access. Review your workspace’s configured permissions instead of assuming a job title automatically grants or hides particular screens.
Connection and execution health: Find missing setup, failed jobs and results that need recovery. Setup and operational health views show supported checks with their evidence. Follow the named recovery step and verify the specific connection or job afterward.
An open-source foundation: Run and extend the MIT-licensed application with infrastructure and provider accounts you control. Use the neutral starter and self-hosting guides for your own installation. Review the documented content exports, data ownership and support arrangements when planning a handoff.