Tell FrappeOps what you need in plain English. It builds the automation, runs it inside your ERPNext or Frappe site, and checks with you before anything important happens.
Every weekday morning, find overdue invoices, write a short summary for finance, and let me check it before it's sent.
Built for teams running
ERPNext Any app built on Frappe Your own custom appsOverdue payments, unanswered quotes, stock running low. Someone has to notice, then remember to act.
Updates get retyped into emails and chat messages, one record at a time.
Even a small automation usually means a script, a ticket, and a wait.
FrappeOps turns a sentence into work that gets done, with you in the loop.
These are real screens from FrappeOps, running on a test site.
Write it the way you'd explain it to a colleague. If something isn't clear, FrappeOps asks you instead of guessing.
Your workflow appears as simple steps you can read top to bottom. Nothing runs until you switch it on.
When something needs your OK, you get the full picture: the email as it will be sent, the records involved, what happens next. Approve, say no, or reply with changes.
Pick your team. Each example is something you can ask for in your own words.
Each weekday, summarise overdue invoices by customer and email finance after I check it.
Finance starts the day with one clear list instead of building it by hand.
When a large sales order comes in, summarise it with the customer's unpaid balance and ask the sales manager before replying.
Big orders get a second look, with the numbers already pulled together.
Every morning, tell me what's waiting for my approval and what went wrong overnight.
One email, and you know where the day stands.
When a new lead arrives, grade how promising it is and send it to the right rep with a heads-up.
Hot leads reach a person quickly, not at the end of the week.
Three days after we send a quote, if the customer hasn't replied, draft a friendly nudge for me to approve.
No quote goes quiet because someone forgot.
When a big order is confirmed, post the details to our sales channel on Slack.
Everyone hears about it without anyone retyping it.
Every morning, find items that are running low and let purchasing know about each one.
Shortages get noticed before they become late orders.
When an item drops below its reorder level, prepare a purchase order and ask me before it's submitted.
The paperwork is ready; the decision stays with you.
Large purchase orders need approval from the manager, then the director.
Each person gets asked in turn, and nothing is submitted until the last one agrees.
Read each email to support, decide how urgent it is, and alert the right people.
Urgent problems surface first instead of waiting in a queue.
When a customer writes in, draft a reply from their order history for an agent to check.
Agents start from a good draft, and every reply is still read by a person.
If any of our automations fails, tell me what happened and why.
Problems come to you. You don't have to go looking for them.
FrappeOps works with any record type on your Frappe site, including the ones in apps your team built. No setup for each one.
Automations see only what the person who set them up can see. Your existing roles and permissions still apply.
Your developers can add actions specific to your business, and they appear alongside everything else.
Letting AI near your business data should feel safe. These are the promises FrappeOps is built on.
Sending emails, changing records and submitting documents wait for approval. You decide what's allowed to run on its own.
Every automation works with the same access as the person who set it up. Nothing more.
FrappeOps runs inside your Frappe site. AI only gets what a step needs, from the AI service you choose, or a model you run yourself.
See what happened, step by step, and who approved what. "Why did this happen?" always has an answer.
If something fails, you're told straight away, with what went wrong and how to fix it.
Set a daily spending limit. If an automation reaches it, it pauses until you decide.
Many apps now offer an MCP server, a ready-made connection for AI. Add one to FrappeOps and your workflows can use it, alongside everything on your Frappe site.
Also connects to your email inbox, and to other web apps through their API.
Brand names and logos belong to their owners and are shown as examples of services FrappeOps can connect to.
One place to see what needs you, what's coming up, and what already happened.
No. FrappeOps installs on any Frappe site. With ERPNext it works with your invoices, orders, stock and leads. Without it, it works with whichever apps you run, including your own.
No. You describe what you want in plain English. FrappeOps asks when something isn't clear, and shows you the result before anything runs.
Only what you allow. Out of the box, looking things up and preparing drafts happen on their own. Sending, changing and submitting ask you first. Deleting is switched off.
Before anything important goes out, you see exactly what will happen, such as the email as it will be sent or the values that will change. Say no and nothing happens. Every run keeps a history, so you can check what was done and why.
You choose. FrappeOps works with major AI services such as Anthropic's Claude, OpenAI and Google, or with a model you run on your own servers, so nothing leaves your system. AI only receives what a step needs, and an admin can switch outside AI services off entirely.
An MCP server is a ready-made connection an app offers so AI tools can work with it. Paste its link into FrappeOps, connect your account, and its tools become steps in your workflows. Slack and GitHub work today, and Notion, Jira and HubSpot are coming soon. FrappeOps also works with every app on your Frappe site, your email inbox, and other web apps through their API.
Leave your email and we'll reach out to tell you more and answer your questions.