30 Claude Prompts That Build Airtable Bases

You are an engineering program manager who designs Airtable bases for agile teams. <context> I need a ready-to-build Airtable base spec to run sprints, tasks, and bugs for a software team, self-contained so I can recreate it in Airtable. </context> <inputs> - Team and product: [ONE LINE] - Task statuses: [E.G. BACKLOG, TODO, IN PROGRESS, REVIEW, DONE] - Sprint length: [E.G. 2 WEEKS] - What I track per task: [E.G. STORY POINTS, PRIORITY, ASSIGNEE, EPIC] - Reports I need: [E.G. SPRINT BURNDOWN INPUTS, WORKLOAD PER PERSON] </inputs> <task> Design tables: Tasks, Sprints, Epics, Team. Give each table its primary field and every field with its exact Airtable type (single/multiple select with options, number, date, long text, linked record naming the target table, lookup, rollup, formula, checkbox, user). Link Tasks to Sprints, Epics, and Team (assignee). Add a formula for whether a task is blocked or overdue, a rollup of total story points per sprint, and a rollup of open points per assignee. Specify views: a Kanban by status, a grid grouped by sprint, a grid grouped by assignee, and a view filtered to the current sprint. Then 3 automations (e.g. set Done date when status is Done, notify assignee on assignment). </task> <constraints> - Use only real Airtable field types and valid formula syntax; single-quote string literals. - Linked fields name the exact target table; each table has one primary field. - Spell out every field; keep flat columns CSV-importable. </constraints> <format> Return a Markdown table per table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations, then the build order. </format>

You are an agency delivery lead who designs Airtable bases for managing client projects. <context> I need a complete Airtable base spec that tracks client projects, deliverables, and time, self-contained and ready to rebuild in Airtable. </context> <inputs> - Types of projects we deliver: [E.G. BRANDING, WEB BUILD, CAMPAIGN] - Project phases: [E.G. KICKOFF, DISCOVERY, BUILD, REVIEW, LAUNCH] - How we bill: [HOURLY / FIXED] - What I track per deliverable: [E.G. OWNER, DUE DATE, STATUS, HOURS] - Reports I need: [E.G. OVERDUE DELIVERABLES, HOURS VS BUDGET] </inputs> <task> Design tables: Projects, Deliverables, Time Entries, Clients. Provide each table's primary field and every field with its exact Airtable type (single/multiple select with options, date, number, currency, linked record naming the target table, lookup, rollup, formula, checkbox, user). Link Deliverables and Time Entries to Projects, and Projects to Clients. Add a formula flagging overdue deliverables, a rollup of logged hours per project, and a formula for percent-of-budget-used from logged hours and the budget. Specify views: a Kanban of deliverables by status, a calendar of due dates, a grid grouped by project, and a view filtered to over-budget projects. Then 3 automations. </task> <constraints> - Only real Airtable field types and valid formula syntax; single-quote string literals. - Linked fields name their exact target table; one primary field per table. - No filler fields; keep flat columns CSV-importable. </constraints> <format> Return one Markdown table per Airtable table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations. Close with the build order. </format>

You are a product operations lead who designs Airtable bases for roadmapping. <context> I need a ready-to-build Airtable base spec to prioritize features and plan a roadmap by quarter, self-contained so I can recreate it fast. </context> <inputs> - Product: [ONE LINE] - Prioritization framework: [E.G. RICE, VALUE VS EFFORT] - Statuses: [E.G. IDEA, PLANNED, BUILDING, SHIPPED] - Timeframes: [E.G. QUARTERS OR MONTHS] - Reports I need: [E.G. ROADMAP BY QUARTER, TOP-SCORED FEATURES] </inputs> <task> Design tables: Features, Themes, Releases, Feedback. Give each table its primary field and every field with its exact Airtable type (single/multiple select with options, number, date, long text, linked record naming the target table, lookup, rollup, formula, checkbox, user). Link Features to Themes and Releases, and Feedback to Features. Add a formula for a RICE or value/effort score from the input fields, a rollup counting linked feedback per feature, and a formula for target quarter from the planned date. Specify views: a grid sorted by score, a Kanban by status, a timeline or calendar grouped by release, and a view grouped by theme. Then 3 automations (e.g. move to Shipped and set ship date on release). </task> <constraints> - Real Airtable field types and valid formula syntax only; single-quote string literals. - Linked fields name the exact target table; one primary field per table. - Spell out every field; keep flat columns CSV-importable. </constraints> <format> Return a Markdown table per table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations, then the build order. </format>

You are a marketing operations manager who designs Airtable bases for campaign execution. <context> I need a complete Airtable base spec to plan campaigns, their tasks, and channel budgets, self-contained and ready to build. </context> <inputs> - Campaign types: [E.G. PRODUCT LAUNCH, WEBINAR, SEASONAL PROMO] - Channels: [E.G. EMAIL, PAID, SOCIAL, EVENTS] - Task stages: [E.G. PLANNED, IN PROGRESS, BLOCKED, DONE] - What I track per campaign: [E.G. GOAL, BUDGET, START, END, OWNER] - Reports I need: [E.G. SPEND VS BUDGET, TASKS DUE THIS WEEK] </inputs> <task> Design tables: Campaigns, Tasks, Channels, Assets. Provide each table's primary field and every field with its exact Airtable type (single/multiple select with options, date, currency, number, linked record naming the target table, lookup, rollup, formula, checkbox, user, URL). Link Tasks and Assets to Campaigns, and Campaigns to Channels. Add a formula flagging tasks due this week, a rollup of total planned spend per campaign, and a formula for percent-of-budget-spent. Specify views: a Kanban of tasks by stage, a calendar of campaign start and end dates, a grid grouped by channel, and a view filtered to over-budget campaigns. Then 3 automations. </task> <constraints> - Only real Airtable field types and valid formula syntax; single-quote string literals. - Linked fields name their exact target table; one primary field per table. - No vague fields; keep flat columns CSV-importable. </constraints> <format> Return one Markdown table per Airtable table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations. End with the build order. </format>

You are a strategy operations lead who designs Airtable bases for company-wide planning. <context> I need a ready-to-build Airtable base spec that connects objectives, key results, and the initiatives that drive them across teams, self-contained and ready to rebuild. </context> <inputs> - Teams: [E.G. PRODUCT, MARKETING, SALES] - OKR cycle: [E.G. QUARTERLY] - Key result types: [E.G. METRIC TARGET, MILESTONE] - What I track per initiative: [E.G. OWNER, STATUS, DUE DATE] - Reports I need: [E.G. OKR PROGRESS, INITIATIVES AT RISK] </inputs> <task> Design tables: Objectives, Key Results, Initiatives, Teams. Give each table its primary field and every field with its exact Airtable type (single/multiple select with options, number, percent, date, linked record naming the target table, lookup, rollup, formula, checkbox, user). Link Key Results to Objectives, Initiatives to Key Results and Teams. Add a formula for key-result progress percent from current and target values, a rollup averaging key-result progress into objective progress, and a formula flagging initiatives that are off-track (past due and not done). Specify views: a grid grouped by team, a grid grouped by objective showing progress, a calendar of initiative due dates, and a view filtered to at-risk initiatives. Then 3 automations. </task> <constraints> - Real Airtable field types and valid formula syntax only; single-quote string literals. - Linked fields name the exact target table; one primary field per table. - Spell out every field; keep flat columns CSV-importable. </constraints> <format> Return a Markdown table per table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations, then the build order. </format>

You are an event operations producer who designs Airtable bases for conferences. <context> I need a complete, ready-to-build Airtable base spec to run a multi-track conference: sessions, speakers, rooms, and attendees, self-contained so I can recreate it in Airtable. </context> <inputs> - Event name, dates, venue: [DETAILS] - Number of tracks and rooms: [NUMBERS] - Session types: [E.G. KEYNOTE, TALK, WORKSHOP, PANEL] - Ticket tiers: [E.G. GENERAL, VIP, SPEAKER] - Reports I need: [E.G. SCHEDULE BY ROOM, SPEAKER CONFIRMATIONS] </inputs> <task> Design tables: Sessions, Speakers, Rooms, Attendees. Provide each table's primary field and every field with its exact Airtable type (single/multiple select with options, date, duration, number, linked record naming the target table, lookup, rollup, formula, checkbox, email, attachment). Link Sessions to Speakers and Rooms, and Attendees to a ticket tier. Add a formula for session end time from start and duration, a formula flagging room double-bookings on overlapping times, and a rollup counting sessions per speaker. Specify views: a calendar of sessions by time, a grid grouped by room, a grid filtered to unconfirmed speakers, and an attendees grid grouped by ticket tier. Then 3 automations (e.g. email speakers on confirmation). </task> <constraints> - Use only real Airtable field types and valid formula syntax; single-quote string literals. - Linked fields name the exact target table; each table has one primary field. - Spell out every field; keep flat columns CSV-importable. </constraints> <format> Return a Markdown table per table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations, then the build order. </format>

You are a wedding planner who designs Airtable bases to run events end to end. <context> I need a ready-to-build Airtable base spec to plan a wedding: guests, vendors, budget, and timeline, self-contained so I can recreate it quickly. </context> <inputs> - Date and venue: [DETAILS] - Guest count and groups: [E.G. FAMILY, FRIENDS, WORK] - Vendor categories: [E.G. CATERING, PHOTO, MUSIC, FLORALS] - Total budget: [AMOUNT] - Reports I need: [E.G. RSVP TOTALS, BUDGET REMAINING, PAYMENTS DUE] </inputs> <task> Design tables: Guests, Vendors, Budget Items, Timeline. Give each table its primary field and every field with its exact Airtable type (single/multiple select with options, date, currency, number, linked record naming the target table, lookup, rollup, formula, checkbox, email, phone). Link Budget Items to Vendors, and Guests to a group and a table assignment. Add a formula for balance due per vendor (cost minus paid), a rollup of total committed spend, a formula for budget remaining against the total, and a rollup counting confirmed RSVPs. Specify views: a grid grouped by RSVP status, a grid grouped by vendor category, a calendar of the day-of timeline, and a payments-due view. Then 3 automations (e.g. remind on upcoming vendor payment). </task> <constraints> - Real Airtable field types and valid formula syntax only; single-quote string literals. - Linked fields name their exact target table; one primary field per table. - No filler fields; keep flat columns CSV-importable. </constraints> <format> Return one Markdown table per Airtable table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations. Close with the build order. </format>

You are a demand-generation lead who designs Airtable bases for virtual events. <context> I need a complete Airtable base spec to run a webinar program: sessions, registrants, promotion tasks, and follow-up, self-contained and ready to build. </context> <inputs> - Webinar topic and format: [E.G. LIVE DEMO, PANEL] - Registration source fields: [E.G. UTM, COMPANY, ROLE] - Promotion channels: [E.G. EMAIL, PAID, PARTNERS] - What I track post-event: [E.G. ATTENDED, WATCHED REPLAY, MQL] - Reports I need: [E.G. REGISTRATION VS ATTENDANCE, LEADS BY SOURCE] </inputs> <task> Design tables: Webinars, Registrants, Promo Tasks, Follow-ups. Provide each table's primary field and every field with its exact Airtable type (single/multiple select with options, date, number, percent, linked record naming the target table, lookup, rollup, formula, checkbox, email, URL). Link Registrants, Promo Tasks, and Follow-ups to Webinars. Add a formula for attendance rate per webinar (attended divided by registered), a formula labeling each registrant's engagement (No-show / Attended / Watched Replay), and a rollup counting registrants per source. Specify views: a grid grouped by webinar, a Kanban of promo tasks by status, a grid filtered to no-shows needing follow-up, and a grid grouped by lead source. Then 3 automations. </task> <constraints> - Only real Airtable field types and valid formula syntax; single-quote string literals. - Linked fields name their exact target table; one primary field per table. - Spell out every field; keep flat columns CSV-importable. </constraints> <format> Return a Markdown table per table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations, then the build order. </format>

You are a workplace experience manager who designs Airtable bases for team offsites. <context> I need a ready-to-build Airtable base spec to plan a company offsite: attendees, travel, agenda, and budget, self-contained so I can recreate it fast. </context> <inputs> - Offsite dates and location: [DETAILS] - Number of attendees and teams: [NUMBERS] - Logistics tracked: [E.G. FLIGHTS, HOTEL, DIETARY, T-SHIRT SIZE] - Agenda blocks: [E.G. SESSIONS, MEALS, ACTIVITIES] - Reports I need: [E.G. TRAVEL STATUS, COST PER HEAD, AGENDA] </inputs> <task> Design tables: Attendees, Agenda, Logistics, Budget. Give each table its primary field and every field with its exact Airtable type (single/multiple select with options, date, time, currency, number, linked record naming the target table, lookup, rollup, formula, checkbox, email). Link Logistics and Budget items to Attendees or Agenda blocks. Add a formula flagging attendees missing travel details, a rollup of total cost, a formula for cost per head against the attendee count, and a formula for agenda-block end time from start and duration. Specify views: a grid grouped by team, a calendar of the agenda, a grid filtered to incomplete travel, and a budget grid grouped by category. Then 3 automations (e.g. remind attendees to submit travel). </task> <constraints> - Real Airtable field types and valid formula syntax only; single-quote string literals. - Linked fields name the exact target table; one primary field per table. - No vague fields; keep flat columns CSV-importable. </constraints> <format> Return one Markdown table per Airtable table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations. End with the build order. </format>

You are an event budget manager who designs Airtable bases to control event spend and vendors. <context> I need a complete Airtable base spec focused on managing vendors, contracts, payments, and budget for any event, self-contained and ready to build. </context> <inputs> - Event type and scale: [ONE LINE] - Vendor categories: [E.G. VENUE, CATERING, AV, DECOR, SECURITY] - Total budget: [AMOUNT] - Payment structure: [E.G. DEPOSIT PLUS BALANCE] - Reports I need: [E.G. SPEND BY CATEGORY, PAYMENTS DUE, VARIANCE] </inputs> <task> Design tables: Vendors, Contracts, Payments, Budget Categories. Provide each table's primary field and every field with its exact Airtable type (single/multiple select with options, currency, date, percent, linked record naming the target table, lookup, rollup, formula, checkbox, attachment). Link Contracts and Payments to Vendors, and Vendors to a Budget Category. Add a formula for balance owed per vendor (contract total minus payments), a rollup of actual spend per category, a formula for variance against the category budget, and a formula flagging payments due within a set window. Specify views: a grid grouped by category showing budget vs actual, a calendar of payment due dates, a grid filtered to unsigned contracts, and a payments-due view. Then 3 automations. </task> <constraints> - Only real Airtable field types and valid formula syntax; single-quote string literals. - Linked fields name their exact target table; one primary field per table. - Spell out every field; keep flat columns CSV-importable. </constraints> <format> Return a Markdown table per table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations, then the build order. </format>

You are a talent operations lead who designs Airtable applicant tracking systems. <context> I need a complete, ready-to-build Airtable base spec for an ATS that moves candidates through a hiring pipeline, self-contained so I can recreate it in Airtable. </context> <inputs> - Roles we hire for: [E.G. ENGINEERING, SALES, OPS] - Pipeline stages: [E.G. APPLIED, SCREEN, INTERVIEW, OFFER, HIRED, REJECTED] - Sources: [E.G. LINKEDIN, REFERRAL, JOB BOARD] - What I track per candidate: [E.G. RESUME, RATING, RECRUITER] - Reports I need: [E.G. PIPELINE BY STAGE, TIME-TO-HIRE, SOURCE MIX] </inputs> <task> Design tables: Candidates, Openings, Interviews, Recruiters. Provide each table's primary field and every field with its exact Airtable type (single/multiple select with options, date, rating, long text, linked record naming the target table, lookup, rollup, formula, checkbox, email, phone, attachment). Link Candidates to Openings and Recruiters, and Interviews to Candidates. Add a formula for days-in-stage, a formula for time-to-hire (hired date minus applied date), and a rollup counting active candidates per opening. Specify views: a Kanban by stage, a grid grouped by opening, a grid grouped by source, and a view filtered to candidates stalled beyond a threshold. Then 3 automations (e.g. email on stage change, flag stale candidates). </task> <constraints> - Use only real Airtable field types and valid formula syntax; single-quote string literals. - Linked fields name the exact target table; each table has one primary field. - Spell out every field; keep flat columns CSV-importable. </constraints> <format> Return a Markdown table per table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations, then the build order. </format>

You are an HR operations manager who designs Airtable bases to manage open requisitions. <context> I need a ready-to-build Airtable base spec that tracks job requisitions, approvals, and hiring targets, self-contained and ready to rebuild. </context> <inputs> - Departments hiring: [E.G. ENGINEERING, MARKETING] - Requisition statuses: [E.G. DRAFT, APPROVED, OPEN, ON HOLD, FILLED] - What I track per req: [E.G. TITLE, HIRING MANAGER, SALARY BAND, TARGET START] - Approval steps: [E.G. FINANCE, HEAD OF DEPT] - Reports I need: [E.G. OPEN REQS BY DEPT, TIME-OPEN, HEADCOUNT PLAN] </inputs> <task> Design tables: Requisitions, Departments, Hiring Managers, Approvals. Give each table its primary field and every field with its exact Airtable type (single/multiple select with options, currency, date, number, linked record naming the target table, lookup, rollup, formula, checkbox, user). Link Requisitions to Departments and Hiring Managers, and Approvals to Requisitions. Add a formula for days-open (today minus opened date, while unfilled), a formula for the salary band midpoint, and a rollup counting open reqs per department. Specify views: a grid grouped by department, a Kanban by status, a grid filtered to reqs awaiting approval, and a view sorted by days-open. Then 3 automations (e.g. notify approver, set opened date on Approved). </task> <constraints> - Real Airtable field types and valid formula syntax only; single-quote string literals. - Linked fields name their exact target table; one primary field per table. - No filler fields; keep flat columns CSV-importable. </constraints> <format> Return one Markdown table per Airtable table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations. Close with the build order. </format>

You are a hiring operations specialist who designs Airtable bases for structured interviews. <context> I need a complete Airtable base spec that captures structured interview scorecards and aggregates feedback per candidate, self-contained and ready to build. </context> <inputs> - Roles being assessed: [E.G. PM, ENGINEER] - Competencies scored: [E.G. PROBLEM SOLVING, COMMUNICATION, CULTURE] - Rating scale: [E.G. 1 TO 4] - Interviewers and rounds: [E.G. SCREEN, TECHNICAL, FINAL] - Reports I need: [E.G. AVERAGE SCORE PER CANDIDATE, HIRE RECOMMENDATIONS] </inputs> <task> Design tables: Candidates, Scorecards, Competency Scores, Interviewers. Provide each table's primary field and every field with its exact Airtable type (single/multiple select with options, rating, number, long text, linked record naming the target table, lookup, rollup, formula, checkbox, user). A Scorecard links a Candidate, an Interviewer, and a round; Competency Scores link to a Scorecard and a competency. Add a rollup averaging competency scores into a scorecard score, a rollup averaging scorecard scores per candidate, and a formula turning the average into a recommendation label (Strong Hire / Hire / No Hire). Specify views: a grid grouped by candidate, a grid grouped by interviewer, a grid filtered to incomplete scorecards, and a candidates grid sorted by average score. Then 3 automations. </task> <constraints> - Only real Airtable field types and valid formula syntax; single-quote string literals. - Linked fields name their exact target table; one primary field per table. - Spell out every field; keep flat columns CSV-importable. </constraints> <format> Return a Markdown table per table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations, then the build order. </format>

You are a sourcing lead who designs Airtable bases to build and nurture a talent pipeline. <context> I need a ready-to-build Airtable base spec to organize sourced candidates, outreach, and a warm talent pool, self-contained so I can recreate it fast. </context> <inputs> - Roles I source for: [E.G. SENIOR ENGINEERS, DESIGNERS] - Outreach stages: [E.G. SOURCED, CONTACTED, REPLIED, IN PROCESS, PASSIVE] - Channels: [E.G. LINKEDIN, GITHUB, REFERRAL, EVENT] - What I track: [E.G. SKILLS, LOCATION, SENIORITY, LAST CONTACT] - Reports I need: [E.G. OUTREACH DUE, RESPONSE RATE, POOL BY SKILL] </inputs> <task> Design tables: Prospects, Outreach, Skills, Roles. Give each table its primary field and every field with its exact Airtable type (single/multiple select with options, date, number, percent, linked record naming the target table, lookup, rollup, formula, checkbox, URL, email). Link Prospects to Skills and Roles, and Outreach to Prospects. Add a formula for days-since-last-contact, a formula flagging prospects due for a follow-up, and a rollup of response rate per channel (replied divided by contacted). Specify views: a Kanban by outreach stage, a grid grouped by skill, a grid filtered to follow-ups due, and a grid grouped by channel. Then 3 automations (e.g. create a follow-up task after outreach). </task> <constraints> - Real Airtable field types and valid formula syntax only; single-quote string literals. - Linked fields name the exact target table; one primary field per table. - No vague fields; keep flat columns CSV-importable. </constraints> <format> Return one Markdown table per Airtable table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations. End with the build order. </format>

You are a campus recruiting manager who designs Airtable bases for early-career hiring. <context> I need a complete Airtable base spec to manage university recruiting: schools, events, applicants, and offers, self-contained and ready to build. </context> <inputs> - Programs I recruit for: [E.G. SUMMER INTERNSHIP, NEW GRAD] - Schools targeted: [NAMES OR TIERS] - Event types: [E.G. CAREER FAIR, INFO SESSION, HACKATHON] - Applicant stages: [E.G. APPLIED, ASSESSMENT, INTERVIEW, OFFER, ACCEPTED] - Reports I need: [E.G. APPLICANTS PER SCHOOL, OFFER ACCEPTANCE RATE] </inputs> <task> Design tables: Applicants, Schools, Events, Offers. Provide each table's primary field and every field with its exact Airtable type (single/multiple select with options, date, number, percent, currency, linked record naming the target table, lookup, rollup, formula, checkbox, email, attachment). Link Applicants to Schools and Events, and Offers to Applicants. Add a formula for the applicant's current stage age in days, a rollup counting applicants per school, and a formula for offer acceptance rate per school (accepted divided by offers made). Specify views: a Kanban of applicants by stage, a grid grouped by school, a calendar of recruiting events, and a grid filtered to offers awaiting a response. Then 3 automations (e.g. remind on offer-response deadline). </task> <constraints> - Only real Airtable field types and valid formula syntax; single-quote string literals. - Linked fields name their exact target table; one primary field per table. - Spell out every field; keep flat columns CSV-importable. </constraints> <format> Return a Markdown table per table (Field | Type | Notes), then Views, a Formulas block with exact text, and Automations, then the build order. </format>