docs(snowflake): document scheduling frequency and webhook workaround for table source

[george-dilthey]

What changed

snowflake-integration.md had no information about scheduling frequency for the Import from Snowflake table source. A user asked "Import from Snowflake looks to be schedulable once-an-hour at most. Is there a way to schedule it more frequently than that?" and had to be escalated to a human support agent, who answered:

"Hourly is the floor for the built-in scheduled trigger for Snowflake, but you can hit the table with a webhook to trigger runs as soon as new Snowflake data lands."

Added a "Scheduling imports" subsection to the Source Import from Snowflake section documenting:

• The built-in scheduler supports hourly (Enterprise only), daily, weekly, or monthly
• Daily is the fastest available schedule on non-Enterprise plans; Enterprise customers can import as often as once per hour
• For sub-hourly syncing (or below daily for non-Enterprise), use a Clay webhook instead — point your Snowflake pipeline at the Clay table's webhook URL and it kicks off enrichment immediately on each batch

Why

Intercom ticket #215474349578021 — customer asked directly about Snowflake Import scheduling frequency and was escalated to a human because the docs covered only connection setup and inputs, with no scheduling information.

The existing scheduled-sources.md documents hourly scheduling in general terms but is not surfaced from the Snowflake integration doc, and no webhook workaround is mentioned anywhere in the Snowflake docs.

Source link(s)

• Intercom conversation: https://app.intercom.com/a/apps/w28k1kwz/conversations/215474349578021
• Code — schedule frequency enum (hour, day, week, month): /workspace/clay-base/apps/frontend/src/components/Sources/types/action/registry/utils.ts
• Code — Snowflake Import default is daily: /workspace/clay-base/apps/frontend/src/components/Sources/types/action/registry/ActionSourceRegistry.ts:1141,1163,1184 (all Snowflake sources use CronConfigType.Daily)
• Code — hourly is Enterprise-only gate: /workspace/clay-base/libs/shared/src/feature-flags/featureFlags.ts — EnableHourlyCronForSources flag, enabled only for Enterprise plan in plan.ts:271
• Verifier verdict: PASS for scheduling frequency and plan gating

Uncertainties

None. All claims verified against code (verifier sub-agent).

Related observations

• snowflake-integration.md also has no mention of the 50,000-row table limit or the fact that auto-delete does not bypass the row limit for Snowflake Import (incompatible source type). The customer's follow-up in the same ticket hit this gap; they have a PLG workflow expected to grow to 6 figures and didn't know about the row cap. The incompatibility is documented in auto-delete.md but there's no cross-reference from the Snowflake doc. Keeping out of scope for this PR (separate gap), but worth a follow-up.

Confidence

Confidence: high — scheduling frequency and plan gating verified against code (PASS). Change is small, scoped to one new subsection in one file, no existing content modified. The corrected nuance (daily = non-Enterprise floor, hourly = Enterprise floor) is confirmed by code constants and the verifier.