TradingView options automation needs an explicit contract, opening or closing intent, quantity and exit association. A bullish or bearish chart signal does not supply those decisions automatically. Identify the option the broker will trade, confirm the action it will receive, and establish how later exits will reach that same position.
Table of Contents
- Key takeaways
- Before setup: is the selected connector ready for this workflow?
- Which contract fields must TradingView options automation define?
- Why is buying a put different from selling an option?
- How should you select strike and expiration?
- Can the signal chart differ from the traded option?
- How do you make exits close the contract you opened?
- How should stops, targets and planned risk be expressed?
- What happens if only part of the order fills?
- Do multiple exits mean multi-leg spreads are supported?
- Worked example: close a long put without selecting a new option
- Troubleshooting contract, action and exit mismatches
- What should you test before enabling options automation?
- What happens near expiration or assignment?
- Frequently asked questions
- Write the complete option instruction before sending the alert
A common mistake is treating “bearish” as a Sell instruction. Buying a put can express a bearish view while creating a long option position. Selling an option can close a long position or open a short obligation. Choosing call or put and choosing buy or sell are separate decisions.
This guide develops a contract-first workflow for PickMyTrade.io, using its IBKR and Tradier documentation with broker and Options Industry Council references. Examples are hypothetical; they do not represent tested orders, listed-contract recommendations or a universal payload for every connector.
Key takeaways
- Record underlying, option type, strike, expiry and broker contract identity.
- Distinguish buy/sell from opening/closing intent.
- Confirm dynamic selection against the actual listed option chain.
- Bind exits to the position opened, not a newly selected ATM contract.
- Treat partial exits and multi-leg orders as separate capabilities; verify fills and remaining exposure.
Before setup: is the selected connector ready for this workflow?
Proceed to controlled testing only when the contract resolver, action mapping and close scope are documented for your selected route. This article explains the decisions; it does not certify a universal options payload. Use the following checkpoints to distinguish a complete plan from one that still needs product clarification.
| Checkpoint | Ready for testing when | Pause setup when |
|---|---|---|
| Contract selection | The broker recognizes the resolved contract and its terms | Strike, expiry or symbol is guessed or unavailable |
| Opening/closing action | The generated instruction has a confirmed broker-level meaning | A Sell label conflicts with a buy-put example |
| Exit association | The close identifies the held contract and remaining quantity | The exit merely reruns a dynamic entry selector |
| Protection | Units, order type and update owner are defined | An underlying price is being used as an option-premium price |
| Several legs | The supported submission and recovery process is documented | Separate messages are assumed to create an atomic spread |
Which contract fields must TradingView options automation define?
An underlying ticker identifies a family of options, not one executable contract. Call/put, strike and expiration narrow the selection, while broker identifiers and contract terms establish the actual instrument. Record the resolved contract at entry so later instructions can be checked against the position held in the account.
| Field | What to establish |
|---|---|
| Signal source | Chart symbol, script, timeframe and event producing the instruction |
| Underlying | The asset on which the selected option is based |
| Option type | Call or put |
| Strike | Actual listed exercise price, not a guessed rounded value |
| Expiration | Actual listed expiration date for the intended series |
| Broker identity | Broker-recognized option symbol or qualified contract identifier |
| Contract terms | Multiplier, deliverable, currency, trading class or exchange where applicable |
| Account and environment | Destination account, paper/live environment and options permissions |
PickMyTrade’s Settings guide describes broker symbol and instrument configuration. Use the selected connector’s definitions for lot size and tick settings. Do not assume a field named “lot size” means the same thing as order quantity or option deliverable in every setup.
Check standard versus adjusted contracts. The OIC glossary explains that corporate actions can alter contract terms, including deliverables and multipliers. Two contracts with similar displayed names may not represent the same exposure. Verify the complete broker description before enabling a new mapping.
Why is buying a put different from selling an option?
A put identifies the option’s rights; buy and sell describe transactions. Opening and closing specify whether the transaction establishes or reduces exposure. Tradier’s order definitions distinguish buy-to-open, sell-to-open, buy-to-close and sell-to-close. Use those broker outcomes to verify what an integration’s simpler action field actually produces.
| Intended outcome | Broker-level intent | Result if fully executed as intended |
|---|---|---|
| Purchase a call | Buy to open call | Long call |
| Purchase a put | Buy to open put | Long put |
| Exit a purchased call or put | Sell to close the same contract | Long position reduced or closed |
| Write an option | Sell to open call or put | Short option obligation |
| Exit a written option | Buy to close the same contract | Short position reduced or closed |
These are broker-level meanings, not literal PickMyTrade JSON values. Use the payload generated for your route and verify its translation at the broker. A generic sell field should not be chosen solely because the underlying signal is bearish. Check the contract type, action and resulting position together.
Documentation discrepancy: the IBKR options guide and Tradier indicator guide contain Sell rows described as opening short exposure while illustrating buying a put. Those are different intentions. Resolve the actual connector mapping before relying on either example; this article does not infer an execution rule from the inconsistent wording.
How should you select strike and expiration?
Choose from contracts actually listed and eligible in the broker’s chain. If a rule selects ATM, ITM, OTM or an offset, inspect what it resolves to when the signal fires. A number produced by rounding the underlying price is not evidence that a contract with that strike and expiration exists.
Offset fields need a documented unit. “One strike away” can mean a step in the available chain, while a dollar offset is a price distance. Those are not interchangeable. Ask how the connector handles gaps in strike spacing, ties around ATM, unavailable contracts and adjusted series. Verify representative resolved results before running unattended.
Relative expiry labels also require verification. “Next day” might encounter a weekend, holiday or a date with no listed expiry for the product. Confirm how the selected connector resolves that case, including its reference date and timezone. Document the supported fallback, or treat the selection as unavailable.
The public setup guides include arithmetic strike illustrations and dated expiry tables. Treat those as explanations of controls, not authoritative option-chain listings or a current calendar. The broker’s actual contract description is the relevant evidence for the order you are about to submit.
Can the signal chart differ from the traded option?
Yes, in a specifically supported mapping workflow. But document the source and destination separately. PickMyTrade’s IBKR indicator options guide describes mapping a signal from one option contract to another configured option. That example does not establish arbitrary cross-asset conversion or automatic translation of price levels between unrelated instruments.
If a workflow permits an underlying-stock signal to trigger an option, confirm that support for the selected connector. The stock price and option premium use different scales. An AAPL-chart stop at 210 cannot be pasted into an option-premium stop field simply because the option is based on AAPL.
For an underlying-price exit, the strategy may instead need to send a supported close event when the underlying condition occurs. That is different from placing a broker-held option-premium stop. Identify which component watches the condition, what happens if it stops running, and what protection remains at the broker.
How do you make exits close the contract you opened?
Bind the exit to the actual entry contract and remaining quantity. A dynamic entry selector can resolve to a different strike or expiry later. Re-running “ATM, next expiry” at exit time is not inherently a request to close the earlier position. Confirm how the connector associates closes with existing trades.
| Entry-time record | Why the exit needs it |
|---|---|
| Account and broker contract identity | Prevents selecting a different account or option series |
| Call/put, strike and expiry | Provides a readable cross-check against the held position |
| Filled quantity and later partial exits | Determines the remaining exposure to close |
| Entry/order reference or supported grouping | Associates an exit with the intended trade where the route supports it |
| Working protective orders | Allows inspection of cancellation, modification and remaining protection |
A generic Close command can have broader scope than one strategy entry. Establish whether it closes a specific contract, matching group, symbol position or another documented scope. When several strategies share an account, do not assume a strategy name or comment creates broker-level isolation. Confirm the route before combining positions.
After any exit, inspect both position and working orders. A long option may be flat while an old sell order remains active. Another entry may still be pending. Treat cancellation, a cancellation request, and confirmed cancellation as different states, particularly when an order might fill during the change.
How should stops, targets and planned risk be expressed?
Specify whether protection uses option premium, a distance from the option entry, percentage change, total position P/L or a signal on the underlying. Then verify units, quantity scope and supported order type. A setting described as dollars can refer to cash risk or price distance depending on the connector’s definition.
For a hypothetical standard equity option with a premium multiplier of 100, buying two contracts at 2.50 costs $500 before fees. A planned exit at 2.00 implies $100 of premium loss before fees and execution differences: (2.50 − 2.00) × 100 × 2. These are illustrative premium prices, not quotes for a specific contract.
The assumption of a 100 multiplier must be checked against the actual contract. OIC’s general options information describes the usual standard equity contract, while adjusted contracts require separate inspection. Do not multiply by 100 twice if the selected integration field already represents a total amount.
A stop is an execution instruction, not a guaranteed loss ceiling. A limit order can remain unfilled, and a triggered exit may execute at a different price or remain pending under its rules. Inspect accepted protection and actual fills. For a long option, a stop-based plan also differs from the premium paid at entry.
In the premium example, the entry debit is $500, while the stop-based price-loss estimate is $100. Those are different budgets. If you use percentage sizing, confirm which amount the connector sizes against and whether it includes fees or execution allowances. A short-option obligation must not be sized as though the premium received were its maximum loss.
What happens if only part of the order fills?
Manage the quantity actually filled, not only the original requested quantity. If a two-contract purchase fills one contract, there can be one long contract and one working entry. Closing the long without resolving the remaining entry can leave a route that opens another position after you believed the trade had ended.
| Order state | Required inspection |
|---|---|
| Entry partially filled | Filled quantity, remaining entry and protection for the filled portion |
| Cancellation requested | Broker acknowledgement and any fill occurring before cancellation completes |
| Exit partially filled | Remaining position and working exit quantity |
| Entry rejected | Whether any other entry or spread leg was accepted |
| Unknown response | Broker orders and positions before any resend |
Check option bid/ask quotes, quote timestamps, supported tick increments and your permitted order type before submission. A market instruction prioritizes execution over price control; a limit constrains price but can remain unfilled. Do not automatically chase, convert or resend an order unless that behavior is part of the supported and tested plan.
Do multiple exits mean multi-leg spreads are supported?
No. Scaling out of one contract position and trading a spread are different capabilities. Selling one of two identical long calls is a partial exit. Opening a vertical involves different contracts. The workflow must define every leg’s identity, side, quantity ratio and relationship, as well as the combined closing process.
PickMyTrade’s options overview advertises multi-leg automation through IBKR and Tradier. That product claim does not supply a complete executable template or establish how a specific connector handles combination orders, partial fills and failures. Obtain the applicable documented workflow before treating a one-leg tutorial as spread instructions.
Tradier’s trading API documentation distinguishes option and multi-leg order classes. Broker capability alone does not prove the integration exposes every order class. Sending separate webhooks for separate legs is not evidence that the broker received a native combination order.
- Submission: one broker-native combination or separate orders?
- Pricing: net debit/credit or independent leg prices?
- Fills: can quantities remain partially executed, and at what ratios?
- Failure: what happens if a leg or the full order is rejected?
- Cancellation: which unfilled orders are cancelled and how is confirmation checked?
- Closing: how does the route identify and close the actual remaining legs?
Worked example: close a long put without selecting a new option
Suppose a permitted workflow uses a bearish underlying signal to buy two puts. The resolver selects contract A: a particular put, strike and expiration, confirmed in the broker chain. Record that actual contract after execution. The entry is a purchase to open, regardless of the bearish direction of the signal.
| Event | Intended instruction | What to verify |
|---|---|---|
| Entry signal | Buy to open 2 of resolved contract A | Correct account, put, strike, expiration, broker ID and fills |
| Underlying moves | No contract change unless the plan explicitly calls for one | A later ATM selection does not replace the recorded entry identity |
| Partial exit | Sell to close 1 of contract A | One contract remains; protection matches remaining size |
| Final exit | Sell to close the remaining 1 of contract A | Position flat for A; no unintended working orders |
| New trade later | Resolve a fresh entry contract under the chosen rule | Separate entry from the prior trade’s closing process |
This is a hypothetical sequence, not a tested PickMyTrade payload or confirmation that every connector supports grouped partial exits. If the supported close command has a different scope, adapt the trading design before execution. Never substitute a newly resolved contract B and assume it offsets contract A.
Troubleshooting contract, action and exit mismatches
| Symptom | First checks |
|---|---|
| Broker reports unknown contract | Actual option chain, expiry, strike, type and complete broker identifier |
| Put purchase becomes an unintended sale | Broker-level side and opening/closing mapping; stop the route until resolved |
| Exit targets a different strike | Whether the close reruns the selector instead of using the held contract |
| Stop price is implausible | Underlying price versus option premium; distance versus absolute level |
| Contract changes around date boundaries | Expiry resolver reference date, timezone and listed-expiry behavior |
| Position reopens after exit | Unfilled entry, duplicate alert or unconfirmed cancellation |
| Spread has unintended exposure | Filled legs, remaining orders and supported recovery workflow |
When the outcome is uncertain, stop unintended new entries and inspect the broker’s current positions and orders. Preserve protection needed for existing exposure. Collect the redacted request, resolved contract, expected action, broker response and order IDs. Do not try to correct a mapping error by repeatedly sending opposite orders.
What should you test before enabling options automation?
Use the broker’s authorized paper or test environment where available. Tradier documents separate production and sandbox endpoints in its trading reference. Confirm the integration’s selected environment too. A successful connection to one environment does not prove live permissions, current data or identical fills in the other.
- Verify options approval and buying power for the intended long, short or spread order.
- Resolve the contract and inspect the full broker description.
- Send a controlled entry and compare action, quantity and order state.
- Verify protection in the broker record rather than only the generated message.
- Test partial and full closes against the contract actually held.
- Test repeats, changed selectors and unavailable strike/expiry outcomes.
- Inspect rejected, partially filled and cancelled orders before retrying.
- Confirm no obsolete alerts or leftover orders can submit another instruction.
Trace events through PickMyTrade’s monitoring workflow and the broker records. If an order response is uncertain, inspect current exposure before resending. Share the selected environment, redacted configuration, resolved contract, timestamp and order IDs with support; remove passwords and tokens.
What happens near expiration or assignment?
Define the plan for positions that remain open near expiration, including broker deadlines and any exercise or assignment consequences. Do not assume an unfilled close order removes exposure. OIC’s assignment FAQ explains that short positions can remain exposed to assignment while open, and broker exercise procedures matter.
An options-only automation route may not manage a stock position created by exercise or assignment. Check the actual contract’s exercise style and settlement terms, the broker’s handling, and the resulting account exposure. Set a deliberate monitoring and closing process rather than treating expiration as a universal automatic flatten command.
Frequently asked questions
PickMyTrade documents options workflows for selected brokers, including IBKR and Tradier. Use the guide for your connector, alert type and instrument. The alert must resolve a supported contract, action, quantity and exit route. A TradingView underlying signal alone does not identify every required option instruction.
Do not choose Sell solely because the signal is bearish. Buying a put is an opening purchase that creates a long option position. Verify how the selected connector translates its generated action into the broker order. Public examples with conflicting labels must be resolved before execution.
Confirm the connector’s close association and scope. A dynamic selector can resolve a different strike or expiration later, so it is insufficient to assume the entry rule also identifies the exit contract. Record the actual held contract and verify the close affects its remaining quantity.
Not directly unless the workflow explicitly supports interpreting the underlying condition. A stock price and an option premium are different values. Use an appropriate premium-based protective order or a supported signal-driven close. Confirm the units and which component monitors the exit condition.
No. A partial exit reduces quantity in an existing position; a multi-leg spread involves distinct contracts and specified ratios. Confirm combination-order support, pricing, partial fills, rejection and closing behavior for the connector. Separate webhooks do not by themselves establish a broker-native spread order.
Write the complete option instruction before sending the alert
For TradingView options automation, define the source signal, resolved contract, opening or closing intent, quantity and exit association together. Use the IBKR options guide or Tradier indicator guide for the selected route, resolve contradictory examples, and verify broker outcomes in controlled tests before depending on the setup.
Disclaimer:
This content is for informational purposes only and does not constitute financial, investment, or trading advice. Trading and investing in financial markets involve risk, and it is possible to lose some or all of your capital. Always perform your own research and consult with a licensed financial advisor before making any trading decisions. The mention of any proprietary trading firms, brokers, does not constitute an endorsement or partnership. Ensure you understand all terms, conditions, and compliance requirements of the firms and platforms you use.
Also Checkout: How to Test TradingView Automation Safely Before Going Live
Connect your alerts with PickMyTrade — automated trade execution, no coding required. Start free →