Opinion → Polymarket Hedge + Telegram

Who is this for?

This workflow is for users who want to buy YES on Opinion’s BTC 1-hour up/down market and, as soon as that order fills, automatically hedge by buying NO for the same amount on Polymarket’s matching 1h BTC up/down market, and get a Telegram notification. No Polymarket market slug is configured—it is derived from the current 1h window so it always matches the Opinion market.

What problem is this workflow solving? / Use case

• You want to hedge an Opinion YES position by buying NO on Polymarket for the same 1h window.
• You want the hedge and notification to run as soon as the Opinion order fills, without pasting market slugs or configuring two markets manually.

What this workflow does

1. Starts when you trigger the workflow and submit the config (order amount in USD, Opinion credentials, Polymarket credentials, and optional Telegram credentials).
2. Finds the current BTC 1h up/down market on Opinion.
3. Places a YES buy order at best bid on that market. The workflow asks you to sign in your wallet (EIP-712). The order is then submitted and the workflow waits for it to fill.
4. When the Opinion order fills:
   • It derives the Polymarket market slug for the same 1h window (e.g. bitcoin-up-or-down-february-12-9am-et for the 10AM ET expiry window). No config input is used for the slug.
   • It builds a NO market buy order on Polymarket for the same USD amount, asks you to sign that order in your wallet, then submits it.
   • If you added Telegram credentials, it sends a Telegram message with the fill and hedge details.
5. Stops after the hedge and notification (one run per fill).

When it runs / stops

• Runs: Repeats internally until the Opinion YES order fills in the current window; then it runs the Polymarket hedge and Telegram once and stops.
• Stops: After the hedge and notification complete, or when you stop or remove the workflow, or the workflow engine restarts. If the Opinion order does not fill before the window ends, the workflow will try again in the next window.

Setup

1. Opinion credentials: In the config node, attach your Opinion credentials (API key, EOA address, Opinion account address). The EOA is the wallet you will use to sign the Opinion order when prompted.
2. Polymarket credentials: Attach your Polymarket credentials (API key, secret, passphrase, address). The workflow will look up your proxy wallet and use your address to sign the Polymarket NO order when prompted.
3. Order amount (USD): The amount in dollars to use for both the Opinion YES order and the Polymarket NO order (e.g. 15).
4. Telegram credentials (optional): Attach Telegram credentials if you want a notification when the Opinion order fills and the Polymarket hedge is placed.
5. Start: Trigger the workflow. When the Opinion YES order fills, you will be prompted to sign the Polymarket NO order; after you sign, the hedge is submitted and (if configured) Telegram is notified.

Key Features

• No market slug config: The Polymarket market is derived from the current 1h window (ET), so it always matches the Opinion market.
• Same amount: The Polymarket NO order uses the same USD amount as the Opinion YES order.
• Wallet signing for both Opinion and Polymarket (no private keys in the workflow).
• Telegram notification when the hedge runs, if Telegram credentials are set.

Nodes in Use

• User configuration: Collects order amount (USD), Opinion credentials, Polymarket credentials, and optional Telegram credentials.
• Opinion: Find the current BTC 1h up/down market and place a YES buy order at best bid after you sign.
• Polymarket: Look up your proxy wallet, build the NO market buy order for the derived market, and submit the order after you sign.
• Human-in-the-loop: Ask you to sign the Opinion order and the Polymarket order in your wallet when each is placed.
• Telegram: Send you a message when the Opinion order fills and the Polymarket hedge is placed (if you provided Telegram credentials).

Reference

• Opinion
• Polymarket
• Telegram