Send a Slack alert when a Juro contract is signed

When a contract is signed in Juro, this workflow posts a message to a Slack channel, so sales, finance or onboarding hear about the signature without checking Juro or waiting for an email.

Juro

Slack

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.3k sites Free to import

The Send a Slack alert when a Juro contract is signed workflow on the FlowMattic canvas, with 2 steps across Juro, Slack — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

A signed contract is often the signal for other people to start work: finance sends the first invoice, onboarding books a kickoff, sales updates the forecast. If that news sits in one person's inbox, the next steps wait. This workflow puts it in Slack.

The Juro trigger reacts when a contract instance is signed. FlowMattic takes the data Juro sends about that contract and passes it to Slack. The Send Channel Message step then posts your message to the channel you pick, with contract details mapped in, such as its name or the counterparty, where Juro includes them.

The template posts one message per signed event and has no Filter. Juro's own wording is that the trigger fires when a contract instance is signed. On contracts with several signers, check with a test whether you get one message per signature or one at the end. Each run is listed in Task History with the data Juro sent.

Closed deals in the sales channel

Customer agreements signed in Juro post to #wins, so the account executive's team sees the deal close and finance knows to raise the invoice.

Offer letters for the people team

When a new hire signs their offer in Juro, the HR channel hears about it and can start ordering equipment and setting up accounts.

Supplier agreements for operations

Operations gets a Slack post as each supplier contract is signed, so they know when they can place the first order.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Juro Contract Signed
Fires when a contract instance is signed in Juro. The contract data Juro sends is passed on for the Slack message.
Step 2Action
Slack Send Channel Message
Sends your signing alert into a Slack channel. Write the text and map in contract details from Juro, such as the contract name, so the team knows which agreement was signed.

What you need

FlowMatticCore
Juro AccountAccount
Slack 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.

Want to know earlier in the process? Build a second workflow on Juro's Contract Approval Process Finished trigger, which fires when everyone has approved the contract.
If the channel is private, use Slack's Send Private Channel Message action in place of this step.
Add a Filter after the trigger to post only certain contract types, using a value from the Juro data such as the template name, if your test run shows one.

Questions about this workflow

Does the Slack message include the signed Juro contract file?

No. Slack receives a written alert only, with no file attached. You can include details Juro sends, and a link to the contract if the trigger data carries one; check a test run to see.

Will a contract with two signers post twice?

It may. Juro describes the trigger as firing when a contract instance is signed. Run a test with a two-party contract and check Task History to see how many runs it creates.

Can I send Juro signing alerts to one person instead of a channel?

Yes. Swap the step for Slack's Send Direct Message action and choose the teammate who should receive each one.