[ More ]
Blockscout integration for your workflows.
Connect Blockscout to Collabase once and use 34 actions in your workflows. No code needed, hosted in Switzerland.
Blockscout in Collabase
Connect Blockscout to Collabase once and use 34 actions in your workflows. No code needed, hosted in Switzerland.
[ About the service ]
Blockscout is a tool for inspecting and analyzing EVM chains.
How to connect it
- Open the integrations in the workspace settings.
- Choose Blockscout and connect your account.
- Add a trigger or an action to the workflow.
Blockscout triggers
Blockscout does not start a workflow on its own. You use its actions after any other trigger.
Blockscout actions
| Name | Description | Fields |
|---|---|---|
| Search | Search for addresses, transactions, blocks, or tokens |
|
| Check Search Redirect | Check if a search query should redirect to a specific resource |
|
| Get Blocks | Get list of blocks | 0 |
| Get Main Page Blocks | Get blocks for main page display | 0 |
| Get Block by Hash or Number | Get block info by its hash or block number |
|
| Get Block Transactions | Get list of transactions for a specific block |
|
| Get Block Withdrawals | Get list of withdrawals for a specific block |
|
| Get Transactions | Get list of transactions | 0 |
| Get Main Page Transactions | Get transactions for main page display | 0 |
| Get Transaction by Hash | Get transaction details by its hash |
|
| Get Transaction Token Transfers | Get list of token transfers in a transaction |
|
| Get Transaction Internal Transactions | Get list of internal transactions in a transaction |
|
| Get Transaction Logs | Get list of logs generated by a transaction |
|
| Get Transaction Raw Trace | Get raw trace data for a transaction |
|
| Get Transaction State Changes | Get list of state changes in a transaction |
|
| Get Transaction Summary | Get a human-readable summary of a transaction |
|
| Get Addresses | Get list of native coin holders | 0 |
| Get Address by Hash | Get address info by its hash |
|
| Get Address Counters | Get counters (transactions count, token transfers count, etc.) for an address |
|
| Get Address Transactions | Get list of transactions for an address |
|
| Get Address Token Transfers | Get list of token transfers for an address |
|
| Get Address Logs | Get list of logs generated by an address |
|
| Get Address Blocks Validated | Get list of blocks validated by an address |
|
| Get Address Token Balances | Get list of token balances for an address |
|
| Get Address Tokens | Get list of tokens owned by an address with filtering options |
|
| Get Address Withdrawals | Get list of withdrawals for an address |
|
| Get Address Coin Balance History | Get list of coin balance changes for an address |
|
| Get Address Coin Balance History By Day | Get list of coin balance changes for an address grouped by day |
|
| Get Tokens | Get list of tokens | 0 |
| Get Token by Address | Get token info by its contract address |
|
| Get Token Transfers | Get list of token transfers |
|
| Get Token Holders | Get list of token holders |
|
| Get Token Counters | Get token counters (holders count, transfers count, etc.) |
|
| Get Token Instances | Get list of token instances (NFTs) |
|
[ More ]
Related integrations
Tools that often share a workflow.
Questions about Blockscout
What can I automate with Blockscout in Collabase?
Blockscout brings 34 actions and 0 triggers, for example Search, Check Search Redirect, Get Blocks, Get Main Page Blocks and 30 more. You combine them in a workflow without code and mix them with every other integration.
How do I connect Blockscout to Collabase?
You open the integrations in the workspace settings, choose Blockscout and connect your account once. After that all triggers and actions are available in the workflow.
Does the Blockscout integration cost extra?
No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.
Test it against your own content. A proof of concept is ready within days.
We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.
