Help
Last updated: March 2026
DynTab is about dynamic tables: we take structured data from HTML pages and APIs and present it as one interactive table—sortable and filterable in the browser. The sections below explain how to do that in the app, from creating a source to editing it and choosing URLs. New and Edit use the same layout (live table on the left, form on the right); you must be signed in.
1. End-to-end flow
Each table starts from one source URL—whether it returns HTML or an API payload. From the header, open New. Pick a unique slug (published at /tab/{slug}), enter a title, and paste that URL. Add an optional description, custom prompt for the model, auto-refresh interval, and private mode. Click Generate preview: we fetch a sample, generate a parser, run it once, and show rows on the left. When there is at least one data row and it looks right, click Create data source—you land on the public table page. Later, use Edit from your dashboard or in-product links to change metadata or refine the parser; View table opens the same slug read-only.
2. How HTML/API data becomes your table
The conversion is powered by a saved parser program tailored to your URL—not a single hard-coded template for every site. We send a normal HTTP GET and pass the response body into the pipeline. There is no headless browser, so JavaScript on the page does not run. OpenAI produces or updates a small Node parser from that sample plus your title, description, and prompts. We execute it on the server; it must output Tabulator-style JSON (columns and rows). The UI renders that so you can sort and filter. The saved data source stores the program and settings; loading /tab/{slug} runs the parser again on a fresh fetch of the same URL, and auto-refresh follows the interval you configured.
3. New table (/new)
The slug must be 8–191 characters (lowercase letters, digits, hyphens) and is checked for availability as you type. Generate preview requires a URL. The first successful run creates a parser from scratch; later Generate preview calls can refine the current program using your custom prompt. Create data source stays disabled until the preview has at least one row, the slug is available, and required fields are filled. Private hides the table from the public home list so only you can open /tab/{slug} while signed in. Auto-refresh: 0 means off; when greater than zero the value is normalized and must be at least 120 seconds for scheduled background refresh.
4. Picking a URL (HTML page vs API)
Both static HTML and JSON-style APIs are valid inputs as long as the structured data appears in the first HTTP response body—not only after JavaScript or WebSocket updates. If the data you need appears only after load, a bare page URL is often wrong; prefer a URL that already returns the dataset (for example a JSON API). To inspect raw HTML, open view-source: in front of your URL in the address bar; if values are missing there, use DevTools → Network to find the request that returns them and paste that URL into DynTab.
5. Edit table (/edit/{slug})
Slug and source URL cannot be changed after creation—create a new table if you need a different address. The left side is the same interactive table as on /tab/{slug}; after a successful save it remounts with fresh data. Regenerate & save compares your change request for the model with the last saved text: if it is unchanged, we skip the model, reuse the stored parser, and still save title, description, refresh interval, and private flag. If you change the prompt, we ask the model to rewrite the program, save it, run it, and refresh the preview. Delete table removes the source and all run history after you confirm.
6. When something fails
Errors may mention a stage—sample fetch, OpenAI, run program, or parser result—to show where it failed. Check that the URL is reachable from our servers, returns what you expect on a plain GET, and does not need credentials you have not supplied. Fetches run on our backend, so browser CORS does not apply. If the table was created but the first parser run failed, follow Open editor when the UI offers it. For product questions or bugs, use Feedback in the footer.