Field Mapping & Schema Discovery

Overview

Field mapping routes incoming webhook data into your Commander Tables automatically. Instead of manually copying data from events, you map source fields (from the webhook payload) to destination columns (in your table), and Commander writes the data for you on every incoming event.

Schema Discovery

Before you can map fields, you need a destination table. Schema Discovery analyzes your recent webhook events and suggests table columns based on the data you're receiving.

How It Works

1. Commander looks at your last 50 webhook events
2. Extracts all unique top-level fields from the payloads
3. Infers the column type from sample values
4. Shows you a table of suggested columns

Suggested Column Types

Type	Detected When
text	String values (default)
number	Numeric values or numeric strings
boolean	True/false values
date	ISO-formatted date strings
json	Objects or arrays

Discovery Table

Each discovered field shows:

Column	Description
Checkbox	Toggle whether to include this field
Field	The field name from the webhook payload
Type	Inferred column type (text, number, boolean, date, json)
Freq	How often this field appears across your events (as a percentage)
Sample	Example values from recent events

Creating a Table

1. Review the suggested fields and uncheck any you don't need
2. Edit the Table Name (pre-filled as "{Connection Name} Data")
3. Click Create Table

The table is created in Commander with the selected columns, ready for field mapping.

If you haven't received any events yet, Schema Discovery shows: "No events received yet. Send a webhook to this connection first, then we can analyze the payload and suggest table columns."

Setting Up Field Mapping

Prerequisites

You need:

• A webhook connection with at least a few events received
• A destination table in Commander (create one via Schema Discovery or manually)
• The destination table selected in your connection's Settings

Auto-Detect

Click Auto-Detect to let Commander match source fields to table columns automatically:

• Exact match — field names that match column names (case-insensitive)
• Normalized match — underscores and dashes are removed for comparison (e.g., first_name matches firstname)

Auto-Detect shows a toast with how many fields were matched. You can then adjust any mappings manually.

Manual Mapping

The mapping editor shows a 4-column grid:

Column	Description
Source Field	Field name from webhook payload (monospace)
Arrow	Visual indicator showing the mapping direction
Table Column	Dropdown to select the destination column, or "Skip" to ignore
Status	Green "mapped" badge or gray "skipped" badge

Source fields are extracted from your last 10 webhook events. For each source field, select the destination column from the dropdown, or choose "-- Skip --" to ignore it.

Preview

Click the Preview toggle to see how your mapping will transform real data. Preview shows the last 3 events as they would be written to your table:

source_field: value  →  column_name: value

This helps you verify your mapping is correct before saving.

Saving

Click Save Mapping when you're happy with the configuration. The mapping is applied to all future incoming events.

Mapping Results

After mapping is configured, each incoming event shows mapping results in its expanded details:

• Mapped fields — fields that were successfully written to your table
• Failed mappings — fields that couldn't be mapped, with the reason (e.g., type mismatch, missing column)

No Table Selected

If you haven't selected a destination table, the mapping editor shows: "Set a destination table to configure field mapping. Go to Settings to choose a destination table."

Tips

• Start with Schema Discovery if you're not sure what columns to create — let the data tell you
• Use Auto-Detect first, then adjust manually for any fields it couldn't match
• Check the Freq column in Schema Discovery — fields that appear in less than 50% of events might be optional or event-type-specific
• Use Preview to verify your mapping before saving, especially if you have complex payloads
• If a mapping fails, check the event details for the specific error — common issues are type mismatches (sending text to a number column)