Spreadsheet or database tool
Not a CRM - fails on core objects, pipeline stages, status, resolution, value, scope of work, expected close date, actual close date, opportunity owner, linked buyer, record preservation, email sync, schedulable activity types, opportunity reporting
Core objects
Not at all
Airtable ships no predefined record types. Its field reference lists only generic types (text, select, date, link-to-record, etc.); Opportunity/Person/Organization/Activity are not vendor object types. The published Sales CRM template is duplicated into the buyer's own workspace as an editable base, not a maintained product.
Source: https://airtable.com/developers/web/api/field-model, https://www.airtable.com/templates/sales-crm/expaRDyCNa7YNZQoO
Verification: Verified
Pipeline stages
Not at all
No shipped pipeline or stage object exists. A buyer builds an ordered stage sequence themselves using a generic Single select field inside a table they design, as shown in the duplicated Sales CRM template.
Source: https://airtable.com/developers/web/api/field-model, https://www.airtable.com/templates/sales-crm/expaRDyCNa7YNZQoO
Verification: Verified
Status
Not at all
No shipped opportunity object exists to carry an open/closed value. Any open-vs-closed field is entirely buyer-built using a generic Single select or Checkbox field type.
Source: https://airtable.com/developers/web/api/field-model
Verification: Verified
Resolution
Not at all
No shipped won/lost field or stage-metadata mechanism exists on any object, because no opportunity object ships. Buyers add a generic Single select field to record won/lost.
Source: https://airtable.com/developers/web/api/field-model
Verification: Verified
Value
Not at all
The Currency field type is a generic number format, not a field shipped on any opportunity object. A buyer adds it to a table they design themselves; nothing money-related ships attached to a deal record.
Source: https://support.airtable.com/docs/number-based-fields-in-airtable
Verification: Verified
Scope of work
Not at all
No shipped line-item, product, or description structure exists on any opportunity object, since no such object ships. Any representation of what is being sold is buyer-built from generic fields or linked tables.
Source: https://airtable.com/developers/web/api/field-model
Verification: Verified
Expected close date
Not at all
Date is a generic field type, not a native system field tied to an opportunity object. A buyer adds and labels a date field themselves, which the ruling treats as buyer-built, never Partial.
Source: https://airtable.com/developers/web/api/field-model
Verification: Verified
Actual close date
Not at all
Same generic Date field type applies; no native system field records when a deal actually closed. Buyer-built custom date fields do not qualify under the gate ruling.
Source: https://airtable.com/developers/web/api/field-model
Verification: Verified
Opportunity owner
Not at all
Collaborator is a generic field type available on any table; no opportunity object ships with an owner field already attached. A buyer must add and populate it themselves.
Source: https://airtable.com/developers/web/api/field-model
Verification: Verified
Linked buyer
Not at all
Link to another record is a generic field type usable between any two tables a buyer creates; no shipped opportunity object ships pre-linked to a person record.
Source: https://airtable.com/developers/web/api/field-model
Verification: Verified
Record preservation
Not at all
No shipped opportunity or status object exists, so there is no vendor-documented behavior for how closed records are retained or fed into reporting; the entire concept is buyer-built.
Source: https://airtable.com/developers/web/api/field-model
Verification: Verified
Structured lost reasons
In part
No shipped lost-reason field exists, but a buyer-built Single select field is natively countable through Airtable's grouping and summary bar, meeting the buyer-built-but-countable exception.
Source: https://airtable.com/developers/web/api/field-model
Verification: Verified
Email sync
Not at all
No native mailbox connection exists. Airtable's own Emailed Data sync only ingests CSV/xlsx attachments sent to a generated address, not email content; its Gmail integration runs through third-party Zapier automations, not a native sync.
Source: https://support.airtable.com/docs/airtable-sync-integration-emailed-data, https://www.airtable.com/integrations/gmail, https://support.airtable.com/docs/airtable-sync-integrations-overview
Verification: Verified
Calendar sync
In part
Airtable's native Google Calendar sync integration is documented as one-way only: it pulls calendar events into an Airtable table, and the vendor states changes made in Airtable cannot sync back to Google Calendar.
Source: https://support.airtable.com/docs/airtable-sync-integration-google-calendar
Verification: Verified
Schedulable activity types
Not at all
No shipped activity object or fixed set of activity types (call, meeting, task) exists. Any scheduling and type classification is buyer-built from generic fields and views.
Source: https://airtable.com/developers/web/api/field-model
Verification: Verified
Opportunity reporting
Not at all
No native stage-to-stage conversion rate, win rate, or revenue forecast exists, because no opportunity, stage, status, or value object ships for such metrics to be calculated against.
Source: https://airtable.com/developers/web/api/field-model
Verification: Verified