Automation Triggers Guide
A trigger is the event that starts your automation workflow. StackBloom Automations supports five trigger types — each suited for different use cases.
Schedule Trigger
Runs your workflow automatically on a recurring schedule. Ideal for reports, digest emails, data sync jobs, and recurring reminders.
Frequency Options
All schedules run in UTC by default. You can change the timezone in your workflow settings.
Webhook Trigger
Receive an HTTP POST request from any external system to start your workflow. Use this to connect StackBloom with Stripe, Shopify, GitHub, or any tool that supports webhooks.
How to Configure
- Select "Webhook" as your trigger type
- StackBloom generates a unique webhook URL for your workflow
- Copy the URL and paste it into the external tool's webhook settings
- Send a test payload to verify the connection
- Map payload fields to workflow variables for use in actions
Example Webhook Payload
{
"event": "payment.completed",
"customer": {
"email": "jane@example.com",
"name": "Jane Smith"
},
"amount": 9900,
"currency": "usd"
}Form Submission Trigger
Fires every time a respondent submits one of your StackBloom Forms. All form field values are automatically available as workflow variables.
- Select "Form Submission" as your trigger type
- Choose the form from the dropdown (lists all your published forms)
- Optionally filter to specific forms or fields using conditions
- Reference form fields in your actions using variable syntax:
{{field.email}}
Available Variables
{{form.id}} — Form ID{{form.name}} — Form name{{submission.id}} — Unique submission ID{{field.[field_name]}} — Any field value{{submission.created_at}} — Submission timestampEmail Received Trigger
Trigger a workflow when an email arrives at a StackBloom-managed inbox. Works alongside InboxBridge to route, categorize, and respond to incoming emails automatically.
- Select "Email Received" as your trigger type
- Choose which connected email account to monitor
- Add conditions to filter by subject, sender, or keywords
- Use email data in your actions — reply, forward, or create records
This trigger requires an active InboxBridge subscription with at least one connected email account.
API Call Trigger
Trigger a workflow programmatically from your own code or infrastructure using the StackBloom API. Useful for internal tools, server-side events, and custom integrations.
Example API Call
POST https://stackbloom.io/api/automations/trigger
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
{
"workflow_id": "wf_abc123",
"payload": {
"user_id": "usr_xyz",
"event": "signup_completed"
}
}- Select "API Call" as your trigger type
- Note your workflow ID from the settings panel
- Generate an API key from your account settings
- Call the trigger endpoint with your payload from any system
Trigger Tips
One Trigger Per Workflow
Each workflow has exactly one trigger. If you need multiple triggers to run the same actions, create separate workflows or use an Automations template.
Test Your Trigger First
Before adding conditions and actions, use the "Test Trigger" button to send a sample payload and verify that data arrives correctly.
Webhook Security
Each webhook URL includes a secret token. Validate the X-StackBloom-Signature header in your receiving service to prevent unauthorized triggers.
Next Steps
Open Automations
Go to the Automations dashboard and start building workflows
Creating Workflows
Full walkthrough of building your first automation workflow
Adding Conditions
Learn how to filter when your workflows run using IF/AND/OR logic
Get Help
Contact support if you need help configuring a specific trigger type