docs(audiences): document enrichment workflow beta option

[george-dilthey]

What changed

Added a paragraph to docs/audiences.md in the "Adding enrichments" section documenting the "Create enrichment workflow" option — a beta feature that lets users create a Workflow-backed enrichment directly from an Audiences segment.

Why

Intercom conversation #215475667573528: a customer on the People audience page (/people) clicked "add enrichment table" and got the error "Failed to create enrichment. Please try again later." Fin couldn't answer the question and escalated. Human support agent Adhvita Ahuja explained that creating enrichment tables directly from an audience is being replaced by Workflows for workspaces in a migration cohort, and walked the customer through the Workflows-based enrichment path.

The docs had no coverage of the "Create enrichment workflow" option at all. Fin had nothing to retrieve.

Verifier verdict: BETA — AudiencesEnrichmentCenterSidebar.tsx:302 confirms a "Create enrichment workflow" button exists, labeled with <BetaBadge color="blue">, guarded by Eppo flag enable-audiences-workflow-enrichments. Legacy "create enrichment table" creation controls are hidden only for workspaces that satisfy all three conditions: flag enable-audiences-workflow-enrichments-only enabled, non-Enterprise plan, and workspace has never previously created a bulk enrichment. The new path is BETA; the old bulk-enrich path still works for most users. The new paragraph includes explicit beta framing ("currently in beta") and instructs users to fall back to Enrich → Add bulk enrich if the option isn't visible.

Slack context from verifier (⚠️ Slack discrepancy noted): The Slack thread in #support-copilot confirms workspace 476391 is in the rollout cohort. Grant Empey in #workstream-pricing (Aug 4) noted "Any enrichments created in audiences will be deprecated for workflows 2 weeks after launch since bulk enrich is going away in favor of workflows in audiences." Zona Zhang in #team-audiences (Aug 12) confirmed bulk enrich via audience "is not a great experience and we are deprecating that soon." The beta framing in the doc accurately reflects current state (gated rollout) while direction-of-travel is GA.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/inbox/_/inbox/conversation/215475667573528
• Verifier code evidence: clay-base/apps/frontend/src/components/Audiences/AudiencesCommandCenterSidebar/Workflows/AudienceEnrichment/useAudienceWorkflowEnrichmentFlags.ts (Eppo flag gate) and AudiencesEnrichmentCenterSidebar.tsx:302 (BetaBadge)
• Slack trigger: https://clay-hq.slack.com/archives/C0BEGMVUA3U/p1787828548191039
• Slack rollout signal: https://clay-hq.slack.com/archives/C085P55RL31/p1785849415682969 (Grant Empey, Aug 4)
• Slack deprecation signal: https://clay-hq.slack.com/archives/C08B9DAQQP3/p1786566881242039 (Zona Zhang, Aug 12)

Uncertainties

The "Create enrichment workflow" entry point from within Audiences (Enrich → + → Create enrichment workflow) is confirmed in code with a BetaBadge. The exact UI label may change as the feature approaches GA. The doc uses the customer-facing description from the support agent's reply ("Create enrichment workflow option in the Enrich menu") which matches the code.

Related observations

There are 22+ existing open PRs on docs/audiences.md flagged by pre_pr_check (#2395, #2383, #2370, #2356, #2354, #2349, #2348, #2345, #2323, #2321, #2305, #2303, #2295, #2291, #2288, #2280, #2272, #2261, #2251, #2245, #2232, #2231, #2225, #2224). This change is on a distinct topic — the new Workflow-backed enrichment creation path from Audiences — not addressed by any of them. All existing PRs cover different topics: ad platform syncing, Upsert segment record, workspace movement, Salesforce export timing, Lookup scoping, deduplication, legacy plans, HubSpot fields, SOQL imports, etc. A reviewer merging this PR should be aware of the other open PRs and ensure they don't introduce conflicts.

Closes DOC-2185

[linear-code]

DOC-2185