Create a project in HandsHQ from simPRO via Zapier

Use Zapier to integrate HandsHQ and simPRO in a few easy steps!

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

Summary

This article explains integrating your simPRO account with HandsHQ RAMS via Zapier (an integration management tool). We focus on the specific example of triggering a new HandsHQ project with key project details populated when a new job is raised in simPRO.

In this article:


Integrate simPRO and HandsHQ via Zapier

Set up a trigger in Zapier

If you need more context about using HandsHQ with Zapier, read our Zapier setup guide here.

  1. Create New Zap in Zapier

  2. Search for simPRO and add it

  3. Choose a trigger (an event)

We went with New Job.

However, you can choose a different trigger; below are the options provided by simPRO.

3. Connect your simPRO account

4. Test your trigger by clicking on Test.

You’ll receive a message that a record was found if everything is set up correctly.


Setting up an action

  1. Add the HandsHQ app to your list by following this link https://zapier.com/developer/invite/109205/be272b2f17edc2d47d4eae5eaacf1472/

  2. Search for and add HandsHQ

  3. Choose an action (event)

In our case, it’s Create Project.

4. Connect your HandsHQ account by navigating to https://app.handshq.com/settings/api_configuration (Settings > API)

⇒ copy the API token and paste into a window like this:

If you have multiple divisions in HandsHQ, you will have a unique API key for each division. If you want to integrate multiple divisions, each one will need its own separate Zap workflow.

5. Map the fields from your simPRO trigger to the project details of the HandsHQ project

6. Test the action.

If everything is set up correctly, you’ll see a message that a project has been sent to HandsHQ.

7. Publish your Zap, and you're ready to go!


What happens next?

Every time a job is raised in simPRO, a draft project will be created in HandsHQ, with the project details filled in. You will still need to complete the project and add the risk assessments and method statement details as normal.

Did this answer your question?