Airtable Destination

Overview

The Airtable destination writes evaluation results to your Airtable Contacts and Companies tables. TrailSpark maps scores, reasoning, and evaluation dates to fields you specify in your Airtable base, and optionally pushes buying-group coverage data when you enable that section.

Prerequisites

• Airtable integration connected with table mapping configured
• Fields created in your Airtable Contacts table for TrailSpark data
• Admin or Owner role in TrailSpark

Fields in Airtable

Create these fields on your Contacts table:

For company propensity, create on your Companies table:

To store the ICP or Score status on Contacts too, add matching fields to your Contacts table.

Buying-group fields are documented below — add them only if you plan to use that feature.

Configuration

Go to Settings > CRM Integration > Destinations tab.

Destination Settings

• Send Evaluations to Airtable -- Toggle to enable/disable the destination
• Airtable Integration -- Select which connected Airtable instance to use (auto-selected if only one exists)
• Create Records if Not Found -- When enabled, creates new Contact records if no match exists. Filter by score level (Hot, Warm, Cold)

Contact Field Mapping

Map three required fields to your Airtable Contacts table:

TrailSpark loads your Airtable field metadata automatically. Select fields from the dropdown. If a previously mapped field no longer exists in Airtable (e.g., it was renamed or deleted), the mapping resets to blank.

Company Propensity Score

The propensity score card configures where account-level propensity (high/medium/low) is written:

• Company Propensity Field (primary) -- Written to the Companies table when a linked company exists
• Contact Propensity Field (fallback) -- Written to the Contacts table when no company is linked

Both fields are optional.

ICP

The ICP card configures where the name of the ICP each account was scored against is written on the Companies table. It travels on the same account-level sync as the propensity score, so downstream automations can branch on which ICP produced a score. The field is optional. When an account was scored without a specific ICP, nothing is written.

AI reasoning

The AI reasoning card configures where each account's plain-language explanation is written on the Companies table — the same narrative you see on the account in TrailSpark and in Slack alerts. It travels on the same account-level sync as the propensity score and always describes that score, so the two can never disagree.

Map it when you want the "why" behind a score readable directly in your base — on the record, in a grid view, or in an interface. This is separate from the Contact-level Reasoning Field, which explains an individual person's score; map either, both, or neither.

The field is optional. When an account's evaluation has no explanation, nothing is written — your existing field value is left untouched rather than blanked. When an account's score is retired, the last explanation stays in place and Score status flips to retired.

Score status

The Score status card configures where each account's score status is written on the Companies table (and, on the Contact mapping, on Contacts). It travels on the same sync as the propensity score and takes one of three values:

• current -- the pushed propensity score reflects the account's live standing.
• retired -- the account no longer matches the ICP it was scored against, so its last pushed score is stale and should no longer be trusted.
• not_evaluated -- the account has no evaluation yet.

When an account leaves the ICP it was scored against, TrailSpark promptly updates this field to retired in Airtable (for destinations that map it) — you don't have to wait for the account's next sync. Without the field, a retired account simply stops receiving score updates and its last pushed score silently goes stale, so an automation cannot tell a fresh score from a stale one. Map it to let automations suppress or flag scores that are no longer current. The field is optional; unmapped, nothing is written.

Account Fields

The Account Fields card writes company data into fields you choose in your Airtable base. All fields are optional and only write when you map them. Unlike the Salesforce and HubSpot destinations, each row here also has its own source choice:

• Best known (CRM + enrichment) (default) -- TrailSpark's best-known value for the field: your connected CRM's own value when it has one, filled in with data from your connected enrichment providers when it doesn't. This is the same value shown on the account page.
• Enrichment data -- the raw value from your connected enrichment providers only (for example Clay or Reo.dev), regardless of what your CRM has for that field.

This writes on the same account-level sync that pushes propensity and buying-group coverage, for accounts linked to a record in your Companies table. A field is left blank if its chosen source has no value for that account; it is never filled from the other source.

Custom enrichment fields

If your enrichment provider sends fields beyond the standard five and you've turned them on under Enriched fields (see Enrichment Rules & Budget Caps), each active field gets its own extra row on this card, using the label you gave it. Map it to a field in your Companies table the same way as the standard fields -- custom fields are always sourced from enrichment data (there's no Best known / Enrichment data choice, since there's no CRM value to blend with). Turning a field off later doesn't remove an existing mapping -- the row is kept and marked "No longer active," and it stops writing until the field is reactivated.

Buying Group Fields

Enable the Push buying-group fields toggle to push coverage data alongside evaluation scores. All fields in this section are optional — they write only when you map them.

Account properties

For what these values mean, see Account coverage.

How Record Matching Works

TrailSpark matches records by email address:

1. Looks up the contact's email in your Airtable Contacts table
2. If found, updates the existing record with evaluation results
3. If not found and Create Records is enabled, creates a new Contact record
4. For propensity and buying-group fields, follows the Contact → Company linked record to find the associated company

Troubleshooting

Next Steps

• Salesforce Destination
• HubSpot Destination
• Account coverage -- Understand the values being pushed