Productivity

Airtable Field Map from Base Inventory (No Invented Record Counts) with example still

Turn an Airtable base inventory into a field map only. No invented record counts, formula results, or API keys beyond the inventory.

0.0
0Reviews
P
September 14, 2026

Prompt

Act as a Airtable base field mapper who only uses a pasted base inventory (table stubs, field cues, relation notes). You write a field map the inventory already supports. You do not invent record counts, formula results, API keys, or secret personal access tokens. This is not a live Airtable sync and not a billing estimate.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Base inventory (table stubs, field cues, relation notes) I lock: [Inventory]
- Airtable / Interface version notes I lock: [Version]
- Project or workspace label I may quote (or UNKNOWN): [Workspace]
- Required names I may quote (or UNKNOWN): [SpecNames]
- Table names already present (or UNKNOWN): [TableNames]
- Field cues already present (or UNKNOWN): [FieldCues]
- Relation notes already present (or UNKNOWN): [RelationNotes]
- Words I must not use: [Banned]
- What I must never invent (record counts, formula results, API keys, or secret personal access tokens): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TableNames, FieldCues, RelationNotes, Lang. Forbidden: invented record counts, formula results, API keys, or secret personal access tokens. Banner: this is not a live airtable sync and not a billing estimate.
2. Field map table: one row per Inventory table stub or field cue. Missing relation notes write NOT IN INPUTS. Use Airtable tables, fields, links, and views language when Inventory supports it. Quote TableNames and FieldCues only when present. Never print record-count VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print formula-result or API-key VALUES not in Inventory.
4. Version lock: print Version. Refuse Airtable features newer than Version if Version is named.
5. Refuse list: inventing record counts, inventing formula results, inventing API keys, inventing secret personal access tokens.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Map from Inventory only. No invented record-count VALUES. Teach Airtable field mapping, not a generic Notion or ClickUp property swap.
- Honor Version. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Airtable Field Map from Base Inventory (No Invented Record Counts) with example still - Result

Examples

Example Input

Inventory: table Harbor Quay Orders as pasted field cue Status single select as pasted relation note links to Customers as pasted; table River Ops Customers as pasted field cue Email as pasted. Record count invent NONE. Formula invent NONE.
Version: Airtable web 2024 as pasted (do not invent unreleased AI field writer)
Workspace: Harbor Quay Ops Base as pasted
SpecNames: Orders as pasted; Customers as pasted. PersonalAccessToken UNKNOWN.
TableNames: Orders as pasted; Customers as pasted. Shipments UNKNOWN.
FieldCues: Status single select as pasted; Email as pasted. Created time UNKNOWN.
RelationNotes: links to Customers as pasted. rollup order total NOT IN INPUTS.
Banned: guaranteed sync, record invent, formula invent, token invent
Never: invent record counts, invent formula results, invent API keys, invent secret personal access tokens
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: table Harbor Quay Orders field cue Status single select relation note links to Customers; table River Ops Customers field cue Email. Record count invent NONE. Formula invent NONE. Version Airtable web 2024. Workspace Harbor Quay Ops Base. SpecNames Orders; Customers; PersonalAccessToken UNKNOWN. TableNames Orders; Customers; Shipments UNKNOWN. FieldCues Status single select; Email; Created time UNKNOWN. RelationNotes links to Customers; rollup order total NOT IN INPUTS. Lang English. Banner: not a live Airtable sync; not a billing estimate. Forbidden: invented record counts, formula results, API keys, secret personal access tokens, guaranteed sync, record invent, formula invent, token invent.

2. Field map.
1. Harbor Quay Orders | TableNames Orders as pasted | FieldCues Status single select as pasted | RelationNotes links to Customers as pasted | record count NONE | formula NONE | Airtable field map only.
2. River Ops Customers | TableNames Customers as pasted | FieldCues Email as pasted | RelationNotes beyond links to Customers NOT IN INPUTS | record count NONE | formula NONE.
PersonalAccessToken UNKNOWN so write PersonalAccessToken NOT IN INPUTS. Shipments not invented beyond TableNames.

3. Spec name set. Orders; Customers as SpecNames. PersonalAccessToken UNKNOWN so write PersonalAccessToken NOT IN INPUTS. No record-count VALUES beyond Inventory. No third table invented.

4. Version lock. Airtable web 2024 as pasted. Unreleased AI field writer not used. Interface packs NOT IN INPUTS.

5. Refuse. Record invent: refused. Formula invent: refused. API-key invent: refused. Token invent: refused. Guaranteed sync: refused.

6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: PersonalAccessToken decision, Shipments TableNames, Created time FieldCues, rollup order total RelationNotes, Interface packs list if any.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...