Tuesdays with Tadabase - September 23rd 2025

[Adi]

Fall has arrived and the autumnal brisk air is breathing new life into our team. Let’s take a whiff of this update, together

Our engineers have added:

New Importer live on select tiers for beta testing:

We’re beyond excited to finally be launching our new Importer! The new importer is rebuilt from the ground up with all the knowledge and insight we’ve gathered over the years on what a good importer should look like. Can’t wait to hear what you think!

Some of the most powerful features include the ability to import from nearly any API, save that configuration, and trigger it on demand. For example, you could import all transactions from Stripe daily and automatically match each transaction to a specific customer.

In addition, we’ve focused heavily on UI, UX, and overall import speed. Even subtle improvements, like highlighting the field you’re working on, make it easier to map columns to fields and improve visibility during the import process.

Improved Record Matching:

We’ve reworked how record matching works, especially when using multiple fields to match and update existing records. This means that instead of only inserting new records each time, the system can now update existing records more accurately, improving data integrity and reducing duplicates.

You’ll now see the new “Import V2 Beta” appear in your builder. We’d love to hear your feedback as you explore the updated import experience!

Bug Fixes, including:

• Dependent Dropdown: Fixed an issue where the selected value was not retained in the edit form.

For a complete list of fixes, see our release notes.

Sunsetting Dropbox on new apps:

We are retiring the Dropbox file storage option in Tadabase and will no longer support saving files directly to Dropbox for new implementations.

While this method has been useful, we’ve identified security and reliability concerns that make it less suitable going forward. Existing Dropbox setups will continue to function until December 31st, 2026, giving you ample time to transition.

Moving ahead, we are focusing our efforts on strengthening and expanding our S3 integrations, including both Tadabase’s default S3 bucket and your own custom S3 buckets. These options provide a more secure, scalable, and future-proof solution for file storage within Tadabase.

We’re stopping here, Tadabasers. Happy building and see you next week!

[SWalker]

@Adi @moe Which tiers are getting the Import V2 Beta? We have a use case where it would be extremely useful, especially the import via API! We are currently in our maintenance phase before the start of the grant year, so we can provide you with some quick feedback/ bug testing.

[Dan]

Hi,

I also do not see it now with Pro Plan?

Thanks

Dan

[SWalker]

@moe @Adi I just got access to import v2 and have run into a couple of issues. Since the request is being made in the browser, it is being blocked by a CORS POLICY no ‘access-control-allow-origin’.

This is a request that has been validated in custom pipes so it seems to be an issue with the importer using the browser to make the request.

The importer also does not allow for passing parameters into the URL via {} like pipes. All parameters are placed at the end of the request which has caused issues with a request like this: https://api.papersurvey.io/surveys/{survey_id}/entries/questions

Another big missing feature is scheduling. Especially for the use case listed in the posting about daily imports. Would it be possible to tell an automation task to trigger the import.

Is there a way to save API import templates or will that information have to be entered everytime?

[moe]

We’ll definitely take a look at the issue with CORS.

The importer is not meant for dynamic imports like where you must pass the Survey ID in your case. We can look into that, but that’s not the goal of this feature since its not going to be added into rules/action links etc where those things can be defined. It’s a static import only.

[SWalker]

Thank you for the explanation and for looking into the CORS issue. It looks like I lost access to the import V2 Beta over the weekend (after I saved a template of my import). Even if the import can not be triggered via an action or table rule, I think it would be invaluable to be able to trigger an import template via an automation task. Thank you, as always, for entertaining my problems!