I’ve faced a similar issue before, and it can be frustrating. One thing that helped me was double-checking the field names in Airtable and n8n. Sometimes, even a slight mismatch can cause this problem. For example, if your Airtable field is called ‘Name’ (with a capital N), but in n8n you’re mapping to ‘name’ (lowercase), it might not work.
Another thing to consider is data types. Make sure the data you’re sending from n8n matches the expected type in Airtable. If you’re trying to send a date to a text field, for instance, it might not work correctly.
Lastly, I’d recommend using the ‘Test’ feature in n8n for each node. This can help you see exactly what data is being passed between nodes and might reveal where the information is getting lost.
If none of these work, you might want to try creating a simple workflow with just the Airtable node to isolate the issue. Hope this helps!