Transaction Lookup

PolygonScan indexes every transaction on the Polygon network by hash, block, and status. When a workflow references a payment or transfer, an agent looks the hash up, reads whether it is pending, confirmed, or failed, and applies your rule, such as marking an order paid once confirmations pass a set count. It records that state where the connector allows and notifies the owner when a transaction stalls or reverts. Anything that looks inconsistent, like a mismatched amount or an unexpected recipient, is routed to a person before any status change is committed.

Address & Balance Queries

Address pages on PolygonScan show a wallet's MATIC balance, token holdings, and transfer history. An agent queries an address on a trigger, reads the current balance and recent activity, and follows an approved rule, for example confirming that funds arrived before releasing a next step. It updates the associated record or posts a summary where account permissions allow. Balances that fall short, wallets with unfamiliar token movements, or activity outside expected patterns are flagged and handed to a person, so releases never proceed on an address the agent cannot confirm.

Contract Event Tracking

Smart contracts on Polygon emit events that PolygonScan records and exposes for inspection. An agent watches a named contract, reads new events as they appear, and applies your rule, such as recording a mint or transfer into an internal ledger. It notifies the responsible team when an expected event is late or absent. Events with unusual parameters, or contracts the agent has not been cleared to interpret, are set aside for a human, keeping automated bookkeeping tied to activity that a person has already deemed safe to act on.