Transfer Data now requires a Table?

Hi ​@DimitrisT 

Here's the Zapier doc that might help: Link

If you're still running into issues, drop a screenshot of the error and a quick description of what your Zap is doing, happy to take a look!

Hey ​@DimitrisT 👋

You're right, the new Transfer data experience works differently to the legacy version. Now when the Transfer data option is selected you need to add your data into Tables first before you can transfer it to the Zap to run through.

That said, if the Zap has already triggered on the emails but it missed certain details due to the structure changing, then you might not need use that transfer feature at all. If those Zap runs are still in your Zap history, you could:

1. Update the Zap to remap the fields to match the new email structure
2. Publish the updated version of the Zap
3. Replay the previous Zap runs, which will reuse the original trigger data but run it through using the updated version of your Zap

More details on how to replay entire Zap runs can be found in our Replay Zap runs guide.  

Let us know how it goes!

Hi ​@DimitrisT, 

I can understand the frustration.

From what I've seen, the newer Transfer Data flow is more tightly connected to Zapier Tables, which can feel like an extra step if you're just trying to replay missed records.

Without seeing your setup, I'm not sure whether you actually need a Table here or if there's a simpler way to reprocess those emails.

Happy to take a quick look if you'd like:
--link removed by moderator--

I’m in the same boat. I usually just change some information in my google sheet and then transfer that data for one zap. Now I have to map fields and it takes forever.

I’m confused why this is now harder and takes longer. 

All I want to do is change one cell of data in one line of my google sheet and replay that line through the zap. This 5 second task now takes forever (and there are so many fields to map).

So disappointed.

Hi ​@Ourem 👋

Totally hear you on that, and I've passed this over to our Product team so they're aware of how this is affecting your workflow. 

Just want to check, are you editing the Google Sheet data and then manually transferring it each time? Or is this a one-off thing where you're trying to update to historical data?

If you're regularly editing sheet rows and wanting them to run through a Zap, you might not need to use the Transfer data option at all. You could set up a Zap with a New or Updated Spreadsheet Row trigger, which would automatically run whenever you make edits or add a new row. Or if you only want to trigger on updates (not new rows), you could use the Updated Spreadsheet Row trigger instead. With that approach you wouldn't need to do manual transfers.

Do you think that could work for your setup?

Thank you so much, this is a great idea.

I might create a trigger column in my Google sheet as sometimes I update information but don't need to run a zap. That way it'll be easy to control when I want to rerun zaps. 

Appreciate your reply and suggestions. 👍

Such a good idea to use a trigger column for the Google Sheet ​@Ourem! 🙌 Let us know if you need any help with it.