Short answer: Drop the "SignWell → SignWell Send Document" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Document Name name | string | Required | — |
File URL file_url | string | Required | A fully qualified URL (https://...) for the file url. |
Email Subject subject | string | Optional | Message subject line. |
Email Message message | string | Optional | — |
Recipient Email recipient_email | string | Required | The email address. Used as the recipient or identifier depending on context. |
Recipient Name recipient_name | string | Required | — |
Test Mode test_mode | options | Optional | — |
{"name": "{{trigger.name}}","file_url": "e.g. https://example.com/path","subject": "e.g. Quick update","message": "{{trigger.message}}","recipient_email": "e.g. user@example.com"}
{"id": "doc_abc","name": "Contract","status": "Sent","signing_urls": [{"url": "https://signwell.com/...","recipient_id": "1"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.