How can I seamlessly switch between Chat Trigger and Form Trigger workflows?

Below is one way to design your solution while retaining chat context between distinct workflows:

1. Divide Your Process into Two Workflows
   • Workflow A: Starts with a Chat Trigger node that runs your chat using the AI agent.
   • Workflow B: Uses a Form Trigger (or similar webhook trigger for form submissions) that collects additional details from the user.

2. Share the Conversation Context via a Memory Node
   To maintain state across workflows, you can store key parts of the conversation (for example, the user’s name, conversation ID, etc.) in a memory store. Both workflows can connect to the same memory sub‑node so that when the user returns from submitting the form, the chat workflow can load the previous session.
   Refer to the Chat Trigger’s “Load Previous Session” option in the node parameters. When set to an option like “From Memory”, make sure the Chat Trigger (in workflow A) and any Agent node connected to it are using the same memory sub‑node. This creates a single source of truth for your conversation context.

3. Pass Context When Handing Off to the Form Workflow
   • In Workflow A, when you are ready to switch to the form (for example, after asking “May I know your name?” and collecting initial details), include a link for the form.
   • Append any necessary identifiers (like a conversation or session ID) as URL parameters. That way, Workflow B can know which chat session to update once the form is submitted.

4. Resuming the Chat After the Form Is Submitted
   • Once the user fills out and submits the form in Workflow B, update or append the conversation context (for example, adding form results such as driving violations) into the common memory store.
   • Then, instruct Workflow B to trigger a follow‑up action in Workflow A (for example, via a webhook call, an API endpoint, or even using the Custom n8n Workflow Tool node to invoke a specific part of your chat workflow) so that the chat session resumes using the updated context.

5. A Sample Conceptual Flow

MERMAIDCopied
flowchart TD
    A[Chat Trigger Workflow (A)]
    B[Form Trigger Workflow (B)]
    M[Memory Node]
    
    A -- "Store conversation context" --> M
    A -- "Provide form link with session ID" --> B
    B -- "Receive form submission and update context" --> M
    B -- "Trigger follow-up (via webhook or Custom Workflow Tool)" --> A

6. Additional Considerations
   • Use expressions or parameter passing to ensure that both workflows have access to the conversation context.
   • In Workflow A’s Chat Trigger node, enable the “Load Previous Session” option and connect it to the same memory node that Workflow B updates.
   • If needed, use the Custom n8n Workflow Tool node (already detailed for other integrations) to efficiently call or integrate the form workflow so that data passes smoothly between workflows.

This strategy ensures that once the form is submitted, the AI chat resumes contextually—picking up exactly where it left off with all the essential details of the conversation. If you need further details on setting up memory or linking workflows, the Chat Trigger and Custom n8n Workflow Tool sections in the documentation provide additional insights.