Skill

Automate SignNow E-Signature Workflows

Let LlamaIndex agents run SignNow e-signature workflows via the SignNow MCP server.

Works with signnowllama index

80
Spark score
out of 100
Updated 8 days ago
Version 0.14.23

Add to Favorites

Why it matters

Integrate LlamaIndex agents with SignNow e-signature capabilities to automate document signing processes. This asset enables agents to manage templates, send invites, track status, and download signed documents.

Outcomes

What it gets done

01

Discover and expose SignNow tools to LlamaIndex agents.

02

Manage e-signature workflows including template creation and sending invites.

03

Track the status of signing processes and retrieve signed documents.

04

Facilitate embedded signing, sending, and editing experiences.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/li-tool-tools-signnow | bash

Overview

Llama Index Tools Signnow

A LlamaIndex ToolSpec that connects agents to a SignNow MCP server, exposing 15 tools covering the full e-signature workflow. Use for automating SignNow document creation, sending, embedded signing, status tracking, and downloads through an agent.

What it does

This ToolSpec is a plug-and-play bridge that lets LlamaIndex agents use SignNow e-signature workflows through the SignNow MCP server. It discovers the MCP server's tools automatically and exposes them to the agent, so setup stays simple for developers already working with LlamaIndex. Configuration is environment-first: typical deployments need no code changes, since credentials are read from environment variables via SignNowMCPToolSpec.from_env.

The SignNow MCP server exposes 15 tools covering the full e-signature lifecycle: list_all_templates and list_document_groups for discovery, create_from_template for document creation, send_invite for emailed signing invites with ordered recipients, create_embedded_invite/create_embedded_sending/create_embedded_editor for in-app embedded flows without email delivery, three one-shot template-to-action variants (send_invite_from_template, create_embedded_sending_from_template, create_embedded_editor_from_template, plus create_embedded_invite_from_template), get_invite_status for tracking, get_document_download_link and get_document for retrieval, and update_document_fields for prefilling text fields. The source itself names the common flow: list templates, create a document from one, then either a one-shot action or send an invite, then check status, then download.

When to use - and when NOT to

Use it when a LlamaIndex agent needs to create, send, track, or retrieve e-signature documents through SignNow - for example generating a document from a template and producing an embedded signing link, or checking whether a sent invite has been completed. Use the embedded variants when you want the signing, sending, or editing experience to happen inside your own app without an email round-trip, and the invite-based variants when email delivery is the right channel. Do not use it without a running SignNow MCP server and valid SignNow authentication (either a SIGNNOW_TOKEN or an email/password/basic-token combination) configured via environment variables.

Inputs and outputs

Inputs are natural-language requests to the agent ("create a document from template X", "send an invite to Y") that map onto the 15 underlying MCP tools, each with its own structured parameters (template names, recipient emails and signing order, document/group IDs). Outputs include lists of templates or document groups, invite and document status, direct download links, and normalized document/group structures with field values.

Integrations

pip install -U llama-index llama-index-tools-mcp llama-index-tools-signnow

Built on the Model Context Protocol: the ToolSpec connects to the SignNow MCP server (STDIO spawn by default) and converts its tools into LlamaIndex-compatible tools via to_tool_list_async(), so it wires into any LlamaIndex agent that supports function/tool calling, alongside llama-index-tools-mcp as the underlying MCP client.

Who it's for

Developers building LlamaIndex agents that need to automate SignNow e-signature workflows - creating documents from templates, sending or embedding signing flows, and tracking or retrieving completed documents - without hand-writing SignNow API integration code.

Source README

llama-index-tools-signnow

A plug‑and‑play ToolSpec that lets LlamaIndex agents use SignNow e‑signature workflows through the SignNow MCP server.
It discovers the server’s tools, exposes them to your agent, and keeps setup simple for users who already work with LlamaIndex.


✨ What you get

  • One‑liner tool discovery for the SignNow MCP server (STDIO spawn by default).
  • Works with any LlamaIndex agent that supports function/tools.
  • Covers common e‑signature flows end‑to‑end (templates, invites, embedded signing/sending/editor, status, downloads).
  • Environment‑first configuration (no code changes required for typical deployments).

Installation

### Core LlamaIndex + MCP client + SignNow ToolSpec
pip install -U llama-index llama-index-tools-mcp llama-index-tools-signnow

Quick start

import asyncio
from llama_index.tools.signnow import SignNowMCPToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import (
    OpenAI,
)  # or any LLM that supports tool/function calling


async def main():
    # Option A: pass credentials directly (no .env needed)
    spec = SignNowMCPToolSpec.from_env(
        env_overrides={
            # Option 1: token-based auth
            # "SIGNNOW_TOKEN": "your_signnow_token_here",
            # Option 2: credential-based auth
            "SIGNNOW_USER_EMAIL": "login@example.com",
            "SIGNNOW_PASSWORD": "password",
            "SIGNNOW_API_BASIC_TOKEN": "basic_token_base64",
        }
    )

    # Fetch tools from the MCP server
    tools = await spec.to_tool_list_async()
    print({"count": len(tools), "names": [t.metadata.name for t in tools]})

    # Wire them into a LlamaIndex agent
    agent = FunctionAgent(
        name="SignNow Agent",
        description="Query SignNow via MCP tools",
        tools=tools,
        llm=OpenAI(model="gpt-4o"),  # make sure your LLM supports tools
        system_prompt="Be helpful.",
    )

    # Ask for something useful
    resp = await agent.run("Show me the list of templates and their names.")
    print(resp)


if __name__ == "__main__":
    asyncio.run(main())

Prompt ideas

  • “Create a document from the template ‘NDA v3’ and generate an embedded signing link for alice@example.com
  • “Send an invite to bob@example.com for document XYZ with signer order Alice first, Bob second.”
  • “What’s the current invite status for document ABC?”
  • “Give me a direct download link for the completed document (merged if it’s a group).”

Available tools (provided by the SignNow MCP server)

  • list_all_templates - List templates & template groups with simplified metadata.
  • list_document_groups - Browse your document groups and statuses.
  • create_from_template - Make a document or a group from a template/group.
  • send_invite - Email invites (documents or groups), ordered recipients supported.
  • create_embedded_invite - Embedded signing session without email delivery.
  • create_embedded_sending - Embedded “sending/management” experience.
  • create_embedded_editor - Embedded editor link to place/adjust fields.
  • send_invite_from_template - One‑shot: create from template and invite.
  • create_embedded_sending_from_template - One‑shot: template → embedded sending.
  • create_embedded_editor_from_template - One‑shot: template → embedded editor.
  • create_embedded_invite_from_template - One‑shot: template → embedded signing.
  • get_invite_status - Current invite status/steps for document or group.
  • get_document_download_link - Direct download link (merged output for groups).
  • get_document - Normalized document/group structure with field values.
  • update_document_fields - Prefill text fields in individual documents.

Tip: A common flow is listall_templates → create_from_template → one‑shot or send_invite / create_embedded* → get_invite_status → get_document_download_link.


Configuration

The ToolSpec read

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.