erpclaw-esign

Automate ERPClaw signature workflows with SQLite-backed audit trails and domain actions routed through db_query.

5|6|Updated Mar 8, 2026

Search Tags:#workflow-automation #audit-trail #electronic-signature #contract-signing #esign #erpclaw #signature-requests

Ready to run

npx skills add https://github.com/avansaber/erpclaw-addons --skill erpclaw-esign

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: erpclaw-esign
Source: https://github.com/avansaber/erpclaw-addons/tree/main/erpclaw-esign
Command: npx skills add https://github.com/avansaber/erpclaw-addons --skill erpclaw-esign

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires erpclaw_lib, and includes scripts (resource) components.

What problem does it solve?

ERPClaw esign automates electronic signature workflows within ERPClaw, enabling contract signing, signer status tracking, and a complete audit trail in a local database.

Core Features & Use Cases

Signature requests: draft, send, remind, and track status across multiple signers.
End-to-end signing workflow: from creation to completion with audit events and optional decline/cancel/void paths.
Local-first storage: all data stored in the ERPClaw SQLite database with no external API calls.

Quick Start

Create a signature request and send it for signing, then monitor signer status and audit events.

Frequently Asked Questions about erpclaw-esign

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage electronic signature requests and track signer status locally?▼

Manage electronic signature requests by drafting, sending, and tracking signer status using a local SQLite backend. The workflow routes 13 domain actions through a db_query router to maintain data integrity and track status across multiple signers.

Can I generate an audit trail for contract signing without external API calls?▼

Generate an audit trail for contract signing locally without external API calls. The system logs end-to-end signing events into a two-table SQLite schema, capturing optional decline, cancel, and void paths for complete data integrity.

How does the e-signature workflow handle void and decline paths?▼

The e-signature workflow handles void and decline paths by routing specific domain actions through a db_query router. It logs these events into the signature event table, ensuring the audit trail captures every possible signing outcome.

Do I need the erpclaw_lib dependency to automate signature workflows?▼

Yes, you need the erpclaw_lib dependency to automate signature workflows. It provides the foundational library required by the self-contained module to manage parameterized SQL queries and execute the domain actions within the local database.

What is the best way to maintain data integrity for e-signatures in a local database?▼

Maintain data integrity for e-signatures by using parameterized SQL within a local SQLite database. The schema separates signature requests and signature events into two tables, ensuring privacy and reliable audit trail tracking.

What database schema is used for tracking electronic signature events?▼

The database schema for tracking electronic signature events uses two tables: esign_signature_request and esign_signature_event. This structure supports end-to-end signing processes and maintains an audit trail through parameterized SQL operations.