ChainLinkAgents

Chainlink CCIP community node for BizFirst.Ai — build cross-chain messages, track their delivery, and read Router/Lane state as workflow steps.

What it does: The Chainlink node (chainlink) wraps Chainlink's CCIP (Cross-Chain Interoperability Protocol) as BizFirst.Ai workflow operations across three resources — message, router, and lane — 11 operations in total. This is CCIP only, not Chainlink Data Feeds. No operation holds a wallet or signs a transaction — sending a built message (ccipSend(...)) is a separate step on the Ethereum ExecutionNode.

Get Started

Full Guide

11-page reference — configuration, networks, every resource's operations, CCIP concepts, examples, troubleshooting.

Source Code

Browse the full C# implementation — Domain, Services, and Executor projects.

GitHub Repo

Star it, file an issue, or open a PR.

Operations at a Glance

Resource	Operations
`message`	`build`, `getStatus`, `checkManualExecutionRequired`, `getTokenTransferRateLimit`
`router`	`getAddress`, `isChainSupported`, `getFee`, `convertChainSelector`
`lane`	`getSupportedLanes`, `getLatency`, `getRiskManagementStatus`

Full field-by-field reference for every operation: see the Full Guide.

Only two operations need an RPC URL: router/isChainSupported and router/getFee make a real, independent on-chain read and require Chainlink:NetworkRpcUrls:{network} to be configured. Every other operation is either pure local computation (message/build) or calls the free, public CCIP API v2 (api.ccip.chain.link/v2) — no wallet, signing key, or SDK required anywhere.

Configuration & Networks

Chainlink:BaseUrl defaults to the real public CCIP API and rarely needs overriding. Chainlink:NetworkRpcUrls is required only for the two on-chain-read operations above. The bundled per-network reference table covers ethereum-mainnet, arbitrum-mainnet, and base-mainnet — only Ethereum mainnet's chain selector is independently confirmed; the other selectors and all three Router contract addresses are placeholders pending a live CCIP Directory pull. An optional CCIP API key (an API_KEY-type vault credential) raises rate-limit headroom but isn't required for any implemented operation.

Roadmap

checkManualExecutionRequired only reports eligibility today — actually submitting a manual execution needs a confirmed authorization/calldata shape. getTokenTransferRateLimit returns a prepared call descriptor rather than a resolved value, since no on-chain rate-limiter ABI was confirmed during design review. Live CCIP Directory integration (replacing the static reference table) is also planned. Two originally-designed operations — get message by transaction, list messages by address — were cut entirely, as no real CCIP API endpoint was found to back either.

About BizFirst.Ai

BizFirst.Ai is a workflow automation platform for building AI-driven business processes. This node is one of many community connectors that plug into its ProcessEngine — browse the full node catalogue and developer guides at docs.bizfirstai.com, or join the discussion at community.bizfirstai.com.