Amazon Managed Blockchain Query
Read list transaction events, list transactions, batch get token balance from ManagedBlockchain Query (SigV4).
OCNORA ships 3 typed Amazon Managed Blockchain Query operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Amazon Managed Blockchain Query
- Authentication
- API key
- Credential
- {"access_key_id", "secret_access_key"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Amazon Managed Blockchain Query
Operations, grouped by what they do to your data.
Read and search 2
Other operations 1
A sample Amazon Managed Blockchain Query workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon Managed Blockchain Query trigger is needed.
- 2List Transaction Eventsmanagedblockchain_query.list_transaction_eventsLists all the transaction events for a transaction This action will return transaction details for all transactions that are confirmed on the blockchain, even if they have not reached finality.
- 3Batch Get Token Balancemanagedblockchain_query.batch_get_token_balanceGets the token balance for a batch of tokens by using the BatchGetTokenBalance action for every token in the request.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 3
- Batch Get Token BalanceGets the token balance for a batch of tokens by using the BatchGetTokenBalance action for every token in the request.managedblockchain_query.batch_get_token_balance
- List Transaction EventsLists all the transaction events for a transaction This action will return transaction details for all transactions that are confirmed on the blockchain, even if they have not reached finality.managedblockchain_query.list_transaction_events
- List TransactionsLists all the transaction events for a transaction.managedblockchain_query.list_transactions
Amazon Managed Blockchain Query questions
- How does OCNORA authenticate with Amazon Managed Blockchain Query?
- With a stored API key credential, shaped {"access_key_id", "secret_access_key"}. A connection test can check it when you add it.
- What can I automate with Amazon Managed Blockchain Query?
- 3 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Amazon Managed Blockchain Query operation I need is not listed?
- Where Amazon Managed Blockchain Query has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Amazon Managed Blockchain Query?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Amazon Managed Blockchain Query calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Amazon Managed Blockchain Query workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.