At minimum, the add-on must retain access to the connected system used by the flow and to the workflow context that runs the prompt and passes its output downstream. A connection showing a warning or error may need to be fixed or reauthenticated, while prompt output must remain usable by the downstream actions that depend on it. The available guidance does not establish that every system in the current toolchain must remain in place.
Which system dependencies matter?
| Existing dependency | Why it matters | Verification |
|---|---|---|
| The system connected to the active flow | A warning or error on its connection can interrupt the required integration. | Each active connection is reviewed for warning and error icons. Where one appears, the documented options are Fix connection or Re-authenticate. |
| The workflow environment containing the prompt action | The prompt runs within a flow, and its output is generated as flow variables. | The prompt action remains present and its generated variables are available to the flow. |
| Downstream actions that consume those variables | The prompt output has a practical dependency only where later actions use the generated flow variables. | Each downstream action is checked to determine whether it references those variables. |
These are functional dependencies rather than a fixed list of product names. Systems that are connected but not used by the active path are not shown by the available evidence to be mandatory.
How the integration check works
The first step is a connection check. Every connection involved in the active workflow is reviewed. If a connection displays a warning or error, the established response is to select that connection and choose Fix connection or Re-authenticate.
The second step is an output-dependency check. The Run a prompt action generates flow variables for use in downstream actions. Those variables are then traced to the actions that actually consume them. This identifies the workflow and downstream action context that genuinely need to remain available.
The result is a narrower answer than “keep every existing system”: preserve access to the active connection, the flow that executes the prompt, and the downstream actions that use its output.
What still requires confirmation
The available documentation does not identify a universal set of external systems, state that every configured connection is mandatory, or explain whether a legacy system can be retired once its data has been transferred. It also does not specify all credential, availability, or replacement conditions for a particular setup.
Those points must be confirmed against the add-on’s current documentation and the actual workflow configuration. Until then, the supported requirement is access to the active connection plus the prompt’s workflow and any downstream actions that consume its generated variables.