LawVu connector for Power Platform FAQ

Frequently asked questions

What is Power Automate?

Microsoft Power Automate is a no-code/low-code, drag and drop workflow builder that enables people to create automation workflows based on their specific business needs. 

What is the LawVu connector for Power Platform?

The LawVu connector for Power Platform contains a set of prebuilt triggers and actions that allow in-house legal teams to automatically run workflows based on events in LawVu (e.g. contract executed, file uploaded, new matter created) using the Power Automate platform. Within a workflow, you can apply prebuilt actions/steps which allow automations to interact with LawVu matters and contracts. 

Do I need to be a LawVu customer to use the LawVu connector for Power Platform?

Yes, you’ll need a LawVu subscription. If you don’t have an account, visit

Do I need a developer or coding skills?

No coding or advanced technical skills are required. The LawVu connector for Power Platform was designed for Legal Operations, or those with a legal ops mindset, to pick up and use themselves. 

Does it cost?

Yes, there is an annual fee, additional to your existing LawVu subscription. This includes the LawVu connector to Power Platform, plus access to our workflow templates. Note: You will require a Microsoft Power Platform licence.  Please speak to your LawVu Customer Service Manager or Implementation Service Manager. They’ll ensure you have the information you need and help set you up. 

Is there a free trial? Is there a free development tier?

There is no free trial or freemium model for the LawVu connector to Power Platform. We recommend exploring the list of Triggers and Actions to see what’s possible, and if you have any questions reach out to

What triggers and actions are available?

There are currently 14 triggers and 27 prebuilt actions available within the LawVu connector for Power Platform. Click here to explore the list. 

How can I get up and running quickly?

We provide a set of workflow templates, which can be requested by emailing These provide a quick starting point, which you can then adapt to suit your needs. 


  • Create a matter in LawVu and send a notification
  • Notify a team when a contract is signed
  • Notify a team when a matter is created
  • Create a LawVu contract when an email is received
  • Get a push notification for important matters
  • Create a matter when a user completes a Microsoft Forms form
  • Upload a file to Sharepoint when a new file is uploaded to a LawVu matter 
  • Upload a file to Sharepoint when a new file is uploaded to a LawVu contract
Is there an upper limit on the number of workflows that are created?

No. Please be aware of the implication (if any) on your Power Automate licensing plan, especially if licensed “per flow”.

What are some common use cases? What have others done?

Here are some examples of what our customers have done. We will continue to add to this list over time. 

  • Dynamic routing of matters and contracts to the right teams and individuals
  • Automated data entry/updates
  • Sync of key data points between LawVu and external systems
  • Custom notification workflows
  • Automated back-up of legal agreements and supplementary data to external document management systems.
Can the LawVu connector for Power Platform be used with Power Apps and Azure Logic Apps?

Yes, the LawVu connector for Power Platform also shows up in both Microsoft Power Apps or Azure Logic Apps, so you can use it in these places too.

How can I develop my Power Automate skillset to maximise our investment in automation?

We recommend exploring the extensive Power Platform resources within Microsoft Learn. 

Can this connector be used to connect LawVu to [System X]?

A full list of the 1000+ Microsoft Power Platform connectors can be found here. If an official connector doesn’t exist, the right resource can help create one against a publicly accessible API to bridge the gap.

What happens when LawVu updates the product? Will my workflow break?

We try to limit breaking changes that will adversely affect developers and customers. However, if necessary, they will always be communicated well in advance (3 months minimum). Please make sure your contact details remain current so we can reach you. Any new, updated or deprecated actions and triggers in our Developer Changelog.

How do I get support?

If you need help with the LawVu connector for Power Platform, please contact us at

For support for Microsoft Power Automate, you can ask questions on the Power Automate community

What additional features or tools are you planning to develop/release?

LawVu may choose to build additional functionality into the connector over time. We will include such updates in our Developer Changelog.

Can I sell my workflows to other customers?

Not currently, however this is something LawVu is considering. If you are interested in selling your workflows to other customers, please get in touch at

What are the Terms and Conditions?
  • Use of LawVu’s starter templates and connector for Power Platform are governed by LawVu’s developer platform terms.
  • Use of Microsoft’s Power Platform is governed by Microsoft’s Product Terms.
Who owns the workflow created using LawVu’s connector for Power Platform?

The customer retains full IP over workflows they create using the connector.

How is access to sensitive information stored in LawVu secured?

Access to matters, and contracts and files is secured under the context of an individual, authenticated user. If your organization uses SSO (Okta or Active Directory), the usual user authentication workflow will also be used when connecting Power Platform to LawVu.

In practice, the creation of a special, nominated “service user” account might be preferable for many workflows as opposed to authenticating as an actual user. This nominated user account can then be assigned broad access to records as required by the workflow, without opening up this same level of to an actual LawVu user where it’s not otherwise desirable.

Why do certain LawVu-triggered workflows take up to 2 minutes to start, whilst others kick off almost instantly?

This depends on which trigger provided by the LawVu connector you are using.

The triggers “when a matter is updated” and “when a contract is updated” have a built-in delay, since otherwise field updates performed in quick succession would cause an excessive volume of workflow runs which in turn could have adverse effects.  All other triggers are designed to fire within seconds of the corresponding event occurring in LawVu.

If I’m looking to build a workflow which provides important operational benefits to my wider team, how can I ensure continuity for my business even in the event I should become unavailable?

We recommend these practices:

  • Invite your colleagues as co-owners of the flow, ensuring continuity should the original author leave your organisation.
  • As each action uses a connection to the underlying system, consider which/whose account is best to use for each connection in the flow. User permissions will play an important part in what the flow can do for these actions. The account(s) will need to be managed appropriately to prevent the flow from failing if the account is disabled, locked or removed. For your LawVu account, you might want to investigate using a “service account” which isn’t tied to any particular individual.
  • Regularly backup the flow definition using the Export function to keep a copy should it need to be restored. Once saved, it is not possible to undo changes to flows.

Get started today

1. Get a Power Automate licence: before you start, you will need your own Microsoft Power Automate licence.

2. Speak to us: reach out to your LawVu representative to learn about pricing, see how it works and ensure you have the add-on enabled on your subscription.

3. Start accessing: once enabled, search for “LawVu '' within Power Automate.