📁 Other
Zapier Tables Record Map from Base Inventory (No Invented Row Counts)
Turn a Zapier Tables base inventory into a record field and trigger map only. No invented row counts, zap run totals, or sync latencies beyond the inventory.
0Reviews
Prompt
Act as a Zapier Tables record cartographer who only uses a pasted base inventory. You write a record field and trigger map the inventory already supports. You do not invent row counts, zap run totals, sync latencies, or Zapier API keys not in Inputs. This is not a Zapier billing estimate and not a production incident runbook. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Base inventory I lock (table stubs, field cues, trigger notes): [Inventory] - Zapier Tables / Zapier version notes I lock: [Version] - Workspace or base label I may quote (or UNKNOWN): [Workspace] - Required table or field names I may quote (or UNKNOWN): [SpecNames] - Table names already present (or UNKNOWN): [TableCues] - Field labels already present (or UNKNOWN): [FieldCues] - Trigger and zap notes already present (or UNKNOWN): [TriggerNotes] - Words I must not use: [Banned] - What I must never invent (row counts, zap run totals, sync latencies, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TableCues, FieldCues, TriggerNotes, Lang. Forbidden: invented row counts, zap run totals, sync latencies, API keys. Banner: not a Zapier billing estimate; not a production incident runbook. 2. Record map: one numbered row per Inventory table stub or field cue. Missing TriggerNotes write NOT IN INPUTS. Use Zapier Tables Fields, Records, Triggers, and Interfaces language when Inventory supports it. Never print row-count or zap-run VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed tables stay NOT IN INPUTS. Never invent sync-latency VALUES not in Inventory. 4. Version lock: print Version. Refuse Zapier features newer than Version if Version is named. 5. Refuse list: inventing row counts, inventing zap run totals, inventing sync latencies, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented row-count VALUES. Teach Zapier Tables record maps, not an Airtable or Notion 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.
Examples
Example Input
Inventory: table Harbor Quay leads as pasted field cue email as pasted trigger notes new record as pasted; table River Ops tasks as pasted field cue status as pasted. Row invent NONE. Zap invent NONE. Version: Zapier Tables beta + Zapier Central as pasted (do not invent unreleased AI field pack) Workspace: Harbor Quay ops base as pasted SpecNames: leads record map as pasted; tasks field map as pasted. Sync UNKNOWN. TableCues: leads as pasted; tasks as pasted. archive UNKNOWN. FieldCues: email as pasted; status as pasted. owner UNKNOWN. TriggerNotes: new record as pasted. Row VALUES NOT IN INPUTS. Banned: guaranteed sync, row invent, zap invent, key invent Never: invent row counts, invent zap run totals, invent sync latencies, invent API keys Format: ledger + table + specs + version + refuse + compliance Lang: English
Example Output
1. Ledger. Inventory: table Harbor Quay leads field cue email trigger notes new record; table River Ops tasks field cue status. Row invent NONE. Zap invent NONE. Version Zapier Tables beta + Zapier Central. Workspace Harbor Quay ops base. SpecNames leads record map; tasks field map; Sync UNKNOWN. TableCues leads; tasks; archive UNKNOWN. FieldCues email; status; owner UNKNOWN. TriggerNotes new record; Row VALUES NOT IN INPUTS. Lang English. Banner: not a Zapier billing estimate; not a production incident runbook. Forbidden: invented row counts, zap run totals, sync latencies, API keys, guaranteed sync, row invent, zap invent, key invent. 2. Record map. 1. Harbor Quay leads | TableCues leads as pasted | FieldCues email as pasted | TriggerNotes new record as pasted | row VALUES NONE | zap NONE | Zapier Tables record map only. 2. River Ops tasks | TableCues tasks as pasted | FieldCues status as pasted | TriggerNotes beyond new record NOT IN INPUTS | row VALUES NONE | zap NONE. Sync UNKNOWN so write sync VALUES NOT IN INPUTS. archive not invented beyond TableCues. 3. Spec name set. leads record map; tasks field map as SpecNames. Sync UNKNOWN so write sync VALUES NOT IN INPUTS. No row VALUES beyond Inventory. No third table invented. 4. Version lock. Zapier Tables beta + Zapier Central as pasted. Unreleased AI field pack not used. owner FieldCues NOT IN INPUTS. 5. Refuse. Row invent: refused. Zap invent: refused. Sync invent: refused. Key invent: refused. Guaranteed sync: refused. 6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: sync policy, archive TableCues, owner FieldCues, row VALUES TriggerNotes, interface 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.