Workflows
Triggers
Learn about the different events that can start your workflows, from schedules to webhooks.
A Trigger is the starting point of every workflow. It defines the event that initiates the automation process. Each workflow must have exactly one Trigger node.
Types of Triggers
Scheduled Trigger
The Scheduled Trigger runs your workflow on a recurring basis. This is perfect for tasks like daily reports, weekly data syncs, or monthly cleanups.Configuration
The type of schedule to use.Options:
interval, cron, daily, weekly, monthlyThe value for the schedule. This is required for
interval and cron types.- For
interval: A string like “5 minutes” or “1 hour”. - For
cron: A standard cron expression like0 9 * * *(every day at 9 AM).
An optional description for what this trigger does.
Webhook Trigger
The Webhook Trigger provides a unique, secure URL. When an external service sends aPOST request to this URL, the workflow will start. This is ideal for real-time integrations.
The webhook URL is automatically generated and secured by the system when you save the workflow. You do not need to configure it.
Configuration
An optional description for what this webhook is for.
Behavior
The entire JSON body of the incomingPOST request, along with all HTTP headers, will be available as the output of this trigger node.
Manual Trigger
The Manual Trigger allows a workflow to be started on-demand by a user clicking the “Execute” button in the user interface. This is useful for tasks that need human initiation.Configuration
An optional description of the manual process.
Behavior
When executed, a user can provide an optional JSON object as the initial data for the workflow run. This allows for passing in specific parameters for that particular execution.SNS Trigger
The SNS Trigger listens for specific internal system events published to a topic. This is an advanced trigger used for deep integration with other parts of the Altostrat platform.Configuration
The specific event pattern to listen for. Wildcards (
*) are supported. For example, user.created or payment.*. You can listen for multiple patterns by separating them with a comma, but they must share the same root category (e.g., user.created,user.updated is valid, but user.created,payment.succeeded is not).An optional description for what this trigger does.
Workflow Trigger
This special trigger allows a workflow to be called by another workflow using the Trigger Workflow Action. It turns a workflow into a reusable subroutine or function.A workflow with this trigger cannot be started manually or by a schedule. It can only be started by another workflow.
Configuration
An optional description of what this callable workflow does.
Define the data structure you expect to receive from the calling workflow. This is for documentation purposes and helps when building the calling workflow.