Short answer: Drop the "signNow → signNow 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 ID document_id | string | Required | — |
Signer Email signer_email | string | Required | The email address. Used as the recipient or identifier depending on context. |
Sender Email from_email | string | Required | The email address. Used as the recipient or identifier depending on context. |
Subject subject | string | Optional | Message subject line. |
Message message | string | Optional | — |
{"document_id": "{{trigger.document_id}}","signer_email": "e.g. user@example.com","from_email": "e.g. user@example.com","subject": "e.g. Quick update","message": "{{trigger.message}}"}
{"status": "success"}
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.