Flow Blockchain

Flow is a public blockchain with an open HTTP Access API. Agents read blocks, collections, transactions and their results, accounts, keys, and events, execute read-only Cadence scripts, and submit signed transactions to mainnet or testnet.

Verified 21 actions No credentials available

Platform Documentation Capability data verified 2026-08-25

A scheduled sweep runs from the last block height the flow processed

Get Events returns every event of the watched type across that height range

Execute Script reads the contract state those events point at, such as a balance or an owner

Get Network Parameters confirms the connection is pointed at the chain you meant

Get Account Key returns the proposal key's current sequence number for the prepared transaction

The agent posts what the transaction moves, who pays for it, and which account authorizes it

A person confirms, and only then does Submit Transaction broadcast the signed envelope

What This Integration Enables

Flow is a public chain, and its Access API is open. There is no key to manage, no plan to buy, and no rate contract to negotiate: the public mainnet and testnet access nodes answer unauthenticated. If you run your own access node, or need history older than the current spork, the connection points at your node instead. That combination, an open read surface plus a self hosted option, is what makes Flow practical to put inside a business workflow rather than inside a wallet.

FlowRunner agents read blocks, collections, transactions, execution results, receipts, accounts, keys, and events. They run read only Cadence scripts, which is how anything living inside a contract is reached, from a token balance to an ownership record to a marketplace listing. Almost everything interesting the chain returns is base64, so every operation that can carry encoded content decodes it in place and hands the flow ordinary JSON. Exactly one operation changes state, and FlowRunner does not sign it. The platform holds no private keys, which means Submit Transaction is a submission channel for an envelope that a wallet, the Flow CLI, or an SDK already signed.

Without FlowRunner

Chain data read by hand Someone opens a block explorer, copies an address, and reads a balance into a spreadsheet

Base64 in the way Scripts, arguments, and event payloads arrive encoded, so branching on them means decoding them first

Sealed read as successful A transaction that reached a sealed block is treated as done, even when its own result carries an error

With FlowRunner

Chain data as a scheduled feed Events are walked by height range and contract state is read with a script, on a schedule

Decoded on arrival Cadence source, arguments, and payloads come back as ordinary JSON a flow can branch on

Result read, not assumed The status code and error message on the result decide what the workflow does next

Use Case Scenarios

Watching a contract for the events that matter

A team needs to know when a specific event type fires on a contract they depend on. On a schedule the agent stores the last height it processed, calls Get Events for the range since then, and walks long histories in chunks because an access node caps how wide a single range can be. Each decoded payload is enriched with a read of the current state through Execute Script, then written to Airtable as a row and summarized into Slack. Get Node Version Info is checked first, since a query below the node's compatible range returns nothing at all rather than an error.
Treasury reporting across accounts

Finance wants a daily position across a set of on chain accounts without anyone opening an explorer. The agent reads each address with Get Account, which returns the balance, the public keys, and optionally the Cadence source of every deployed contract. Balances arrive as integers in the smallest unit and as strings, because they do not fit a JavaScript integer safely, so the agent scales them before writing. The daily position lands in Google Sheets alongside the fiat conversion, and any account whose key set changed since the previous run is flagged rather than filed.
A verification pass that does not trust a sealed block

An operations flow depends on a transaction that another system submitted. The agent polls Get Transaction Result until the status reaches sealed, then reads the status code and the error message on the result rather than treating sealed as done, because a sealed transaction can still have failed. A success continues the downstream process. A failure posts the error, the computation used, and the transaction id into Microsoft Teams, with Get Transaction alongside it so the reviewer sees the Cadence script and its arguments in readable form.

Human-in-Loop Highlight

Submit Transaction is the only operation on this connector that changes anything, and everything about it is final. The transaction is broadcast to a public chain, its payer and its effects are permanently readable by anyone, and there is no cancel. The dry run available here does not cover it either: Execute Script runs read only Cadence, so it can prove a precondition but it cannot simulate the mutation the envelope will perform. On top of that, the envelope was signed somewhere else, and three things must still line up at broadcast time, the proposal key's sequence number, the order of the authorizers, and the signing weight on each account. So the agent verifies what it can and then stops. It posts: "Signed envelope moves 1,250 FLOW from the treasury account to the payout contract. Proposal key index 0 shows sequence 418, the envelope was built at 417. Rebuild, or submit anyway?" A person decides. The agent goes back to polling Get Transaction Result afterward, and reads the result rather than the seal.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

21 actions

Blocks

Get Blocks Reads one or more blocks by height. Accepts a single height, a list, or the latest sealed and latest finalized sentinels.
Get Block By ID Reads one or more blocks by identifier.
Get Block Payload Reads a block's collection guarantees and block seals. The guarantees name the collections whose transactions the block includes.
Get Collection Reads one collection, the batch of transactions a collection node guaranteed and a block then included.

Transactions

Get Transaction Reads one transaction with its Cadence script, arguments, payer, proposal key, authorizers, and signatures, decoded into readable form.
Get Transactions By Block Reads every transaction in one block, addressed by block id or height.
Get Transaction Result Reads a transaction's execution result, including whether it succeeded, its error message, its computation used, and the events it emitted.
Get Transaction Results By Block Reads the execution result of every transaction in one block. The efficient way to process a block's outcomes in bulk.
Submit Transaction Submits an already signed transaction and returns the id the network assigned. FlowRunner holds no private keys, so this is a submission channel rather than a signer.

Scripts

Execute Script Runs a read only Cadence script against the execution state and returns the value it produced. How a flow reads anything that lives inside a contract rather than in a block or an account.

Accounts

Get Account Reads an account's balance, its public keys, and optionally the Cadence source of every contract deployed to it.
Get Account Keys Reads every public key on an account with its index, algorithms, sequence number, weight, and revocation flag.
Get Account Key Reads one public key by index. Its sequence number is the one a transaction's proposal key must carry, so read it immediately before building rather than from cache.
Get Account Balance Reads an account's balance from the dedicated balance route. Published in the specification, but not served by every node, so prefer the account read unless your node supports it.

Events

Get Events Reads every event of one type across a block height range or an explicit set of blocks. The event type is a dotted name that carries the contract address without its hex prefix.

Execution

Get Execution Results By Block Reads the execution results produced for one or more blocks.
Get Execution Result Reads one execution result by its own identifier rather than by the block it belongs to.
Get Execution Receipts By Block Reads the execution receipts for one block. Each receipt is one execution node's signed commitment.
Get Execution Receipts By Result Reads every receipt that commits to one execution result, which is how you see how many nodes agreed on it.

Network

Get Network Parameters Reads the access node's chain id. The cheapest way to assert a new flow is pointed at the network you meant, since every read otherwise succeeds against the wrong chain and returns nothing.
Get Node Version Info Reads the node's software version, its current spork, and the block height range it can answer for. Check that range before concluding data is missing.

Frequently Asked Questions

What can FlowRunner do with Flow Blockchain?

FlowRunner agents can run Get Blocks, Get Block By ID, and Get Block Payload in Flow Blockchain, plus 18 more actions.

Does connecting Flow Blockchain to FlowRunner require OAuth?

No. Flow Blockchain needs no credentials at all, so there is no key to obtain, store, or rotate.

Can Flow Blockchain trigger a FlowRunner workflow automatically?

Flow Blockchain doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Flow Blockchain

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us