Docs / Actions & workflows
Destinations
A fired action is delivered to a connection: a named destination you set up once under Settings → Connections. Requests and workflows only name it ("connection": "trading-desk"); URLs, tokens and addresses stay encrypted on our side and are never shown again.
| Destination | do | Connection holds | What is sent | Good for |
|---|---|---|---|---|
| Slack live | slack | A Slack incoming-webhook URL for one channel | A text message (message) posted to that channel | Desk alerts, daily reads, workflow digests |
| Webhook (HTTPS) live | webhook | Any public https:// URL, plus optional headers (for example an auth token) | A JSON POST of your body template, signed with X-Jev-Signature and retried 3 times | Your OMS or execution system, risk systems, Zapier / Make / n8n, Microsoft Teams or Discord incoming webhooks (shape the body as they expect, e.g. {"text": …} or {"content": …}) |
| Email soon | email | One or more members of your organization | An email with your subject and messageNot sending yet on this server: rules and dry runs work, delivery turns on once the mail sender is configured. | Personal daily reads, escalations |
Same destinations everywhere
Actions on a single request, per-symbol actions in a workflow, and a workflow's digest all use these three. One request can fire several actions to different destinations, for example a Slack alert and a webhook to your OMS.
Not supported yet
SMS, mobile push and placing broker orders directly. For any of these, point a webhook at your own system or an automation tool (Zapier, Make, n8n) and send from there.
Create an account Open the Playground
Everything here also lives in the console, next to your keys and usage.