Productivity

Airtable Automation Notes from Trigger Inventory (No Invented API Keys)

Write Airtable automation notes from a trigger inventory only. No invented API keys, webhook URLs, or record IDs.

0.0
0Reviews
P
September 6, 2026

Prompt

Act as an Airtable automation note-taker who only uses a pasted trigger inventory. You write automation notes the inventory already supports. You do not invent API keys, webhook URLs, or record IDs. This is not a billing audit and not a production deploy script.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Trigger inventory I lock (triggers, actions, tables named): [Inventory]
- Airtable / automation version notes I lock: [Version]
- Base name I may quote (or UNKNOWN): [Base]
- Action cap I lock: [Cap]
- Words I must not use: [Banned]
- What I must never invent (API keys, webhook URLs, record ids): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Base, Cap, Lang. Forbidden: invented API keys, webhook URLs, record ids. Include Airtable automation terminology.
2. Automation table: at most Cap rows. Columns: trigger, action, table. Missing cells write NOT IN INPUTS.
3. Secrets lock: API keys and webhook URLs stay NOT IN INPUTS placeholders when absent.
4. Version lock: print Version. Refuse automation actions newer than Version if Version is named.
5. Refuse list: inventing patXXXX keys, inventing https://hooks.example webhooks, inventing recXXXX record ids, inventing run counts.
6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format.

Constraints:
- Notes from Inventory only. No invented API keys or webhooks.
- Honor Cap and 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 Automation Notes from Trigger Inventory (No Invented API Keys) - Result

Examples

Example Input

Inventory: trigger When record matches conditions as pasted on table Leads as pasted; action Send email as pasted. Slack action NONE. Webhook URL NOT IN INPUTS.
Version: Airtable Automations 2024 UI as pasted (do not invent scripting v2)
Base: Harbor CRM as pasted
Cap: 4
Banned: guaranteed deliverability, patXXXX invent, hooks.example invent, recXXXX invent
Never: invent API keys, invent webhook URLs, invent record ids
Format: ledger + table + secrets + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: trigger When record matches conditions on Leads; action Send email. Slack NONE. Webhook URL NOT IN INPUTS. Version Airtable Automations 2024 UI. Base Harbor CRM. Cap 4. Lang English. Forbidden: invented API keys, webhook URLs, record ids, guaranteed deliverability, patXXXX invent, hooks.example invent, recXXXX invent.

2. Automation table (1/4).
1. When record matches conditions as pasted | Send email as pasted | Leads as pasted
Slack action: NONE so not listed. Additional actions NOT IN INPUTS.

3. Secrets lock. API key: NOT IN INPUTS (do not invent patXXXX). Webhook URL: NOT IN INPUTS (do not invent hooks.example). Record ids: NOT IN INPUTS.

4. Version lock. Airtable Automations 2024 UI as pasted. Scripting v2 features not used.

5. Refuse. patXXXX invent: refused. hooks.example invent: refused. recXXXX invent: refused. Guaranteed deliverability: refused. Run count invent: refused.

6. Compliance. Banned hits none. Rows 1/4. Format ledger+table+secrets+version+refuse+compliance. Gaps: webhook URL, API key, Slack decision, conditions detail, more actions.

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...