After a WPsigner trigger or action runs, later steps can map these fields. Signing URLs and field values can be turned off under Settings.
Capture a sample by turning the workflow On and running the WPsigner event once. A workflow left Off does not store that sample.
Document
Section titled “Document”| Field | Contents |
|---|---|
DOCUMENT_ID | Document ID |
DOCUMENT_TITLE | Title |
DOCUMENT_STATUS | Status key, such as sent or completed |
DOCUMENT_CREATED_AT | Created time |
DOCUMENT_COMPLETED_AT | Completed time |
DOCUMENT_EXPIRES_AT | Expiration |
DOCUMENT_ADMIN_URL | Link to the document in wp-admin |
DOCUMENT_DOWNLOAD_URL | Secure download URL when one is available |
DOCUMENT_AUDIT_URL | Audit screen for this document |
DOCUMENT_CERTIFICATE_ID | Certificate ID |
DOCUMENT_OWNER_ID | WordPress user ID of the owner |
DOCUMENT_OWNER_EMAIL | Owner email |
DOCUMENT_TAGS | Tag names |
DOCUMENT_FIELDS | JSON of non-signature field values |
TEMPLATE | Template name, when the origin was recorded |
TEMPLATE_ID | Template ID, when the origin was recorded |
FIELD_* | One token per template variable, when field values are enabled |
The completed PDF path on disk is never included.
Signers
Section titled “Signers”| Field | Contents |
|---|---|
SIGNER_ID | Signer ID for this event |
SIGNER_NAME | Name |
SIGNER_EMAIL | |
SIGNER_STATUS | Status key |
SIGNER_ROLE | signer or approver |
SIGNER_WP_USER_ID | WordPress user ID when the email matches a user |
SIGNER_IS_WP_USER | yes or no |
SIGNING_URL | Signing link, unless the person already signed or declined, or the setting is off |
SIGNERS_EMAILS | Email list |
SIGNERS_JSON | All signers as JSON |
SIGNERS_PENDING_JSON | Pending signers as JSON |
signers | Array for Iterator |
pending_signers | Pending signers array for Iterator |
DECLINE_REASON | Present on Document declined |
Signer removed still includes the removed person’s name, email, and role. It does not include a signing URL.
Filter and Iterator
Section titled “Filter and Iterator”FlowMattic has no Automator-style condition or loop objects. Use the steps FlowMattic already provides:
| Step | Point it at |
|---|---|
| Filter | DOCUMENT_STATUS, TEMPLATE_ID, DOCUMENT_TAGS, SIGNER_ROLE, or SIGNER_IS_WP_USER |
| Iterator | signers or pending_signers |
The same lists are available as SIGNERS_JSON and SIGNERS_PENDING_JSON when a step needs text instead of an array.
Source, CRM, Cloud, and Payment
Section titled “Source, CRM, Cloud, and Payment”| Field | When it is set |
|---|---|
SOURCE | Form, store, or in-form signing trigger |
SOURCE_ENTRY_ID | Form entry ID, when the hook provides it |
SOURCE_FORM_ID | Form ID |
SOURCE_FORM_TITLE | Form title |
SOURCE_ORDER_ID | WooCommerce order ID |
SOURCE_ORDER_NUMBER | WooCommerce order number |
SOURCE_FEED_ID | Feed ID |
CRM_PROVIDER | hubspot or pipedrive |
CLOUD_PROVIDER | google_drive, dropbox, onedrive, or s3 |
CLOUD_REFERENCE | Provider file ID or path |
CLOUD_URL | HTTPS link when one exists |
PAYMENT_AMOUNT | Decimal amount |
PAYMENT_CURRENCY | Currency code |
PAYMENT_INTENT | Stripe PaymentIntent ID |
PAYMENT_ERROR | Failure message |
PAYMENT_DISPUTE | Dispute ID |
Form answers and order line items stay out of these fields.