Skip to main content

Adobe Sign action

Yeeflow's Adobe Sign Action integrates e-signature requests into workflows, allowing document signing with configurable recipient settings.

Use Adobe Sign to send an attachment from a Yeeflow approval form or data list to Adobe Acrobat Sign. Map two outputs so the workflow can read the agreement status and open the signed file separately. Adobe Sign workflow example


Add the Adobe Sign action

Open the workflow designer and drag Adobe Sign from Integration to the canvas. Connect it to the path that should request signatures, after the attachment and recipient values are available.


Set the properties

Select Adobe Sign on the canvas and click the settings icon below it. Give the action a name such as Sign purchase confirmation.

Adobe Sign settings grouped into agreement details and outputs for the signed file, status and optional audit trail.

Use an Adobe Acrobat Sign Enterprise account with integration keys enabled. An authorized administrator can access Acrobat Sign API → API Information to create the key. Under Adobe Sign integration key, select Edit and enter the key with these scopes.

  • agreement_read

  • agreement_write

  • agreement_send

  • webhook_read

  • webhook_write

The key inherits the permissions of the user who creates it. Keep the key in the integration settings and out of screenshots or test records.

  • Agreement subject. Enter the subject recipients should see in the signing email.

  • Recipients. Use the Expression Editor to select internal users or provide external email addresses from variables or as text. Enter recipients in the intended signing order. If the document uses numbered signer positions, match that numbering to the recipient order. Locate signature positions in Word

  • Cc. Add recipients who need to receive a copy.

  • Source file(s). Choose one or more attachment fields. Adobe Acrobat Sign combines multiple source files into a single agreement before sending it.

  • Save the signed file to. Choose an attachment variable for the signed agreement. Use a separate output variable when you need to retain the original attachment.

  • Signed Status. Choose a text variable for the status returned by Adobe. Common values include OUT_FOR_SIGNATURE, SIGNED, EXPIRED, and CANCELLED. Agreement Status

Run the signing process in a test application before using it for business agreements.

  1. Publish the test workflow and submit a sample agreement with two test recipients. Check the email subject, recipient order, and file Adobe Acrobat Sign presents for signing. If you supplied multiple files, check that the agreement includes all of them.

  2. Have the test recipients sign. In Yeeflow, check that the text variable records SIGNED, then open the attachment variable to confirm it contains the final signed agreement. If you configured Signed Audit Trail, verify it for the same test agreement.

  3. If a later step uses the output, check when it reads both values. If your workflow handles cancellation or expiry, test that case in a separate sample and verify which follow-up step runs.


​

Did this answer your question?