Skip to content
Hardik Zinzuvadiya
Let's connect

ERPNext workflow automation and approvals

Approvals that reach the person who has to decide, document events that fire the next step, and scheduled jobs nobody has to remember, all under your permission rules.

What this covers

  • Approval inboxes: approve, deny, edit or snooze, with what happens on each spelled out
  • Triggers on schedules, document events, date fields, webhooks, inbound email or by hand
  • Notifications to the people who have to act, not to everyone
  • Every step runs as a real Frappe user, under the permission policy
  • Runs you can review before they are armed, and pause mid-way

How an engagement runs

  1. 01

    A first conversation

    You describe what is slow, manual or fragile. I ask questions, not for a budget, and say plainly whether it is work I should do.

  2. 02

    Scope in writing

    What changes, what does not, how we will know it worked, and what I need from you: access, a copy of the site, a person who knows the process.

  3. 03

    Build on a copy

    Work happens on a staging copy of your site. You review it there before anything touches production.

  4. 04

    Go-live with a gate

    Releases and migrations follow a rehearsed plan with a tested rollback. Nothing writes to production without approval.

  5. 05

    After go-live

    Fixes, monitoring and upgrades under support and maintenance, if you want them.

Related work

Shopify to ERPNext operations suiteShopify orders become submitted Sales Orders, Invoices and Delivery Notes on a schedule, with monitors for orders and products.Web Push Notifications for FrappeRule-based browser push from document events and timed reminders, sent from your own server with no third-party relay.

Questions I get asked

Can an automation wait for a person before it posts anything?
Yes, and that is the default for anything that writes. Runs pause mid-graph and resume on approve, deny, edit or snooze, and the waiting decision shows what will happen either way before you choose.
What can start one?
Six kinds of trigger: a schedule, a document event, a date field coming due, a webhook, inbound email, or a person running it by hand.
Does automation get around our permissions?
No. Every step runs as a real Frappe user under the recipe's permission policy, so an automation can never do what the person behind it could not.