Skip to main content

Digital Sign in Power Automate

PDF4me Digital Sign action enables applying cryptographic digital signatures to PDF documents in Power Automate using certificate files for authentication and non-repudiation. This enterprise-grade signing feature supports custom certificate positioning, visibility control, signer information, signature reasons, and location details, providing legally binding signatures with tamper-evident seals for contracts, agreements, and official documents across Microsoft 365 workflows.

Authenticating Your API Request

To access the PDF4me Web API through Power Automate, every request must include proper authentication credentials. Authentication ensures secure communication and validates your identity as an authorized user, enabling seamless integration between your Power Automate flows and PDF4me's powerful digital signature services.

Digital Sign Power Automate

Key Features

  • Certificate-Based Signing: Use X.509 certificates for cryptographic signatures
  • Custom Positioning: Control signature position with X/Y coordinates
  • Visibility Control: Create visible or invisible digital signatures
  • Signer Information: Include signer name, reason, and location details
  • Tamper Detection: Automatic invalidation if document is modified after signing

Parameters

Complete list of parameters for the Digital Sign action. Configure these parameters to control digital signature application.

Important: Parameters marked with an asterisk (***) are required and must be provided for the action to function correctly.

ParameterTypeDescriptionExample
PDF File Content***BinarySource PDF File
• PDF file content to be digitally signed
• Supports PDFs from SharePoint, OneDrive, email
• Can be dynamically retrieved from flows
• Must be valid PDF document
[File Content]
PDF File Name***StringPDF Document Name
• Name of the PDF file
• Used for processing identification
• Should include .pdf extension
• Supports dynamic naming
Contract.pdf
Certificate File***BinaryDigital Certificate
• Certificate file content (.pfx or .p12)
• Contains private key for signing
• Store securely in Azure Key Vault
• Required for cryptographic signature
[Certificate Content]
Certificate Password***StringCertificate Password
• Password protecting the certificate file
• Required to unlock certificate private key
• Store in secure configuration or Key Vault
• Never hardcode in flow
CertPass123!
Page NumberStringSignature Page
• Page number where signature should appear
• Numeric value for specific page
• Use last for final page
• Default is first page if not specified
last
Margin XIntegerHorizontal Position
• Position from left edge of page in points
• Controls horizontal placement of signature
• Used when signature is visible
• Default is 0
100
Margin YIntegerVertical Position
• Position from bottom edge of page in points
• Controls vertical placement of signature
• PDF coordinates start from bottom
• Default is 0
100
WidthIntegerSignature Width
• Width of signature field in points
• Controls signature appearance size
• Only for visible signatures
• Default is certificate default
200
HeightIntegerSignature Height
• Height of signature field in points
• Controls signature appearance size
• Only for visible signatures
• Default is certificate default
50
Sign LocationStringSigning Location
• Geographic location where signing occurs
• Included in signature metadata
• Optional descriptive information
• Example: city, office name
New York Office
Signer NameStringSigner's Name
• Name of person signing document
• Displayed in signature appearance
• Included in signature metadata
• Optional but recommended
John Doe
Sign ReasonStringSigning Reason
• Reason for applying signature
• Included in signature metadata
• Examples: Approval, Agreement, Authorization
• Optional descriptive field
Document Approval
VisibleBooleanSignature Visibility
True - Show visible signature on page
False - Apply invisible signature
• Visible signatures show signer info
• Invisible used for authentication only
true

Output

The PDF4me Digital Sign action returns comprehensive output data for seamless Power Automate flow integration:

Table View

Response data in a structured table format:

ParameterTypeDescription
File ContentBinaryDigitally signed PDF with cryptographic signature applied

Workflow Examples

The PDF4me Digital Sign action in Power Automate provides comprehensive workflow templates designed for real-world business scenarios:

Automated Contract Digital Signing Workflow

Transform your contract execution with automated digital signatures:

Complete Workflow Steps:

  1. Trigger: Contract approved by all parties in approval workflow
  2. Get Contract: Retrieve final approved contract PDF
  3. Get Certificate: Fetch company certificate from Azure Key Vault
  4. Apply Digital Signature: Sign contract on last page at bottom
  5. Add Signer Info: Include CEO name and "Final Approval" as reason
  6. Verify Signature: Validate signature applied correctly
  7. Email Parties: Send digitally signed contract to all stakeholders
  8. Archive Signed: Store signed contract in legal compliance library

Business Benefits:

  • Signs 75+ contracts monthly with company digital signature
  • Provides legally binding automated signatures
  • Eliminates wet signature delays reducing cycle by 5 days
  • Maintains cryptographic proof of authenticity and integrity

Industry Use Cases & Applications

Legal & Professional Services Use Cases

  • Contract Execution: Apply digital signatures to finalized contracts
  • Legal Document Authentication: Sign legal opinions and briefs
  • Power of Attorney: Digitally sign POA documents
  • Settlement Agreements: Apply signatures to settlement documents

Get Help