DocJuris
DocJuris is a contract negotiation workspace that empowers legal and business teams to close deals with speed and accuracy.
This connector is available in the following products and regions:
Service | Class | Regions |
---|---|---|
Logic Apps | Standard | All Logic Apps regions except the following: - Azure Government regions - Azure China regions - US Department of Defense (DoD) |
Power Automate | Premium | All Power Automate regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
Power Apps | Premium | All Power Apps regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
Contact | |
---|---|
Name | DocJuris Support |
URL | https://help.docjuris.com |
support@docjuris.com |
Connector Metadata | |
---|---|
Publisher | DocJuris |
Website | https://www.docjuris.com |
Privacy policy | http://www.docjuris.com/privacy-policy |
Categories | Productivity |
DocJuris for Power Automate empowers users to connect apps together to create useful contract workflows that save time and risk. With the connector, users can leverage DocJuris' innovative contract collaboration and editing capabilities to automate an organization's contract lifecycle from intake to esign to storage. For example, route a contract request from Microsoft Forms to DocJuris and simultaneously notify users in Teams or in Dynamics. DocJuris and Power Automate are a perfect complement to enrich contract processes and enable low code automation for small and large teams.
Prerequisites
DocJuris for Power Automate requires a paid subscription to DocJuris. Please get in touch on www.docjuris.com.
How to get credentials
To authorize DocJuris for Power Automate, visit the Organization
tab in your DocJuris settings. Next, copy the Organization ID
and paste it into the organizationId
field in Power Automate. Third, click Generate new key
and give it a helpful name like "Jill's Power Automate". Click the copy icon to copy the new key and paste the value into the apiKey
field in Power Automate.
Getting started with your connector
In this step-by-step sample flow, we'll submit a contract request form in Microsoft Forms and route a contract to DocJuris. During this example flow, we'll also configure the connector.
Create a Microsoft Form
Create a simple Microsoft Form and include, at a minimum, a file attachment question.
Create a New Automated Cloud Flow
Open Power Automate and click Create. Next, select Automated Cloud Flow
.
Next, Skip
the wizard and arrive to the page to search for connectors and triggers.
Trigger Microsoft Forms
Click Microsoft Forms
or search for it.
Select the Trigger When a new response is submitted
.
Select the form you created earlier from the list next to the Form Id
field and click ``+ New step`.
Get Response Details from Microsoft Forms
To retrieve information from a Microsoft Forms submission, pick Microsoft Forms
as the Action and select Get Response Details
. Next, select the Form Id
and select the Response Id
associated with form submissions. It should be the only Dynamic content
available at this stage.
Setup the DocJuris Connector
Under Choose an operation
, click the Custom
tab and pick DocJuris
from the list. DocJuris will also show up under All
in the future.
Click Create an import file
as the Action
Configuring Connection Information in Power Automate
When you first create a new flow using the DocJuris connector, you will be prompted for connection information:
For Connection Name
pick something meaningful to you, such as "Jill's DocJuris Connection".
The other two values must be found within the DocJuris application.
Grab Keys from DocJuris
After logging in to DocJuris, click the circle icon with your initials in the upper right of the application:
In the resulting page, open the Organization
tab.
- The "Organization ID" at the bottom is the first part of your connection credential. Copy this and paste it into the
organizationId
field in Power Automate. - The second part requires an API Key. Click "Generate new key" and give it a helpful name like "Jill's Power Automate". Click the copy icon to copy the new key- this is the only time you will see it! Paste the value into the
apiKey
field in Power Automate.
Create an Import File in DocJuris
Now that you've configured DocJuris, we can now create an import file. Once the connector is authenticated, you'll see options For Extended data name/value/type
- you can ignore these for now.
- Skip down to
Import file
and pick the field from the Microsoft Form where the user uploaded a file. - Under
Import file name
, you can use a date stamp or other unique identifier or name from the Microsoft forms submission.
Click Save
and proceed to Test the Microsoft Form in trigger. Look for the Test button in Power Automate either Manually
or Automatically
depending on the availability of recent submissions.
If there are no recent submissions, head over to your Microsoft Form and submit the request and attached a contract. For example, you can load the following agreement to Microsoft Forms as an attachment.
After a successful test, confirm that the submission and attachment created an import file in DocJuris.
Power Automate test view:
DocJuris Dashboard:
DocJuris Triggers
- Turn Completed: triggers when a turn is marked complete.
- Turn Created: triggers when a turn is created
- Turn Tagged: triggers when a turn is tagged (e.g., execution copy)
DocJuris Actions
- Analyze New Contract: creates a contract in DocJuris and analyzes it
- Import Contract: stages the contract for creation and analysis and allows a user to complete the contract analysis process in the DocJuris app
- Get Turn: get information about a contract turn in DocJuris such as counterparty name or contract type
- Get Turn Document: get the document for use in other apps and services
Known issues and limitations
DocJuris for Power Automate is not a replacement for customized integrations with other platforms. In some cases, DocJuris' triggers and actions are not a complete implementation of every endpoint in the DocJuris API. Please get in touch at www.docjuris.com to start a conversation about a deeper integration that you might need.
Common errors and remedies
If you encounter any unexpected errors or issues, please contact us at support@docjuris.com!
FAQ
How do you retrieve a document after a contract is analyzed?
Use an action to get turn details.
What's the difference between a staged import and analyze a contract?
Staged imports allow users to engage the analysis window in DocJuris to pick playbooks and complete any missing meta data. This is a good option if the triggering app or service does not have enough information to perform an analysis. Good attributes to trigger a full analysis vs. a staged import include: playbook, contract type, description, and counterparty. In all instances, an attachment is required.
What's a tagged turn?
Tags to a turn refer to attributes set in DocJuris such as "execution copy." These tags can be set in DocJuris when working with a turn in the analyzer.
What are the extended data fields when I load a DocJuris action?
Contracts and turns can be created with extended data. This data will be attached to the contract record, and can be retrieved with later queries. It can be used to store reference data relevant to the caller, or to pass reference urls to DocJuris.
Creating a connection
The connector supports the following authentication types:
Default | Parameters for creating connection. | All regions | Not shareable |
Default
Applicable: All regions
Parameters for creating connection.
This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.
Name | Type | Description | Required |
---|---|---|---|
organizationId | securestring | The organizationId for this api | True |
apiKey | securestring | The apiKey for this api | True |
Throttling Limits
Name | Calls | Renewal Period |
---|---|---|
API calls per connection | 100 | 60 seconds |
Actions
Create a contract |
Create a contract document |
Create an import file |
Import files can be used to create contracts or contract turns within the DocJuris app. |
Create turn |
Create contract turn. |
Delete a callback subscription |
Deletes a subscription |
Download latest turn document |
For "completedWithMarkup" and "completedClean" the return document corresponds to the latest turn. For "original" the return document belongs to the first turn. |
Download latest turn document description |
Get information about a turn document, such as file name and extension. |
Download turn document |
Get contract turn documents. |
Download turn document description |
Get information about a turn document, such as file name and extension. |
Get a contract |
Get details for a contract. |
Get contract types |
Get available contract types. |
Get playbooks |
Get available playbooks. |
Get test callback messages |
Get test messages. |
Get turn details |
Get contract turn details. |
Create a contract
Create a contract document
Parameters
Name | Key | Required | Type | Description |
---|---|---|---|---|
Name
|
name | string | ||
Contract Type
|
contractTypeId | integer |
One of contractType or contractTypeId must be supplied |
|
Playbook
|
playbookId | integer |
Playbook for contract |
|
Counterparty
|
counterPartyName | string |
One of counterPartyName or counterPartyId must be supplied |
|
name
|
name | string |
Name of an extra piece of data that will follow the contract |
|
value
|
value | string |
Value for that extra piece of data |
|
type
|
type | string |
Type for that extra piece of data |
|
Contract file
|
file | byte | ||
Contract file name
|
fileName | string | ||
Owning User's Email Address
|
owningUserEmail | string |
Returns
Create an import file
Import files can be used to create contracts or contract turns within the DocJuris app.
Parameters
Name | Key | Required | Type | Description |
---|---|---|---|---|
name
|
name | string |
Name of an extra piece of data that will follow the contract |
|
value
|
value | string |
Value for that extra piece of data |
|
type
|
type | string |
Type for that extra piece of data |
|
Import file
|
file | byte | ||
Import file name
|
fileName | string |
Returns
Create turn
Create contract turn.
Parameters
Name | Key | Required | Type | Description |
---|---|---|---|---|
Contract Id
|
contractId | True | uuid |
Available in trigger data. |
source
|
source | string |
A string that describes who this turn is from (i.e. internal dept., outside counsel, etc.). If this turn is from the counterparty leave this blank. |
|
description
|
description | string | ||
currentTurnId
|
currentTurnId | uuid |
A string ID of the latest known turn. The API will return an error if this does not match the latest turn's ID (i.e. if another turn was uploaded by another user). |
|
name
|
name | string |
Name of an extra piece of data that will follow the contract |
|
value
|
value | string |
Value for that extra piece of data |
|
type
|
type | string |
Type for that extra piece of data |
|
Contract file
|
file | byte | ||
Contract file name
|
fileName | string |
Returns
Delete a callback subscription
Deletes a subscription
Parameters
Name | Key | Required | Type | Description |
---|---|---|---|---|
Subscription Id
|
id | True | string |
Id of subscription to delete |
Returns
- Body
- ApiStandardResponse
Download latest turn document
For "completedWithMarkup" and "completedClean" the return document corresponds to the latest turn. For "original" the return document belongs to the first turn.
Parameters
Name | Key | Required | Type | Description |
---|---|---|---|---|
Contract Id
|
contractId | True | uuid |
Available in trigger data. |
Document State
|
docState | string |
State of document to download |
Returns
- response
- binary
Download latest turn document description
Get information about a turn document, such as file name and extension.
Parameters
Name | Key | Required | Type | Description |
---|---|---|---|---|
Contract Id
|
contractId | True | uuid |
Available in trigger data. |
Document State
|
docState | string |
State of document to describe |
Returns
Download turn document
Get contract turn documents.
Parameters
Name | Key | Required | Type | Description |
---|---|---|---|---|
Contract ID
|
contractId | True | uuid |
Available in trigger data. |
Turn ID
|
turnId | True | uuid |
Available in trigger data. |
Document type
|
docState | string |
Stage of document to download |
Returns
- Turn Document
- binary
Download turn document description
Get information about a turn document, such as file name and extension.
Parameters
Name | Key | Required | Type | Description |
---|---|---|---|---|
Contract ID
|
contractId | True | uuid |
Available in trigger data. |
Turn ID
|
turnId | True | uuid |
Available in trigger data. |
Document type
|
docState | string |
Stage of document to describe |
Returns
Get a contract
Get details for a contract.
Parameters
Name | Key | Required | Type | Description |
---|---|---|---|---|
Contract Id
|
contractId | True | uuid |
Available in trigger data. |
Returns
Get contract types
Get available contract types.
Parameters
Name | Key | Required | Type | Description |
---|---|---|---|---|
Skip
|
skip | integer |
Skip N types. Default 0. |
|
Take
|
take | integer |
Take N types. Default 200. |
|
Sort Field
|
sortBy | string |
Sort field. |
|
Filter
|
filter | string |
Filter to names including given string. |
Returns
Get playbooks
Get available playbooks.
Parameters
Name | Key | Required | Type | Description |
---|---|---|---|---|
Skip
|
skip | integer |
Skip N types. Default 0. |
|
Take
|
take | integer |
Take N types. Default 200. |
|
Sort Field
|
sortBy | string |
Sort field. |
|
Filter
|
filter | string |
Filter to names including given string. |
Returns
Get test callback messages
Get test messages.
Parameters
Name | Key | Required | Type | Description |
---|---|---|---|---|
Message Type
|
type | string |
Message Type |
Returns
Get turn details
Get contract turn details.
Parameters
Name | Key | Required | Type | Description |
---|---|---|---|---|
Contract ID
|
contractId | True | uuid |
Available in trigger data. |
Turn ID
|
turnId | True | uuid |
Available in trigger data. |
Returns
Triggers
Mention in Turn |
Mention in Turn |
Screening Report Updated |
Screening Report Updated |
Turn Completed |
Turn Completed |
Turn Created |
Turn Created |
Turn Tagged |
Turn Tagged |
Mention in Turn
Screening Report Updated
Turn Completed
Turn Created
Turn Tagged
Definitions
ApiStandardResponse
Name | Path | Type | Description |
---|---|---|---|
meta
|
meta | ApiStandardResponseMeta |
ApiStandardResponseMeta
Contract
Name | Path | Type | Description |
---|---|---|---|
Description
|
description | string | |
Id
|
id | uuid | |
Latest Turn Id
|
latestTurnId | uuid | |
Last Modified Date
|
lastModified | date-time | |
Name
|
name | string | |
ID
|
type.id | integer | |
Name
|
type.name | string | |
Description
|
type.description | string | |
Counterparty
|
counterParty | CounterParty | |
extendedData
|
extendedData | ExtendedData | |
Url
|
urls | Urls |
ContractApiStandardResponse
Name | Path | Type | Description |
---|---|---|---|
meta
|
meta | ApiStandardResponseMeta | |
Contract
|
response | Contract |
ContractType
Name | Path | Type | Description |
---|---|---|---|
ID
|
id | integer | |
Name
|
name | string | |
Description
|
description | string |
ContractTypeList
Name | Path | Type | Description |
---|---|---|---|
totalCount
|
totalCount | integer | |
skip
|
skip | integer | |
take
|
take | integer | |
filter
|
filter | string | |
sortBy
|
sortBy | string | |
contractTypes
|
contractTypes | array of ContractType |
ContractTypeListApiStandardResponse
Name | Path | Type | Description |
---|---|---|---|
meta
|
meta | ApiStandardResponseMeta | |
response
|
response | ContractTypeList |
CounterParty
Name | Path | Type | Description |
---|---|---|---|
ID
|
id | integer | |
Name
|
name | string |
DocumentMeta
Name | Path | Type | Description |
---|---|---|---|
Full Name (with extension)
|
name | string | |
Extension
|
extension | string | |
Original Name
|
originalFileName | string |
DocumentMetaApiStandardResponse
Name | Path | Type | Description |
---|---|---|---|
meta
|
meta | ApiStandardResponseMeta | |
Document File
|
response | DocumentMeta |
ExtendedData
Name | Path | Type | Description |
---|---|---|---|
Extended data
|
namedValues | array of ExtendedDataNamedData |
Optional user-specific data to attach to the the contract. |
ExtendedDataNamedData
Name | Path | Type | Description |
---|---|---|---|
name
|
name | string |
Name of an extra piece of data that will follow the contract |
value
|
value | string |
Value for that extra piece of data |
type
|
type | string |
Type for that extra piece of data |
ObjectIEnumerableApiStandardResponse
Name | Path | Type | Description |
---|---|---|---|
meta
|
meta | ApiStandardResponseMeta | |
response
|
response | array of |
Playbook
Name | Path | Type | Description |
---|---|---|---|
ID
|
id | integer | |
Title
|
name | string | |
Contract Type
|
contractType | ContractType |
PlaybookListApiStandardResponse
Name | Path | Type | Description |
---|---|---|---|
meta
|
meta | ApiStandardResponseMeta | |
response
|
response | PlaybookList |
PlaybookList
Name | Path | Type | Description |
---|---|---|---|
totalCount
|
totalCount | integer | |
skip
|
skip | integer | |
take
|
take | integer | |
filter
|
filter | string | |
sortBy
|
sortBy | string | |
playbooks
|
playbooks | array of Playbook |
StagedImport
Name | Path | Type | Description |
---|---|---|---|
id
|
id | uuid | |
extendedData
|
extendedData | ExtendedData | |
Url
|
urls | Urls |
StagedImportApiStandardResponse
Name | Path | Type | Description |
---|---|---|---|
meta
|
meta | ApiStandardResponseMeta | |
response
|
response | StagedImport |
TurnSubscriptionMessage
Name | Path | Type | Description |
---|---|---|---|
Message ID
|
messageId | string |
id |
Turn ID
|
turnId | string |
id |
Contract ID
|
contractId | string |
contractId |
Event type
|
type | string |
type |
URL to DocJuris
|
url | string |
url |
Tags
|
tags | array of object | |
ID
|
tags.id | string |
id |
Name
|
tags.name | string |
name |
Description
|
tags.description | string |
description |
TurnMentionSubscriptionMessage
Name | Path | Type | Description |
---|---|---|---|
Message ID
|
messageId | string |
id |
Turn ID
|
turnId | string |
id |
Contract ID
|
contractId | string |
contractId |
Event type
|
type | string |
type |
URL to DocJuris
|
url | string |
url |
Tags
|
tags | array of object | |
ID
|
tags.id | string |
id |
Name
|
tags.name | string |
name |
Description
|
tags.description | string |
description |
Text
|
mention.text | string |
text |
First Name
|
mention.mentioningUser.firstName | string |
firstName |
Last Name
|
mention.mentioningUser.lastName | string |
lastName |
Username
|
mention.mentioningUser.userName | string |
userName |
First Name
|
mention.mentionedUser.firstName | string |
firstName |
Last Name
|
mention.mentionedUser.lastName | string |
lastName |
Username
|
mention.mentionedUser.userName | string |
userName |
Commend ID
|
mention.commentId | string |
commentId |
Link to comment in DocJuris
|
mention.url | string |
url |
Turn
Name | Path | Type | Description |
---|---|---|---|
Turn ID
|
id | uuid | |
Is Turn Complete?
|
isComplete | boolean | |
Is Turn Latest?
|
isLatest | boolean | |
Last Modified Date/Time
|
lastModified | date-time | |
Source
|
source | string | |
Original File Name
|
importedFileName | string | |
Description
|
description | string | |
Contract Type
|
type | ContractType | |
Counterparty
|
counterParty | CounterParty | |
extendedData
|
extendedData | ExtendedData | |
Url
|
urls | Urls | |
tags
|
tags | array of TurnTag |
TurnApiStandardResponse
Name | Path | Type | Description |
---|---|---|---|
meta
|
meta | ApiStandardResponseMeta | |
response
|
response | Turn |
TurnTag
Name | Path | Type | Description |
---|---|---|---|
id
|
id | uuid | |
name
|
name | string | |
description
|
description | string |
Urls
Name | Path | Type | Description |
---|---|---|---|
to DocJuris
|
app | string |
binary
This is the basic data type 'binary'.