I’m having trouble with my Make.com (formerly Integromat) scenario that processes customer orders from a JotForm submission. My Airtable setup includes an ‘Order Line Item’ table in the ‘Sales’ base. This table has a linked record column called ‘Inventory ID’ that connects to the ‘Inventory’ table in a separate ‘Inventory’ base. There’s also a link to the ‘Order’ table within ‘Sales’.
When I use Make.com’s ‘Create Record’ action for Airtable, it works fine for the Order ID. But when I try to add the Inventory ID, it says the record doesn’t exist. I’ve tried both the POST API and the Create Record tool, but no luck.
Has anyone else run into this problem? Could it be an issue with the Airtable API? I’m not sure if it’s because the Inventory table is synced from another base. Any ideas on how to troubleshoot this or get it working would be super helpful!
I’ve encountered this issue before when working with linked records across bases. One workaround that’s been effective for me is to use the ‘Find Records’ action in Make.com before the ‘Create Record’ step. This allows you to query the Inventory table first and retrieve the correct record ID.
Another potential solution is to use the Airtable API directly with an HTTP request module in Make.com. This gives you more control over the payload structure and can sometimes resolve issues with linked records.
If these don’t work, you might need to consider restructuring your bases or exploring alternative sync methods. It’s also worth checking if there are any recent API changes or known issues with cross-base linked records in Airtable’s documentation.
As someone who’s dealt with similar Make.com-Airtable sync issues, I can relate to your frustration. One thing that’s worked for me is using the ‘Lookup Record’ action in Make.com before the ‘Create Record’ step. This helps ensure the Inventory ID exists and is correctly formatted.
Another trick I’ve found useful is to manually create a test record in Airtable with the same structure as what you’re trying to sync. Then, use the Airtable API explorer to see exactly how the linked record should be formatted in the API call. Sometimes, the format isn’t quite what you’d expect.
If all else fails, you might consider creating a temporary ‘bridge’ table in your Sales base that mirrors the Inventory data. You could then sync to this table first, and use Airtable’s native features to link it to the actual Inventory base. It’s not ideal, but it can be a workable solution while you troubleshoot the API issues.
hey sophia, ive had similar issues. have u tried using the search module in make before creating the record? sometimes it helps to find the inventory ID first. also, double-check ur field names in make match exactly with airtable. those little things can trip u up. good luck!