Data Fields
Data Fields
Every CRM and data tool has its own idea of what a field should be called. HubSpot calls a person's job title jobtitle. Pipedrive calls it job_title. Salesforce calls it Title. And when your team creates a custom field in HubSpot — say, nps_score or customer_tier — no other system has ever seen it before.
Data Fields is where you make sense of all of that. Outrun automatically discovers fields from your connected sources and brings them here so you can name them, and start using them everywhere.
How fields get discovered
When Outrun syncs data from a source, it records every field it sees. Fields that Outrun already understands natively (like emailAddress or firstName) flow straight through. Everything else appears in Data Fields as a candidate for you to review.
You don't need to do anything to trigger this — it happens automatically as your sources sync.
Field types
Every field has a type that tells you where it came from.
Enhanced
Fields Outrun natively understands — firstName, emailAddress, jobTitle and others. These flow consistently through your workspace and into all your destinations without any setup.
No action required. These are already working.
Platform
Standard fields from your source platform — like HubSpot's own hs_lead_status. Outrun can see them, but they need a name before they can flow to destinations.
Give it a name to make it available workspace-wide.
Custom
Fields you created yourself in your source system — like a custom nps_score or customer_tier field in HubSpot. These are unique to your workspace.
Name it so Outrun can use it across your workspace and destinations.
The review workflow
Needs Review
New Platform and Custom fields land here. Each card shows:
- The field's source name (e.g.
nps_score) - Where it came from (e.g. HubSpot · People)
- Its type badge
- Example values from your real data
Click Review → to open the naming panel.
Naming a field
When you name a field, you're telling Outrun what to call it across your workspace. Use camelCase (e.g. npsScore, customerTier).
Outrun may have already suggested a name based on what the field looks like. You can accept the suggestion or type your own.
Duplicate names
If another field in your workspace already uses the name you've chosen, Outrun will warn you. The last save wins — though we do retain the full history in your data stream, so nothing is lost.
Reserved names
Outrun's built-in field names (like emailAddress or firstName) are reserved. You can't map a custom field to one of these names — doing so would overwrite the data Outrun already has for that field. Choose a different name instead.
Update existing records
When you name a field, you can choose to Update existing records. This triggers a backfill that applies the new name to data already synced from that source. Without it, the name only applies to new data going forward.
Dismissing a field
If a field isn't relevant to your workspace, you can dismiss it. Dismissed fields move to the Dismissed tab and stop appearing in Needs Review. You can always re-review them later.
Enhanced tab
Once a field is named, it moves to the Enhanced tab. Outrun now understands it workspace-wide — it can flow to destinations, appear in filters, and be referenced by AI agents.
This tab also shows Outrun's built-in fields at the bottom. These are the fields Outrun natively understands from your connected sources. They're already enhanced — no action needed — but they're listed here so you can see exactly what Outrun knows about your data.
Destinations
When you configure a destination, you choose which fields flow to it. Named (Enhanced) fields appear in the destination's field list. Unnamed fields don't appear — they stay in your workspace but don't sync until you name them.
This gives you precise control: you decide exactly which fields cross into each destination.
Frequently asked questions
What happens to data from unnamed fields?
It's stored in your workspace. Outrun never discards data — it just waits in the stream until you name the field. Once named, you can backfill all existing records.
Can I rename a field after it's been named?
Yes. Open the field from the Enhanced tab and update the name. We recommend also backfilling existing records when you do this, so everything is consistent.
Why does Outrun suggest names automatically?
Outrun uses AI to look at the field name, its values, and context from your other fields to suggest a camelCase name. These are suggestions only — you're always in control.
I dismissed a field by mistake. Can I undo it?
Yes. Go to the Dismissed tab, find the field, and click Review to reopen it.
Next steps
Configure destinations
Choose which named fields flow to each of your destinations.
View Destinations →Understand standardization
Learn how Outrun transforms raw source data into consistent objects.
Standardization →