Send alerts from Zapier, Make or n8n
Any Zapier, Make or n8n workflow can trigger a trade. Add a webhook step that posts the alert text to your strategy.
Each of the three has a generic webhook or HTTP step. Point it at your strategy's Nyria webhook URL, https://trades.nyria.io/webhooks/<token>, and send a POST with your alert message as the body. Nyria reads the message, checks it against the strategy and places the order through your connected broker, the same as a TradingView alert. The bot's budget per entry sets the size, never the alert.
A live strategy places real orders. Point your first automation at a bot on Nyria Paper and check the result in the strategy's Logs tab.
You need
- A Nyria strategy with a bot on it and a connected broker.
- An account in Zapier, Make or n8n.
- The strategy's webhook URL, from the Integration tab. It starts with
https://trades.nyria.io/webhooks/.
Treat the URL like a password. Anyone who has it can send alerts to that strategy. If it leaks, select Rotate token on the Integration tab and update the URL in your tool.
What to send
Any text that names a ticker and what to do works: AAPL long entry, Close TSLA, Buy BTC limit 64000. For an exact alert, send JSON with a ticker and an action.
{ "ticker": "AAPL", "action": "OPEN", "direction": "LONG" }Set the content type to match: text/plain for free text, application/json for JSON. The message can't carry a position size. Paste a message into the alert tester first to see how Nyria reads it.
Zapier
Add the webhook step
In your Zap, choose any trigger. For the action, pick Webhooks by Zapier. Use the POST event for JSON, or Custom Request to send plain text.
Point it at Nyria
Paste your webhook URL into URL. For POST, set Payload Type to Json and add ticker, action and direction as data fields. For Custom Request, set the method to POST, add a Content-Type: text/plain header and put the message in Data.
Test the step
Run the test. A 200 answer with "status": "processed" means Nyria handed the alert to your bots. Check the strategy's Logs tab for the order.
Make
Add the HTTP module
In your scenario, add HTTP and choose Make a request.
Point it at Nyria
Paste your webhook URL into URL and set Method to POST. Set Body type to Raw, pick Text (text/plain) or JSON (application/json) as the content type, and put the message in Request content. Map a value from an earlier module into it if you like.
Run it once
Run the module. A 200 answer with "status": "processed" means Nyria handed the alert to your bots. Check the strategy's Logs tab for the order.
n8n
Add the HTTP node
In your workflow, add an HTTP Request node.
Point it at Nyria
Set Method to POST and paste your webhook URL into URL. Turn on Send Body. For JSON, set Body Content Type to JSON. For plain text, choose Raw with the content type text/plain.
Execute the node
Run the node. A 200 answer with "status": "processed" means Nyria handed the alert to your bots. Check the strategy's Logs tab for the order.
What Nyria answers
| Status | Body | Meaning |
|---|---|---|
200 | "status": "processed" | Nyria read the alert and handed it to your bots. Check the bot's Logs tab for the fill. |
200 | "status": "rejected" + reason | Normal: the ticker isn't in the strategy's list, the direction is turned off, or there was no position to close. |
200 | "status": "duplicate" | An identical body arrived a moment ago, so this one was dropped. |
400 or 404 | structured error | The token in the URL is wrong or was rotated. Copy the URL again. |
422 | structured error | Nyria couldn't use the alert, for example a missing field. userMessage names the cause. |
429 | structured error | Over the limit. Wait as long as Retry-After says, then resend. |
Your tool shows a non-2xx answer as an error with Nyria's own message. The full table of answers is in send alerts from your own bot.
Good to know
- Repeats are caught. An identical body sent again within 30 seconds counts as a duplicate. To scale into a position, make the message differ, or send JSON with a unique
metadata.message_id. - Limits. Up to 10 alerts at once, then 1 a second. Messages can be up to 256KB.
- Tickers. The ticker has to be in the strategy's list.
- Logs. Every alert has a row in the strategy's Logs tab, with the reason if it didn't place an order.
Questions
Can Zapier place trades through Nyria?
Yes. A Zap posts the alert to your Nyria strategy's webhook URL, and Nyria places the order through your broker account. Zapier never touches your broker.
Can the alert set the order size?
No. The bot's budget per entry sets the size. Change it in Nyria.
Which brokers work?
Any broker you can connect to Nyria. See brokers.
Which tool should I pick?
Whichever you already use. All three post the same alert to the same strategy.
Next steps
- Send alerts from your own bot: every response code, duplicate rules and sample senders.
- Webhook reference: every field Nyria accepts.
- Alert sources: TradingView, Discord, Telegram and TrendSpider.
Send alerts from your own bot
Point your own bot or service at a Nyria strategy's webhook, so its alerts place orders through your connected broker.
Strategies
A strategy holds the rules for a set of alerts: the source, the asset type, the trading behavior and the contract selection. Build one, then deploy bots on it.