Asgard AI

n8n

n8n

System integration

Moves n8n workflows to Asgard by purpose: rebuilds what each one achieves, and explains why and what to do instead where it can't.

Documentation

Moves n8n workflows to Asgard. The FDE Agent reads each workflow, works out what it achieves for whom, and rebuilds that outcome with Asgard's own building blocks, which is often shorter than the original. It only reads n8n and never changes anything there. Each part of a workflow is marked as moving as-is, moving with a change that the organization confirms first, or not movable, with the reason and an alternative.

Supported uses

Use What it does
From an exported file Someone exports a workflow from n8n and hands over the file; the FDE Agent moves it
From n8n directly With an n8n API key, the FDE Agent lists and reads the workflows it needs, which suits moving several at once
Ideas from the template library When the organization has no workflow yet, the FDE Agent suggests use cases from n8n's public template library for the department, then moves the chosen one
Keep it in n8n, call it from Asgard The workflow stays in n8n; an Asgard tool calls it through a webhook with a shared key, so the Agent can trigger it

What you need

  • Someone who can open the workflows in n8n.
  • For reading n8n directly: an n8n plan with the public API and an API key. The FDE Agent walks through creating one; the key is deleted when the move is done.
  • Accounts for the systems the workflows use (for example Gmail or Google Sheets), set up again in Asgard. Passwords never come across from n8n.
  • To call n8n from Asgard: the n8n instance reachable from the internet on its webhook path, and someone who can add a webhook and publish the workflow.

Rollout consultation

n8n is a trademark of its owner.