Contents π
Introduction π
With our Zapier integration, you can input and output structured data from over 5,000 apps to ensure data integrity across your tech stack and automate contract workflows.
Your team can automate your contract workflows, sync your data across multiple applications, reduce human error and speed up your contract flows. In short, you're about to supercharge your contracts.
|
Connecting the integration π
π‘ NOTE: only Organisation Admins can action the following process.
|
To get started, you'll need a Juro template to work with. For more information about creating and building your Juro template, take a look at our dedicated article. Once you've done this:
1. Add the smartfields in your template to your internal Forms flow: this shows the fields in Zapier so they can be mapped in your other app.
|
|
2. Go to the Integrations section of AUTOMATIONS tab in the Juro workspace you'd like to connect the integration for and click the API panel.
|
|
4. Go to Zapier and select the Juro application. Click Sign in to Juro and paste the API key into the field.
|
|
Click Yes, Continue.
|
Creating a Zap π
Now that the integration is live between Zapier and Juro, it's time to create a Zap to automate one of your key flows.
Building your zap in another app *οΈβ£
For Inbound Zaps (Other Application > Juro) you can automatically create and share contracts from Juro based on events in over 5,000 other applications:
Select the first application
Follow the form through to select the account and event
Set Juro as the second application
Select the workspace and specify the template you want to create the contract from.
Building your Zap from Juro ποΈ
To build your Zap from Juro
Select Juro as the first application
Follow the form through to select a workspace and select the event you would like to trigger this zap on.
Outbound Zaps (Juro > Other Application) can be triggered by a wide range of events in the Juro platform, including:
Contract created | When a contract creates a new contract in Juro |
Contract deleted | When the contract is moved to the workspace Archive |
Contract edited | When an edit is made to a contract |
Contracted viewed | When a user views the contract |
Contract sent for signing | When a signing request is sent |
Contract sent for approval | When an approval request is sent |
Contract signed | When any party signs the contract |
Approval in progress | When there are multiple approvers on a contract |
Contract fully approved | When all active approvers have approved the contract |
Contract approval request rejected | When any active approver rejects the approval request |
Contract approval cancelled | When an approver is removed from a contract |
PDF generated from the contract | When a user exports the contract from Juro in PDF format |
Comment left on the contract | When a user (internal or external) leaves a comment on a contract |
When a trigger happens, a range of data points can be passed out of Juro and/or used to create conditional workflows, including
The contract name | The name of the contract as it is in Juro |
The contract template | The template used to create the contract |
The contract owner | The current owner of the contract (this may be different from the contract creator if ownership has been transferred) |
The contract status | Draft, Sent for approval, Signed by them, Fully Signed, etc. |
The contract smartfields | The smartfields present on the contract |
Contract Sharing URL | Shown as the REVIEWERS link in juro. |
Example Zaps β‘οΈ
Juro and Teams
Connecting Juro with Teams is a great way to reduce time spent on routine contract tasks like approval and signing. Instead, you could configure Zapier to post a channel message in Teams to notify approvers and signatories when a contract is ready for them.
Juro and Xero:
By connecting Juro and Xero, you can create new sales invoices when contracts are fully signed in Juro; dramatically streamlining post-signature workflows across your organisation.
Google Forms and Juro:
Using Zapier, you can create new contracts in Juro when responses are submitted on a Google Form.
Please do reach out if you'd like to discuss potential automation - our support and legal engineering teams are here to help.
πββοΈ 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 support@juro.com π
|