dropbox-sign-automation

通过 Rube MCP 自动处理 Dropbox Sign 的签署请求、状态查询与文档流程。

来源

GitHub

更新于

2026-06-07

// 安全评估低风险

仅提示词，不执行代码
开源可审计

正在进行安全审计…

凭证密钥
网络外发
代码执行
数据访问
来源供应链

// 安装

复制安装指令，让 AI 自动完成配置 · 推荐新手

请帮我安装 askskill 上的 "dropbox-sign-automation" 技能：
1. 下载 https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/dropbox-sign-automation/SKILL.md
2. 保存为 ~/.claude/skills/dropbox-sign-automation/SKILL.md
3. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

发起合同签署

输入

先搜索可用工具及最新参数 schema，然后使用 Dropbox Sign 相关工具创建一个签署请求：上传合同文件，收件人是 [email protected]，签署顺序为单人签署，主题为“服务合同签署”，并返回请求 ID 与签署链接。

预期产出

返回已创建的签署请求信息，包括请求 ID、签署链接和发送状态。

查询签署进度

输入

先搜索可用工具及最新参数 schema，然后根据签署请求 ID 查询 Dropbox Sign 文档的当前状态，列出是否已查看、是否已签署、最后更新时间，以及下一步建议。

预期产出

返回清晰的进度摘要，说明签署状态、时间节点与后续操作建议。

自动催签提醒

输入

先搜索可用工具及最新参数 schema，然后查找所有超过 3 天未完成的 Dropbox Sign 签署请求，并为每个请求发送一次礼貌的催签提醒，最后汇总处理结果。

预期产出

返回已提醒的请求列表、提醒发送结果，以及仍需人工跟进的项目。

// 文档

Dropbox Sign Automation via Rube MCP

Automate Dropbox Sign operations through Composio's Dropbox Sign toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/dropbox_sign

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Dropbox Sign connection via RUBE_MANAGE_CONNECTIONS with toolkit dropbox_sign
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit dropbox_sign
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Dropbox Sign operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Dropbox Sign task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["dropbox_sign"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Dropbox Sign-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `dropbox_sign`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`