How do I connect Google Sheets to a decision flow?
Add Google Sheets as a connection in your workspace authenticating with a Google service account, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Google Sheets in a decision without ever seeing the secret.
Can I test Google Sheets without touching production?
Google Sheets exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.
What can a flow call on Google Sheets?
5 operations, including “Read a range”, “Read several ranges at once”, “Read the workbook's structure”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Read a range”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.
Where in a decision should Google Sheets be called?
Some of a policy is numbers rather than logic — a rate card, a regional cut-off, a list of blocked employers — and the person who owns those numbers is rarely the person who edits the flow. Reading them at decision time keeps the two jobs apart, at the cost of a network call on a path that would otherwise never leave the engine, so the response is worth caching.
