Adobe Sign

I'm in a similar situation. We currently have a Formidable Form with a signature field, and it's converting to a PDF with the signature image using e2PDF just fine. However, we need to send the resulting PDF through an e-signature service like Docusign or Adobe Signature to be completely legal.

Do you have any documentation on how to integrate it? I can only find the shortcodes page, and it's not very detailed.

Hi,

Currently Adobe Sign has limited feature and it can send PDF to Adobe Sign and create Agreement automatically. If it will be need to do more automated things, it will require knowing of PHP and using filters listed on this page: https://e2pdf.com/support/docs#shortcode-e2pdf-adobesign.

Basic setup looks like this:

1. Login to Adobe Sign and Create App. (Screenshot 1).

2. Click on created app and click "Configure OAuth for Application"
-- 2.1 Navigate to "E2Pdf" -> "Settings" -> "Adobe Sign" and copy URL to "Redirect URI" ( https://example.com/wp-admin/admin.php?page=e2pdf-settings&action=adobesign ) at "Adobe Sign App". (Screenshot 2).
-- 2.2 Setup needed scopes on the "Adobe Sign App" and at "E2Pdf" -> "Settings" -> "Adobe Sign". It must be same settings. If "checkbox" not checked - it must be selected "disabled" at E2Pdf plugin setting. Keep in mind that "application_read" and "application_write" must not be checked under "Adobe Sign App". Save "Adobe Sign App" (not E2Pdf Settings). (Screenshot 2)..

3. Click on created app and click "View / Edit". You must copy from there (Screenshot 3):
"Application ID" to "E2Pdf" -> "Settings" -> "Adobe Sign" -> "Client ID".
"Secrets" to "E2Pdf" -> "Settings" -> "Adobe Sign" -> "Client Secret"

4. Setup "Region" regarding these docs: https://helpx.adobe.com/sign/using/adobesign-data-centers.html. For example na2.

So at the end you must get filled at "E2Pdf" -> "Settings" -> "Adobe Sign" (Screenshot 4):
-- Client ID
-- Client Secret
-- Region
-- Scopes (which are same as at "Adobe Sign App").

5. Click "Save". You must be redirected to "Adobe Sign" site with request to confirm access. After confirmation all other fields must be filled.

After setup you must be able to use such shortcode at "Success Message" or "Email Body".

[e2pdf-adobesign id="1" recipients="[email protected]"]

So when this shortcode will fire it will send generated PDF document to "Adobe Sign" and will create "Agreement" which must be possible to sign and download/send to other email.

We currently have in todo list integration with DocuSign integration and updating existing Adobe Sign API which must be easier to use, however we do not yet have ETA when this functionality will be released.

We remain at your service.

---

We would really appreciate your feedback at WordPress.org!

The workflow you mention is EXACTLY what we are looking for -- generate the PDF w e2PDF form FF data, send to a signature service, then send a signature request to the customer.

I already have an Adobe Creative Suite application that includes Acrobat and E-sign, but it appears that I need a different type of Adobe E-signature account. Can you share a link with the type of E-signature account we need to make this work?

Hi,

We recommend to create developer account firstly and test the functionality. It must allow to make all tests to be sure that it will fit your needs and if it will work as expected. By default API will be available but it will be written "DEMO" on each page after sending PDF to Adobe Sign API: https://www.adobe.com/sign/developer-form.html. So if you test it successfully you will need to contact adobe directly and check with them to remove the "DEMO".

We remain at your service.

---

We would really appreciate your feedback at WordPress.org!

I finally got Adobe to create a developer account.

I went through the steps above to connect Formidable/e2PDF to the Adobe account, then added the shortcode to the Notification email in Formidable. When I submit, however, nothing shows up on the Adobe side. What's supposed to happen?

Hi,

Did you use [e2pdf-adobesign id="1" recipients="[email protected]"]? Where 1 is the ID of E2Pdf Template Is so:

1. Check if you see request under "API" -> "Adobe Sign Api" -> "Api Request Log" (Screenshot 1).
2. Agreement must appear under "Manage" as on (Screenshot 2).

---

We would really appreciate your feedback at WordPress.org!

P.S. By default "Adobe" must recognize "Signature" field if it will be set "E-Signature" option under E2Pdf Template Signature field to have possibility sign it from adobe.

---

We would really appreciate your feedback at WordPress.org!

Thanks so much for your help. With your guidance I am able to send the document to Adobe for a signature. Adobe is a bit expensive, so I'm going to try to use SignNow, which my client already uses and is familiar with.

I know you don't have a direct connection to SignNow, so I'm going to try Zapier. I'll post a separate question for that workflow.