ChatGPT Plugin

Moonwalk

Write and publish live boards

Brand: Moonwalk

Category: Productivity
Primary Subcategory: Business Data & Low-Code Apps

Integration details

Description

Moonwalk is where you write boards: pages that hold text alongside live tables, charts and interactive widgets, which you can keep private or publish as a public page. This plugin lets ChatGPT write and maintain those boards with you, and build the data and machinery behind them. What ChatGPT can do with it: - Boards: read, search and write pages, reorganize them, and publish a board as a public page. - Data for your boards: create tables, read and write rows, and run read-only SQL queries whose results show live on a board. - Widgets: build interactive screens (charts, forms, dashboards) that sit on a board, and see a picture of what it built. - Automations: create workflows in Python that keep a board's data current, running on a schedule, from a webhook or by hand, and read each run's results. - Files: browse, search, read and edit the files in your base, and upload new ones. - Connections: see which third-party accounts and keys your base holds, and ask you to add one. ChatGPT never sees or types a secret; you enter it in Moonwalk. Safe to hand to an agent: - Everything ChatGPT changes is recorded as yours, with ChatGPT noted as the agent. - Deleted boards, tables, widgets, automations and files go to a 30-day trash and can be restored. - Edits are versioned, and a batch of row changes can be undone in one step. Requires a Moonwalk account (sign up at moonwalk.now). You sign in and approve access on Moonwalk's own screen, and can revoke it at any time from Moonwalk's Agents page.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Productivity
Primary Subcategory: Business Data & Low-Code Apps
Secondary Subcategories: None listed
Brand: Moonwalk
Access: Account required
First tracked: 2026-09-28
Tool count: 94
Market: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Business Data & Low-Code Apps

View Category

Listed in alphabetical order

Primary Subcategory

ActivityInfo.orgComing soonGet notified

ADoorComing soonGet notified

AnyDBComing soonGet notified

BOLDR MAXComing soonGet notified

CongravaComing soonGet notified

MoonwalkComing soonGet notified

Tools

94 tools agents can invoke

Lock this exact version and allow it to fire. Needs steps — the version is always there, because every edit goes into one. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
activate_action
Add a column to a table. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
add_column
Ask the person for a credential you must never see. Name the connection you want and why: `secret`, `basic` or `hmac` for a key they type, or `account` for a service they connect by clicking — then `provider` is the service's slug, like `gmail`. Never ask for an API key, password or token in the conversation, and never accept one there. In the chat panel a box asks them under your message, and their answer comes back to you as the next message: stop and wait for it. Anywhere else, show them the URL this answers and stop; then poll `get_connection_request`. The name is a proposal — bind steps to the name the answer gives, not the one you asked for. For a key, `how_to_get` is required: the path to it from where the person starts, as `site > page > button`, like `platform.openai.com > API keys > Create new secret key`. Add `how_to_get_url`, like `https://platform.openai.com/api-keys`, when you know the page. It shows in the box where they type the key, so write it for someone who has never done it. When you're not sure of the path, say so in it rather than inventing one. An account takes neither. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
request_connection
Bind a base connection to one declared key. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
bind_step_connection
Change a column's type. Refused, naming the rows that stopped it, when a value would not survive the cast. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
change_column_type
Drop one config value, back to the declared default. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
clear_step_config
Create a board, at the end of `group_id` (`list_groups`), or of the tab's default when that is left out: a name and an empty folder, which draws *This board is empty.* until you write its `App.tsx` with `write_board_file`. Every board is at the top level. It starts members only, `medium` wide, notifications off. The id is yours to mint. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
create_board
Make a group in a tab, after `after` or last when it is null. Everyone in the base sees it. Make one for what belongs together, named for what it serves. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
create_group
Add a step. The source is linted at save: it must define a top-level `run(...)` and, for a code step, a `ReturnType` model it returns. Say why in `change_description` — one line a person would understand: "Skips weekends". It is the line the automation's history shows, and code saved without one is refused (422 `change_description_required`). A positional parameter of `run(...)` is an input, filled from the step's `inputs` list in order. `{"step": "trigger", "path": [...]}` reads what fired the run; `{"step": "<hash>", "path": [...]}` reads an earlier step's output. def run(title, file) -> ReturnType: ... inputs=[{"step": "trigger", "path": ["title"]}, {"step": "trigger", "path": ["file"]}] A count that does not match, or the same names in a different order, is refused at save (422 `invalid_step`). A step reaches the base's own tables through the SDK — no connection needed, and tables and columns are named by id, never by name: from mw_sdk import BaseModel, Config, Annotated, Literal, Ge, Le, Gt, Lt, MinLen, MaxLen, MultipleOf, connection_type, SecretConnection, BasicConnection, HmacConnection, AccountConnection, tables, files import uuid class ReturnType(BaseModel): written: int def run() -> ReturnType: tables.write(table_id, [ {"op": "insert", "row": str(uuid.uuid4()), "values": {column_id: value}}, ]) return ReturnType(written=1) `tables.sql`, `tables.columns` and `tables.rows` read; `tables.write` writes, and every write a run makes lands in one transaction, the run's. Undo never takes it back; on each table it touches it is a version of its own. `discard_latest_version` takes it back while it is still the newest, `revert_version` to the version before it once something is on top. An `op` is one of insert, set, delete, restore; `row` is a UUID the caller mints; `values` is keyed by column id. A new row lands last; rows are in # order and cannot be placed. `tables.sql` is read-only Postgres over the base's views: a table is `"v_<hex>"` and a column `"c_<hex>"`, the uuid without its dashes, so a rename never breaks a step. `tables.columns(table_id)` is how a step gets from a name to an id at run time rather than pasting one in. A step reads and writes files under `/files`, its working directory, with plain `open`. Pass any file name that came from outside — a trigger's input, a cell — through `files.inside(folder, name)` before opening it: it answers the absolute path, `/files/<folder>/<name>`, and raises `ValueError` for a name that climbs out of `folder`. A file field (`"format": "file"` on a manual trigger) hands the step the path the file was saved at, `/files/Uploads/<name>`. To delete a file, `files.trash(path)`: it answers nothing, and the file waits in the base's trash for 30 days, so a mistake can be taken back. `os.remove` cannot be. A config (`Config[T]` on `run`) is a setting and never a credential. A key, password or token is a connection, asked for with `request_connection`. Each step gets 1 hour of wall time and 120 CPU-seconds, counted across every process it starts. Past either it is killed, and its step run's `error_type` says which: `wall_time` or `cpu_time`. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
create_step
Create a table and its columns, at the end of `group_id` (`list_groups`), or of the tab's default when that is left out. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
create_table
Create an action. The trigger's mode is set here and never again — a different mode is a different action. `description` is required: one line a person would understand, saying what it does. It is the line its card shows, and an action made without one is refused (422 `description_required`). It lands at the end of `group_id` (`list_groups`), or of the tab's default when that is left out. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
create_action
Stop it firing and unlock it for editing. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
deactivate_action
Trash a board with its folder. `restore_board` brings it back; `list_trash` with `board` shows it. While it is in the trash its view link answers not-found. One with no name and nothing in its folder that nothing but your own open sitting ever touched is deleted outright instead, and has no way back. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
delete_board
Remove one file from a board's folder and compile the rest — answered as `write_board_file` is. The last file gone empties the board, its declaration with it: it draws *This board is empty.* again, and a folder written after needs `set_board_declaration` again before it reads or runs anything. To rebuild a board, write over its files rather than deleting them all. **Every write, edit and delete saves** the file, whatever it holds, then compiles the whole folder. The answer is `built` and `errors`, each `{file, line, column, text}` — or, once it builds, `screenshot`: page 1 of the board as drawn now, from its real rows, in `theme` (`light`, the default, or `dark`), and `thrown`, every message the screen threw while it drew. While the folder does not build the board keeps drawing its last good build and says it is behind. While it draws, every run is refused `not while previewing`, so a picture never writes to the base. When it cannot be drawn the save still stands, and `screenshot` is `{"unavailable": <reason>}`. Your run of saves on one board is one version in its history. **Say why in `change_description`** — one line, in words the person would use: "Shows the week's total above the chart". It is the line the board's history shows, and a save without one is refused (422 `change_description_required`). A locked board refuses all three, `board_locked`. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
delete_board_file
Drop a column. Never refused — every query naming it stops running and says so. `restore_column` takes it back, with its values — and so do `undo`, to the place it held, and reverting the table to a version from before the drop. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
delete_column
Delete a connection. Refused while a step is bound to it. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
delete_connection
Move a file, or a directory and everything in it, into the base's trash, where it waits 30 days. It leaves the tree — `list_trash` with `kind="file"` is where it is now, and `restore_file` takes the `id` from there and puts it back where it was. Never the root, `/files/Uploads` or `/files/Public`. Nothing you do deletes a file for good. Documented at https://docs.moonwalk.now/tools.html#files. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
delete_file
Delete an empty group: 409 `group_not_empty` while it holds a live thing, 409 `group_default` for the tab's default, which is never deleted. What it holds in the trash moves to the default first. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
delete_group
Delete a step and everything under it — an `if` takes both branches. Refused while a step left behind reads one that goes; rewire or delete that step first. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
delete_step
Trash a table. `restore_table` brings it back — unless the table held no rows and nothing but your own open sitting ever touched it, which is deleted outright and has no way back. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
delete_table
Trash an action. Its steps, runs, versions and files are kept and nothing fires it; `restore_action` brings it back with its trigger live. Refused while a board's screen fires it, naming the boards. One with no steps that nothing but your own open sitting ever touched is deleted outright instead, and has no way back. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
delete_action
Replace `old` with `new` in one file of a board's folder, leaving the rest byte for byte, and save it — answered as `write_board_file` is. `old` must appear exactly once — include enough of the lines around it — unless `replace_all`. A refused edit saves nothing, `edit_refused`. **Every write, edit and delete saves** the file, whatever it holds, then compiles the whole folder. The answer is `built` and `errors`, each `{file, line, column, text}` — or, once it builds, `screenshot`: page 1 of the board as drawn now, from its real rows, in `theme` (`light`, the default, or `dark`), and `thrown`, every message the screen threw while it drew. While the folder does not build the board keeps drawing its last good build and says it is behind. While it draws, every run is refused `not while previewing`, so a picture never writes to the base. When it cannot be drawn the save still stands, and `screenshot` is `{"unavailable": <reason>}`. Your run of saves on one board is one version in its history. **Say why in `change_description`** — one line, in words the person would use: "Shows the week's total above the chart". It is the line the board's history shows, and a save without one is refused (422 `change_description_required`). A locked board refuses all three, `board_locked`. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
edit_board_file
Rename a column, or set a select's options. `options` is the full list: keep an option by its id, relabel it under the same id, add one with a label only, leave one out to remove it. Ids never change, so nothing naming them breaks. An option a row still holds cannot be removed. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
edit_column
Replace `old` with `new` in a text file, leaving the rest of it byte for byte. `old` must appear exactly once — include enough of the lines around it to make it unique — unless `replace_all`. Nothing changes when the edit is refused, and the answer says why. To write a whole file, use `write_file`. Documented at https://docs.moonwalk.now/tools.html#files. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
edit_file
Find files and folders by a glob, without listing folders one by one. A pattern with no `/` matches a name at any depth (`*.md`); one with a `/` matches the path from `path`, `**` descending (`notes/**/*.md`), or from the root when it starts `/files/`. Dotfiles are included. At most 100 answers. Documented at https://docs.moonwalk.now/tools.html#files. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
search_files
One board: its name, width, whether notifications are on, whether it is locked, whether its view link is published and who it opens for, and its path, whether its folder is empty or behind, its screen's declaration — each run with what it takes and answers — and what it is built on: the tables it reads, the actions behind it, the connections those use. Its files are `list_board_files`'s. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
get_board
How an ask was answered: `pending` or `filled`, and — once filled — the connection that was actually made, which may not be the name you asked for. 404 `no_such_request` once the person declined it, `expired` once the hour is up. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
get_connection_request
One run: its status, its timings, what it received (`input`) and what it returned (`output`). Either is `{"$over": <bytes>}` past 16 KB. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
get_run
One row per executed step, in execution order — what you debug a run from. `cpu_ms` and `wall_ms` are what the CPU and wall-time limits count: every process it started, from the moment it was sent. Installing its dependencies comes first and is in neither, so a first run can take a minute and report a few hundred ms. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
get_run_steps
What a step declares as config, and the values saved against it. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
get_step_configs
What a step declares as connections, and which base connection is bound to each key. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
get_step_connections
The Python source of one step, as it is on disk. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
get_step_source
One table and every column on it, with each column's type. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
get_table
One version, and what it changed against the version before it. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
get_version
One action: its step tree, its trigger and its state. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
get_action
Get a one-time link for sending a file from your own machine into the base — MCP carries no bytes, so this is how one gets in. Run the `command` it answers with your file's path in place of the placeholder; the upload answers `{"path": "/files/Uploads/…"}`, which is what a file field in `fire_action` takes. The link works once, for 5 minutes. If the upload cannot connect, do what the `note` says. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
request_upload
Where the person gets a webhook trigger's signing secret, never the secret itself. Show them the `url`: on that screen they press the eye on the trigger and copy the secret to paste upstream. `secret_set` is false while an upstream secret has not been pasted in. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
get_webhook_secret
Where the person pastes the upstream's signing secret, never the secret itself. Show them the `url`: on that screen they paste it into the trigger; never ask for it in the conversation. Refused (409 `system_generated`) when Moonwalk made the secret; that one is copied, with `get_webhook_secret`. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
set_webhook_secret
What went wrong with a board's screen, newest first, each with its `kind`: `undeclared_data` and `undeclared_run` for a read or run its declaration never named, `action_gone` for a declared run whose action has left, `render` for a screen that threw, `compile` for a save whose folder did not build. A run's own failure is not here — `get_run` has it. `limit` is capped at 200. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
list_board_errors
Every file in a board's folder, by path, with its size in characters. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
list_board_files
Rows of one table, by limit and offset. To filter, sort, group or join, write SQL — `run_sql`. The table screen's own filter is the UI's and adds nothing an agent holding SQL does not already have. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
list_rows
Every action in the base, in the rail's order, with its steps, its trigger and its group. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
list_actions
An action's runs, newest first. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
list_runs
Every step of an action, in tree order, with its inputs. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
list_steps
Every board of the base, in the rail's order, with its group, its view link's ref, whether that link is published, who it opens for while it is, and whether the board is locked. A link that is not published opens for nobody, whatever `visibility` says. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
list_boards
Every ask in the base still waiting on the person — yours, another chat's, or one made over `/api/mcp` — with its name, kind, who asked, why, and when it runs out (`expires_at`). The list the Connections dot reads. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
list_connection_requests
Every connection the base holds. The fields never come back out. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
list_connections
One directory of the base's tree. A path is absolute from `/files`, the root — `/files/notes/todo.md` — and every answer spells it that way. Documented at https://docs.moonwalk.now/tools.html#files. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
list_files
A tab's groups in the rail's order: `section` is `boards`, `actions` or `tables`. Every board, action and table is in exactly one, named by its `group_id`. Each tab has one default, `is_default`, where a thing lands when nothing names a group; its `name` is null until somebody renames it, and it reads as the tab's own word. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
list_groups
The services an account can be linked for, searched by name — the Connections screen's picker. Look the slug up here before `request_connection` with `account` rather than guessing it. 503 `not_configured` means no account can be linked on this stack at all. This is Moonwalk. `base_id` is an id from `list_bases`. The rules of a Moonwalk base that no single tool states are in `read_overview`.
list_services

FAQs

Moonwalk ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Moonwalk's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Moonwalk alternatives on ChatGPT?

As of 2026-11-02, Moonwalk competes with ActivityInfo.org, ADoor, AnyDB, BOLDR MAX, Congrava, Dreambooth Studio, Everyn, Exportlab and 11 more in ChatGPT Business Data & Low-Code Apps, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.