ActionsignNowUpdated September 2026
How do I send a signNow document?
Short answer: You can signnow send document in signNow by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the signNow signNow Send Document action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
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 | – |
Sample request
{"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}}"}
Returns
{"status": "success"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for signNow Send Document.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about signNow Send Document.
What does the signNow Send Document action do in signNow?
Sends a document invite to specified signers in configured order. For "deal closed → auto-send contract to client + counter-signer" workflows.
What inputs does signNow Send Document require?
Required: Document ID, Signer Email, Sender Email. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if signNow returns an error?
The run history shows the failed step with its input and the error message signNow returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does signNow Send Document support batch operations?
Run signNow Send Document inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within signNow's rate limits.
More actions