How to Avoid Duplicate Records in Airtable When the Same Customer Places Multiple Orders in NuvemShop
IN THIS ARTICLE
If you use NuvemShop to run your online store, you've likely had customers who return and place more than one order. When you track those orders in Airtable, the same customer can end up with multiple records — one for each purchase — making your table harder to manage and your data harder to trust.
Doing this manually for every recurring order takes time and leaves room for error.
Albato bridges the two. Every time a new order comes in through NuvemShop, it checks whether the customer already has a record in Airtable — and either creates a new one or updates the existing one.
Creating the App Connections in Albato
Before starting the automation, both apps must be connected to Albato.
Go to the Apps tab, click Add new connection, and search for NuvemShop. Then repeat the process for Airtable.
If you have any questions during these steps, read the following articles:
How to Create the Automation Step by Step
After confirming both connections are active, go to the Automations tab and click Create new automation.
Click the first step to add a trigger.
Select the NuvemShop app and the Order Created event.
Define whether you want to bring in past orders (data migration) or only new ones going forward.
After clicking Save, add the second step.
Select the Airtable app and the Find Record action.
Several fields will appear to help locate the record. In this case, use the Status - Title field to search.
Please, note: You can use whichever field you prefer, but the parameter coming from NuvemShop must contain the same type of information you normally use in the Airtable record — for example, a customer email or order number.
Click Save, then add the Branching tool to the automation.
Branching splits the flow into two paths: one for when the record already exists, and one for when it needs to be created.
Click to add the first branch condition.
Set the condition: if the Find Record step returns an empty Record ID value, this path should trigger.
Click Save, then add a Create Record action to this branch.
Configure this step as follows.
After saving, fill in the fields you want. These fields contain the information that should be saved from NuvemShop into your Airtable table. For example:
Now repeat the process to create the second branch.
This time, set the condition so it triggers when the Record ID is filled in (non-empty).
Add the Update Record action to this branch.
Unlike the Create Record step, this one requires the Record ID field — it tells Albato which record to update. Use the value returned by the Find Record step.
Then fill in the other fields with information from the NuvemShop order.
After saving, your automation will look like this:
Activate the automation to put it to work.
Now you can keep Airtable records accurate even when the same customer places multiple orders in NuvemShop. If you have any questions, contact our support via chat.
Did this answer your question?