Test your setup
Check connection messaging, then send and verify one TradingView trade on your demo account.
This test works the same whether your account runs on PineConnector Edge or on your own PC or VPS. First check connection messaging, then follow one demo order from TradingView to the broker.
Before you start:
- A connected demo account and the License ID you copied in Connect MT5.
- A TradingView plan with webhooks, and two-factor authentication enabled. TradingView needs both before it will send a webhook alert.
1. Check connection messaging
Section titled “1. Check connection messaging”Signal Authentication enabled? This tool cannot include your secret. Keep authentication enabled and skip to the authenticated TradingView demo message instead.
Otherwise, paste your License ID, review the fixed LicenseID,test,test message and select Send connection test once.
Send a connection test
Check the connection using the fixed message below.
Find the intended ID in Portal → Connections. Check every account using it. This widget does not save what you enter.
- Destination
https://webhook.pineconnector.com- Message
LicenseID,test,test
A connection check, not a broker trade. Your License ID is sent only when you press Send.
Then open Portal → Bridge and find the matching test by time and account. Open its details and inspect the processing result: In Progress is still pending; Success is the processing checkpoint. If it reports an error, resolve that result before continuing. A browser “sent” or “accepted” response alone does not confirm that the terminal processed it. If the browser cannot confirm delivery, check Bridge before trying again. To investigate, use Missing signals or EA Errors.
This check does not place a trade or test TradingView. If you use Send Test Signal in Portal instead, check its selected account first; if its result is unconfirmed, follow the Edge test-signal checks before resending, because a test that requests an order can create a duplicate trade.
2. Prepare the demo message
Section titled “2. Prepare the demo message”
Check that 0.01 lots is permitted for that symbol and that its trading session is open now. For a shared ID, check the exact symbol and permitted volume on every recipient. If EURUSD is closed, wait or use another open demo instrument whose exact name and permitted size you have checked.
Start with a clear demo setup. Use a symbol with no existing positions or other active automation on every recipient. Reusing a setup? Check Pyramiding and Close on Reverse first: existing positions can change what this buy request does. Do not close unrelated positions just to run this test.
This message requests a buy of 0.01 lots on EURUSD, without SL or TP. Replace the License ID and broker symbol. Change 0.01 only if your demo account requires a different permitted volume.
Choose one message. If Signal Authentication is enabled, use Demo buy with authentication below; otherwise use Demo buy message. For the authenticated message, replace YOUR_SECRET privately in TradingView; never type the secret into this page’s License ID field or connection-test tool.
3. Create the TradingView alert
Section titled “3. Create the TradingView alert”Open the alert editor
Section titled “Open the alert editor”- Open a normal price chart receiving live, positive quotes, such as a liquid BTCUSD chart.
- Select the Alerts alarm-clock icon in the right-hand toolbar.
- Select + or Create alert. You can also use AltA on Windows or OptionA on Mac.

The chart only triggers the alert; the message decides the order symbol. A BTCUSD chart can trigger the EURUSD message above, so keep your broker symbol in the message. You need both live chart quotes and an open broker session for the demo order to complete.
Settings: Greater Than 0, only once
Section titled “Settings: Greater Than 0, only once”| Field | Value for this test |
|---|---|
| Condition | Price |
| Operator | Greater Than |
| Value | 0 |
| Trigger | Only Once; some layouts call this Once only |

A positive price is already above 0, so the alert should fire on the next eligible price update. That is not a guarantee of an instant result: no incoming quote, a closed chart session or delivery delays can hold it up. Do not use Crossing, which waits for price to cross the level. See TradingView’s alert operators and one-time frequency.
Message: paste the reviewed buy instruction
Section titled “Message: paste the reviewed buy instruction”- Open Message. Depending on your TradingView layout, this is a tab or a button opening Edit message.
- Name the alert Demo trade test so you can find it later.
- Paste your complete reviewed buy message into Message.
- If the editor has an Apply button, select it to return to the alert settings.

Read it once more: correct License ID → buy → exact broker symbol → intended volume, plus your secret only if authentication is enabled.
Notifications: enable the webhook
Section titled “Notifications: enable the webhook”Open Notifications, tick Webhook URL, and paste this address:
https://webhook.pineconnector.comThe webhook goes in Notifications; the trading instruction stays in Message.

Select Apply if your layout uses it.
Review and create
Section titled “Review and create”Recheck the demo account, exact message, Greater Than 0, Only Once and webhook URL. Then select Create once.
Keep one trade-test alert active. Do not create copies while waiting for a result; a later trigger could produce extra orders.
4. Verify and finish
Section titled “4. Verify and finish”TradingView: check the Alerts log
Section titled “TradingView: check the Alerts log”Open Alerts → Log and find Demo trade test. Confirm its time and the actual message that fired.

Stopped — Triggered is the expected state for a one-time alert after it fires. No event yet? Check that the chart has live positive quotes and that the operator and trigger are correct. Selecting Create does not, by itself, send the message.
Bridge: confirm processing
Section titled “Bridge: confirm processing”- Open PineConnector Portal → Bridge.
- Find the new entry using the alert time and intended account.
- Open its details and compare the message, symbol, action and processing result.

A processing record shows PineConnector handled the message; it is not a broker fill. If the message is missing or rejected, follow Missing signals or the matching EA error.
Broker: confirm the trade
Section titled “Broker: confirm the trade”Open the same broker account in its MT5 mobile app, web terminal or desktop terminal, and open its Trade/positions view. On desktop MT5, the Trade tab is in the lower Toolbox panel.
| Check | Expected for the unchanged example |
|---|---|
| Account | Every intended demo account connected to the selected ID. |
| Symbol | The exact broker symbol you put in the message. |
| Direction | Buy. |
| Volume | 0.01 lots, unless you deliberately changed it to a permitted value. |
| SL / TP | None from this test message. |
| Duplicates | No unexpected additional order. |

Order missing? Read Experts and Journal at the matching time: on Edge, select your instance in Portal → Edge to read both logs in your browser; on your own terminal, open those tabs in MT5.
Before retrying, check the account’s positions and history for an existing order. A delayed notification is not proof that the first request failed.
Finish the test
Section titled “Finish the test”Close the test position on every intended demo recipient through its broker interface, then disable or delete the temporary TradingView alert.
Optional reference
Section titled “Optional reference”Additional checks
Can I send the connection-test message from TradingView instead?
Yes. Follow the same one-time alert procedure above, using the message below instead of the buy message. Name it Connection test.
If Signal Authentication is enabled, append your configured ,secret=YOUR_SECRET and replace YOUR_SECRET privately in TradingView. Keep it out of the docs fields.
Match the event in TradingView and Bridge, inspect the processing result, then remove the temporary alert. This checks message delivery from TradingView; it does not verify a broker order.
Link to this answer

