All Collections
Connecting Juro's Mail integration
Connecting Juro's Mail integration

Transfer your PDF and Word email attachments to Juro

Henry Warner avatar
Written by Henry Warner
Updated over a week ago

Contents πŸš€

Introduction πŸ‘‹

Contracts are often sent back and forth as PDF or Word files via email.

With Juro's Mail integration, you can import documents into your Juro workspace directly via email.

How does it work? 🧐

A counterparty may send you a document as an attachment in a separate email. Instead of having to export the file and reupload it into Juro, you can forward the email (with the attachment included) to the address generated by this integration, and a contract will be created from the original attachment.

Connecting the Mail integration ⛓️

πŸ’‘ NOTE: Only Organisation Admins can see the Integrations tab within Settings. If you cannot see it, please ask your internal Organisation Admin to upgrade your access level. For more information on managing a user's access level, see our dedicated article.

To enable the Mail integration:

1. In your Settings, open the Integrations tab. Then, click the Mail panel.

2. Click Generate mail address: this will generate a unique Juro-hosted inbox. PDF and Word attachments on emails sent to this inbox will be automatically uploaded to your Juro workspace.

3. OPTIONAL: In the Contract Reader tab you can pre-select a default template for uploaded documents.

4. OPTIONAL: Finally, you may opt to set up auto-forwarding from an inbox with your domain.

For example, you could set up a email with filtered auto-forwarding to your unique Juro-hosted inbox.

Using the Mail integration πŸ“¬

Once an email is sent to your unique Juro integrated inbox, PDF and Word attachments will be automatically uploaded into your Juro workspace as contracts.

When you first do this, Juro will create a pinned table view named Mail to host these documents. When you need to refer back to a document uploaded through this integration in the future, this is where you can easily find it.

By default, the table view includes the Document Name column, which pulls its information from the file name of the uploaded document. Other attributes, such as Document Type and Status will depend on the Contract Reader settings.

In the below image, uploaded documents are, by default, set to be uploaded against the "OneNDA" template and so will inherit the name of that template as its Document Type. You can also choose in the Contract Reader settings whether or not the uploaded documents will inherit the template's smart field, approver, and/or signatory setup.

In this example, you can also see that documents are not set to be marked as Fully Signed when uploaded so their status will show as Uploaded when imported into Juro.

When a document is in the Uploaded status it can still go through a Juro signing workflow. If a document is set as Fully Signed it will have this status post-upload. Once this is done, it isn't possible to send that document through the Juro signing flow.

πŸ’β€β™€οΈ As always, our Support Team is happy to help you with anything further if needed. Start a chat with us right here by clicking the Intercom button in the bottom-right-hand corner of this page.

Alternatively, you can email your query to πŸš€

Did this answer your question?