Morpho Blue Supply logo

Catalog action EVM Onchain wallet Gas

Lend loan token into a Morpho Blue market to earn borrow APY. Automatically approves the loan token to the Morpho singleton. Supports slippage protection via slippageBps. Supports Ethereum (1), Optimism (10), Polygon (137), Base (8453), Arbitrum (42161). Ideal for: yield farming, earning lending interest, DeFi deposits, automated savings.

This action can require a wallet connector, gas, token movement, or an external side effect. Test with simulation or a controlled amount before using it in a live workflow.

At a Glance

FieldValue
Action IDmorpho-blue-supply
CategoryEVM Onchain
Connectorwallet
Requires gasYes
Funds movementNone declared
Tagsmorpho, morpho-blue, lending, supply, write, defi, yield

Payload Schema

FieldTypeRequiredDescription
marketIdstringYesMorpho Blue market ID (bytes32 hex)
chainIdnumberYesChain ID. Supported: Ethereum (1), Optimism (10), Polygon (137), Base (8453), Arbitrum (42161)
amountstringYesAmount of loan token to supply in smallest unit (wei). E.g. "1000000" = 1 USDC.
slippageBpsintegerNoSlippage tolerance in basis points (1 bp = 0.01%). Default: 100 (1%). Protects against share-price drift between preview and execution.
gasLimitstringNoOptional gas limit as a positive integer string (e.g., "300000")

Result Schema

FieldTypeRequiredDescription
statusstringYes-
transactionHashstringYes-
transactionUrlstringNoBlock explorer URL for the transaction (e.g. https://basescan.org/tx/0x...\)
blockNumbernumberNo-
estimatedSharesReceivedstringNoEstimated supply shares received (preview taken before broadcast)
estimatedSharesReceivedFormattedstringNoHuman-readable estimated supply shares received

Examples

json
{ "type": "morpho-blue-supply", "payload": { "marketId": "example-marketId", "chainId": 1, "amount": "1000000" }, "children": [], "connector": { "type": "wallet", "id": "conn_wallet" }}

Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.

Ask a question... ⌘I