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.
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.