Button-triggered vs. event-triggered automation: when to use each one in Jestor?

In Jestor, there are two types of automation: button-triggered, which requires a manual action from the user, and event-triggered, which fires on its own when an event happens, like a card moving to a new phase or a field being changed.

The risk of choosing the wrong automation type

Companies automating processes for the first time often aren't sure which path to take. Choosing wrong creates two opposite problems: too much automation with no human control over sensitive decisions, or too little automation, with the team still clicking through steps that could be automatic.

Both types are configurable with no code and keep an execution log within the platform itself.

How to decide which one to use

Assess the risk of the action: the more sensitive it is, the more it's worth keeping a button.
Use a button when the action requires human confirmation, like approving a payment.
Use a trigger when the process can proceed without manual checking, like sending a WhatsApp message on phase change.
Set up custom error messages for when the condition isn't met.
Combine both in the same process, when it makes sense.

Criterion	Button automation	Trigger automation
Who starts the action	The person, manually	The system, upon detecting the event
Best for	Sensitive decisions, like approvals	Repetitive, low-risk steps
Validation before acting	Yes, with conditions and error message	Yes, with conditions on the trigger itself
Execution log	Available on the platform	Available on the platform

Why choose Jestor?

Jestor lets you set up both types with no code, using the same automation engine underneath — the difference is just who starts the action, which makes it easier to design flows that mix automatic steps with human decision points.

Frequently Asked Questions

Can a process have both button and trigger automation at the same time? Yes, it's common to combine both types within the same flow, depending on the step.

Do button automations accept validations before running? Yes, you can set conditions and a custom error message for when the condition isn't met.

Is there an execution history for automations? Yes, Jestor keeps an execution log, available within the platform itself.

Reference Video

Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all without code and with AI support.

Get to know Jestor at jestor.com and see how to take your company's management to a new level of efficiency and integration.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize