Signwell

@signwell show me all documents that are still waiting for signatures and their current status

Based on the account data, there are 4 documents awaiting signatures: (1) 'Q1 Contractor Agreement' sent to jane@example.com 3 days ago, viewed but not signed; (2) 'NDA - Acme Corp' sent to legal@acme.com 1 day ago, not yet opened; (3) 'Equipment Lease Amendment' sent to two signers, one completed, one pending; (4) 'Service Agreement Renewal' sent 7 days ago with a reminder sent yesterday. All documents remain active with no expiration set.

This example uses Get Document (likely in a loop) to surface signing status. The MCP returns structured metadata—signer email, view/sign timestamps, reminder history—but you'll need to call the tool once per document ID. If you have dozens of pending documents, consider filtering by date range first to stay within rate limits.

@signwell create a new signing request for the consulting-agreement.pdf file, send it to alex@startup.io, and set a 7-day expiration

Document created successfully. A signing request for 'consulting-agreement.pdf' has been sent to alex@startup.io with a 7-day expiration (due March 15). The recipient will receive an email with a secure signing link. Document ID: doc_8x3kp2m. You can track status or send reminders through this ID. Note: the file must already be uploaded or accessible via URL; this call does not handle file storage.

This demonstrates Create Document, which bundles file reference, recipient list, and delivery in one API call. The MCP requires you to provide a file URL or base64-encoded content—it won't fetch files from your local machine. Also, sending the document is a side-effect: the recipient gets an email immediately, so double-check details before running this prompt.

@signwell set up a webhook to notify our Slack channel whenever any document is fully signed, and show me the callback URL format we need

Webhook registered. Event type: 'document.completed'. Callback URL: https://hooks.slack.com/services/T00/B00/abc123 (example format). Signwell will POST a JSON payload to this endpoint each time all signers complete a document. The payload includes document ID, signer details, timestamp, and a download link for the signed PDF. Webhook ID: wh_9a4c7f2. You can test delivery by completing a sample document or use List Webhooks to verify it's active.

This uses Create Webhook to automate post-signature workflows. The MCP expects a publicly accessible HTTPS endpoint—localhost URLs won't work. You're responsible for validating the webhook signature (Signwell includes an HMAC header) to prevent spoofed events. If the endpoint returns errors repeatedly, Signwell may disable the webhook, so monitor your receiver logs.

When Signwell fits the one-off contract send workflow

A 6-person SaaS sales team closes 3-5 deals a week and needs to send MSAs or order forms from Slack or a shared workspace. Signwell's Create Document tool handles the entire flow in one call: you pass the PDF, recipient emails, and signing order, and it returns a tracking ID. The team can check status with Get Document without leaving the workspace. This works cleanly when contracts are templated and the send is the final step after verbal agreement. If your team negotiates terms in-flight or needs conditional routing (send to legal if over $50k), Signwell's 8-tool surface doesn't cover that logic—you'd script it outside or pick a heavier e-signature platform. For straightforward send-and-track at small scale, Signwell keeps the workflow in one place.

Signwell for repeatable employee paperwork at 10-30 hires per year

A 12-person startup hires in batches and needs to collect I-9s, offer letters, and NDAs from new employees. The HR lead uses Signwell's Create Document tool to send a packet to each hire, then monitors completion with Get Document calls surfaced in a shared workspace. The List Bulk Sends tool helps when onboarding 3-4 people at once. This scenario works because the document set is fixed and the recipient list is known upfront. If you're onboarding 50+ people a quarter or need conditional sends (send equity docs only to full-time hires), Signwell's API is too thin—you'll spend time building state management around it. At 10-30 hires a year, the simplicity wins and the team avoids a heavier HRIS integration.

When Signwell's webhook model supports async vendor workflows

A 5-person operations team manages 20-30 vendor agreements a year and needs to know when contracts are signed without polling. Signwell's Create Webhook tool registers a callback URL, and the workspace receives events when a vendor completes signing. The team can then trigger downstream steps—update a tracker, notify finance, archive the PDF—without manual check-ins. This works when the ops team controls the callback endpoint and the vendor count stays under 50 active agreements. If you're managing hundreds of contracts or need granular event types (viewed, declined, expired), Signwell's webhook surface is basic and you'll hit limits. For small-team vendor workflows where async notification beats manual follow-up, the webhook model keeps the process moving without dedicated contract software.