Automations

In this section

• Automations OverviewAn automation is a flow that runs on Praxsuite's servers: something happens, and a chain of steps does work in response. Rows get written, emails go out, an external API…
• Trigger NodesA trigger is how an automation starts. Every automation has exactly one, and the choice decides two things: when the flow runs, and what it has to work with when it does.
• Database NodesSeven nodes read and write workspace tables. They are the ones almost every automation uses, so the details here pay for themselves quickly.
• Logic NodesSix nodes decide what runs, how often, and what happens when something breaks. Four of them branch — they have more than one output, and which one fires is the whole…
• Action NodesEleven nodes that make something happen outside the current flow: call an API, start another automation, run an AI agent, manage the people who sign into your apps, or…
• Communication NodesSeventeen nodes reach people: email, push, live calls, scheduled meetings and Instagram. It is the largest category in the catalog, and the one where the constraints come…
• Utility, Vault and Docs NodesThe remaining nodes: secrets, timing, documents, and one that does nothing at all on purpose.
• Create your First AutomationLearn how to create your first automation in Praxsuite step by step. This guide explains how to create an automation, choose a trigger, add action nodes, build the…
• Server-Side LogicMost products that let you build a UI leave you stranded the moment you need something to happen on a server. Automations are Praxsuite's answer to that: they are the…
• Runs and DebuggingWhen an automation misbehaves, the automation is rarely where the answer is. The run is. A run records what actually happened, step by step, with the values that were…