Skip to main content
This article is for educational purposes only and does not constitute financial advice. Trading involves risk of loss. Past performance does not guarantee future results. Consult a licensed financial advisor before making investment decisions.
Getting Started4 min readUpdated October 24, 2026
TW

Choose how Tradewink signals reach your tools

Choose dashboard, email, Discord, workflow integrations, webhooks, or API access. Test delivery before adding any execution step.

The idea, illustrated

Explore the ideas visually

Step through the key sections, then read the complete guide below.

Evidence & contextConcept model
Concept illustration, not market data. The steps use excerpts from this article; the diagram shows the broader topic.
1 / 4

Step 1 of 4: Pick the route that fits your workflow. Paused.

Put this into practice with a watchlist

Build a watchlist, then review each signal’s entry, stop, target, and reasoning. Broker access is optional.

Starter watchlist: SPY, QQQ, AAPL.

Starter examples. Not recommendations; you can edit them before anything is saved.

Public subscriptions are paper-only. Live beta enrolment, copy-trading expansion, and live MCP orders are frozen; a paid plan does not unlock them.

Track these tickers free

Tradewink signal delivery: A delivered alert is a notification, not an executed broker order.

Start with the destination you actually check. A signal is useful only when you can find it, understand it, and make a deliberate decision.

New to the format? Inspect a public recorded signal first. You can read its reasoning and timestamp without connecting a broker or configuring a delivery tool. Then choose one destination and verify receipt there.

Pick the route that fits your workflow

RouteUse it forWhere to start
DashboardRead full context and keep private reviewsSignals
EmailRead digests and account noticesNotification settings
DiscordReceive bot messages in your existing workflowDiscord setup
Slack or Microsoft TeamsRoute ideas to a workspace channelIntegrations
Zapier, Make, n8n, or IFTTTForward or transform signals in your own workflowIntegrations
ntfyReceive notifications through your own ntfy topicIntegrations
Signed webhookDeliver a JSON payload to your serverWebhooks
TradingView-format webhookSend an alert-shaped payload to a compatible receiverTradingView delivery
REST APIFetch signal records in your applicationAPI keys

Check the live availability and plan requirement in the dashboard before setup. The current roster marks Slack, Teams, workflow destinations, ntfy, and signed webhooks as Starter or higher; REST signal access requires Pro or Elite. Email frequency and signal eligibility depend on your account and preferences. The Free sampler can be delayed. Telegram is currently disabled in the roster, and SMS is not an advertised delivery option.

Connect and test one destination

  1. Open Integrations, pick an available destination, and follow its provider-specific setup steps.
  2. Create the receiver in that provider first. For example, create a Catch Hook in Zapier or a production Webhook node in n8n, then use that URL in the destination form.
  3. Save the destination and use its test action where offered. For email or Discord, verify the account/link and check receipt through the supported flow.
  4. Inspect the receiving tool. Confirm the correct channel or workflow received the payload and that you can trace it back to the original signal.
  5. Start with logging or review. Add a broker step only as a separate project after validating the full chain in paper mode.

Treat webhook URLs, feed URLs containing access keys, and destination secrets as credentials. Keep them out of screenshots, public repositories, and AI prompts.

Understand the direction of delivery

Tradewink → your destination → your own workflow → optional broker integration.

TradingView-format delivery means Tradewink sends a compatible payload to a receiver. It does not imply a direct Alpaca connection or automatic placement on a TradingView chart. A receiver such as a third-party automation service has its own account requirements, configuration, and fees. Check its current documentation for the exact payload mapping before using it.

Put the setup on a watchlist first

Use the rules in this guide to evaluate a signal’s entry, stop, target, and reasoning before deciding what, if anything, to do.

Starter watchlist: SPY, QQQ, AAPL.

Starter examples. Not recommendations; you can edit them before anything is saved.

Public subscriptions are paper-only. Live beta enrolment, copy-trading expansion, and live MCP orders are frozen; a paid plan does not unlock them.

Track these tickers free

Before a workflow can submit orders

For a custom receiver, verify signatures where provided, reject stale data, validate required fields, and persist a deduplication record using the signal ID. Treat retries as repeated delivery of the same idea, not fresh permission to trade.

Map the instrument and side explicitly. Apply your own account and size limits, ask for approval, and use a paper broker account while testing. Preserve the signal ID alongside the broker order ID. After submission, reconcile fills and failures from the broker.

Check recorded delivery, not just configuration

Open Settings. The account setup area distinguishes Signal delivery recorded, Delivery prerequisites need attention, and Awaiting the first recorded signal delivery. Check its evaluation age and plan delay. A saved destination, linked account, or completed preference form is not a signal delivery receipt.

A provider accepting a request establishes only that provider event. Inspect the receiving channel or workflow separately before saying a recipient received it. A test message is not evidence that a later eligible signal arrived. An unavailable status is missing evidence; it is not success. No new signal is guaranteed for a chosen stock.

If nothing arrives

Check the destination is enabled, the plan allows it, and the configured receiver is active. Then compare the dashboard signal and its eligibility with the destination history. Watchlist, preferences, limits, and plan delay can affect delivery. A successful test does not mean every future signal will qualify.

For direct programmatic retrieval, continue with the AI and API guide. For interpreting the idea itself, start with your first signal.

Educational information only. Delivery is not a broker order, and neither delivery nor automation guarantees trading results.

Tradewink signal delivery: practical checks

Compare the event timestamp, generation timestamp and delivery receipt. Check a test alert on the channel you intend to use; an email or webhook receipt cannot establish an entry price or a broker fill.

Read the Alpaca paper trading limitations for the underlying definitions and limits. For a next step, use Missed Trading Alerts: Reconcile the Exit Event Chain and I received a trading signal. What do I do next?.

Frequently Asked Questions

Will connecting Zapier place trades?

No. Delivery sends a payload to your workflow. Broker authentication, validation, approval, order submission, and reconciliation must be configured separately.

Is Telegram currently available?

Telegram is disabled in the current published integration roster. Use the availability shown in your dashboard; do not plan around an inactive channel.

Can I send directly into TradingView charts?

The integration sends TradingView-format webhook payloads to a compatible receiver. It is not a promise to inject signals into a TradingView chart.

Does a successful destination test prove execution?

No. It proves at most that the test reached the destination. Verify the downstream workflow and broker records separately.

Why did an alert arrive later than expected?

Check the plan delay, preferences, watched symbols, delivery settings, and destination status. Generation and receipt timestamps are different.

Keep learning with a related guide before putting an idea on your watchlist.

Try AI signals on your watchlist

Send yourself a signal preview, then add tickers to see ranked entries, exits, and risk notes in Tradewink.

Enter the email address where you want to receive a Tradewink AI signal preview.

Sources cited in this guide

TW

Tradewink builds explainable AI trading signals for US stocks and ETFs. Build a watchlist, see what Winkie rejected and why, and paper-track ideas before you decide. Public subscriptions are paper-only. Live beta enrolment, copy-trading expansion, and live MCP orders are frozen; a paid plan does not unlock them.

How we write, source, and correct guides

How this guide is reviewed

Tradewink reviews educational content against its documented market-data sources, risk controls, and product methodology. See our data sources and evaluation methodology for the evidence and limitations behind the platform, and our editorial standards for how guides are sourced, dated, and corrected.

Comments

Comments are reader opinions, not investment advice. A moderator reviews your first comment before it appears, and moderators can remove any comment later.

Loading comments…

Important disclosures

Informational purposes only

Tradewink is published by Tradewink LLC, which is not a registered investment adviser, broker-dealer, commodity trading advisor, or financial planner. All data, signals, and analytics on this page are general, impersonal, and for informational purposes only. They do not constitute investment advice, financial advice, or a recommendation to buy or sell any security or other instrument.

Trading risk

Past performance does not guarantee future results. Trading involves substantial risk of loss, including the possibility of losing more than your initial investment. You are solely responsible for your own trading decisions.