Why Does the Footer Message Disappear in n8n-Chat-Widget Embedded Mode When Workflow is Active?

Below is an explanation based on the current documentation and implementation of the Chat Trigger node and its chat widget:

Why the Footer Disappears

When using the embedded chat widget, the default footer— which includes elements like the “powered by n8n” notice—appears in a non-active state (when the workflow is deactivated) but is intentionally hidden when the workflow becomes active. This behavior is meant to provide a cleaner interface for end users during active chat sessions.

Adding Custom Content While the Workflow Is Active

At the moment there isn’t a dedicated node parameter or built‑in option to always display a footer (or an extra info field/link) in embedded mode when the workflow is running. That said, here are a few approaches you might consider:

1. Customizing the Chat Interface:
   If you need to display additional information (like a link or some info text) when the workflow is active, you can look into modifying the HTML/CSS of your embedded chat widget. For instance, if you have control over the template (similar to how the docs use custom partials for the footer), you could add an extra element that remains visible even when the default footer is hidden.

2. Injecting Custom Text via a Node:
   In workflows where you manually set the chat response (for example, when creating a parameter called text or output), you might incorporate your custom information into the response. This allows you to control what the user sees without relying on the widget’s footer.

3. Overriding CSS:
   Although you mentioned that altering CSS hasn’t resolved the issue, it might be worth revisiting with a focus on overriding the specific classes that hide the footer when the workflow is active. Using a more targeted CSS selector or applying an override at a higher specificity may help reveal your additional element—but do so with care to avoid unintended side effects.

Summary

• The disappearance of the footer in active mode is intended behavior in embedded mode to streamline the chat interface.
• There isn’t a built‑in setting to keep the footer (or add extra fields) visible when the workflow is running.
• Your options include customizing the widget’s HTML/CSS, modifying the response content via workflow nodes, or carefully overriding the default CSS.

For further details on the customization options for embedded and hosted modes, please refer to the Chat Trigger node documentation. If you continue to have issues or if a particular use case isn’t covered, consider raising feedback with the n8n community so that future updates might offer more flexibility.

Feel free to ask if you need additional clarification on any of these points!