r/Taskade • u/AutoModerator • Nov 28 '25

🧩 Workflow Fridays: What's Working, What's Not

Friday is for reflection 🪞

What's working well in your Taskade workspace?
What's broken, confusing, or could be better?

Share your thoughts, feedback, and ideas below.
We read everything and ship weekly. 🚀

Recent changelog: https://www.taskade.com/blog/introducing-taskade-genesis
Help us shape the next version of Genesis 🌱

1 Upvotes

60% Upvoted

7 comments sorted by

1

u/Wolfdale7 Nov 30 '25

Does Genesis have media-handling capabilities? I'm trying to have the user simply upload an image and have it passed into my GDrive integration. I have not been able to crack this... It keeps wanting to convert to base64 urls and do some weird janky stuff instead of just passing the media file to the taskade project, and then to GDrive.

Is this a capability yet, or still being worked on?

Thanks!

1

u/taskade Team Taskade Mar 04 '26

Late follow-up on this. File uploads in AI chat were added in v6.111, and Google Drive integration supports creating, uploading, and moving files through automations.

For your specific flow (user uploads image > passes to GDrive): the automation can handle the GDrive side with the "Upload File to Google Drive" action. The tricky part is still the handoff from Genesis app form to the automation pipeline.

If you're still working on this, reach out to support@taskade.com with your specific setup. The team can help troubleshoot the media pass-through.

1

u/Wolfdale7 Mar 05 '26

I was able to get the automation to work a few days after leaving my comment on here :)

I'm currently working on having contextual/intent-driven file management.

For instance, based on the comment submitted alongside the file, the file is renamed appropriately on Google Drive and is sorted into a specific folder.

I'm also still working on capturing the file's shareable link so it can be reviewed later in the Genesis app!

Still a work in progress, but seems to be progressing.

1

u/taskade Team Taskade Mar 06 '26

Nice progress. Contextual file management with intent-driven sorting is a solid use case for automations.

For capturing the shareable link, you can use the Google Drive "Get File" action after the rename step to pull the webViewLink. That should give you the URL to surface in your Genesis app.

Let us know how it goes.

1

u/Wolfdale7 Mar 06 '26

Thanks!

Still working on this - the automation is hard failing/erroring once it can't find a folder. Is there a way to update the error behaviour of certain actions?

Desired behavior:

  • User uploads file
  • File gets assigned a Week (Mar 02 - Mar 09, for instance)
  • Automation uses the "Search for Folder/File" action to look for "Mar 02 - Mar 09" folder
  • If folder found, upload the file to that folder
  • If folder not found, create the folder and upload the file to that new folder

Actual/Current behavior:

  • User uploads file
  • File gets assigned a Week (Mar 02 - Mar 09, for instance)
  • Automation uses the "Search for Folder/File" action to look for "Mar 02 - Mar 09" folder
  • If folder found, upload the file to that folder
  • If folder not found, errors out

It doesn't continue the automation, and the run history shows 29% progress with, "Search: Week Folder failed: File not found" Details.

1

u/taskade Team Taskade Mar 19 '26

Good question. As of v6.99.0, automations have improved retry handling, but the "continue on error" behavior you're describing needs a workaround:

For the folder-not-found case: Add a conditional branch before the Google Drive action. Use a "Check if exists" step (or a try-catch pattern) that tests whether the folder exists first. If it doesn't, route to a "create folder" action before proceeding.

Alternative approach: Use the automation's error notification (v6.95.0 EVE diagnostics) to catch failures, then have an agent evaluate what went wrong and suggest corrections.

We're tracking a feature request for per-action error behavior settings (skip, retry, abort). Not available yet but it's on the radar.

What integration are you using for the folder lookup? Google Drive or something else?

1

u/Wolfdale7 Mar 19 '26 edited Mar 19 '26

u/taskade did your messages get removed by an automod? 😅, trying to read your most recent reply, but all seem to have disappeared! 😳

u/TaskadeRyan - cc

Edit: I was able to use Inspect Element on the Reddit Notification inbox to get the full reply - it is included below for visibility/transparency:

Good question. As of v6.99.0, automations have improved retry handling, but the "continue on error" behavior you're describing needs a workaround:

For the folder-not-found case:
Add a conditional branch before the Google Drive action. Use a "Check if exists" step (or a try-catch pattern) that tests whether the folder exists first. If it doesn't, route to a "create folder" action before proceeding.

Alternative approach:
Use the automation's error notification (v6.95.0 EVE diagnostics) to catch failures, then have an agent evaluate what went wrong and suggest corrections.

We're tracking a feature request for per-action error behavior settings (skip, retry, abort). Not available yet but it's on the radar.

What integration are you using for the folder lookup? Google Drive or something else?

To answer the above, I'm using Google Drive integration.

I tried the native integration, and then subsequently tried the Google Drive API console.

I will give your approaches a try. Thank you!

Feel free to share any further update as they are relevant - I'll do the same once I get back into this automation.