# Core Concepts

### <mark style="color:blue;">1. Accounts</mark>

### <mark style="color:blue;">2. Workflows</mark>

* 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.
* <mark style="color:orange;">Analogy:</mark> *A relay race where one runner passes the baton to the next until the finish line.*

### <mark style="color:blue;">3. Triggers</mark>

* 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.
* <mark style="color:orange;">Analogy:</mark> *Like flipping a light switch to power on a circuit.*

### <mark style="color:blue;">4. Actions</mark>

* 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.
* <mark style="color:orange;">Analogy:</mark> *Dominoes falling one after another — each action pushes the next forward.*

### <mark style="color:blue;">5. Nodes</mark>&#x20;

* Each Trigger or Action sits inside a Node.
* Types of nodes:
  * Trigger nodes
  * Action nodes
  * Utility nodes (IF/ELSE, delays, loops, approvals, etc.)
* *<mark style="color:orange;">Analogy:</mark>* Each node is like a LEGO brick — each one does something specific, and you connect them together to build something beautiful.

### <mark style="color:blue;">6. Connections</mark>

* The lines between nodes define data flow (what output from one step becomes input for the next).&#x20;
* 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 🚀”*.

### <mark style="color:blue;">7. Logic & Control</mark>

* 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.
* *<mark style="color:orange;">Analogy:</mark>* *Like choosing different routes in Google Maps depending on traffic conditions.*

### <mark style="color:blue;">8. Execution</mark>

* 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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.decimal.at/technical/learning-path/core-concepts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.