Create a ClickUp task when a Juro contract approval is denied
When an approver rejects a contract in Juro, this workflow opens a ClickUp task so the rejection has an owner, a place for notes and a due date, instead of sitting unnoticed in Juro.
Juro
ClickUp2 steps Setup ~5 min Used on 3.5k sites Productivity Free to import
What this workflow does
A rejected approval stalls a deal or a hire until someone revises the contract. If the person who drafted it misses the notification, the contract can sit for days. This workflow turns each denial into work in the project tool your team plans in.
The Juro trigger fires when one of the approvers rejects a contract. FlowMattic passes the details of that event to ClickUp, where Create Task adds a new task to the list you choose. You set the task name and description, inserting contract values from Juro so the assignee knows which agreement to fix.
The task is created once per rejection. Because the trigger fires for each approver who rejects, a contract turned down by two approvers yields two tasks. Each rejection that came through is listed in Task History.
Legal revisions queue
Each denied contract becomes a task in a Legal Revisions list, where the counsel on duty picks it up and updates the draft.
Sales deal desk
When finance rejects discount terms in Juro, the deal desk gets a ClickUp task to rework the pricing with the rep.
Vendor agreements
Procurement tracks every rejected supplier contract in ClickUp to see which vendors need renegotiation.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Juro Contract Approval DeniedFires when one of the approvers rejects a contract in Juro. The event's contract details are available to map into the ClickUp task.
- ClickUp Create Task
Creates a new ClickUp task in the list you choose. Put the contract name in the task name and add details from Juro to the description; check a test run to see which values Juro provides.
What you need
- FlowMatticCore
- Juro AccountAccount
- ClickUp AccountAccount
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- Include the contract's name or ID from the Juro event in the task name so people can find the agreement in Juro quickly.
- If only some agreements need a ClickUp task, add a Filter after the trigger on a value the Juro event carries, such as the template name.
- Set an assignee and due date in the ClickUp step, if your list uses them, so the rejection lands with a named owner.
Questions about this workflow
Does a ClickUp task get created for every approver who rejects the Juro contract?
Yes. The trigger fires when one of the approvers rejects, so several rejections on one contract give several tasks.
Is the ClickUp task closed when the contract is approved?
No. The template only creates the task. Your team closes it in ClickUp once the contract is revised and approved.
Can the rejection comment from Juro go into the task?
Only if the Contract Approval Denied event carries it. Reject a test contract after import and check the captured data before mapping.
More Project Management workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted