
# Automating Workflows with Raw Paste Endpoints

The raw endpoint (e.g. `/api/pastes/raw/:id`) is more than a convenience feature: it is an automation primitive. This article shows how to embed **FragBin** into command-line and CI workflows.

## Why Raw Matters
- Predictable `text/plain` output
- No markup stripping required
- Ideal for piping into tools

## Shell Pipelines
With this bash command you can get the content of a paste:
```bash
PASTE_ID=abc123
curl -fsSL "$BASE/api/pastes/raw/$PASTE_ID" | grep ERROR | sort | uniq -c
```

## 3. Dynamic Config Injection
```bash
export APP_FEATURE_FLAGS=$(curl -fsSL "$BASE/api/pastes/raw/$PASTE_ID")
```

## 4. CI/CD Use Cases
| Scenario | Benefit |
|----------|---------|
| Rollback notes | Quick operator access |
| Feature toggles | Centralize ephemeral flags |
| Hotfix instructions | Single source link |

## 5. Security Tips
- Avoid storing secrets in raw pastes
- Use password + expiration for sensitive operational notes
- Rotate IDs by recreating pastes when content changes materially

## 6. Observability Hooks
Track automated fetch frequency. Unexpected spikes may indicate leakage.

## 7. Putting It Together
Raw endpoints enable *text-as-an-interface*. With FragBin, your CLI tooling ecosystem gains a lightweight content distribution layer.


Scenario	Benefit
Rollback notes	Quick operator access
Feature toggles	Centralize ephemeral flags
Hotfix instructions	Single source link