Dino ERP is built, sold and supported by TechDino — one-time purchase with full source code.
+91 70936 08698 info@techdino.inBuy Dino ERPBuild event-driven rules with conditions and ordered actions to move routine work forward across the company.
Automation runs
Workflow automation in Dino ERP lets you build event-driven rules with conditions and ordered actions, test them before enabling, and review every run. Actions include sending e-mail, creating tasks, posting signed webhooks and scheduling delayed follow-ups. Loop protection stops chains of automated events from running away.
Last updated · TechDino
Workflow automation
Choose an event, define the conditions that matter and test a rule before enabling it.
Automation runs
Completed
Notify buyer
Scheduled
Create follow-up
Matched
Create follow-up
Queued
Send e-mail
Workflow automation
Send e-mail, create tasks, post signed webhooks and schedule follow-up actions.
Automation runs · activity
Purchase request approved
Completed · Notify buyer
Invoice overdue
Scheduled · Create follow-up
Invoice due soon
Matched · Create follow-up
Scheduled follow-up
Queued · Send e-mail
Workflow automation
Review run outcomes and errors, with loop protection for chains of automated events.
Automation runs
What's included
Works across every branch of your company, with role-based access, approvals, attachments, comments and a full audit trail on every record.
In detail
You can create rules that fire on business events, such as an approved purchase request or an overdue invoice, check conditions, and then run actions. This removes routine hand-offs like notifying a buyer or opening a follow-up task.
A rule can send an e-mail notification, create a task, post a signed webhook to another system, and schedule a delayed follow-up action. Actions run in the order you set.
Yes. You can test a rule against sample data before enabling it, so you can check that conditions match as intended without triggering real actions.
Run history lists each execution with its outcome, and failed runs show error details. This gives you an audit-friendly record of what the automation did.
Loop safeguards limit chains of automated events, so a rule that triggers another rule cannot repeat indefinitely. Delayed actions run through the background job queue.
Webhook actions are signed, so the receiving system can verify the payload came from your Dino ERP installation. Access to automation settings is controlled by admin permissions and changes are audited.
FAQ
For many routine tasks, no. Rules and signed webhooks are built in. For connecting to external systems you can also use the API and webhooks directly.
Yes. E-mail goes through the SMTP server configured for your installation.
Yes. Rules can schedule delayed follow-up actions.
No. Approvals are a separate engine with steps, limits and separation-of-duties rules. Automation handles notifications, tasks and webhooks.
Delayed and queued work runs through the Redis-backed job worker that ships with the Docker Compose deployment.
Works great with
See Dino ERP in a live demo, then get a one-time quotation for your scope. Hosted on your server, under your brand.