Skip to main content

​
What Are Workflow Triggers?

Workflow triggers are the starting events that launch your automation processes. Every workflow requires exactly one trigger that defines when and how the automation begins executing. Available trigger types:
  • Scheduled: Run workflows on recurring schedules
  • Webhook: Respond to external HTTP requests
  • Manual: Start workflows on-demand from the dashboard
  • SNS Events: React to internal platform events
  • Workflow Calls: Enable workflow-to-workflow communication

​
Complete Trigger Types Reference

Choose the right trigger type based on how you want to start your workflow automation:

​
Scheduled Trigger: Automate Recurring Tasks

Scheduled triggers run workflows automatically on recurring time schedules. Perfect for regular maintenance tasks, periodic data synchronization, automated reports, and time-based business processes. Common use cases:
  • Daily backup and maintenance tasks
  • Weekly report generation
  • Monthly billing and invoicing
  • Hourly data synchronization
  • Custom interval monitoring

​
Configuration

​
schedule_type
string
required
The type of schedule to use.Options: interval, cron, daily, weekly, monthly
​
schedule_value
string
The 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 like 0 9 * * * (every day at 9 AM).
​
description
string
An optional description for what this trigger does.

​
Webhook Trigger: Real-Time External Integrations

Webhook triggers provide secure, unique URLs that start workflows when external services send HTTP POST requests. Essential for real-time integrations, API callbacks, and event-driven automation. Common use cases:
  • Payment processing callbacks
  • Form submission handling
  • Third-party service notifications
  • API integration endpoints
  • Real-time data ingestion
The webhook URL is automatically generated and secured by the system when you save the workflow. You do not need to configure it.

​
Configuration

​
description
string
An optional description for what this webhook is for.

​
Behavior

The entire JSON body of the incoming POST request, along with all HTTP headers, will be available as the output of this trigger node.

​
Manual Trigger: On-Demand Workflow Execution

Manual triggers enable on-demand workflow execution through the user interface. Users can start these workflows manually and provide custom input data for each execution. Common use cases:
  • One-time data migrations
  • Administrative maintenance tasks
  • Testing and debugging workflows
  • Custom reporting requests
  • Emergency response procedures

​
Configuration

​
description
string
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: Platform Event Integration

SNS triggers listen for internal platform events, enabling deep integration with other Altostrat services. Advanced users can create workflows that respond automatically to system events and user actions. Common use cases:
  • User lifecycle automation (registration, activation)
  • Payment and subscription event handling
  • System monitoring and alerting
  • Cross-service data synchronization
  • Audit trail and compliance workflows

​
Configuration

​
event_name
string
required
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).
​
description
string
An optional description for what this trigger does.

​
Workflow Trigger: Create Reusable Workflow Components

Workflow triggers enable workflow-to-workflow communication, creating reusable automation components that can be called from multiple parent workflows. Build modular, maintainable automation systems. Common use cases:
  • Shared utility functions (data validation, formatting)
  • Common notification workflows
  • Reusable integration patterns
  • Modular business logic components
  • Complex workflow orchestration
A workflow with this trigger cannot be started manually or by a schedule. It can only be started by another workflow.

​
Configuration

​
description
string
An optional description of what this callable workflow does.
​
expected_variables
array
Define the data structure you expect to receive from the calling workflow. This is for documentation purposes and helps when building the calling workflow.
⌘I