Triggers

Triggers are the entry point to any flow in Agistry. They define when and how a flow should be executed, without requiring any manual SDK calls. This allows you to build fully automated pipelines that react to events: like a document upload, a Stripe payment, or a Slack command — all with zero code changes to your app.

Trigger Type	Use Case
Manual	Button in UI or CLI
Webhook	External services (Stripe, Discord)
Scheduled	Time-based automation
API Call	From backend using SDK

Whether you're building one-off automations or full-blown agents, Agistry give you a visual and modular way to scale your thinking into action. With adapters, triggers, and agent logic all managed in one place, you can ship faster, update in real time, and let the platform handle the execution complexity, so you can stay focused on the outcomes that matter.

---

Agistry Hub offers pre-built triggers(you can also build custom triggers using our framework). To add a new trigger to your agent, access the agent page and click "Add new" in trigger list.

This will open a modal where you can select triggers from pre-built trigger list:

Triggers are different and require configuration, all triggers have different inputs and configuration.

Triggers don’t perform actions themselves, they simply tell the system when an action should happen. The actual action is executed by an Adapter. Make sure to install the necessary adapters for your agent to function properly.