ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified productivity Safety 3/5

openclaw-docusign-agreements

Send client agreements for signature by detecting signature blocks with NanoPDF and placing DocuSign tabs automatically. Use when a user needs an OpenClaw workflow to ingest a PDF agreement, find signature coordinates, map signers, and dispatch a DocuSign envelope without manual tab placement.

Why use this skill?

Automate your contract signing process with OpenClaw. Detect signature blocks via NanoPDF and dispatch DocuSign envelopes automatically with audit-ready tracking.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/danielfoch/openclaw-docusign-agreements
Or

What This Skill Does

The openclaw-docusign-agreements skill provides a robust automated pipeline for digitizing and dispatching legal agreements. By integrating NanoPDF’s computer vision capabilities with the DocuSign API, the skill removes the manual burden of positioning signature tabs on complex contracts. It automatically detects signature blocks within a PDF, maps them to designated signers based on your configuration, and executes the envelope creation process. This ensures consistent, accurate, and scalable contract workflows directly within the OpenClaw environment.

Installation

To integrate this skill, ensure you have the OpenClaw CLI configured, then run the following command in your terminal: clawhub install openclaw/skills/skills/danielfoch/openclaw-docusign-agreements

Use Cases

  • Client Onboarding: Automatically trigger NDAs and Service Agreements for new clients the moment they are generated.
  • High-Volume Contracting: Streamline the dispatch of standard operational contracts that require identical placement of signature fields across hundreds of documents.
  • Audit-Ready Workflows: Maintain a clean trail of contract metadata, coordinate detection, and signing status stored locally in a structured audit output directory.

Example Prompts

  1. "OpenClaw, please process the NDA located at contracts/nda.pdf for the signers defined in contracts/signers.json and save the envelope as a draft for my final review."
  2. "Send the updated service agreement to John Doe at [email protected] using the detected signature blocks and set the email subject to 'Pending Action: Q4 Agreement'."
  3. "Automate the signing flow for the contract in the sales folder; ensure all detected blocks are mapped to the correct signers and report back with the final status of the DocuSign envelope."

Tips & Limitations

  • Validation First: Always inspect the docusign_payload.json generated in your output directory. If NanoPDF detects an unexpected number of signature blocks, the script will halt. Never proceed blindly if the mapping seems ambiguous.
  • Environment Safety: Keep your DOCUSIGN_ACCESS_TOKEN and NANOPDF_API_KEY stored securely in environment variables or a .env file; never hardcode these into your automation scripts.
  • Manual Fallback: If a PDF layout is non-standard, the detection might fail. In such cases, use the --status created flag to allow manual adjustment of the tabs in the DocuSign web UI before authorizing the final send. This skill works best with standardized, high-quality document templates.

Metadata

Stars2102
Views1
Updated2026-03-06
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-danielfoch-openclaw-docusign-agreements": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags(AI)

#docusign#automation#pdf#contracts#workflow
Safety Score: 3/5

Flags: network-access, file-write, file-read, external-api, code-execution