Étape 3 : Connecter Project Monitor aux Triggers

Presentation

The application Project Monitor met à disposition un certain nombre d’actions et de d’événements (triggers) afin de s’interconnecter via Zapier à d’autres applications.

Authentication

Pour pouvoir utiliser les actions et les triggers de l’application, il est nécessaire de s’authentifier. Pour cela, lors de la sélection de l’application Project Monitor in a Zap, you are presented with a login screen.

The login and password are those used to connect directly to the platform. Project Monitor.

The UP field must contain the code of the UP to which the user connects on the platform. Project Monitor. This field is optional, but is necessary if there are duplicate users on 2 UPs.

The URL field is the one entered in the browser to access the platform. Project Monitor. Only the part between https:// and .p-monitor.com.

This form allows you to retrieve the authentication token Project Monitor.

Figure 10 Connection screen

Triggers

A trigger is an event completed by an application that triggers the execution of a Zap. When a trigger is used, a webhook is automatically configured in Project Monitor.

New Project

Event triggered when a project is created on the user's login up.

Fournit l'ensemble des données du projet, ainsi que les logins de l'équipe, les rattachements et les attributs.

Field	Description
`Id`	Identifier Project Monitor internal project
`Code`	Project code
`Title`	Project title
`Description`	Project description
`LongTitle`	Long project title
`ExternalReference`	External project reference
`ExternalApplicationCode`	External project application code
`StateTitle`	Project status
`StateCode`	Project status code
`ProjectManagerLogin`	Login of the user assigned as project manager
`ProjectManagerName`	First and last name of user assigned as project manager
`ModificationDate`	Project modification date (timestamp: 1600781172177)
`BeginDate`	Project start date (timestamp: 1600781172177)
`EndDate`	Project end date (timestamp: 1600781172177)
`CreationDate`	Project creation date (timestamp: 1600781172177)
`TemplateCode`	template code used to create the project
`TemplateId`	Id of the template used to create the project

Updated Project

Evènement déclenché lors de la modification d’un projet. Mêmes données que New Project.

Field	Description
`Id`	Identifier Project Monitor internal project
`Code`	Project code
`Title`	Project title
`Description`	Project description
`LongTitle`	Long project title
`ExternalReference`	External project reference
`ExternalApplicationCode`	External project application code
`StateTitle`	Project status
`StateCode`	Project status code
`ProjectManagerLogin`	Login of the user assigned as project manager
`ProjectManagerName`	First and last name of user assigned as project manager
`ModificationDate`	Project modification date (timestamp: 1600781172177)
`BeginDate`	Project start date (timestamp: 1600781172177)
`EndDate`	Project end date (timestamp: 1600781172177)
`CreationDate`	Project creation date (timestamp: 1600781172177)
`TemplateCode`	template code used to create the project
`TemplateId`	Id of the template used to create the project

Deleted Project

Evènement déclenché lors de la suppression d’un projet sur la plateforme choisie par l’utilisateur.

Field	Description
`Id`	Identifier Project Monitor internal project
`Code`	Project code
`Title`	Project title
`ExternalReference`	External project reference
`ExternalApplicationCode`	External project application code

New Task

Evènement déclenché lors de la création d’une tâche. On retrouve aussi les attributs de la tâche.

Field	Description
`Id`	Identifier Project Monitor internal task
`Title`	task title
`Description`	task description
`ExternalReference`	External task reference
`ExternalApplicationCode`	External task application code
`StateTitle`	task status
`StateCode`	task status code
`PriorityTitle`	task priority
`PriorityCode`	task priority code
`ProjectExternalReference`	External reference for the task project
`ProjectId`	Identifier Project Monitor of the task
`ProjectTitle`	task project title
`CreatorLogin`	Login of the user who created the task
`AssignedLogin`	Login of the user assigned to the task
`ModificationDate`	task modification date (timestamp: 1600781172177)
`BeginDate`	task start date (timestamp: 1600781172177)
`TargetBeginDate`	Scheduled task start date (timestamp: 1600781172177)
`EndDate`	task end date (timestamp: 1600781172177)
`DueDate`	task deadline (timestamp: 1600781172177)

Updated Task

Evènement déclenché lors de la modification d’une tâche. Mêmes données que New Task.

Field	Description
`Id`	Identifier Project Monitor internal task
`Title`	task title
`Description`	task description
`ExternalReference`	External task reference
`ExternalApplicationCode`	External task application code
`StateTitle`	task status
`StateCode`	task status code
`PriorityTitle`	task priority
`PriorityCode`	task priority code
`ProjectExternalReference`	External reference for the task project
`ProjectId`	Identifier Project Monitor of the task
`ProjectTitle`	task project title
`CreatorLogin`	Login of the user who created the task
`AssignedLogin`	Login of the user assigned to the task
`ModificationDate`	task modification date (timestamp: 1600781172177)
`BeginDate`	task start date (timestamp: 1600781172177)
`TargetBeginDate`	Scheduled task start date (timestamp: 1600781172177)
`EndDate`	task end date (timestamp: 1600781172177)
`DueDate`	task deadline (timestamp: 1600781172177)

Deleted Task

Evènement déclenché lors de la suppression d’une tâche.

Field	Description
`Id`	Identifier Project Monitor internal task
`Title`	task title
`ExternalReference`	External task reference
`ExternalApplicationCode`	External task application code

Utilisation d’un trigger

Configurer un zap

The first step is to create a new zap with a trigger as its starting point. Project Monitor.

Figure 11 Creating a zap: Application and trigger selection

For example, in the Choose App & Event, sélectionner l’application Project Monitor and the trigger New project.

Figure 12 Creating a zap: Selecting the login account

The next tab Choose account permet de renseigner les informations de connexion.

Figure 13 Creating a zap: Trigger configuration

The tab Customize Project demande le nom du webhook à créer : utiliser un nom explicite et éviter les doublons entre 2 Zaps.

Figure 14 Creating a zap: Trigger test

The next tab Find Data allows you to test the trigger configuration. To do this, click on the blue button Test trigger. If the webhook has worked, Zapier will find a request (this is the object you've just created). If this step works, your trigger configuration is complete. You can now add any action you like to the trigger.

Figure 15 Query found by Zapier

Gestion du webhook

Creating and deleting webhooks in Project Monitor est automatisée et dépend de l’état des Zaps. L’activation d’un Zap crée un webhook, sa désactivation le supprime.

View webhooks in Project Monitor :

Click on Administration > Advanced settings > Technical configuration > Webhook.
Click on a webhook to view it.

On peut y voir l’url renseignée automatiquement depuis le Zap, complétée par les champs à transmettre.

Trigger de création/modification : uniquement OBJET.ID suffit ; Zapier charge le reste via l'identifiant.

Figure 17 Webhook creation/modification screen

Trigger de suppression : l'objet étant supprimé, il faut passer directement les infos utiles : OBJET.ID, OBJET.LIBELLE, OBJET.REFERENCEEXTERNE ou OBJET.CODEAPPLICATION (utiles notamment pour du bidirectionnel).

Figure 18 Setting up a delete webhook

Il est possible de filtrer les objets donnant lieu à un déclenchement directement dans cet écran, ou d'ajouter des filtres dans Zapier.

Figure 19 Filters applicable to a webhook: Event field

Créer un objet dans Project Monitor

Pour pouvoir tester le webhook, il est nécessaire de créer un objet (que l'on pourra supprimer ensuite) afin de valider le point d’entrée du zap.