Triggers
Cron, webhooks, and data-change triggers that run your workflows automatically.
Define what should happen and when. Fastero triggers fire on a schedule, in response to an inbound webhook, or when a monitored query result changes — then run SQL, notebooks, Slack alerts, and AI agent plans without manual intervention.
Trigger types and actions
Three trigger types. Six action types. One configuration surface.
Pick the trigger type that matches your use case, attach one or more actions, and the system runs reliably in the background. No custom code, no infrastructure to manage.
Cron schedules
Run SQL queries, refresh dashboards, or execute notebooks on a recurring schedule. Standard cron syntax with timezone support — set it once and forget it until you need to change the cadence.
Webhook triggers
Receive inbound webhooks from Stripe, Salesforce, GitHub, or any system that can POST JSON. Each trigger gets a unique endpoint with HMAC signature verification so you know the payload is authentic.
Data-change detection
Monitor a table or query result for changes. When a row is inserted, updated, or deleted, the trigger fires. Useful for alerting when a metric crosses a threshold or when new data lands in the warehouse.
Actions: SQL, notebooks, Slack, email, webhooks
When a trigger fires, it can run a SQL query, execute a Jupyter notebook, send a Slack message, fire an email, call an external webhook, or kick off an AI agent plan. Chain multiple actions in sequence.
AI agent plans in the loop
Triggers can execute AI agent plans that use NL2SQL, charting, and the full 89-tool toolkit. A cron trigger can ask "summarize yesterday's revenue by region" every morning and post the answer to Slack.
Composio app integrations
Connect triggers to approximately 90 third-party apps through Composio — including Google Sheets, Jira, HubSpot, and Notion. The trigger fires, the action runs, and the result lands in the system your team already uses.
When to use triggers
Automate the recurring work your team does by hand today.
Scheduled reporting without manual work
Set a cron trigger to run a revenue query every Monday at 8 AM and post the result to a Slack channel. No one has to remember to pull the numbers — the trigger handles it.
Reacting to external events
When Stripe sends a payment webhook, the trigger can update a tracking table, refresh a dashboard, and notify the account manager. The response happens in seconds, not hours.
Threshold-based alerts
Monitor a query result (e.g., "daily signups") and trigger a Slack alert when it drops below a threshold. Data-change detection catches the problem before someone notices a flat dashboard.
Keeping apps and caches fresh
Wire data-change triggers to hosted Streamlit apps so they reload when the underlying data updates. Users always see current numbers without manual refreshes or fixed polling intervals.
Related capabilities
Triggers are the starting point. Workflows and actions are the follow-through.
Workflows
Chain conditions, thresholds, and multi-step actions after a trigger fires.
NL2SQL
Use AI-generated SQL as the query a trigger monitors or runs on schedule.
Hosted apps
Connect triggers to Streamlit apps so they refresh when data changes.
API and webhooks
Receive inbound webhooks as triggers and send outbound events as actions.
Frequently asked questions
Common questions about triggers.
What trigger types does Fastero support?
Three types: cron schedules (standard cron syntax with timezone support), incoming webhooks (each trigger gets a unique endpoint with HMAC verification), and data-change detection (monitors a query result and fires when rows are inserted, updated, or deleted).
What actions can a trigger run?
A trigger can run a SQL query, execute a Jupyter notebook, send a Slack message, fire an email, call an external webhook, or kick off an AI agent plan. You can chain multiple actions in sequence so a single trigger fires a multi-step workflow.
How do webhook triggers verify that a payload is authentic?
Each webhook trigger endpoint supports HMAC-SHA256 signature verification. The sending system signs the payload with a shared secret, and Fastero verifies the signature before processing. You can also restrict triggers to specific IP addresses with allowlists.
Can triggers run AI agent plans automatically?
Yes. A cron trigger can execute an AI agent plan that uses NL2SQL, charting, and the full tool suite. For example, a daily trigger can ask "summarize yesterday's revenue by region" and post the AI-generated answer to a Slack channel every morning.
How many third-party app integrations are available?
Triggers can deliver results to approximately 90 third-party apps through Composio integrations, including Google Sheets, Jira, HubSpot, Notion, and Slack. The trigger fires, the action runs, and the result lands in the system your team already uses.
How does data-change detection work?
You define a SQL query that returns a result set. Fastero polls the query on a configurable interval and compares the current result to the previous one. When a difference is detected — new rows, changed values, or deleted rows — the trigger fires.
Let the data tell you when something needs attention.
Set up a trigger in minutes. Cron for schedules, webhooks for external events, data-change detection for threshold alerts. Free to start.