Zapier Tables Record Map from Base Inventory (No Invented Row Counts)
PpromptstudioยทSep 17, 2026
No rating
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.
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.