IGNITRAOpen the app

Onchain automation · Robinhood Chain

When the chain moves,
everything follows.

IGNITRA turns anything that happens on Robinhood Chain into actions in the tools you already use: Telegram, webhooks, email, Google Sheets, any HTTP API, push notifications. No bot to run, and every run explains itself.

  • 10 triggers
  • 8 actions
  • 1 run per event, ever
liveblock …0 runs

ember: real runs · gray: illustrative

Live instrument

Each ember above is one of these runs.

A real flow on Robinhood Chain mainnet, read the way you would build it. When a transfer matches, the run lands here within seconds: the transaction, how long it took from its block, and its result.

How a flow reads
  1. WHENToken transfer · USDG
  2. IFamount_decimal ≥ 10,000
  3. THENTelegram → #desk
  4. THENGoogle Sheets → “Big moves”
  5. THENWebhook → your API (signed, retried)
01

How a flow reads

Three parts, always in this order. Pick them from the catalog; nothing to code.

WHEN

Something happens

  • Contract event
  • Token transfer
  • New holder
  • Balance threshold
  • Contract deployed
  • State change
  • Schedule
  • Inbound webhook
  • VIGIL alert
  • Pons launch
IF

It matters to you

  • amount_decimal ≥ 10,000
  • percent_of_supply ≥ 0.5
  • to in your watchlist
  • from_trust_score ≥ 700
  • body.status = “paid”
THEN

Your stack follows

  • Webhook
  • Telegram
  • Web Push
  • Email
  • Google Sheets
  • HTTP request
  • Read contract
  • Onchain transaction
02

Ready in two minutes

Templates are complete flows: fill in a token or a wallet, pick where it goes. All templates →

03

Why it holds up

Automation you can leave running: the guarantees are in the database and on the chain, not in a promise.

  1. One run per event

    A unique key per event and flow, in Postgres. A replayed stream or a restarted listener never runs anything twice.

  2. Every run explains itself

    The transaction, block and log; each condition with the value it saw; every request and response. Skips and failures say why.

  3. Confirmed by default

    Runs start after confirmations, so reorgs do not reach your tools. Fast mode acts at the head and tells your webhooks about reorgs.

  4. Delivered, or retried

    Signed webhooks with the same idempotency key on every retry. Steps that fail for good wait for you, never repeat what succeeded.

  5. Nothing to custody

    Sign in with your wallet. Secrets are encrypted, outbound calls guarded against SSRF, runaway flows pause themselves.

04

System status

Checked 2026-11-12 22:08:36 WIB.

APIunreachable
Chain listenerunknown
ChainRobinhood Chain · 4663

One event.
Every action.

Start from a template, or build a flow from the catalog. Testing a flow never counts against your plan.