Component · UI components
CSV export
A custom component that gathers the rows of one table the viewer is allowed to see (up to 5,000, newest first) and offers them as a CSV file that opens in any spreadsheet. Pick the columns or let it use every field. The template adds it with an Export page for the role you choose.
Use in AppbricxFree. Already have an account? Log in
use_template { slug: "csv-export" } adds
- Components
- CsvExport
- Pages
- /export
What it adds to your app
Component CsvExport (props: title, entity, columns). An Export page.
Pages
/exportExport (‹page_role›)
Components
CsvExportDownload the rows of a table the viewer may see as a CSV file, with a preview of the first rows
Where it attaches
Params point the template at your own tables and roles. Leave out the ones with defaults; a wrong one is refused with the options your app has.
| Param | What it is | Example |
|---|---|---|
entity | The table the Export page offers as CSV. | order |
page_role | The role the Export page is for. Optional. | staff |
Use with your coding agent
- Connect the Appbricx MCP server to Claude Code, Cursor or any MCP client (quickstart).
- Paste the prompt. The agent reads the template, previews the merge with dry_run and shows you the diff.
- It applies to dev. Check it, then deploy when you are happy.
Add the CSV export template (slug "csv-export") to my Appbricx project. Read it with get_template, run use_template with dry_run first and show me the diff, then apply it. Ask me where it attaches if you can't tell from my contract (entity: table to export; page_role: who sees the export page).{
"tool": "use_template",
"arguments": {
"slug": "csv-export",
"project_id": "<your project id>",
"params": {
"entity": "order",
"page_role": "staff"
},
"dry_run": true
}
}appbricx templates use csv-export --param entity=order --param page_role=staff --dry-run