Can Zapier trigger a real trade on my exchange through Autoview?

Yes. Zapier's Webhooks by Zapier action can POST your Autoview command to your webhook from any Zap, so almost anything Zapier can trigger on (a spreadsheet row, an RSS item, an email, another app's event) can end in a real order.

Does Zapier's free plan support this?

No. Webhooks by Zapier is a premium action, not available on Zapier's Free plan. You need at least a Starter or Professional plan to add a webhook step to a Zap.

Which Webhooks by Zapier event should I use?

Custom Request. The plain POST and PUT events parse your Data fields into a structured payload like {"symbol": "...", "side": "..."}, which Autoview rejects; Custom Request lets you set the request body yourself, either the raw command string or the command wrapped as {"alert": "..."} JSON, both of which Autoview accepts.

Connect Zapier to Autoview

Q: Can I test a Zapier-triggered command before it trades real money?

Yes. Append d=1 to the command in your webhook step and Autoview logs the order it would have placed without sending it to the exchange. Remove the flag once a test run in your Zap history looks right.

Autoview · Signal source · Updated September 12, 2026

Zapier connects thousands of apps into no-code automations called Zaps: a trigger in one app, one or more actions in others. Your trading signal doesn't have to come from a trading platform at all. A new row in a Google Sheet, an RSS item, a Slack message, an email matching a filter, anything Zapier can trigger on can end with a real order on your exchange.

What Zapier is and who automates trades with it

Zapier is built for people who want to connect apps without writing code. For trading, that means the signal source can be anything Zapier already integrates with, not just a charting platform. If your trade idea starts as "when X happens in app A, do Y," Zapier can watch for X and Autoview can execute Y.

How a Zap reaches Autoview

Add a Webhooks by Zapier action to your Zap and set its event to Custom Request. Set the method to POST, the URL to your Autoview webhook, and the Data field to your command as raw text, not Zapier's key/value data fields:

# Text command
s=BTCUSDT b=buy q=1 t=market

# JSON body (Content-Type: application/json)
{"alert": "s=BTCUSDT b=buy q=1 t=market"}

Both work. JSON is the one that matters for a sender like Zapier that speaks JSON by default: "Webhooks by Zapier" now has a first-class path here without needing a raw-text workaround.

Custom Request matters here: Zapier's plain POST and PUT events parse whatever you enter into a structured payload like {"symbol": "...", "side": "..."}, which Autoview's /hook/ endpoint rejects -- it only reads a command string, either raw or wrapped as {"alert": "..."}. Custom Request is what lets you set the body to one of those shapes yourself. You can still pull values from earlier steps in the Zap into that string with Zapier's normal field insertion.

Test with d=1 appended to the command before you trust a live Zap. Autoview logs the order it would have placed without sending it to the exchange, and Zapier's own Zap history shows you exactly what request went out.

What you can trade once connected

A Zap can drive any exchange Autoview supports: forex through OANDA, futures through Tradovate, US stocks through Alpaca, TradeStation, or Schwab, and more than a dozen crypto exchanges including Kraken, Bybit, OKX, Coinbase, and Crypto.com. See the full list on the guides hub.

Other ways to send Autoview a signal

The same command format works from TradingView, n8n, your own code, or an AI agent talking to Autoview directly. See every intake surface on the signal sources page.

Create your free Autoview account