Skip to main content

Migration from AI Chains

SimplAI previously had two near-identical primitives: Tools (task-first, typed inputs and JSON outputs) and AI Chains (conversation-first, Chat History input and a single reply). These have been unified — AI Chains are now Tools with Conversation mode on.

This page covers what changed for existing users.

What was migrated​

A one-time platform-wide backfill migrated every existing AI Chain — across all projects and tenants, in both Draft and Published states — to a Tool with Conversation mode on.

The following are preserved end-to-end:

  • Name and description
  • All intermediate nodes and wiring
  • Chat History seeds (system instructions, example turns)
  • Custom Attributes
  • Final Output template (the "Add to conversation" reply)
  • Every Published version and version history
  • Integrations bound to the resource
  • Credits / run history
  • Audit log entries

Resource ID continuity​

Each migrated AI Chain keeps a stable identifier so existing callers continue to work without code changes:

  • API/SDK callers that called the old AI Chain endpoint continue to receive the same responses.
  • Agent bindings that referenced the AI Chain continue to resolve to the migrated Tool.
  • Integration configurations (MCP, embeds, webhooks) continue to function.

If the underlying ID namespace differs internally, the platform maintains an alias from the old AI Chain ID to the new Tool ID. You should not need to update any caller code.

URL changes​

URLs that pointed at the old AI Chains surface have been redirected:

  • /ai-chains/{slug} → the corresponding Tool with Conversation mode on.
  • /docs/ai-chains/* → the corresponding Conversation mode docs.

If you've bookmarked an AI Chain in Studio, the bookmark still works — it resolves to the migrated Tool.

Visual identification​

In the Tools list, migrated AI Chains (now conversation-mode Tools) are visually distinguished from standard Tools with a "Conversation" chip/badge. The builder's top bar reads Tool · Conversation mode so you always know which mode you're in.

The AI Chains sidebar entry​

The dedicated AI Chains entry in the left navigation has been removed. Conversation-mode Tools live in the Tools list alongside everything else.

What to do (probably nothing)​

For most users, no action is required — the migration is invisible. Your existing API callers, agent bindings, and integrations keep working.

If you do anything voluntarily, it's likely:

  • Rename, if you want to drop "AI Chain" from your Tool names.
  • Refactor, if you want to convert a conversation-mode Tool to a task-mode Tool now that you can switch modes inline. See Switching mode for the destructive warning.

FAQ​

Q: I had an unpublished AI Chain draft. Is it still here? A: Yes. Draft AI Chains were migrated alongside Published ones. Open the corresponding Tool in your Tools list — Conversation mode is on, and your draft is intact.

Q: My Agent referenced an AI Chain. Do I need to re-wire it? A: No. Agent bindings continue to resolve to the migrated Tool by ID.

Q: I have an SDK or curl call hitting /api/v1/ai-chains/{id}/run. Will it still work? A: Yes. The legacy endpoint is preserved as an alias for the unified Tool endpoint.

Q: Where are the AI Chains docs? A: At /tools/conversation-mode/ — every page from the old AI Chains docs has a corresponding page here, organized around the unified Tool primitive.