Choose how Tradewink signals reach your tools
Choose dashboard, email, Discord, workflow integrations, webhooks, or API access. Test delivery before adding any execution step.
Put this into practice with a watchlist
Build a watchlist, then review each signal’s entry, stop, target, and reasoning. Broker access is optional.
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
| Route | Use it for | Where to start |
|---|---|---|
| Dashboard | Read full context and keep private reviews | Signals |
| Read digests and account notices | Notification settings | |
| Discord | Receive bot messages in your existing workflow | Discord setup |
| Slack or Microsoft Teams | Route ideas to a workspace channel | Integrations |
| Zapier, Make, n8n, or IFTTT | Forward or transform signals in your own workflow | Integrations |
| ntfy | Receive notifications through your own ntfy topic | Integrations |
| Signed webhook | Deliver a JSON payload to your server | Webhooks |
| TradingView-format webhook | Send an alert-shaped payload to a compatible receiver | TradingView delivery |
| REST API | Fetch signal records in your application | API 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
- Open Integrations, pick an available destination, and follow its provider-specific setup steps.
- 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.
- 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.
- Inspect the receiving tool. Confirm the correct channel or workflow received the payload and that you can trace it back to the original signal.
- 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.
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.
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.
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.
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.
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.
Read next
Keep learning with a related guide before putting an idea on your watchlist.
I received a trading signal. What do I do next?
A practical first-signal checklist: understand the setup, check freshness, choose paper practice or skip, and distinguish delivery from a fill.
Use Tradewink with Claude, Codex, and the signals API
Connect an AI assistant through MCP, retrieve signal records through the API, and use a preview-first workflow with explicit order approval.
How to practice a Tradewink signal with Alpaca
Translate a stock signal into an Alpaca paper order, check the account and ticket, and verify order status without confusing a signal with a fill.
Ready to evaluate a signal?
Start free with a watchlist and inspect the context before you consider a broker connection.
Try AI signals on your watchlist
Send yourself a signal preview, then add tickers to see ranked entries, exits, and risk notes in Tradewink.
Key Terms
Tradewink builds explainable market research for self-directed traders. Build a watchlist, inspect signal reasoning and risk context, and paper-track ideas before you decide. Public subscriptions are paper-only; separately approved private beta accounts may submit live broker orders.
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.