# Persist Appearance options to localStorage (`aspiring_hypotenuse_ior/persist-appearance-options-to-localstorage`) Actor

Persist UI appearance options (nodes, edges, labels) to localStorage, a repetitive task that could be automated with a tool.

- **URL**: https://apify.com/aspiring\_hypotenuse\_ior/persist-appearance-options-to-localstorage.md
- **Developed by:** [Lore Nest](https://apify.com/aspiring_hypotenuse_ior) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Persist Appearance options to localStorage

Persist UI appearance options (nodes, edges, labels) to localStorage, a repetitive task that could be automated with a tool.

This Actor stores UI appearance options in `localStorage`, accepting a payload of UI configuration and persisting it for later retrieval. By automating this repetitive task, it removes the need for manual storage calls and ensures appearance settings are reliably captured in a structured JSON format.

### Use Cases

- **Save user-customized graph views** — Persist a user's preferred node styling, edge styling, and label display settings so the same visualization is restored the next time they open the application.
- **Sync appearance presets across sessions** — Store a single named appearance configuration (nodes, edges, labels) in `localStorage` so that reopening the tool or browser tab reloads the exact same visual layout.
- **Capture presentation-ready configurations** — Save a polished appearance setup (such as specific node colors, edge weights, and label visibility) before sharing a visualization with stakeholders, ensuring the look is preserved.
- **Persist developer debugging profiles** — When iterating on graph visualizations, store different combinations of node/edge/label options to `localStorage` and switch between them without re-entering values each time.
- **Maintain a single canonical appearance record** — Overwrite the `appearance` key in `localStorage` with the latest settings on every run, guaranteeing that only the most recent configuration is retained as the source of truth.

### How It Works

The Actor receives a dictionary payload and filters it to retain only the keys `nodes`, `edges`, and `labels`, discarding any extraneous fields. These filtered values are passed into an `AppearanceOptions` dataclass, serialized to JSON via `asdict`, and then written to an internal `_local_storage` dictionary under the key `"appearance"`. The Actor returns a `{"status": "success", "data": payload}` response, confirming the options have been stored. Because storage is held in an in-memory dictionary, the persistence is scoped to the Actor's own runtime rather than the browser's actual `localStorage`.

### Usage on Apify

Run it directly from the Apify Console ("Start"/"Try for free"), or call it via the API:

```
POST https://api.apify.com/v2/acts/persist-appearance-options-to-localstorage/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>
Content-Type: application/json

{}
```

### Pricing

Pay-per-event, billed automatically by Apify -- no separate account or payment step:

- Actor start: $0.00005 per GB of memory (minimum one event per run)
- Result: $0.005 per item returned -- this is the primary, usage-based charge

Also independently available at $0.0100 USDC (Base) per call via the x402 payment protocol (`POST /tools/persist-appearance-options-to-localstorage`) for callers outside the Apify platform.

### Example output

Real output captured from this tool's own build-time smoke test (input above):

```json
{
  "status": "success",
  "data": {}
}
```

# Actor input Schema

## `edges` (type: `string`):

Real parameter read as payload\['edges'] in this tool's own generated code.

## `labels` (type: `string`):

Real parameter read as payload\['labels'] in this tool's own generated code.

## `nodes` (type: `string`):

Real parameter read as payload\['nodes'] in this tool's own generated code.

## Actor input object example

```json
{}
```

# Actor output Schema

## `output` (type: `string`):

Real dataset items pushed via Actor.push\_data() in src/main.py -- each item is exactly the dict this tool's own run() returns. This tool's own real, build-time-captured output had these top-level fields: data, status.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("aspiring_hypotenuse_ior/persist-appearance-options-to-localstorage").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("aspiring_hypotenuse_ior/persist-appearance-options-to-localstorage").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call aspiring_hypotenuse_ior/persist-appearance-options-to-localstorage --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,aspiring_hypotenuse_ior/persist-appearance-options-to-localstorage"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/7OTHSuygCpn2Wtgjn/builds/d6C7IKsmc6goN5yaF/openapi.json