[{"data":1,"prerenderedAt":127},["ShallowReactive",2],{"blog-en-build-your-own-automations-visual-editor":3},{"id":4,"title":5,"body":6,"categories":106,"date":109,"description":12,"draft":110,"excerpt":111,"extension":112,"image":113,"lang":114,"meta":115,"modified":116,"navigation":117,"noindex":110,"path":118,"related":111,"seo":119,"seoDescription":120,"seoTitle":121,"slug":122,"sourcePath":123,"sourceRoute":111,"stem":124,"tags":111,"translated":110,"type":125,"wpId":111,"__hash__":126},"blog\u002Fen\u002Fblog\u002Fbuild-your-own-automations-visual-editor.md","Build your own automations – no programming skills required",{"type":7,"value":8,"toc":97},"minimark",[9,13,18,21,25,28,32,35,39,64,71,75],[10,11,12],"p",{},"Handling recurring processes in your CRM or ERP by hand costs time that many teams simply do not have. Traditionally, automation means either rigid rules defined by the software vendor – or a development team that programs custom logic. 1Tool takes a third route: with the visual automation editor, you assemble your own workflows by drag and drop, right in the interface, without writing a single line of code.",[14,15,17],"h2",{"id":16},"a-canvas-instead-of-a-code-editor","A canvas instead of a code editor",[10,19,20],{},"Technically, the editor is based on a node-based canvas – a principle you may know from tools such as Zapier or n8n. Instead of writing conditions as text or in configuration files, you place individual building blocks as nodes on a canvas and connect them with your mouse to form a workflow. Each node represents a clearly defined step: a trigger, a condition or an action. The entire structure – node positions, the connections between them, even the zoom level of the view – is saved. So an automation you have built can be reopened, understood and adjusted at any time, including by colleagues who did not create the workflow themselves.",[14,22,24],{"id":23},"getting-started-name-description-trigger","Getting started: name, description, trigger",[10,26,27],{},"Every automation in 1Tool starts with three simple inputs: a name, a short description and the choice of a trigger – the event that sets the automation in motion in the first place. Which triggers are available is not hard-coded in the editor itself but loaded from the system in a structured way, with a name and description for each option. This means the range of possible triggers can grow over time without anything changing in how you use the editor. Once you have chosen the trigger, you extend the workflow with conditions and actions, which you connect to the trigger as further nodes.",[14,29,31],{"id":30},"who-this-approach-is-for","Who this approach is for",[10,33,34],{},"This approach is particularly valuable for teams that do not have their own IT or development department behind them – in other words, for most small and medium-sized businesses. Instead of writing a development brief and waiting for it to be implemented, business users design their workflows themselves, right where they work with the data. This not only significantly shortens the time from idea to running automation, it also ensures that the people who know a business process best can map it themselves – without a detour via a technical intermediary.",[14,36,38],{"id":37},"frequently-asked-questions","Frequently asked questions",[10,40,41,45,48,49,52,54,55,58,60,61],{},[42,43,44],"strong",{},"Do I need to be able to program to build an automation?",[46,47],"br",{},"\nNo. The editor is deliberately designed so that you arrange and connect building blocks by drag and drop – no programming skills required.\n",[42,50,51],{},"Where can I see which triggers, conditions and actions are available?",[46,53],{},"\nThey are shown directly in the editor with a name and description and are loaded from the system, so you always see the options currently available.\n",[42,56,57],{},"Can I change an existing automation later on?",[46,59],{},"\nYes. The complete setup, including the arrangement and connections of the nodes, is saved and can be reopened and adjusted at any time.\n",[42,62,63],{},"Would you like to see how the automation editor could be used in your company?",[10,65,66],{},[67,68,70],"a",{"href":69},"\u002Fen\u002Fappointment-request\u002F","Book a demo",[14,72,74],{"id":73},"read-more","Read more",[76,77,78,85,91],"ul",{},[79,80,81],"li",{},[67,82,84],{"href":83},"\u002Fen\u002Fblog\u002Ftrigger-condition-action-automation-logic\u002F","Trigger, condition, action: how 1Tool automation thinks",[79,86,87],{},[67,88,90],{"href":89},"\u002Fen\u002Fblog\u002Fbranching-automations-multiple-paths\u002F","Branching automations: when a simple if-then is not enough",[79,92,93],{},[67,94,96],{"href":95},"\u002Fen\u002Fblog\u002Fautomation-builder-use-cases\u002F","What you could build with the automation builder",{"title":98,"searchDepth":99,"depth":99,"links":100},"",2,[101,102,103,104,105],{"id":16,"depth":99,"text":17},{"id":23,"depth":99,"text":24},{"id":30,"depth":99,"text":31},{"id":37,"depth":99,"text":38},{"id":73,"depth":99,"text":74},[107,108],3329,3330,"2026-06-02T09:00:00",false,null,"md","\u002Fmedia\u002F2026\u002F07\u002Fautomatisierungen-selbst-bauen-visueller-editor.jpg","en",{},"2026-07-25T08:23:04",true,"\u002Fen\u002Fblog\u002Fbuild-your-own-automations-visual-editor",{"title":5,"description":12},"Build automations yourself by drag and drop: the visual automation editor in 1Tool, no programming skills required.","Build your own automations without code","build-your-own-automations-visual-editor","\u002Fen\u002Fblog\u002Fbuild-your-own-automations-visual-editor\u002F","en\u002Fblog\u002Fbuild-your-own-automations-visual-editor","posts","MG6g429GpFMoXrpuXrByZbcr3sfvMD3yIw8u1plNtqE",1791582060591]