Procedures are the next step in Fin’s ability to handle complex queries. Tasks deliver strong results, but often require more technical expertise and complex setup.
With Procedures, we’ve taken what worked and made it simpler and smarter: a simple document-style editor ability to add code and data connectors within steps. This makes them faster to set up, easier to maintain, and more reliable to run—especially as processes get more complex.
If you currently use Fin Tasks, you’ll continue to see the existing interface until Procedures are enabled for your workspace. Once enabled, all new builds will be created as Procedures. All existing Tasks remain fully supported, with simple ones auto-migrating and complex ones staying in place until you’re ready to move.
Key differences between Tasks and Procedures
| Tasks | Procedures |
Creation | Workflow-based setup required splitting logic across multiple instruction blocks, often needing technical expertise and more time. | A single, document-style editor that feels as natural as writing a standard operating procedure (SOP). Easy to copy existing documentation and get started quickly. |
Maintenance | Task instructions can be spread across multiple blocks, making them harder to read and manage as processes grow more complex. | Procedures consolidate instructions, rules, and logic into one document, enabling easy updates. |
Consistency & Reliability | Instruction blocks provide a flexible foundation, though handling advanced logic (e.g. if/else) typically requires additional workflow steps to ensure consistent behavior. | Natural language instructions can be combined with deterministic controls through if/else branching logic to keep Fin adaptable and reliable. |
Advanced Logic | Only available through code blocks in Data connectors. | Code can be directly embedded within natural language steps. Improves accuracy, reduces latency, and makes logic easier to write, debug, and maintain. |
Customer Experience | More suitable for linear workflows, limiting ability to revisit earlier steps or switch context mid-conversation. | Fin evaluates the next best step based on the conversation. It can jump sections, switch Procedures, or revisit earlier steps seamlessly. This makes interactions more natural, flexible, and human. |
FAQs
Once I have access, will I need to move Fin Tasks to Procedures right away?
Once I have access, will I need to move Fin Tasks to Procedures right away?
No, migration will not be forced. Some Tasks — specifically those with a single instruction block and no additional workflow steps — will be eligible for automatic migration once Procedures are available on your workspace. You’ll receive advance notice before that happens. All other Tasks will remain supported for at least 18 months.
We’ll work closely with you to guide and support migration when it makes sense for your business.
How will my existing Fin Tasks work alongside Procedures?
How will my existing Fin Tasks work alongside Procedures?
Your Tasks will keep running with no disruption. When Procedures are rolled out to all Tasks customers (later this year), single-block Tasks will auto-migrate — with advance notice and no impact on you or the customer experience.
More complex Tasks won’t auto-migrate but will remain fully supported. Over time, new capabilities like Simulations will be best suited to Procedures. We’ll collaborate with you on migration when the timing is right for your business.
What’s the benefit of continuing to build Fin Tasks now?
What’s the benefit of continuing to build Fin Tasks now?
The work you put into using Fin Tasks and Data connectors will carry forward, because the same logic, instructions, and flows can be easily adapted once you have access to Procedures.
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts