What happens after a run goes wrong, and what happens when you point a flow at eleven thousand old rows. Which errors get retried and which never will, how a queue looks different from a failure, and the backfill settings worth checking twice.
beginner
5:48
Map fields between Notion and Airtable
Two apps that disagree about what a field is. This one walks through select options that do not match, dates that look a day off, and the value translation table that fixes both without touching either database.
Video placeholder
A two column mapping panel filling the frame. Left column shows Notion properties, right column shows Airtable fields, four lines connecting them, one line highlighted amber with a small warning dot. No people, no logos beyond the app glyphs.
Chapters
From the transcript
The two apps disagree about what a field is, and that is the whole reason this video exists. Notion gives me a select called Stage. Airtable wants a single select called Status, and the option names do not match. Watch what happens when I drop Stage onto Status without thinking about it. The test row goes through and the run history flags it: option Ready for review does not exist in the destination. Nothing was written, which is exactly what you want. So I open the mapping and add a value translation. Ready for review becomes Ready. In progress becomes Doing. Everything else falls through to a default I set to Backlog, because a blank single select is worse than a wrong one you can see. Dates are the other one to watch. Notion sends UTC, Airtable stores UTC, and your eyes see local time in both, so when the day looks off by one it is almost always the display and not the data. Run the test again. Clean row, right stage, right date.
More videos
One trigger, three actions, and the order decides whether the result is usable. A first payment creates the contact, moves the deal and opens the onboarding card, each step handing its output to the next, with a clean stop when the first one fails.
The flow is rarely broken. One record is failing over and over, and the history names it in about thirty seconds. Sort by failed, read the two columns beside the error rather than the error itself, fix the mapping, replay the backlog in one pass.