mirror of
https://github.com/n8n-io/n8n.git
synced 2026-10-21 20:20:03 +02:00
a70071a8eb
Answers: how does a workflow tell the app where to redirect? It doesn't need a dedicated mechanism - it's just a JSON field on the response (redirectTo), read by generated frontend code that calls React Router's navigate(). The run-workflow endpoint from the previous commit already carries this with no changes. What hadn't been tested: does an actual multi-route app navigate correctly once built and served this way. Built a 2-route react-router-dom app (list page + /success) and confirmed both: - client-side navigation after an action's redirectTo, no page reload - direct/hard navigation to the same sub-path, via the static-serving route's existing index.html fallback (no new code needed) Also fixed a bug in the spike's own test app (not the platform): the run-endpoint nests output by node name (data.Code[0]...), and an early version of the action handler read redirectTo off the wrong level. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| @n8n | ||
| cli | ||
| core | ||
| extensions/insights | ||
| frontend | ||
| modules | ||
| node-dev | ||
| nodes-base | ||
| testing | ||
| workflow | ||