Skip to content

Add n8n workflow-automation node (tool_n8n) #1230

@kgarg2468

Description

@kgarg2468

Summary

Add a first-class n8n integration node (tool_n8n) so RocketRide pipelines and agents can trigger self-hosted n8n workflows and consume their results — and so n8n can call back into RocketRide (round-trips).

Assigned internally; filing this to track the work and link the PR.

Scope

  • Dual node — usable as a pipeline step and an agent tool (the db_postgres pattern).
  • RR→n8n: webhook trigger — sync (Respond-to-Webhook) or async (poll executions via the public REST API with a correlation id); list/inspect workflows + executions; activate/deactivate gated by a read-only toggle.
  • Rich I/O: simple or structured payloads (documents + metadata); files/binary both ways (image/audio/video lanes via multipart); table output lane.
  • Safety / DX: SSRF containment (the agent never chooses the host); none/header/basic/bearer/JWT webhook auth; TLS-verify toggle; deploy-aware reachability preflight (host.docker.internal hint); 404→activate and ack→Respond-node guidance; configurable sync/async timeouts; n8n execution deep-links.
  • n8n→RR + round-trips documented with importable templates under examples/n8n/.

Out of scope (tracked as follow-ups)

  • A dedicated n8n community node (n8n-nodes-rocketride, separate TypeScript package).
  • RR-core hardening: HMAC-signed / idempotent webhook ingress + executionId↔run-id trace binding.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions