- Automations
- Conga + Snowflake
AI-native automation
Automate work across
Conga and
Snowflakewith Caddi AI Agents.
Automate anything you do across Conga, Snowflake, and the rest of your tools. Sign in, show or tell Caddi what you want, and it runs end to end. No workflow builder.
How to connect Conga and Snowflake

Connect Conga to Caddi
Allow1Sign in to Conga
One click with your own Conga login. No API keys.
Connect Snowflake to Caddi
Allow2Sign in to Snowflake
The same click again. Both tools are connected.
Write rows in Snowflake when document generated in Conga.
ScreenshareType it3Show or tell it
Screenshare the job, or type it in chat. Change it any time.
- Running

14 done1 for review
4Watch it run
Caddi does the work and flags anything unsure for review.
What Caddi is and how it works
An AI teammate that runs your back-office loops.
- Doesn't break. Caddi reads intent, so when fields move or UIs change, your loop keeps running.
- Taught like a new hire. Walk Caddi through the work once. Tweak it later by chat, with no workflow builder to re-architect.
SOC 2 attested · Human-in-the-loop · Full audit trail · 150+ tools across legal, finance, and operations
Practical ways to use Conga and Snowflake together
- 01
Write rows in Snowflake when document generated in Conga.
Caddi watches Conga for document generated and write rows in Snowflake. No copy-paste, no missed records.
- 02
Generate document in Conga when query returns rows in Snowflake.
Caddi watches Snowflake for query returns rows and generate document in Conga so the two systems stay in lockstep.
- 03
Update rows in Snowflake from Conga events.
When contract executed happens in Conga, Caddi update rows in Snowflake with the right context attached.
Actions Caddi can take across Conga and Snowflake
CongaDocument generated
Triggers when Conga produces a document from a template.
CongaContract executed
Triggers when a contract is fully signed.
CongaApproval requested
Triggers when a document is sent for approval.
CongaGenerate document
Run a Conga template against a CRM record.
CongaSend for signature
Route a generated document for e-signature.
CongaUpdate contract
Write status and dates back to the contract record.
- Snowflake
Query returns rows
Caddi runs a query on a schedule and hands the rows it returns to the next step.
- Snowflake
Write rows
Insert rows into a table in Caddi's schema.
- Snowflake
Update rows
Update the rows that match a condition in a table in Caddi's schema.
- Snowflake
Create table
Create a table in Caddi's schema.
- Snowflake
Run query
Run a read query and return the rows.
- Snowflake
Read table
Read the rows of any table or view Caddi's role can see.
Common questions
How does Caddi connect Conga and Snowflake?
Conga and Snowflake just run together. You teach Caddi the way you'd teach a new hire: walk it through how you use them today, with no workflow builder to wire up. Caddi turns that walkthrough into a verified loop and runs it against Conga and Snowflake end-to-end.
Do I need engineering help?
No. Whoever does the work today walks Caddi through it on a call, the same way they'd train a new hire. Caddi builds the loop. No code, no IT ticket.
Is my data safe?
Yes. Caddi is SOC 2 attested. The AI watches and builds the automation, and once the loop ships it runs as deterministic code, repeatable and logged, with any model step scoped and reviewable.
Can Caddi connect Conga and Snowflake to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first Conga + Snowflake loop is live, Caddi suggests other tools and other workflows to fold in.
How fast can it go live?
Typical first loops ship within a week of that first walkthrough. The Caddi team reviews every loop before it runs in production.
Ready to automate Conga and Snowflake?
Drop your work email and we'll show you Caddi running end-to-end against Conga, Snowflake, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.






