n8n-api-bridge

To update and deploy n8n workflows via REST API, you fetch the workflow JSON, modify the nodes and connections, and push the updated definitions back through n8n's REST endpoints. This requires setting the N8N_API_URL and N8N_API_KEY headers.

The three-layer sticky-note merge preserves your original Layer 1 sticky notes (color=4) while replacing or inserting AI-generated Layer 2 and Layer 3 (color=5) content into the workflow JSON before pushing it back to n8n via REST API.

Yes, you can activate or deactivate n8n workflows by ID or URL after pushing updates. The bridge enforces idempotency checks and prompts before overwriting Layer 3 content to ensure safe write and activate behavior through REST endpoints.

No, you do not need direct database access to modify n8n workflow JSON. The bridge avoids unsafe direct SQL modifications by exclusively using n8n's REST API to fetch, merge, and write back workflow definitions securely.

Limitations of using the REST API for n8n workflow deployment include requiring valid N8N_API_URL and N8N_API_KEY headers for all calls. Additionally, the system enforces idempotency checks and prompts before overwriting Layer 3 sticky notes to prevent data loss.

Yes, n8n-api-bridge is suitable for listing and reading existing workflows in production. It fetches workflows by ID or URL through REST endpoints and applies production guardrails like idempotency checks and safe write behavior to ensure reliable deployment.