Core Concepts

Decimal is built on a few simple building blocks. Once you understand these, you can create anything — from a simple reminder to a cross-chain automation spanning dozens of apps.

1. Accounts

2. Workflows

• A workflow is a sequence of steps that runs automatically.

• Each workflow has:

  • Trigger(s) → what starts it.

  • Action(s) → what it does.

  • Optional Logic → how it decides to branch, repeat, or stop.

• Analogy: A relay race where one runner passes the baton to the next until the finish line.

3. Triggers

• Triggers are events that start a workflow.

• Types of triggers:

  • Web3: Wallet balance change, new transaction, token price movement, NFT mint, DAO proposal.

  • Web2: New form submission, calendar invite, payment received, webhook.

• Analogy: Like flipping a light switch to power on a circuit.

4. Actions

• Actions are what happens next once a workflow is triggered.

• Examples:

  • Send funds, mint/burn an NFT, post to Discord, email your team, run an API call.

• Analogy: Dominoes falling one after another — each action pushes the next forward.

5. Nodes

• Each Trigger or Action sits inside a Node.

• Types of nodes:

  • Trigger nodes

  • Action nodes

  • Utility nodes (IF/ELSE, delays, loops, approvals, etc.)

• Analogy: Each node is like a LEGO brick — each one does something specific, and you connect them together to build something beautiful.

6. Connections

• The lines between nodes define data flow (what output from one step becomes input for the next).

• Connections can be 1-on-1s, splits or merges to manage sequential or parallel execution paths.

• Example: A “Price Feed Node” outputs ETH = $2500 → “Telegram Node” takes that and sends: “ETH just hit $2500 🚀”.

7. Logic & Control

• Not everything is linear. Decimal supports:

  • If/Else Conditions → branch your workflow.

  • Loops → repeat until done.

  • Delays / Scheduling → run later or at intervals.

  • Approvals → require human confirmation.

• Analogy: Like choosing different routes in Google Maps depending on traffic conditions.

8. Execution

• Once satisfied, a Web3 workflow can run:

  • Autonomously → executes end-to-end without interruption using Decimal Account.

  • With Approvals → pauses at certain points until a human confirms using User Account or certain Web2 nodes.

• Key idea: You decide the balance between speed vs control.