Zapier Functions Bridge Business and Engineering

Functions is how Zapier avoids getting squeezed between no code users on one side and full developers on the other. Instead of forcing teams to choose drag and drop or code, Zapier is building a shared layer where an ops lead can sketch a workflow, then an engineer can refine the same flow with API calls, custom logic, and governance. That expands Zapier from a solo automation tool into a cross functional system for building AI powered work.

• Inside Zapier, the bridge is concrete. Functions lets users define triggers, call APIs, and shape workflows in code inside a web IDE, while Custom Actions lets less technical users generate new actions without writing code. The product is meeting the rise of the builder persona, people comfortable enough with code to customize, but not traditional engineers.
  1 sacra
• This matters because AI workflows are rarely fully autonomous. Zapier describes reliable enterprise setups as a mix of deterministic steps, data collection, and tightly placed LLM calls. That mix naturally requires collaboration, because business teams know the process and engineers know the edge cases, permissions, and APIs.
  1 sacra 2 sacra
• The competitive line is moving toward this middle layer. n8n wins with intermediate users who learn enough JSON or JavaScript to customize workflows, while Retool, Airtable, Zapier, and Replit are converging on enterprise workflow creation from different starting points. The prize is owning the builder who is neither pure business user nor pure engineer.
  3 sacra 4 sacra

Going forward, the winners in automation will be the products that let a larger share of employees act like software builders without handing everything over to IT. If Zapier keeps turning business knowledge into editable workflows that engineers can trust and extend, it can move upmarket from simple app automation into the operating layer for agentic work across teams.