AgentSkillsCN

signnow-embedded-sending

指导嵌入式发送功能的实现——在应用内发起签名请求，让用户无需离开您的应用即可创建并发送签名邀请。

SKILL.md
--- frontmatter
name: signnow-embedded-sending
description: Guides implementation of embedded sending — in-app signature request sending where users create and dispatch signing invites without leaving your application.
model_invokable: true
auto_activate:
  - "embedded sending"
  - "embedded send"
  - "in-app sending"
  - "send invite embed"
  - "send for signature embed"

SignNow Embedded Sending

You are an embedded sending specialist for SignNow. When the user wants to let their end users send documents for signature from within the host application, use this skill.

Behavior

  1. •

    Retrieve current docs — Use the get_signnow_api_info MCP tool with query "embedded sending" and search_signnow_api_reference with category "invites" to verify current endpoint behavior.

  2. •

    What is embedded sending? Embedded sending allows API users to embed SignNow's invite-sending interface into their website or app. End users can select signers, configure signing options, and send signature requests — all without leaving the host application. Users can also add fields to the document or document group before sending.

  3. •

    Embedded sending workflow:

    code
    Upload Document → (Optional: Add Fields) → Generate Sending Link → Embed Sender UI → User Configures & Sends → Signers Receive Invite

    Step 1: Upload document

    • •POST /document — upload the document

    Step 2: Optionally add fields

    • •Pre-place fields via API, or let the user add fields in the embedded sender UI

    Step 3: Generate embedded sending link

    • •Use the embedded sending API to generate a URL for the sending session
    • •Configure available options (signers, fields, sending behavior)

    Step 4: Embed the sender UI

    • •Load the sending URL in an iframe within your application
    • •The user sees SignNow's sending interface

    Step 5: User configures and sends

    • •User adds recipients (signers, viewers)
    • •Optionally modifies fields before sending
    • •Clicks send to dispatch signing invites
  4. •

    Use cases:

    • •CRM integration — sales reps send contracts from within the CRM
    • •HR portal — HR sends onboarding documents from the employee management system
    • •Document management — users send documents for signature from a document repository
    • •Client portal — professionals (lawyers, accountants) send documents to clients
  5. •

    Embedded sending vs API-based invites:

    ApproachBest for
    Embedded sendingEnd users who need a visual UI for configuring invites
    API invites (POST /document/{id}/invite)Automated workflows, bulk operations, system-triggered sends
  6. •

    Configuration options:

    • •Pre-populate signer information
    • •Restrict available options (field types, signer configuration)
    • •Enable/disable field editing before sending
    • •Apply branding to the sending UI
    • •Redirect URL after sending is complete
    • •Document group support for multi-document packages
  7. •

    Best practices:

    • •Pre-fill known information (signer emails, names) to reduce user effort
    • •Use the embedded sending UI for user-initiated sends, API for automated sends
    • •Implement webhooks to track invite status after sending
    • •Apply branding for a seamless user experience
    • •Handle the completion callback to update your application state
  8. •

    Reference documentation: