> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Use Trigger-Based Automation Inside a BPM Process
- URL: https://blog.jestor.com/trigger-based-automation-bpm/
- Published: 2026-09-15T20:23:05.000Z
- Updated: 2026-09-15T20:23:05.000Z
- Author: Bruno Bannach

Using trigger-based automation means an action fires automatically the moment a specific event happens — a card changes stage, a field updates, a new record is created — instead of requiring someone to click a button every time. In **Jestor**, this is one of two native automation types, alongside button-triggered automation.

Button-triggered automation still requires someone to remember to click it. Event-triggered automation removes that dependency entirely, firing the moment the underlying condition is met.

## What manual, button-only automation still requires

- Someone remembering to click the automation trigger at the right moment
- Delays between the actual event and the automation firing
- Inconsistent execution if different people forget the manual step
- No automation for events that happen outside anyone's active attention

## How event-triggered automation works

- Automations fire based on a **trigger** — a stage change, a field update, a new card
- No manual click required; the automation runs the moment the condition is met
- Multiple triggers can exist within the same process for different events
- Execution logs show exactly what ran, and in response to which trigger

## Why Jestor fits this use case

- Both trigger types (button and event) are native, not a premium add-on
- Event-based triggers remove dependency on someone remembering a manual step
- Combines naturally with conditional logic for more precise automation
- Execution logs keep every trigger-based action auditable

| Automation type  | How it fires                          |
| ---------------- | ------------------------------------- |
| Button-triggered | Manual click, with defined conditions |
| Event-triggered  | Automatically, on a specific event    |

## Frequently Asked Questions

**Can a process use both trigger types together?** Yes, button and event triggers can coexist in the same process. More at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

**Does event-triggered automation require coding?** No, it's configured without code.

**Are trigger-based actions logged for auditing?** Yes, execution logs show what ran and why.

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.