Snowflake StrawberryInsert single row in Snowflake (OAuth), on your say-so
Snowflake (OAuth) exposes 3 operations and a companion can work all of them: insert a single row, insert multiple rows and execute a SQL query. Anything that changes a record waits for your click.
Open the multiple row. Check it against something else. Write the change. Move to the next one. That is the Snowflake (OAuth) afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a multiple row until you approve it.
What it can do is exactly what Snowflake (OAuth) exposes to an account you authorise and nothing beyond it: 3 operations, no reads and 3 writes. In practice that means it can insert a single row, insert multiple rows and execute a SQL query, and work across the multiple rows, single rows and sql queries.
The Snowflake (OAuth) API stops at Snowflake (OAuth). A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the multiple rows or ask you for them?
In the tab. Snowflake (OAuth) exposes no read operation to a connected account, so a companion opens Snowflake (OAuth) in the session you are already signed into and reads the screens you would.
The multiple rows are what most of this inventory is about, alongside the single rows. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of Snowflake (OAuth) admin becomes a queue you review.
What happens before it can insert single row?
All 3 write operations wait for you. A companion can insert a single row, insert multiple rows and execute a SQL query, and each one is staged on an approval card first: you see the multiple row, the field and the new value before it lands in Snowflake (OAuth).
Nothing in Snowflake (OAuth) is sent, changed or deleted on your behalf without that click, and a rejected card leaves the multiple row exactly as it was. The gate is the same one on every surface, described at security.
- Insert Single Row
- Insert Multiple Rows
- Execute SQL Query
Does the multiple row sweep have to be asked for every time?
Yes. Saved as a routine, the Snowflake (OAuth) multiple rows pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The research and analysis playbook catalogues the other recurring shapes of the queries, the Snowflake (OAuth) multiple rows sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents