docs(salesforce): add managed package AppExchange and Flow automation FAQs

[george-dilthey]

What changed

Added two new FAQ entries to docs/salesforce-integration-faqs.md:

1. "Is the Clay Salesforce managed package available on the public AppExchange?" — Answers that the package is not on AppExchange, is installed via a private direct link from the Clay account team, and links to the Notion setup guide.

2. "Can the Launch Enrichment button be triggered automatically from a Salesforce Flow?" — Answers that the button is manual-only, and recommends Salesforce Flow HTTP Callout to a Clay webhook URL for automated triggering — including a 3-step setup guide.

Why

Triggered by Intercom conversation #215475615366287 (HiBob / Ruth Getahon). The customer asked:

• Is the Salesforce managed package on the public AppExchange or installed via a direct link?
• Can the Launch Enrichment button be triggered automatically from a Salesforce Flow?
• What's the right approach for passing Account ID + Flow-calculated values to a Clay workflow?

The first Clay rep (James Ferguson) answered "yes, Clay has a managed package" and linked the Salesforce FAQ doc — but the FAQ had no answers to these three follow-up questions. A second rep (Richard Bleach) gave the correct answers manually. The docs need to cover this so Fin can answer next time.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/inbox/w28k1kwz/inbox/conversation/215475615366287
• Slack thread (customer → Clay reps): https://clay-hq.slack.com/archives/C09RQM4ANQ4/p1787495327680089?thread_ts=1787495327.680089&cid=C09RQM4ANQ4
• Corroborating Slack — AppsFlyer thread (Jan 2026, manual-only + HTTP Callout recommendation): https://clay-hq.slack.com/archives/C07BLHDTX71/p1768476754702539
• Corroborating Slack — Nextdoor thread (Jul 2026, package description + install instructions): https://clay-hq.slack.com/archives/C0BBMCR1PAL/p1783453631139679
• Notion setup guide: https://clayrun.notion.site/Clay-Salesforce-Package-V8-With-Videos-1307e66eb014807bbde2dca8ec26ce63
• Verifier: Claim 2 (manual-only) UNKNOWN from code (Apex package is external to the repos); all Slack evidence consistent. Claim 3 (HTTP Callout) PASS with clay-base webhook source evidence and multiple Slack confirmations.

Uncertainties

AppExchange / plan availability (FAQ 1): Multiple CS/support Slack messages (e.g., #ent-nextdoor-clay Jul 2026) say the package is "available on Enterprise plans." However, the verifier returned FAIL on the Enterprise-only claim: engineer Matthew Quan stated in #team-integrations (Aug 24, 2026) "ya i think technically you don't even need a flag actually" — meaning there is no technical plan gate. The corrected doc drops the Enterprise-only claim and tells customers to reach out to their account team to confirm availability, which is safe across both the commercial-policy and no-gate interpretations.

"No supported way to invoke from Flow" (FAQ 2): The verifier returned UNKNOWN — the package is a Salesforce Apex project, not present in clay-base or public-actions, so implementation details cannot be confirmed from code. All observable Clay support guidance (multiple Slack threads) consistently steers customers away from Flow invocation toward the HTTP Callout pattern. The Apex button action could technically be called from a Salesforce Flow as an Invocable Action, but Clay has never documented, supported, or recommended this path.

Related observations

PRs #2237, #2241, #2247, #2268, #2304, and #2306 are also open on this file but address unrelated error-handling and UI FAQs (INVALID_CROSS_REFERENCE_KEY, DUPLICATES_DETECTED on Update Record, Map fields UI, Account ID in Create Contact, Salesforce list source limits, and lead-converted campaign membership). None overlap with the AppExchange or Flow-automation content added here. Reviewers should reconcile these PRs at merge time to avoid line conflicts.

Closes DOC-2084

[linear-code]

DOC-2084