Once connected, a menu is available on the left:

Accesses the list of Zaps defined on the profile.

Finally, a contextual menu lets you perform actions on a Zap.

• Edit: Allows you to administer Zap (cf. Mémo Zapier - 4.1 Setting up a Zap).
• Rename: Renames the Zap.
• Share Zap: Allows you to share a link to the Zap (cf. Mémo Zapier - Shared folders).
• Move to folder : Moves the Zap to a folder created in Private folders. Mémo Zapier - Private folders
• Task History: Open the Zaphistory (cf. Mémo Zapier - 2.3.4 Task history).
• Copy: Creates a copy of the Zap.
• Trash: Deletes the Zap.

Regroups all connections to applications defined in Zaps.

You can rename them, test the connection status and connect or disconnect them.

For each Zap, you can see its name, the last execution date, the number of Zapier tasks consumed and the number of errors raised by the Zap.

Open in Editor : Redirects to Zap administration (cf. Mémo Zapier - 4.1 Setting up a Zap).

View Task log : Redirects to Zap taskhistory (cf. Mémo Zapier - 2.3.4 Task history).

Regroups the entire taskhistory for all Zaps defined on the profile.

For each Zap execution, we show its status (successful, failed, filtered), its name, the execution date and the number of associated Zapier tasks.

Click on a line to access the Zap execution details. For each Zap step, you'll find the execution status, the date and, depending on the step, the input and output data, the completion of conditions, etc.

To be able to use the actions (cf. Mémo Zapier - 3.5 Actions) and triggers (cf. Mémo Zapier - 3.4 Triggers) of the application, authentication is required. To do this, when selecting the 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.

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

For example, in the Choose App & Eventwe select the application Project Monitor and the trigger New project.

The next tab is the Choose account to enter the application's connection information Project Monitor. It is possible to select an account already entered in the list. My Apps (cf. Mémo Zapier - 2.3.3 My Apps) or add an account directly (cf. Mémo Zapier - 3.3 Authentication).

The next tab Customize Project displays a field to be filled in with the name of the webhook to be created. It's advisable to use an explicit name, and to avoid duplicates between 2 Zaps.

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.

The list of created webhooks is displayed. Click on a webhook to view it.

This screen shows the url automatically filled in from Zap. It is completed by the fields you wish to pass to Zapier.

Creation/modification trigger: OBJECT.ID only. Zapier will use the task or project ID to load the rest of the fields.

Delete trigger : As the object is deleted, it is not possible to load all its fields from its identifier. You can, for example, pass the information OBJECT.ID, OBJECT.LIBEL, OBJECT.REFERENCEEXTERNAL or OBJECT.CODEAPPLICATION. The last 2 fields can be very useful if you want to do bidirectional work. For example, a task initially created in Trello (and therefore created in Project Monitor), which you then wish to reinject into Trello according to the changes in Project Monitor.

Here is an example of how to set up a deletion:

The full url is :

'https://hooks.zapier.com/hooks/catch/7389244/ofef2s8?id='+OBJET.ID+'&referenceExterne='+OBJET.REFERENCEEXTERNE+'&libelle='+OBJET.LIBELLE+'&codeApplication='+OBJET.CODEAPPLICATION

Note that you can filter the objects triggered by the Event.

If the filters on this screen aren't enough, you can also add filters directly in Zapier. Just because a webhook notification is sent doesn't mean you have to use it.

1. Click on Administration.
2. Click on Field settings.
3. Click on Hierarchies.

La liste des hiérarchies de la plateforme est affichée.

4. Choisir la hiérarchie concernée.
5. Vérifier que pour l’objet rattaché project template, le champ Mandatory est bien coché. S’il ne l’est pas, le modifier en conséquence.
6. Click on Register si vous avez réalisé des modifications.

1. Click on Administration.
2. Click on Model settings.
3. In the Templatesclick on Project.

La liste des gabarits existants s’affiche.

4. Click on Add.
5. Compléter les champs suivants :
• Wording
• Code : (sera utilisé dans les Zap)
• Description
• Attachments

It is possible to create multiple templates for project creation via Zapier. All you need to do is configure the Zaps to use the relevant templates according to the data.

In Project Monitortasks and projects can have attributes of various types. Here is the list of types supported (or not) by the application's actions Project Monitor via Zapier.

Project creation uses the following fields:

Zapier	Description	Monitor project
Title	Project title (required)	Wording
Description	Project description	Description
Project Code	Code Project Monitor project (required)	Code
Start Date	Project start date (required)	Start date
End Date	Project end date (required)	End date
Project Manager Login	Identifier Project Monitor of the user assigned as leader of the new project	project manager
State Code	Project status	status
Template Code	Code for template v to be applied to the new project.	current project template
External Reference	Project identifier in external application. If left empty, the project can be modified and/or deleted via the code Project MonitorProject Monitor.	Internal field
Source Application	External application code (mandatory)	Internal field
Custom Attributes	List of attributes associated with the project	form >> attribute
Reference Links	List of project links	form >> CODE_HIERARCHY

• For a string type: Enter the string ;
• For a multiline type: Enter the character string ;
• For a Boolean type: Enter 'True' or 'False'.
• For a numeric type: Enter the number
• For the date type: Enter the timestamp
• For list type: Enter the code of the list value (the list must also have a code)

It is perfectly possible to use results extracted from previous triggers or zap actions.

Links must be transmitted in the same way as attributes. Each structure link must be on a single line. In the first field, enter the structure code. In the second field, enter the structure value code, or the level value codes separated by commas.

Modify an existing project in Project Monitor.

Editing a project uses the following fields:

Zapier	Description	Monitor project
Title	Project title (required)	Wording
Description	Project description	Description
Project Code	Code Project Monitor the project	Code
Start Date	Project start date	Start date
End Date	Project end date	End date
Project Manager Login	Identifier Project Monitor of the user assigned as project leader	project manager
State Code	Project status	status
External Reference	Project identifier in external application. If left blank, the Project Code must be filled in.	Internal field
Source Application	External application code (mandatory)	Internal field
Custom Attributes	List of attributes associated with the project	form >> attribute
Reference Link Mode	0 = No change to project links 1 = Reference Links attachments added 2 = Replacement by attachments designated by Reference Links
Reference Links	List of project links	form >> CODE_HIERARCHY

Login :

Customize trigger conditions, here we want to filter the activity (we only want a trigger for a project creation). For your information, there's also the Filter by Zapier to filter data in a zap more efficiently, but this increases the number of monthly tasks.

Here you need to create a project to validate that the trigger works properly, then click on Test trigger :

Let's take the example of a project or task creation in Trello that needs to be reflected in Project Monitorsome data exist in both Trello and Project Monitorbut are not described in the same way. (Project status, project manager login, task priority). It is therefore necessary to associate these values to make the zap fully dynamic. To do this, add a new action and use Formatter by Zapier.

In the Transform field, select Lookup table.

In lookup key, select the field you wish to test. In our example, the field is board closed which indicates whether the project is open or closed.

This will allow us to associate, depending on the field value board closeda value corresponding to the status a project Project Monitor.

For board closed = false then the code will be status

For board closed = true then the code will be status.

• The data status come from the get_databut you can type them directly into this field if you know the status codes.

Once associated, the value deduced can be used in the application's project creationaction Project Monitor :

A zap must end with an action, in this case theaction new project in Project Monitor. The goal is for Trello data to be dynamically retrieved in Project Monitor.

The data title, description and project code are data taken directly from Trello. Simply click in a field and click on the data you wish to associate with it.

The data state code is an associated datum as seen in Mémo Zapier - 4.1.2 Making associations between target and source systems it is deduced using Zapier formatter. To select it, click in the field.

The field Application source is compulsory, it defines the application that produced the trigger (in this case, Trello).

It is also possible to enter attributes Project Monitor in the last field, the number of attributes is unlimited and all types are accepted except file typesDocument). The following syntax must be observed: CODEATTRIBUTE=VALUEATTRIBUTE. In the example, this is attribute list or _TEST_ATT_3 is a list value code.

For details of prices and types of Zapier licenses go to https://zapier.com/app/billing/plans