Your first alert.
A paper fill on your Mac.

If macOS refuses to open the app, use a fresh download from BridgePit and keep the exact error for support. There can be several causes; a chat download is not the only one.

Forgot your password? Use Forgot it? on the password screen and follow the local recovery instructions. There is no recovery email.

Port 8787 already in use? Quit an older BridgePit through its own Settings if one is running. Otherwise contact support with the error; do not close an unidentified program or change ports by guesswork.

In Strategies → Instruments → + Add instrument, search for it and select the matching result. Check TradingView symbol, Contract root and Exchange, then press Save and select it in your strategy.

Use the contract root without a month or year, such as MNQ. BridgePit resolves the current contract. If the instrument is not in the search results, confirm its mapping and broker support before adding it manually.

Open Settings → Alert setup, select your strategy and use Send a test signal. Review any pause or safety message it shows.

This is a local check. It does not prove that TradingView or your public address works. Continue below for that.

For BridgePit 1.4.19, or if assisted setup is unavailable, open the manual setup area under Your public address (the commands are shown directly in older versions). Review any existing Tailscale Serve/Funnel configuration first; a Funnel command can replace a route or make other routes on that port public. Copy the command shown by BridgePit into Terminal and run it. It normally reads tailscale funnel --bg 8787. Follow any Tailscale approval link, then run it again. Paste the returned HTTPS address into Your public address and press Save; BridgePit adds /webhook. Use Check the path before continuing.

If Terminal cannot find tailscale, try the bundled command below, using the port shown in BridgePit:

/Applications/Tailscale.app/Contents/MacOS/Tailscale funnel --bg 8787

Funnel needs MagicDNS, HTTPS and Funnel permission in your Tailscale network. Follow its approval prompts; a managed network may require its administrator. For version-specific macOS prompts, use Tailscale's system-extension instructions.

tailscale funnel status reports the saved serving configuration. BridgePit's Check the path also tests reachability; a connected Tailscale app alone does not prove it.

Copy block in the app is the normal route. It fills your strategy name and token. This example is for reference only; its name and token are placeholders.

{
  "strategy_name": "YourStrategyName",
  "data": "{{strategy.order.action}}",
  "quantity": "{{strategy.order.contracts}}",
  "price": "{{close}}",
  "bar_time": "{{time}}",
  "fired_at": "{{timenow}}",
  "token": "YOUR-TOKEN"
}

Two clocks, two jobs: bar_time identifies the bar for duplicate checks; fired_at checks entry freshness. Preserve both placeholders. Keep your token private. Never add broker credentials to the alert.

The app's strategy name need not be the TradingView script title: the copied message must match the name saved in BridgePit. The instrument and account are selected in BridgePit, not taken from the chart. BridgePit submits market orders.

Moving from PickMyTrade requires your new BridgePit URL and message. The compatible BridgePit path /v2/add-trade-data does not transfer a PickMyTrade hostname or make its old message compatible.

A quiet strategy or closed market can leave you waiting; this guide cannot promise a fixed completion time. For a separate public-path test, BridgePit has Settings → Your public address → Send a test alert the long way round. It starts from this Mac, not TradingView, and is not proof of your TradingView configuration.

If TradingView has no event, check the strategy, market hours and alert expiration there. If it has an event but delivery failed, check the webhook URL and path. If BridgePit has a rejection, use that reason below. An HTTP delivery success alone does not prove a paper fill.