Trigger Nodes in Automations

Trigger nodes define how an automation starts. Every automation needs one trigger.

System Event

The System Event node starts an automation when something happens inside the workspace.

This is useful when you want the automation to react automatically to platform activity instead of waiting for manual execution or a schedule.

What it does

It listens for internal Praxsuite events related to a selected feature.

How to configure it

The configuration panel includes:

• Name

  Defines how the node appears in the canvas and in run logs.

• Feature

  Lets you choose which area of the system the event belongs to. The screenshots show options such as:

  • Table

  • Form

  • User

  • Workspace

  • Flow

  • Status

• Match mode

  Defines how filters should be interpreted:

  • All conditions must match

  • Any condition matches

• Require value change

  When enabled, the trigger fires only if a field value actually changed.

When to use it

Use System Event when the automation should react to changes made inside Praxsuite, such as updates to records, form activity, or other workspace actions.

Webhook

The Webhook node starts an automation when Praxsuite receives an incoming webhook.

This is useful for integrations with external systems that need to send data into Praxsuite.

What it does

It waits for an external HTTP request and uses its payload to start the workflow.

How to configure it

The configuration panel includes:

• Node label

  The display name of the webhook node.

• Webhook Receiver

  Lets you choose the receiver endpoint that will be associated with this trigger.

• Link

  Connects the selected receiver.

• Sample Payload

  Displays an example of the expected JSON body, which helps you understand the shape of incoming data.

When to use it

Use Webhook when another system needs to trigger your automation, such as:

• e-commerce platforms

• CRMs

• external forms

• custom applications

• partner systems

Manual

The Manual node starts an automation manually or via API.

What it does

It allows the automation to be run on demand instead of reacting to an event or schedule.

How to configure it

In the current UI shown in the screenshot, this node has no additional settings yet.

The panel indicates:

Settings for this node type are not yet implemented.

When to use it

Use Manual when:

• you want to test a workflow

• the automation should only run when a user decides

• the flow is not meant to run continuously or automatically

Schedule

The Schedule node starts an automation at a defined time or interval.

What it does

It runs the automation based on time.

How to configure it

The configuration panel includes:

• Node label

  The display name of the trigger.

• Schedule mode

  Defines how the timing works. The screenshots show options such as:

  • Every N seconds

  • Daily at a specific time

• Run every (seconds)

  Used when the mode is interval-based. The screenshot shows an example of 60.

• Time of day (HH:MM, 24-hour)

  Used when the mode is daily scheduling. The screenshot shows an example such as 09:00 a.m.

Praxsuite also shows a timezone note indicating that the schedule is interpreted using the workspace timezone and then converted to UTC automatically.

When to use it

Use Schedule when the automation should run:

• every few seconds

• every few minutes

• once a day

• at a recurring operational time

This is especially useful for recurring checks, alerts, syncs, and daily jobs.