frappe-workflow-generator

Venkateshvenki404224's avatarfrom Venkateshvenki404224

Generate Frappe Workflows for document state management and approvals. Use when creating approval workflows, state transitions, or multi-step document processes.

⭐1stars🔀1forks📁View on GitHub🕐Updated Dec 15, 2025
[Business Platforms]

When & Why to Use This Skill

The Frappe Workflow Generator is a specialized Claude skill designed to streamline the creation of document state management systems and multi-step approval processes within the Frappe Framework. By generating production-ready JSON configurations, it simplifies the implementation of complex business logic, role-based access controls, and conditional state transitions, ensuring efficient document lifecycle management and accelerating ERPNext development.

Use Cases

  • Automating multi-tier financial approval workflows where routing is determined by document values, such as grand totals or departments.
  • Defining comprehensive document lifecycles for HR modules, managing transitions from initial application to final hiring or rejection.
  • Implementing strict role-based editing permissions and state transitions for sensitive documents like Sales Invoices, Purchase Orders, or Legal Contracts.
  • Rapidly prototyping and deploying custom business process automations within the Frappe ecosystem to ensure consistent document handling.
namefrappe-workflow-generator
descriptionGenerate Frappe Workflows for document state management and approvals. Use when creating approval workflows, state transitions, or multi-step document processes.

Frappe Workflow Generator

Generate production-ready Frappe Workflows for document state management, approvals, and business process automation.

When to Use This Skill

Claude should invoke this skill when:

  • User wants to create approval workflows
  • User needs document state transitions
  • User requests multi-step approval processes
  • User mentions workflows, approvals, or document states
  • User wants role-based approval routing
  • User needs to implement document lifecycle management

Capabilities

1. Workflow JSON Generation

Basic Approval Workflow:

{
  "name": "Sales Invoice Approval",
  "document_type": "Sales Invoice",
  "is_active": 1,
  "workflow_state_field": "workflow_state",
  "states": [
    {
      "state": "Draft",
      "doc_status": "0",
      "allow_edit": "Sales User",
      "update_field": "status",
      "update_value": "Draft"
    },
    {
      "state": "Pending Approval",
      "doc_status": "0",
      "allow_edit": "Sales Manager",
      "update_field": "status",
      "update_value": "Pending"
    },
    {
      "state": "Approved",
      "doc_status": "1",
      "update_field": "status",
      "update_value": "Approved"
    },
    {
      "state": "Rejected",
      "doc_status": "2",
      "update_field": "status",
      "update_value": "Rejected"
    }
  ],
  "transitions": [
    {
      "state": "Draft",
      "action": "Submit for Approval",
      "next_state": "Pending Approval",
      "allowed": "Sales User",
      "allow_self_approval": 0
    },
    {
      "state": "Pending Approval",
      "action": "Approve",
      "next_state": "Approved",
      "allowed": "Sales Manager"
    },
    {
      "state": "Pending Approval",
      "action": "Reject",
      "next_state": "Rejected",
      "allowed": "Sales Manager"
    },
    {
      "state": "Rejected",
      "action": "Revise",
      "next_state": "Draft",
      "allowed": "Sales User"
    }
  ]
}

2. Conditional Transitions

Workflow with Amount-Based Routing:

{
  "transitions": [
    {
      "state": "Draft",
      "action": "Submit",
      "next_state": "Pending L1 Approval",
      "allowed": "Sales User",
      "condition": "doc.grand_total <= 10000"
    },
    {
      "state": "Draft",
      "action": "Submit",
      "next_state": "Pending L2 Approval",
      "allowed": "Sales User",
      "condition": "doc.grand_total > 10000 && doc.grand_total <= 50000"
    },
    {
      "state": "Draft",
      "action": "Submit",
      "next_state": "Pending Director Approval",
      "allowed": "Sales User",
      "condition": "doc.grand_total > 50000"
    }
  ]
}

References

Frappe Workflow Core:

Official Documentation: