Full-Time
Updated on 8/23/2026
Open-source, node-based workflow automation platform
$205.9k - $251.7k/yr
Boston, MA, USA + 5 more
More locations: Texas, USA | Florida, USA | New York, NY, USA | Massachusetts, USA | New Jersey, USA
Remote
Travel to key events is required, primarily in the US and occasionally in EMEA.
See people who can refer or advise you
n8n is an open-source workflow automation platform with a visual, node-based editor for building multi-step automations. It runs on Node.js and supports triggers and actions (webhooks, API calls, database queries, logic, loops, notifications) plus optional custom JavaScript or Python code. It offers self-hosted and cloud options, a fair-code license, 400+ native integrations, templates, and developer tools like version-controlled JSON exports and Git-based pipelines, plus native AI integrations (OpenAI, LangChain, Claude, Hugging Face). Its goal is to give teams flexible, controllable automation with data ownership and customizable AI-powered workflows.
Company Size
1,001-5,000
Company Stage
Series C
Total Funding
$254M
Headquarters
Berlin, Germany
Founded
2019
See people who can refer or advise you
Help us improve and share your feedback! Did you find this helpful?
Health Insurance
Competitive compensation
Ownership
Work/life balance
Career growth
Remote Work Options
Transparency
Giving back
Ambitious but kind culture
These 7 AI startups have a surprising investor: Telekom. 18:37, 10 Aug. 2026 From the telephone booth to unicorn shepherd. Telekom has invested in some of the most renowned German technology startups. When you think of Telekom, you usually think first of mobile phone masts and the company's own magenta. Less well known: The DAX group has been acting as a startup investor for years. Some stakes are tiny, others strategically interesting; together they paint a picture of where the journey could go. T.Capital, as the investment vehicle is called, pursues a two-pronged approach. The venture arm typically invests in Series A to Series C financing rounds and takes stakes of up to five million euros in companies. In addition, there is a tech fund with significantly larger tickets of up to 300 million euros. This allows Telekom to both accompany young providers early on and play a role in larger technology bets. The stakes show that the group has long been interested in more than just classic telecommunications. Many investments revolve around software, artificial intelligence, cloud infrastructure, or data-driven business models. Isn't everything somehow AI these days in the end? N8n. The Berlin startup N8n develops a platform for workflow automation. Companies can use it to connect different software services and automate recurring processes. The topic is interesting for Telekom because large organizations have to coordinate countless IT systems. According to the commercial register, Telekom holds a 0.08 percent stake in N8n. Quantum Systems. Quantum Systems from Bavaria develops drones and airborne reconnaissance systems for civilian and - now also - military applications. The systems generate large amounts of data that need to be transmitted, processed, and evaluated. That is exactly where Telekom's classic strengths lie. According to the commercial register, Telekom's stake amounts to 1.27 percent. Interestingly enough, until a few years ago many investors wanted nothing to do with weapons of war. That is why Quantum initially focused on civilian use. That has changed. Dash0. Dash0 develops software for monitoring and analyzing complex cloud infrastructures. Such observability platforms help companies quickly detect errors in their applications and run digital services reliably. For Telekom, which operates large network and IT landscapes worldwide, the strategic proximity is obvious. However, the exact stake size is not publicly visible because the company is organized via a US parent company in the form of a so-called Delaware flip. Lovable. The Swedish startup Lovable is one of the best-known European providers of platforms for vibe coding. Lovable enables users to create software applications with the help of artificial intelligence. For Telekom, this offers a glimpse into the next generation of software development and AI tools. The ownership structure is also not directly traceable in the German commercial register here, as Lovable is organized via a US parent company. Black Forest Labs. Black Forest Labs from Freiburg develops AI models for image generation and is one of the best-known European AI startups of recent years. Artificial intelligence is also becoming increasingly relevant for telecommunications providers, for example in customer service, software development, or network management. The specific size of Telekom's stake is not publicly visible, as Black Forest Labs has also used a Delaware flip and is organized as a US corporation. Equativ. Equativ is a French adtech company that develops technologies for digital advertising. The business is based on processing large amounts of data and efficiently operating digital platforms. The company thus operates in an environment closely connected to the digital ecosystems of large telecommunications providers. The participation runs through the company's French parent company. Kinexon. Kinexon develops tracking and positioning technologies for industry, sports, and logistics. The systems capture movements and positions in real time and make processes measurable. Such applications benefit from powerful networks and reliable data transmission, a core area of Telekom. According to the commercial register, the group holds around 0.77 percent here. In the end, the portfolio shows above all one thing: Telekom is investing not only in the next mobile communications generation, but also in the software and AI world that builds on it. A mix of German industrial expertise, international cloud software, and European AI.
How to automate pricing updates on Shopify. Automating pricing updates means automating the workflow around the decision, not the decision itself: exporting sales data on a schedule, feeding it to a pricing model, pushing approved prices back into Shopify through the Admin API, and notifying your team when it's done. The analysis itself takes minutes. Most of the time merchants lose is in the manual steps around it, exporting CSVs, cross-referencing cost sheets, editing product pages one by one. Key Takeaways * Pricing is really three separate jobs: data collection, analysis, and execution. Most merchants automate the middle one and do the other two by hand. * Shopify Flow and third-party connectors can automate the data export step so sales history lands in a consistent format without manual clicking. * Pushing recommended prices back into Shopify has three options, the bulk CSV editor, Flow plus tags, or the Admin API, with the API being the only one that scales cleanly to large catalogs. * Confidence scores matter for automation specifically: only push high-confidence recommendations automatically, route low-confidence ones to a manual review queue. * Automate the plumbing before you trust the model, not before. Run recommendations manually a few times first so you know what a good one looks like. The pricing workflow has three parts. Think of pricing as three distinct jobs: data collection, pulling sales history, cost data, and competitor prices into one place; analysis, running that data through an elasticity model to find the profit-maximizing price for each SKU; and execution, pushing the new prices back into your store, updating internal reports, and notifying your team. Most merchants automate the second part, or let a tool handle it, and do the first and third by hand. That's where the time disappears. | Step | What it involves | Typically automated? | | 1. Data collection | Sales history, cost data, competitor prices | Rarely | | 2. Analysis | Elasticity model, confidence scoring, price recommendation | Usually, by the pricing tool | | 3. Execution | Updating product prices, reporting, team notification | Rarely | Step 1: Automate the data export. Shopify lets you export order history as a CSV, but doing it manually every week gets old fast. Shopify Flow can trigger an export on a schedule, and third-party connectors (Mesa, Alloy, Zapier) can route that file to Google Sheets, email, or a cloud folder automatically. The goal is simple: your sales data lands in a consistent format, in a consistent place, without you clicking "Export." If you also track competitor prices, that's a second data stream worth automating. Competitor sites change layouts, block scrapers, and rotate pricing tiers, so scheduled browser automation is generally more reliable than a one-off script. WebRun's guide to integrating browser automation with n8n walks through setting up scheduled competitor price checks, including how to handle timeouts and poll for results when a task takes longer than expected. Step 2: feed the data into your pricing model. Once your data export is automated, the next step is connecting it to whatever runs your pricing analysis. With Zorin, you upload a CSV of past transactions and the demand model fits automatically, returning a recommended price, expected profit lift, and confidence score for each product. The whole process takes about five minutes from upload to recommendation, the same elasticity coefficient that would otherwise take a spreadsheet and a statistics background to calculate by hand. The key detail is that your export format needs to match what your pricing tool expects. Zorin parses quantities, prices, and dates from your CSV. If your automated export includes extra columns or different headers, add a transformation step, a simple Google Sheets formula or a Zapier formatter, to clean the file before it hits the model. Step 3: push price changes back into Shopify. This is where most workflows fall apart. You have a list of recommended prices. Now what? * Option A, Shopify's bulk editor: download your recommendations, format them as a Shopify product CSV, and upload via the admin. Semi-manual, but faster than editing products one by one. * Option B, Shopify Flow plus tags: tag products that need price changes, then use a Flow to apply specific price rules based on tags. Works for simple adjustments but gets messy with per-SKU recommendations. * Option C, the Shopify Admin API: with a no-code automation tool like Make or n8n, connect your pricing output directly to the Shopify API. The automation reads each row of your recommendation file, calls the API to update the product variant price, and logs the change. No manual uploading. Option C is the most reliable for stores with large catalogs. Once it runs, every recommended price is live in your store within minutes, and you have a log of exactly what changed, which matters if you're pricing an entire catalog rather than a handful of products. Step 4: close the loop with notifications. Price changes affect more than just the product page. Your team needs to know what moved and why. A few things worth automating after prices update: * Slack or email alert listing every SKU that changed, the old price, and the new price. * Margin report recalculated with the new prices and your current cost of goods. * Calendar reminder to review results in 7 to 14 days, once enough sales data accumulates to measure the impact. These are simple automations in any workflow tool. The point is to avoid the scenario where prices changed three weeks ago and nobody remembers which ones or why. What this looks like end to end. A fully automated pricing workflow runs on a weekly or biweekly cycle. Monday morning, your sales data and competitor prices are automatically exported and cleaned. You upload the data to your pricing model, or it pulls automatically, and five minutes later you have recommendations with confidence scores. You review the recommendations, approve the ones above your confidence threshold, and hit go. The automation pushes approved prices to Shopify, logs every change, and pings your team. Two weeks later, you review performance against the old prices, which is also a good moment to revisit how often you're actually changing prices versus how often the model has something worth acting on. The human stays in the loop for the decision. Everything else runs without them. Where merchants get stuck. Two common mistakes show up with pricing automation. The first is automating too early: if you haven't run your pricing model manually a few times, you don't yet know what a good recommendation looks like. Automate the workflow after you trust the output, not before. The second is ignoring confidence scores. Not every recommendation is equally strong. A product with an elasticity R-squared of 0.91 is telling you something reliable. A product with sparse sales data and low confidence is a guess. Build your automation to filter on confidence, so only strong recommendations get pushed automatically and weaker ones go to a review queue. The pricing decision is the valuable part. Everything around it, the exports, the formatting, the uploads, the notifications, is plumbing. Automate the plumbing, keep your hands on the lever. Connect your sales history to see the recommendation side of this workflow running on your own catalog. Frequently asked questions. Can I fully automate Shopify pricing updates without a developer? Yes. No-code tools like Shopify Flow, Zapier, Make, and n8n can handle the data export and price-push steps without custom code, connecting directly to the Shopify Admin API. What's the best way to push bulk price changes into Shopify? For large catalogs, connecting your pricing output to the Shopify Admin API through a no-code automation tool is the most reliable option. It updates every variant directly and logs the change, unlike the bulk CSV editor or Flow-plus-tags approaches, which get harder to manage at scale. Should I automate every price change a model recommends? No. Filter on confidence score first. High-confidence recommendations are reasonable to push automatically, while low-confidence ones, usually from products with sparse sales history, should go to a manual review queue instead. How often should an automated pricing workflow run? Weekly or biweekly is typical, enough time for meaningful sales data to accumulate between cycles without letting stale recommendations sit unused. What format does my sales data need to be in before feeding it to a pricing model? It needs to match what the tool expects, typically quantities, prices, and dates per transaction. If your automated export includes extra columns or different headers, add a cleanup step before the file reaches the model. Do I need to automate competitor price tracking too? Only if your pricing process uses it. Scheduled browser automation is more reliable than manual checks for this, since competitor sites frequently change layouts and block scrapers. What's the risk of automating pricing before trusting the model? You won't yet recognize a bad recommendation when you see one. Run the model manually a few times first, get a feel for what a reasonable output looks like, and automate the surrounding workflow once you trust the recommendations themselves. Getting a pricing recommendation is one thing. Acting on it across 200 SKUs is another, and that gap is almost entirely a plumbing problem, not a modeling one. Automate the data export, the price push, and the notifications, and keep the actual pricing decision, and a healthy dose of skepticism toward low-confidence recommendations, in human hands. Dexter is part of the team at Zorin, building tools that help ecommerce merchants price with data instead of guesswork.
What's next for n8n? In The Loop 2026 conference to unveil automation roadmap. 05 August 2026 n8n is hosting its first major in-person conference, In The Loop 2026, in Berlin on October 13-14, 2026, to share its future vision and product roadmap for automation and AI. n8n has just confirmed its first big, in-person conference, 'In The Loop 2026,' happening in Berlin on October 13 and 14, 2026. This is huge news for anyone interested in automation and AI! If you're wondering where n8n is heading, this event is designed to give you a peek into their long-term vision and product roadmap. But hold on, don't expect immediate announcements of new features or release dates; it's more about the direction and future plans. The event will take place at Wilhelm Studios and aims to bring together n8n's community, including developers, engineers, IT and operations leaders, partners, ambassadors, and enterprise teams. The importance of this announcement lies in establishing a clear public forum for n8n to discuss the future of its automation platform. While the conference will feature forward-looking discussions, it's not the place to look for specific new features, integrations, or release dates right now. Instead, think of In The Loop as a roadmap-focused event to understand n8n's strategic direction rather than a product launch pad. The program is set to cover the company's product roadmap and overall vision, along with broader trends in automation and AI. It's also crafted as a community and ecosystem event, offering talks, product demonstrations, hands-on workshops, an expo floor, a startup showcase, and plenty of networking opportunities. The conference has a neat split format. October 13, 2026, is designated as a 'Partner Day,' which is invite-only and focuses on engaging with n8n's partner network. The following day, October 14, 2026, is an 'Ecosystem Day,' open to everyone and serving as the main conference activity for the wider community. With a capacity of about 1,200 attendees, it promises to be a vibrant gathering. So, if you're keen to grasp the future trajectory of n8n's automation and AI endeavors, mark your calendars for this significant event.
SAP team secretly developed a competing product to partner n8n. On stage, SAP celebrated the partnership with the startup n8n - at the same time, a team was secretly working on a competing product. The board has taken action. 04.08.2026 - 15:56 SAP board member Steinhäuser (left), n8n founder Oberhauser: partners and at the same time competitors? Photo: Imago, picture alliance, n8n [M] Düsseldorf. Software development at SAP is running faster than ever. Products that used to take months are now sometimes ready within weeks, developers and managers report. Programming assistants such as Cursor, Claude Code, and Codex significantly increase productivity thanks to artificial intelligence (AI). However, the speed can result in a loss of control - as a case shows that is causing a stir at the DAX group.
What n8n actually costs, in Euro. n8n publishes its cloud pricing, which already puts it ahead of Glean and Open WebUI, neither of which publishes anything. Prices are in Euro on annual billing, and the billing unit is unusual in a good way: one execution is one full run of a workflow, no matter how many steps it contains or how much data it moves. Competitors that bill per step make long workflows expensive by design. The genuinely buyer-friendly part is that every plan has unlimited seats. In a category where per-user pricing is the norm and Glean has an effective floor of hundreds of users, that is a real structural difference for a mid-sized company. | Starter | 20 € | 2,500 | Unlimited | Entry tier | | Pro | 50 € | 10,000 | Unlimited | 20 concurrent executions | | Business | 667 € | 40,000 | Unlimited | Still no SSO | | Enterprise | On request | Custom | Unlimited | 200+ concurrent, SSO, SLA | | Community (self-hosted) | 0 € | Unlimited | Unlimited | Internal business use only | The row that matters for a compliance-minded buyer is the third one. SSO, SAML and LDAP are Enterprise-only, which means the 667 Euro Business plan still cannot authenticate your staff against your identity provider. Also Enterprise-only: external secret store integration, log streaming, unlimited shared projects, 365 days of insights and a support SLA. This is the same pattern Teamazing found across the category. Onyx and Flowise both put SSO behind a commercial licence too. The one exception is Open WebUI, which includes SSO, OIDC and LDAP for free and charges for branding instead. Where n8n beats everyone else in this cluster. Having been hard on the licence, credit where it is due. On European compliance paperwork n8n is the strongest vendor Teamazing has reviewed in this category, and it is not close. - A pre-signed DPA you can simply download. n8n publishes a data processing agreement as processor, ready to countersign and return. Glean does not. Onyx does not. This alone removes weeks from a procurement cycle. - A subprocessor document exists in its trust centre, which Glean's privacy policy does not provide. - SOC 2 Type 2 and SOC 3, with GDPR listed. Reports are behind an access request rather than fully public, and ISO 27001 is not listed. - A German legal entity. n8n GmbH is subject to German law, so there is no international transfer question to assess at the vendor level at all. One honest gap: n8n does not disclose its cloud hosting region on its own trust centre. Third-party write-ups state Frankfurt on Azure, and that is plausible for a Berlin company, but Teamazing could not confirm it from n8n's own documentation. Ask them in writing and get it into the contract, exactly as you would with any other vendor. Where n8n wins. * German GmbH, German law, no vendor-level transfer question * Pre-signed DPA available for download, not on request * Published pricing in Euro, unlimited seats on every plan * Billing per workflow run, not per step * Genuinely free and unlimited for your own internal automation Where it costs you. * Most restrictive licence of the seven tools Teamazing audited * Agency and reseller use is not covered by the default licence * SSO, SAML and LDAP are Enterprise-only, even at 667 Euro * Cloud hosting region not disclosed in its own trust centre * Non-master branches are not licensed at all What to do about it, depending on who you are. Find out where n8n is already running. With 199,000 stars and a one-line install, it is probably already automating something in your company. Free, anonymous. How to check your own position in ten minutes. Read the limitations section yourself. Open `LICENSE.md` in the n8n repository and read the four sentences under Limitations. It takes ninety seconds and it is the single most consequential thing in this article. Write down who benefits from each workflow. For every production workflow, name the party it serves. If that party is your own company, you are fine. If it is a client who pays you, flag it for legal review. Grep your instance for .ee. files in use. Enterprise-licensed features are not always obvious from the interface. If you are running a self-hosted build, confirm which enterprise-gated capabilities are actually switched on before you assume you are on the community terms. Download the DPA before the procurement meeting. n8n's pre-signed data processing agreement is available without asking. Bring it to the first meeting with your data protection officer. Very few vendors in this space let you do that. Get the hosting region in writing. The trust centre does not state it. Ask which region and provider your tenant runs in, and have the answer written into the contract rather than inferred from a blog post. Verdict: excellent product, licence you must actually read. n8n is the best-documented European vendor in this whole cluster. A German GmbH with a downloadable DPA, published Euro pricing, unlimited seats and SOC 2 is a genuinely easier procurement conversation than any US alternative Teamazing has reviewed, Glean included. The licence is the catch, and it is a real one rather than a technicality. Only for your own internal business purposes is a narrow permission, and an entire services industry has grown up around a product whose default terms do not obviously cover services. n8n is not hiding this. It sells commercial licences for exactly these cases, and the file has been public the whole time. But almost nobody writing about n8n mentions it. Use it for your own automation and it is one of the best deals in software. Build a business on top of it and buy the right licence first. Teamo AI: access control is not a surcharge. Who sees what is settled from day one. Permissions, plugins and tools are standard in Teamo AI, not an enterprise upgrade you discover later. 14 days free, no credit card, your team invited in minutes. The short version. The licence permits use only for your own internal business purposes. Agency and reseller work is not covered by the default terms. Not open source. The Sustainable Use License is flagged `NOASSERTION` by GitHub, and `.ee.` files need a separate Enterprise Licence on top. Branches other than master are not licensed at all. SSO, SAML and LDAP are Enterprise-only, even on the 667 Euro Business plan. Best compliance paperwork in the category: German GmbH, pre-signed downloadable DPA, subprocessor document, SOC 2 Type 2. But the cloud hosting region is not disclosed on n8n's own trust centre. Get it in the contract.