Schema CSV
textareaRequired input
Noderan MarketplaceData & Intelligence
Demo ReadyLive E2E verifiedDeterministic~10s
Data Dictionary Builder
Returns headers, row counts, findings, and preview rows.
Create data dictionary findings from schema CSV rows.
Workflow summary
Create data dictionary findings from schema CSV rows.
What is Data Dictionary Builder?
Data Dictionary Builder is a ready-to-run Noderan marketplace workflow for data & intelligence teams. It helps users move from a manual process to a repeatable automation with visible credit cost and app-based execution.
- Who is it for?
- Data teams
- What problem does it solve?
- Create data dictionary findings from schema CSV rows.
- How does it work?
- Create data dictionary findings from schema CSV rows.
- How does pricing work?
- 1 credit per run.
- What is the next action?
- Open the app marketplace to activate this workflow, or review credit pricing.
Data Dictionary Builder FAQ
Short answers for activation, pricing, inputs, and execution review.
Returns headers, row counts, findings, and preview rows.
Expected inputs
Demo input
Schema Csv
field,type,description requestId,string,Request identifier status,string,Request status credits,number,Credit costView raw JSON
{
"schemaCsv": "field,type,description\nrequestId,string,Request identifier\nstatus,string,Request status\ncredits,number,Credit cost"
}Output highlights
- rowCount
- columnCount
- headers
- findings
- previewRows
Example result
Row Count
3Column Count
3Headers
namestatusscore
Findings
Schema includes request status and credit cost fields.No empty header names detected
Preview Rows
1 structured item
View raw JSON
{
"rowCount": 3,
"columnCount": 3,
"headers": [
"name",
"status",
"score"
],
"findings": [
"Schema includes request status and credit cost fields.",
"No empty header names detected"
],
"previewRows": [
{
"name": "Alpha",
"status": "ready",
"score": "92"
}
]
}Use cases
- Profile schema rows before analytics handoff.
How it works
- 1
Review the workflow and expected credit cost.
- 2
Connect the tools or inputs required for execution.
- 3
Run the workflow and inspect outputs in the app history.