Fin 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.
Your existing Tasks will remain fully supported, allowing you to edit, pause, and manage them as usual. Starting March 12, 2026, new Task creation will be disabled, and all new builds must be created as Procedures. To assist with this transition, we will provide guidance and tooling to help you convert your existing Tasks into Procedures.
Procedures build on the foundations of Tasks by simplifying the authoring process, improving reliability, and supporting more natural conversations with your customers.
Note: Fin Procedures is currently in managed availability. Access is limited during this period and available only to select customers with a contract. Please contact your account manager to confirm eligibility and learn how to join.
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. This ensures Fin stays on track, even during non-linear or incomplete conversations |
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. |
Procedures are simpler to author, easier to test, and more resilient in real-world conversations. By combining natural language instructions with structured logic in a single document, Procedures reduce setup and maintenance overhead. This allows Fin to adapt seamlessly when customers interrupt, change direction, or require multi-step resolution.
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. There is no immediate requirement to migrate your Fin Tasks to Procedures the moment you gain access. Your existing Fin Tasks will continue to function as they do now, allowing you to maintain your current workflow without disruption. We'll offer tooling to help you replicate your existing Tasks into Procedures.
How will my existing Fin Tasks work alongside Procedures?
How will my existing Fin Tasks work alongside Procedures?
Your existing Tasks will continue to run with no disruption. On 12 March 2026 you will not be able to create new Tasks. After that date, existing Tasks will still be be visible and editable - you can continue to change them, set them live or pause them.
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. This helps ensure a smooth transition when Procedures become available to your workspace.
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts