# Fair-code workflow or AI employee: how Viktor compares with n8n > Published 2026-11-06 > Source: https://viktor.com/blog/viktor-vs-n8n-ai-employee Viktor vs n8n: [Viktor](https://viktor.com) is the [AI employee](https://viktor.com/ai-employee) who lives in Slack and Microsoft Teams, connects to 9,800+ tools and does the work, while n8n is a fair-code, node-based workflow builder where a technical builder designs, tests and maintains the logic. A team that wants to describe a job in chat and get back the finished report, spreadsheet or CRM update will find Viktor the closer fit. A team that wants to own its pipelines node by node, and possibly host them on its own servers, will find n8n the closer fit. This page answers one narrower question: should your team build its work as fair-code workflows, or hand it to an AI employee? For the full product-by-product comparison, read our [Viktor vs n8n overview](https://viktor.com/blog/viktor-vs-n8n), and for other tools in this category see [n8n alternatives](https://viktor.com/blog/n8n-alternatives). ## Viktor vs n8n at a glance Viktor and n8n differ on who builds the work, where it runs and how it is billed: ```json:object { "_key": "k31", "_type": "table", "rows": [ { "_key": "k21", "_type": "tableRow", "cells": [ "Category", "Viktor", "n8n" ] }, { "_key": "k22", "_type": "tableRow", "cells": [ "What it is", "AI employee who takes a job in plain language and returns the finished result", "Visual workflow builder for automations and AI workflows, on n8n Cloud or self-hosted" ] }, { "_key": "k23", "_type": "tableRow", "cells": [ "Interface", "Chat in Slack, Microsoft Teams, the web app and Discord", "Node canvas in the n8n editor, plus hosted chat and Slack or Teams nodes inside workflows" ] }, { "_key": "k24", "_type": "tableRow", "cells": [ "Who sets up work", "Anyone in the workspace, by asking", "A technical builder who designs, tests and maintains each workflow" ] }, { "_key": "k25", "_type": "tableRow", "cells": [ "Integrations", "9,800+ tools, most through one-click OAuth; Viktor can usually build custom connections through an API or MCP server", "500+ native integrations (homepage), 2,622 listed in the integrations directory; HTTP Request node for any REST API" ] }, { "_key": "k26", "_type": "tableRow", "cells": [ "Triggers", "Scheduled tasks and event triggers: channel message, meeting, deal won, form filled, webhook", "Schedule Trigger, Webhook node, app event and polling triggers, Chat Trigger, MCP Server Trigger" ] }, { "_key": "k27", "_type": "tableRow", "cells": [ "Approvals", "Approval cards with Approve and Reject; admins mark tools “needs approval” or “forbidden”", "Send and Wait for Response steps, Wait node, human review before AI tool calls" ] }, { "_key": "k28", "_type": "tableRow", "cells": [ "Hosting", "Managed cloud only, US-hosted by default", "n8n Cloud (Azure, Frankfurt) or self-hosted on your own infrastructure" ] }, { "_key": "k29", "_type": "tableRow", "cells": [ "License", "Proprietary", "Sustainable Use License (fair-code) plus the n8n Enterprise License" ] }, { "_key": "k30", "_type": "tableRow", "cells": [ "Pricing model", "Usage-based credits shared across the workspace, no per-seat fee", "Billed per workflow execution on paid plans; free self-hosted Community Edition" ] } ] } ``` ## How Viktor and n8n compare on the work Viktor takes a plain-language job and delivers the finished work in the thread. n8n runs logic that someone has built by hand on a canvas, and it runs that logic the same way on every execution. ### AI employee vs workflow automation tool Viktor plans a job, works on his own cloud computer and hands back finished work: a Word report, an Excel file with formulas, a PowerPoint deck, an updated CRM record, or a pull request on a branch for someone to review. That follows from [what an AI employee is](https://viktor.com/blog/what-is-an-ai-employee): a hire who owns the outcome and adapts the steps to reach it. n8n is built around predictable execution. Its founder and CEO, Jan Oberhauser, frames the design this way: “Trustworthy AI systems combine deterministic workflows, probabilistic models, & human oversight.” In n8n’s own guidance, its AI Agent node “is one step inside of a workflow that runs to completion,” and builders bound it with IF and Switch branches, approval steps and error handling. Every run lands in the execution history, which gives engineers a step-by-step record of what happened. Work with irregular inputs, cross-tool context and judgment calls (the Monday ad spend recap, a board update pulled from three systems) suits Viktor. Work where every step is known in advance and must run identically thousands of times, such as syncing CRM records to an internal database, suits n8n. n8n describes itself as fair-code and distributes its main repository under the Sustainable Use License, which n8n created in 2022 and applied from March 17, 2022, replacing an Apache 2.0 with Commons Clause arrangement. Files marked `.ee.` fall under the separate n8n Enterprise License, and n8n’s documentation states that because OSI-approved licenses cannot restrict use, n8n doesn’t call itself open source. The license permits use “only for your own internal business purposes or for non-commercial or personal use,” and embedding n8n in a product you sell requires a separate commercial agreement. ### Where the work happens Viktor has been generally available in Microsoft Teams since 18 June 2026 ([changelog](https://viktor.com/changelog)), where he handles DMs, channel @mentions, group chats, followed threads, approval cards, files, scheduled tasks and workspace memory. In Slack, people DM him or @mention him in channels he belongs to, and he replies in a thread; he can also create canvases and Lists and work in Slack Connect channels with a private preview before posting, while Teams lacks some Slack features, including canvases, Lists, Slack Connect, and reaction or membership triggers. Companies that use neither Slack nor Teams can start in the web app at app.viktor.com or run Viktor in Discord, and you can see how [Viktor works in Slack](https://viktor.com/integrations/slack) and [Viktor in Microsoft Teams](https://viktor.com/integrations/microsoft-teams). n8n work is built on the editor canvas, and chat apps connect through nodes: the Slack node sends, searches and updates messages, manages channels and uploads files, and the Slack Trigger starts a workflow on events such as Bot / App Mention, New Message Posted to Channel or Reaction Added, after someone creates a Slack app with event subscriptions and a workspace admin installs it. The Microsoft Teams node posts chat and channel messages, manages channels and schedules online meetings, the Teams Trigger fires on new channel messages, chats and team members, and a Microsoft Agent 365 Trigger, released in n8n 2.20 on 5 May 2026, lets people @mention an n8n workflow in Teams. n8n’s docs describe approvals inside Slack but no built-in conversational chat inside Slack; teams build that from templates that pair the Slack Trigger with an AI step. ### Setup and who on the team can use it Getting Viktor started means signing up free, connecting tools and assigning work in plain language. Adding him to Slack or Teams needs the workspace or tenant admin’s approval. After that, anyone in the workspace can ask the same Viktor for work, and nobody builds a workflow. Workspace memory keeps the team’s context, decisions and preferences across conversations. Skills are written procedures the team can open, edit and share. An operations lead can screen-record a messy process once, with narration, and Viktor turns it into an editable skill; if the job repeats, he proposes a scheduled task that stays paused until someone approves it. n8n needs a builder, and self-hosting raises the bar further. n8n’s docs say self-hosting requires technical knowledge, including “Setting up and configuring servers and containers,” “Securing servers and applications” and “Configuring n8n,” and add: “n8n recommends self-hosting for expert users. Mistakes can lead to data loss, security issues, and downtime.” On either Cloud or self-hosted, builders map data with expressions such as `{{ $json.city }}` and write JavaScript or Python in the Code node for custom logic. Upkeep continues after launch. n8n ships a new minor version most weeks and recommends pinning versions. Saved workflows keep the node version they were built with, but major releases still require attention: - **n8n 2.0:** n8n’s developers blocked environment variable access from Code nodes by default and disabled the ExecuteCommand node by default. - **n8n 3.0:** n8n’s developers removed Edit Image node versions 1 and 1.1, so workflows still using them fail until upgraded. They also made a signing secret on the Slack credential mandatory before Slack Trigger workflows will publish. With Viktor, a change to the job is a message in the thread (“split this by deal owner from now on”), and he adjusts the task. ### Integrations, triggers and webhooks Viktor connects to [9,800+ tools](https://viktor.com/integrations) across CRM, ads, analytics, finance, project management, docs, support and engineering, including HubSpot, Salesforce, Pipedrive, Stripe, QuickBooks, Shopify, Notion, Jira and GitHub. Each connection can be shared with the workspace or kept private to the person who added it and the people they choose. For a missing tool with an API or an MCP server, Viktor can usually build the connection himself. A gateway adds API keys and tokens at run time, so the model never reads the credentials. Recurring work runs as scheduled tasks set up in plain English, and event triggers start work when a message lands in a channel, a meeting starts or ends, a deal is won, a form is filled or a webhook fires. n8n’s integration count depends on the page. The homepage says “500+ native integrations,” the AI page says 600+, and the integrations directory lists 2,622 (November 2026). The HTTP Request node covers the gaps: n8n describes it as able “to query data from any app or service with a REST API,” with curl import, pagination and generic auth (Basic, Header, OAuth1, OAuth2 and more). n8n’s trigger set includes: - **Schedule Trigger:** Intervals in seconds, minutes, hours, days, weeks or months, or a custom cron expression. Since n8n 2.45 (20 October 2026), runs are stored in the database before they are due, so a restart no longer drops them. - **Webhook node:** A test URL that listens for 120 seconds and a production URL registered when the workflow is published, with Basic, Header or JWT auth and a 16MB payload limit. - **App triggers:** Event-based triggers such as Slack and Teams, and polling triggers such as Airtable and Google Drive for services without webhooks. - **Chat and MCP:** A Chat Trigger for chat interfaces, plus an MCP Server Trigger and MCP Client Tool for connecting to MCP clients and servers. ### Approvals and human-in-the-loop Both products pause for a human before sensitive actions. They differ in where the rule lives. Viktor’s approvals are policy. Before a sensitive action, he posts an approval card with Approve and Reject, and a rejected action never runs. Admins set any tool to “needs approval” or “forbidden,” and that setting applies to every job anyone hands him. Some actions always need approval: joining channels, changing workspace settings, changing integration access, setting spend limits and installing skills. Teams supports approval cards but not the “Always approve this tool” button available in Slack. n8n’s approvals are steps the builder places in each workflow. The Send and Wait for Response operation exists on the Slack, Microsoft Teams, Gmail, Outlook, Discord, Telegram, Google Chat, WhatsApp Business Cloud and Send Email nodes. Supported options vary by node; Microsoft Teams offers Approval, Free Text and Custom Form response types and an optional Limit Wait Time. In Slack, approvers click inside Slack, provided the n8n instance is reachable over public HTTPS and the Signing Secret is set. Since n8n 2.6 (26 January 2026), builders can require human approval before specific tools inside the AI Agent node run, and since n8n 2.30 (7 July 2026) every Send and Wait response records a `respondedAt` timestamp. ### One task in both tools: a weekly CRM report in Slack As an illustration, take one recurring job: every Monday morning, post last week’s new leads and closed-won deals from HubSpot to a sales channel in Slack. In n8n, the closest published starting point is the Weekly HubSpot lead report to Slack template. The input is HubSpot data; the output is a Slack message such as “Last week we generated X leads.” A builder works through these steps: - Connect HubSpot and Slack credentials through OAuth2. - Set the Schedule Trigger to weekly (the template’s example is Mondays 07:00) and check the timezone setting. - Configure “Get all contacts” to pull the `hs_v2_date_entered_lead` property, and optionally “Get all deals” with `hs_is_closed_won`, `hs_closed_won_date` and `amount`. - Filter to the last 7 days and use the Summarize node to count leads and sum deal amounts. - Pick the Slack channel, then save, publish and activate the workflow. - Build a separate error workflow that starts with the Error Trigger, so a failed run sends an alert. The Error Trigger only fires on automatic runs, so manual testing does not exercise it. The result is explicit and inspectable, and each weekly run counts as one production execution. Adding an owner leaderboard, a trend line or a second data source means editing nodes, and the builder maintains it through the version changes described under setup. With Viktor, the input is one message in Slack: “Every Monday at 7, pull last week’s new leads and closed-won deals from HubSpot, add revenue from Stripe, and post the summary in #sales.” Viktor turns that request into a scheduled task, using the team’s connected HubSpot and Stripe accounts, and the output can be the channel summary, an Excel file with formulas, or a doc he keeps current at the same link. The team types changes into the thread in plain language, and the scheduled task shows the time it saved and its credit cost. Hand Viktor your own Monday report: [Start free with up to $100 in credits, no credit card, every integration included →](https://app.viktor.com/signup) ### Pricing model Viktor meters shared workspace credits; n8n meters workflow executions. Viktor’s pricing is usage-based. Credits power everything he does and are shared across the whole workspace, with no per-seat fee. The free start includes up to $100 in credits, no credit card, every feature and every integration, and free credits never expire. The Team plan is $100 a month for 40,000 credits, and Enterprise is priced with sales. [Pricing](https://viktor.com/pricing) as of October 2026. The Activity view shows credit use by person and task, and spend limits and auto top-ups with a monthly cap keep usage predictable. n8n bills paid plans by workflow execution (pricing checked November 2026). n8n defines an execution as “a single run of your entire workflow. It doesn’t matter how many steps are in the workflow or how much data it processes.” - Cloud plans (Starter and Pro) include a monthly execution allowance with unlimited users and workflows; Business is self-hosted only; Enterprise is priced through sales. - Manual test runs and sub-workflow runs do not count toward the quota, and neither do attached error workflows from n8n 2.38 on Cloud and 2.28.0 on self-hosted Business and Enterprise. - Workflows keep running past the quota, though overage charges may apply. The self-hosted Community Edition is free under the license terms, and the team pays for its own infrastructure and maintenance time. Embedding n8n in a product requires a separate commercial agreement. ### Hosting, security and data control n8n offers a choice of hosting; Viktor runs only as a managed service. - **Cloud hosting:** n8n Cloud runs on Microsoft Azure with data stored in the EU, on servers in Frankfurt. - **Self-hosting:** Self-hosted n8n runs on your own infrastructure under the Sustainable Use License, on-premises or in a private cloud through Docker Compose or the one-line setup, with npm installs deprecated from n8n 3.0. Self-hosters handle encryption at rest, TLS, backups and upgrades themselves. - **Security and access:** n8n’s Trust Center lists SOC 2 Type 2 and SOC 3, with the SOC 2 report available to enterprise customers. SSO and LDAP come with self-hosted Business and with Enterprise, while audit logging, log streaming and external secret stores are Enterprise features on the pricing table. - **Data processing:** For n8n Cloud, n8n includes a DPA with Standard Contractual Clauses in its standard terms. Viktor has no self-hosted or on-premise option and is US-hosted by default. His security status is [SOC 2 Type 1](https://viktor.com/security), with SOC 2 Type 2 and ISO 27001 in progress. He is GDPR aligned with a public DPA and CCPA compliant, uses TLS 1.2+ in transit and AES-256 at rest, and keeps each workspace’s skills, memory, files and connections isolated, while customer data is never used to train Viktor’s models or his model providers’ models. Enterprise adds SAML SSO, audit logs that include integration tool calls, per-user spend caps and invoicing. Viktor doesn’t offer HIPAA or BAAs, SCIM provisioning, role-based access control or configurable data retention. ## Which one fits your team Viktor fits teams that want jobs done across their tools by asking in chat, without anyone building workflows. n8n fits teams whose engineers want to design, inspect and host rule-based pipelines themselves. **Choose Viktor if:** - The whole team should be able to hand off work by asking in Slack, Microsoft Teams or the web app. - Recurring reports and digests, like the Monday pipeline update or a weekly KPI summary, currently get assembled by hand. - Jobs cross several tools and need judgment, such as reconciling the CRM against Stripe before a report goes out. - Nobody on staff has time to build and maintain workflows. - You want finished deliverables (documents, spreadsheets, CRM updates, pull requests for review) and per-workspace pricing in place of seats. **Choose n8n if:** - Policy requires self-hosting or on-premise deployment, or data has to stay on infrastructure you control. - The work is a deterministic, high-volume pipeline where every step is known and per-execution billing suits many steps per run. - Engineers want node-level control, code steps, Git-based version control (self-hosted Business and Enterprise) and full execution logs. - The team wants to own its automation infrastructure end to end. ### Can you use Viktor and n8n together? Yes, and the split is natural: n8n runs the fixed pipelines, and Viktor takes the judgment work that arrives in chat. The documented connection points are the webhook triggers on both sides (Viktor’s event triggers and n8n’s Webhook node), Viktor’s [public API](https://viktor.com/docs), Viktor’s MCP server at api.viktor.com/mcp, and n8n’s HTTP Request node, which calls REST APIs. Teams weighing other options in this category can compare them in the guide to [n8n alternatives](https://viktor.com/blog/n8n-alternatives). ## FAQ ### Do I need technical skills to use Viktor or n8n? Viktor needs none: people describe the job in plain language and he does it, and only adding him to Slack or Teams needs an admin’s approval. n8n needs a builder who can design workflows, write expressions and, for custom logic, JavaScript or Python in the Code node. n8n recommends self-hosting only for expert users. ### Can Viktor be self-hosted or run on-premise? 1. Viktor runs as a managed cloud service, US-hosted by default, and the customer deploys and maintains nothing. Teams with a firm self-hosting or on-premise requirement should look at n8n, which runs on your own infrastructure. ### How do Viktor credits compare with n8n executions? Viktor uses credits shared across the whole workspace with no per-seat fee, and the Activity view shows where they go by person and task. n8n counts one execution per full workflow run regardless of steps, and test runs and sub-workflows are excluded, as are attached error workflows on recent versions. Current plans are on Viktor’s and n8n’s pricing pages. ### Do Viktor and n8n work in Slack and Microsoft Teams? Yes, both work in Slack and Microsoft Teams: Viktor lives in both, where people DM him or mention @Viktor and he replies in threads, with Teams generally available since 18 June 2026. n8n connects to both through its Slack and Teams nodes and triggers, which builders configure inside workflows edited on the n8n canvas. ### How do approvals work in each? Viktor posts an approval card with Approve and Reject before sensitive actions, and admins set tools to “needs approval” or “forbidden” across every job. In n8n, builders add Send and Wait for Response steps or Wait nodes to each workflow and can require human review before specific AI tool calls run. ### What security and compliance credentials do Viktor and n8n hold? n8n lists SOC 2 Type 2 and SOC 3, with SSO on self-hosted Business and Enterprise and audit logs on Enterprise. Viktor holds SOC 2 Type 1, with SOC 2 Type 2 and ISO 27001 in progress, a public GDPR DPA, and SAML SSO plus audit logs on Enterprise. For a company-wide rollout or security review, [talk to the Viktor team →](https://viktor.com/contact-sales) about onboarding and spend controls. ### What is the first step to running Viktor and n8n side by side? Keep existing n8n pipelines where they are, and hand Viktor one recurring chat-based job such as the Monday report. Connect the two later through webhooks, Viktor’s public API or his MCP server if a job needs to cross between them. Pick the report your team rebuilds by hand every week and [hand it to Viktor free](https://app.viktor.com/signup), with up to $100 in credits and no credit card. [Add Viktor to your workspace – free to start →](https://viktor.com/?utm_source=blog&utm_medium=cta&utm_campaign=viktor-vs-n8n)