Skip to main content
Integrate HandsHQ projects via Power Automate

Connect HandsHQ to your Microsoft tech stack via PowerAutomate (MicrosoftFlow)

Iryna Struk avatar
Written by Iryna Struk
Updated over a year ago

Summary

This article focuses on integrating your HandsHQ RAMS account with different systems via Power Automate. We use an example of connecting gmail to trigger the creation of a HandsHQ project, but it can be used for many other automated workflows.

Covered in this article:


Integrate HandsHQ with other software using Power Automate

What is Power Automate?

Power Automate (previously MicrosoftFlow) is a Microsoft service that helps you create automated workflows between HandsHQ and other software. It's an alternative to Zapier and can be used if you are connecting to other Microsoft products, for example, Sharepoint.

Get started: Create a custom connector

  1. Go to your PowerAutomate account

  2. Go to Data ⇒ Custom connectors ⇒ New custom connector ⇒ Import an Open API file

3. Download the file from here and import it to PowerAutomate

4. Click on Create connector


Create a flow

  1. Click Create (panel on the left) ⇒ Automated Cloud flow

  2. Add a flow name and choose your trigger

We selected Gmail as an example.

3. Click on New step ⇒ Type HandsHQ in the search bar **** (or if you named your custom connector differently, type that name)

4. Go to Actions ⇒ Select Creates a project on HandsHQ

5. Add a name and an API key from https://app.handshq.com/settings/api_configuration

(Settings > API)

Please note that the API key is division-specific in HandsHQ

6. Now add dynamic content into the project details

We’ve added the below as an example.

7. Save ⇒ Test

You are all set now!

You will still need to edit in the project on HandsHQ to add your risks, tasks and site-specific information. The project will be created with the set project details filled in so that you don't have to copy and paste these.


FAQs

I’m getting an error which says that user details aren’t valid

For the user mentioned in the flow to be able to create a project in HandsHQ, the user needs to exist in the respective division.

API keys are division-specific on HandsHQ.

Did this answer your question?