Skip to main content

Custom extraction routing, reusable workflow reports + 2 more

Route each record to the extraction agent that fits it​

You can now define extraction-agent routing rules in Settings. Your rules are evaluated from top to bottom before NEXT’s default rules, letting you adapt processing for records that need different handling while keeping the standard setup in place.

How to use:

  1. Open Settings > Teamspace > Prepare with AI > Extract Memories
  2. Go to the "Choose extraction agent" section
  3. Add a rule that matches the records you want to treat differently, then choose the extraction agent to use.
  4. Arrange rules in priority order when more than one rule could match a record.

Learn more about Extraction Agents.

Extraction-agent rules that match records and assign an extraction agent

Create consistent HTML reports from your workflows​

Workflows now include a Create report step. Provide instructions for the report or define a fixed card structure, and NEXT generates validated report content using approved elements such as timelines, stat grids, and comparisons. The step returns both the report’s card JSON and rendered HTML.

How to use: Add a Create report step to a workflow, then describe the report content and structure you need. Use workflow variables in the instructions when the report should reflect workflow data.

Learn more about workflows.

Create report workflow step with instructions for report content and structure

Keep chat answers aligned with the sources you selected​

AI chat now keeps selected sources and uploaded files consistent across follow-up questions and page reloads. Each message carries its own selected sources, reducing the chance that a source from an earlier question unexpectedly affects a new answer.

How to use:

  1. Open "New chat" page
  2. Select the sources or upload the files you want to use
  3. Start a follow up message
  4. Review the selection in chat when changing topics or starting a new query.

Learn more about chat data sources.

Identify API tokens by what they are for​

Creating an API token now requires a short, human-readable name, such as “MCP,” “Internal reporting,” or “Development.” Names make it easier to distinguish tokens created for different integrations or uses.

How to use:

  1. Open Settings > Teamspace > General > Security & Privacy
  2. Generate a new API token
  3. Click default token name, and enter a descriptive name that identifies its purpose
  4. Click outside the name field to save it

Learn more about API tokens.

API token list showing human-readable token names