IGNITRAOpen the app

IGNITRA docs

IGNITRA runs flows for you: when something happens on Robinhood Chain (chain id 4663), it checks your conditions and runs your actions. You never run a bot or a server, and every run keeps a trace that explains what happened.

FLOW = TRIGGER → CONDITIONS → ACTIONS

WHEN  Token transfer · token 0x5fc5…d168       ← trigger: what starts a run
IF    percent_of_supply ≥ 0.5                   ← conditions: filters on the trigger data
AND   is_mint = false
THEN  Read contract → balanceOf(address)        ← actions, in order; later ones use
THEN  Telegram → "🔥 {{trigger.amount_formatted}} {{trigger.token.symbol}}"   earlier outputs

Quick start

  1. Sign in with your wallet at /app. You sign a message (Sign-In with Ethereum): no transaction, no gas, no private key ever leaves your wallet.
  2. Add a connection (where messages go): a Telegram chat, a webhook, an email address, a Google account or HTTP secret headers. Secrets are stored encrypted and never shown again.
  3. Pick a template from the gallery, or build a flow from scratch. Paste an address and IGNITRA detects the token or contract.
  4. Test it: “Load the latest real event” shows real data from the chain, and “Test flow” runs the actions once with it. Test runs are labelled TEST and never count towards your plan.
  5. Activate. Runs appear in the flow's history with a step-by-step trace, and “Why it did not run” lists matches the conditions or limits filtered out.

Guarantees

TraceableEvery run stores the trigger evidence (transaction, block, log index), each condition with its actual value, and every action attempt with its request summary, response, duration and status.
Exactly-once intentOne run per event and flow: the database enforces a unique key such as 4663:<tx hash>:<log index>:<flow id>. Restarts and replays never run a flow twice for the same event.
At-least-once deliveryActions are retried with backoff. Every retry carries the same X-Ignitra-Idempotency-Key, so receivers can deduplicate.
Reorg-safeFlows run on confirmed events by default. In fast mode, a run whose event is reorged out is marked, and webhooks get a signed run.reverted notice.
Safe by defaultOutbound requests cannot reach private networks (SSRF guard, DNS pinning, no redirects), templates cannot run code, and a flow far over its hourly cap pauses itself.

Plans

PlanActive flowsRuns / monthIncludes
free3500 (then matches wait for next month)Telegram, webhooks, Web Push, HTTP requests, contract reads, every chain trigger, inbound webhooks
builder2010,000 + metered overage+ email, Google Sheets, schedules (every minute)
teamunlimited100,000 + metered overageeverything in Builder, with unlimited active flows

Usage resets on the 1st of each month (UTC). Test runs are never counted.

Conventions

  • Times are stored in UTC and shown in your timezone (WIB, Asia/Jakarta, by default). Template variables offer both, e.g. {{trigger.time.iso}} and {{now_wib}}.
  • Addresses and hashes are lowercase hex in data and conditions. Comparisons with hex values are case-insensitive.
  • Token amounts come three ways: amount in raw base units (exact), amount_decimal in token units (exact) and amount_formatted for display.

Reference

  • Triggers: every trigger, its params and the data it provides.
  • Conditions: operators, AND / OR groups and exact semantics.
  • Actions: every action, its params, outputs, retries and TEST labels.
  • Variables: the {{…}} template language.
  • Webhooks: signatures, the envelope, idempotency, and inbound webhooks.
  • Integrations: VIGIL alerts, TRUST LAYER scores, MANDATE policies, Pons launches.
  • Onchain actions: transactions from your Safe through a scoped, revocable session key.
  • API: sign-in, endpoints, errors.
  • SDK & API keys: @ignitra/sdk, keys and rate limits.