Low-code and no-code platforms have evolved from niche tools into a multi-billion-dollar segment in 2026, with the market valued in the tens of billions of dollars and projected to approach fifty billion by the end of the decade. According to Mordor Intelligence’s low-code development platform market report, the low-code development platform market is estimated at roughly $31.6 billion in 2026, up from about $26.3 billion in 2025, with growth to $78.9 billion by 2031 at a 20.1% CAGR. Research and Markets’ low-code forecast projects the market at $52.5 billion in 2026, growing to $88.6 billion by 2032, while Forrester’s analysis suggests the low-code market could approach $50 billion by 2028. InfoWorld’s coverage and IDC’s worldwide forecast underscore that growth is driven by developer shortages, legacy modernization, regulatory deadlines, and the need for rapid application delivery, with AI-driven development and generative AI integration accelerating adoption.
At the same time, many no-code and low-code platforms now offer custom code steps so that power users and developers can extend workflows beyond pre-built actions. Zapier’s Code by Zapier and Power Automate’s scripting actions allow Python (and in some cases JavaScript) to run inside visual workflows, so that a Zap or flow can call a small Python snippet to parse data, compute a value, or call an API that has no native connector. According to Zapier’s guide to Code by Zapier, Code steps support Python and JavaScript, enabling tasks such as lookup tables, line-item processing, cleaning raw data (e.g., XML parsing), dynamic date logic, and formatting AI-generated output. Zapier’s help on using Python in Zaps notes that code runs in a sandboxed Python 3.7.2 environment with inputData from previous steps, so that a few lines of Python can turn a no-code workflow into a hybrid automation. Microsoft’s Power Automate scripting reference states that desktop flows can run PowerShell, Python, VBScript, JavaScript, and C#/VB.NET, giving automation authors an escape hatch when pre-built actions are not enough.
A typical pattern is to use a Code step when the platform has no native action for a given API or transform. For example, a Zap might fetch a webhook payload, then run a short Python block to normalize or validate the payload before sending it to a spreadsheet or CRM. In practice, that might look like reading from the input dictionary, applying a transform, and returning a result for the next step—all in a handful of lines that run inside the same no-code canvas.
# Code by Zapier (Python): normalize webhook payload for next step
def main(input_data):
raw = input_data.get("raw_payload", "{}")
# e.g. parse, validate, or reshape
return {"normalized": raw.strip()}
From there, the next step in the Zap uses the returned fields; the point is that Python extends the no-code layer without leaving the workflow builder.
What Low-Code and No-Code Are in 2026
Low-code platforms provide visual builders (drag-and-drop, form designers, flow editors) and pre-built connectors so that users can build applications or workflows with minimal hand-written code; no-code platforms aim to require no code at all for typical use cases, though many now offer optional code steps or expressions for power users. The line between low-code and no-code is blurry: tools like Airtable, Notion, Zapier, Make (Integromat), and Power Automate are often called no-code for end-to-end automation, while OutSystems, Mendix, Salesforce Lightning, and Microsoft Power Apps are typically classified as low-code for application development. In 2026, the important distinction is less “code vs no-code” and more who builds what, how fast, and under what governance—with citizen developers and business analysts building a large share of automations and simple apps, and IT or developers stepping in for integration, security, and complex logic.
According to Mordor Intelligence, cloud deployment accounted for about 60% of market share in 2025, web-based development for about 54% of revenue, and large enterprises for about 63% of the market, though SMEs are growing faster. BFSI and education are among the leading adopters. Asia-Pacific is the fastest-growing region in many forecasts, while North America holds the largest share of revenue.
Citizen Development and the Developer Shortage
Citizen development—non-IT staff building applications and automations with low-code or no-code tools—has become a strategic response to developer shortages and backlogs. When business users can build their own workflows and simple apps, IT can focus on architecture, security, and integration while still governing what tools and data are allowed. According to Forrester and Mordor Intelligence, growth is fueled by legacy modernization, regulatory and compliance deadlines, and the need for rapid delivery; AI-driven development and generative AI are further accelerating adoption by suggesting flows, formulas, and even code steps. The risk is shadow IT and unmanaged sprawl, so enterprises are increasingly standardizing on a small set of approved low-code/no-code platforms and defining governance, training, and support so that citizen development scales safely.
Python and JavaScript Inside No-Code Workflows
Code by Zapier and similar features in other platforms let users insert Python or JavaScript steps into otherwise visual workflows. According to Zapier’s Code by Zapier guide and Zapier’s help on Python in Zaps, code steps can act as triggers or actions, receive inputData from previous steps, and return data to the next step; they run in a sandboxed environment with time and memory limits that depend on plan. Use cases include lookup tables, parsing XML or JSON, date and string formatting, and shaping AI output before it is sent to another app. Microsoft’s Power Automate scripting documentation states that desktop flows can run Python (among other languages) for scripting actions, often with administrator rights when accessing protected resources. The result is a hybrid model: most of the workflow is no-code, with Python (or JavaScript) filling the gaps where no connector or action exists.
Zapier, Make, and the Automation Stack
Zapier and Make (formerly Integromat) are among the most widely used no-code automation platforms, connecting thousands of apps with pre-built triggers and actions. Users build Zaps or scenarios by chaining steps visually; when a trigger fires (e.g., new row in a sheet, new email), the workflow runs through a sequence of actions (e.g., create a record, send a message). Code steps allow custom logic in the middle of that chain, so that data can be transformed, validated, or enriched with a few lines of Python before continuing. The same pattern appears in Airtable Scripting, Notion formulas and integrations, and Google Apps Script—each offering a scripting or code layer for users who need more than point-and-click. In 2026, the automation stack for many teams is no-code first, with Python or JavaScript used only where necessary.
Power Platform and Enterprise Governance
Microsoft Power Platform (Power Automate, Power Apps, Power BI) has become the default low-code stack for many enterprises already on Microsoft 365 and Azure. According to Mordor Intelligence and Research and Markets, large enterprises hold the majority of market share, and governance—who can create what, which connectors are allowed, and how data is shared—is a key differentiator. Power Platform offers environments, data loss prevention (DLP) policies, and admin centers so that IT can enable citizen development while controlling risk. Power Automate supports cloud flows (no-code and low-code) and desktop flows (RPA and scripting), with Python available for desktop flow scripting as noted in Microsoft’s scripting reference. The combination of broad adoption, enterprise governance, and optional code has made Power Platform a central piece of the low-code landscape in 2026.
AI-Assisted Development and the Next Layer
Generative AI and AI-assisted development are reshaping low-code and no-code. Copilots can suggest flows, generate formulas, and draft code steps from natural language, so that users describe what they want and the tool proposes a workflow or a Python snippet. According to IDC’s worldwide low-code forecast and Mordor Intelligence, AI-driven development and generative AI integration are key growth drivers; techniques such as RAG and fine-tuning are increasingly relevant for developers and platform vendors. The boundary between code and no-code is shifting: more users can author or modify code steps with AI assistance, while traditional developers can use low-code to prototype or hand off maintenance to business users. In 2026, the trend is toward convergence—one canvas where visual and code coexist, with AI helping both sides.
Security, Governance, and Shadow IT
Security and governance remain critical as low-code and no-code spread. Unmanaged workflows can expose data, violate compliance, or create integration debt. Enterprises are addressing this with approved platforms, DLP policies, audit logs, and training so that citizen developers build within guardrails. Python and other code steps add another dimension: they run in sandboxed environments in many products, but they can still access data passed from previous steps and send it to the next; review and approval of code steps is part of mature governance. In 2026, best practice is to treat low-code/no-code as first-class development—with ownership, change control, and security review—rather than as ad hoc tooling.
Conclusion: Low-Code, No-Code, and the Hybrid Layer
In 2026, low-code and no-code platforms form a multi-billion-dollar segment approaching fifty billion dollars in market size, with double-digit growth driven by developer shortages, legacy modernization, and AI-assisted development. Citizen development is mainstream, and Python (and JavaScript) inside no-code workflows—via Zapier Code, Power Automate scripting, and similar features—extends automation beyond pre-built actions without leaving the visual builder. A typical pattern is to build most of a workflow with triggers and actions, then add a short Python step when a transform or API call has no native connector; that keeps the workflow manageable while retaining the power of code where it matters.
The rise of generative AI is blurring the line between code and no-code further: more users can author or edit code steps with AI help, and more developers can hand off maintainable automations to business users. For enterprises, the priority is governance—approved platforms, DLP, and review of code steps—so that low-code and no-code scale safely. For practitioners, Python once or twice in a Zap or flow remains the escape hatch that makes no-code sufficient for most real-world automations.
