Operational map
Use the operational map to understand who creates your records and who works on them afterward. It connects people, automations, and API sources through their activity on the same records. The date range above the map sets the observation you are reading.
Find the sources behind the work
Hover over a source for a quick summary, then click it to inspect its insights and connections. Look for who creates records, which fields a source regularly changes, and whether its edits tend to follow another source's changes.
A creation insight such as "Main source creating" identifies where a table's new records usually originate. The info icon gives the count and share of observed creations. "Creates 100%" means all observed creations in that table and period, rather than every record currently in the table.
Use Explore connections to focus on that source's relationships. This is useful when a busy map makes it hard to follow one person's or automation's activity. All sources returns to the broader view.
Study one table's lifecycle
To study how records in a particular table move between sources, open Tables, choose Hide all, then enable just that table. The search box helps find it in a large base. Searching narrows the choices; selecting the table changes the map.
With one table visible, follow its creators and inspect their connections to later editors. Useful questions include:
- Where do new records enter, and who picks them up afterward?
- Which fields do people change, and which do automations or API sources change?
- Do the same sources repeatedly work on the same records or fields?
Click a connection to read the patterns and their supporting record counts. This can reveal a recurring sequence, such as one source updating a field before another changes a different field. It gives you a starting point for understanding the table's lifecycle, rather than a complete path that every record follows.
Table filtering narrows the map's connections, connection insights, and example records. A source's own creation and field insights can still mention other tables: those describe its broader activity. Connection strength may become unavailable in a filtered view because the saved workload totals cannot be separated by table.
Keep all source types visible when studying the whole lifecycle. Hiding people, automations, or API sources removes their connections from the view. Use Show all in Tables to restore the broader map.
Interpret a connection
A shared-record connection means both sources worked on the same records. A same-field pattern means their work overlaps on particular fields. A "creates, then edits" or "changes, then changes" insight adds observed order. Order alone does not establish that one action triggered the next; an external process or another source may explain the sequence.
Connection strength helps you find relationships worth inspecting. It reflects how much work the sources share, with same-field changes and consecutive edits contributing where available. Small samples carry less weight. A strong connection does not measure work quality, speed, or whether an automation is configured correctly.
Read each pattern's record count alongside its wording. Several patterns may involve the same records, so their counts should not be added together. Sparse or varied activity may appear only as shared-record activity, or produce no repeated pattern.
Check the records behind an insight
Expand Example records in connection details to open supporting records in Airtable. For the captured sequence of changes, use Activity and changelog. Examples help you investigate a pattern; they are a sample of its evidence.
Use the map to choose what to investigate or improve: an unexpected creator, repeated edits to the same field, or a recurring transition between sources. Confirm the record history and the intended workflow before changing an automation or assigning ownership.
The map reflects captured activity within your observation scope. A missing connection is not proof that two sources never interact. Moving dots and animations illustrate activity; they are not a live replay or a measure of elapsed time.