Q&A from the Live Session | Quick Automate - Demystifying Agentic AI

Q&A Transcript from Webex

Q: How long did it take to build quality agents with AI?

A: You can do it easily sometimes in an hour and often in a day. Set yourself that target — be aggressive. You can get a lot done very quickly now. Agents are very powerful, and Quick Automate is a very powerful platform that lets you spin up lots of agents fast. There’s a great feature called Planner — you don’t even have to build the agents yourself. You just tell it what you’re trying to do and it builds the flow and picks the agents to include. Pick a small use case, set yourself a timeline of one day, and see what you can get done. You’ll be pretty happy!


Q: What are some of the critical features you liked in Quick Automate?

A (Harrison from Rhino AI): A few favorites:

  • Planner — Having an AI that builds the workflow for you is amazing. Sometimes the pain of dragging a hundred nodes in a workflow builder is real, and Planner eliminates that.
  • Parent flow and subflow functionality — This type of automatic organization of steps is really critical. Quick Automate automatically groups flows into logical groupings of nodes and allows you to zoom in and zoom out, which keeps things from becoming the zigzag, crisscrossing madness you often see in other low-code platforms.

Q: What are the biggest challenges of using and building Agentic AI, and any common pitfalls?

A (Harrison from Rhino AI):

  1. Using the wrong tool for the job — The biggest pitfall is making something deterministic when it should be agentic, and vice versa. You’ll sometimes build an entire agent just to evaluate a simple boolean condition, or conversely, write a hundred hard-coded business rules when you should have just asked the agent to say yes or no. Developing the intuition for when to use each approach takes practice.
  2. Not planning for latency — Agentic workflows are eventually consistent systems. They’re going to finish at some point, and data will be updated over the course of the run. Long-running processes won’t be done in two seconds but will have an effect on your data and state. Plan for this upfront.

Q: What would be your suggestions for teams to get started on Quick Automate?

A: The most important thing is to identify the right process. Once you identify the right process, you have the technology to automate it. It all starts with what you want to automate and defining the goal — everything else is easy. Create a portfolio of processes and just start building. That’s the best way.