Activepieces Todos is live 🚀

Activepieces Todos is live :rocket:

Automation isn’t about replacing humans, it’s about teaming up.

Some workflows need a human eye :eyes: : a decision, a quick review, or a green light :white_check_mark:.

That’s why we’re excited to launch Todos, a new way to pause workflows until the right person steps in.

Think of it as humans :handshake: automations working together to get things done better, faster, and smarter.

How it works

  • Define approval statuses like Accepted, Rejected, or Pending. With your own custom labels.
  • Assign tasks to teammates, leave comments , and request clarifications before moving forward.
  • View and manage unresolved tasks directly from your dashboard.

Example Use Cases :bulb:

  • Invoice Approval: Pause for finance to approve before payment.
  • Employee Onboarding: HR reviews and verifies documents.
  • Content Review: Approve posts before they go live.
  • Expense Reimbursements: Managers approve or reject requests.

You’ll now see Todos in your sidebar :arrow_right:

Go test it out and tell us what you think :boom:

Get the template for the flow in the video to test ToDos directly

https://cloud.activepieces.com/templates/J9N6FHMPlcpbbXGFwy2Uw

Hats off to @hazemadelkhalel :clap: and @AGamalX

4 Likes

Is this cloud only or available on Self-Host?

@Christian_DeRamos both

2 Likes

Hi Team, @Kareem_Nofal @hazemadelkhalel

I love the new Todo solution, I think it’s great!

I was running a few test as i am planning to move over to the Todo form the Approval links pieces. But I noticed the following.

I think there is missing some data for the ‘Create Todo and Wait’ and ‘Wait for approval’ part. The ‘Todo and Wait’ piece isn’t showing a task ID. which is needed for the ‘wait for approval’, Could you please look into this?


Also I would recomment changing the name ‘wait for approval’ to ‘wait for reponse’ as i can assume if an invoice is not approved you would like to follow a different flow.

Please let me know when this is resolved so I start investigating further :slight_smile:

KR Bram

Hello @Bram ,

Create Todo and Wait are designed to work together as a single piece (Create Todo + Wait for Approval), where the output is the result of the approval response.

On the other hand, there’s another strategy called External Channel, which separates the flow into two distinct pieces: one for creating the todo and another for waiting (by ID) for the response.


For renaming “Wait for Approval” to “Wait for Response”, I will send you feedback to the team.

Thank you for your feedback.

Hope you like the Todo feature :pray:

Hi @hazemadelkhalel,

Thanks for the reply! there was no example output to work with in the piece, but i think it’s fixed in the mean time.

I ran into another issue, could you please look into this? I am getting a 400 error, but not sure what the reason is. Please let me know if any other details are required from my end.

Hi @Bram

I was having a similar issue with the Todo piece, and it seems that deleting the old one and replacing it with a newly created one fixed the issue for me.

Not sure if it will work for you, but that is what I did to get things going again.

As a side note, I had also spun up and tested an Approvals Link creation piece before I removed and added the new ToDo piece. So, if you aren’t having luck with just replacing it outright from the start, this may be something else to try.

Cheers

Hi @Stitched ,

Thanks for the suggestion, i have tried it too but still no working perfectly, I noticed sometime issues are related to flows, like some memory is there. I have a workaround for now and as soon as I find time to recreate the flow i will probably do so.

Cheers

Hi @Bram,

I’m sorry to hear that it didn’t work for you.

As a final suggestion, which you might have already tried, I experimented a bit more and created a duplicate of the workflow that wasn’t working. However, simply duplicating it did not resolve the issue. It was only after I created a new ToDo item within the duplicate that the problem was fixed.

So, if you haven’t already attempted this, it may be worth trying. This method might eliminate the memory retained by the non-working flow.

Cheers!