> ## Documentation Index
> Fetch the complete documentation index at: https://docs.frayme.io/llms.txt
> Use this file to discover all available pages before exploring further.

# action

> Auto-approve, auto-deny, or block. Optional team notification.

`action` nodes execute a terminal action without involving a human. They're the alternative to `manualReview` on cleared / blocked branches.

## Configuration

```jsonc theme={null}
{
  "id": "act-block",
  "type": "action",
  "data": {
    "label": "Block – Sanctions / blocklist",
    "actionType": "deny",
    "message": "Counterparty flagged as blocklisted or severe-risk. Case denied.",
    "notifyTeam": true
  }
}
```

## Action types

| `actionType`      | Effect                                                                                            |
| ----------------- | ------------------------------------------------------------------------------------------------- |
| `approve`         | Marks the decision `auto_approved` and routes to the success terminal output.                     |
| `deny` / `reject` | Marks the decision `denied`.                                                                      |
| `block`           | Same as `deny` but additionally registers the originator / counterpart / wallet on the blocklist. |

## notifyTeam

When `true`, fires a notification to the configured team channel (Slack / email / pager — depending on the deployment's notification config). Used for high-stakes block actions so compliance has eyes on the decision in near-real-time.

## When to use vs manualReview

|                         | action                                                                       | manualReview                                             |
| ----------------------- | ---------------------------------------------------------------------------- | -------------------------------------------------------- |
| **Fires when**          | The graph reached a deterministic conclusion (rule fired, hard reject label) | Decision needs human judgement                           |
| **Blocks the workflow** | No (instant)                                                                 | Yes (pauses until response)                              |
| **Audit footprint**     | Just the node's input + action type                                          | Reviewer identity, response, timestamps, evidence packet |

Use `action` for deterministic gates (sanctions, hard reject, severe on-chain band, prohibited region) and `manualReview` for borderline cases.