34
edits
Lpierson002 (talk | contribs) (Page layout modification and content completion) |
Lpierson002 (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
== Connecting to n8n == | ==Connecting to n8n== | ||
As explained in previous parts, once you have created your n8n self-hosted instance on your computer and started it with the command : | As explained in previous parts, once you have created your n8n self-hosted instance on your computer and started it with the command : | ||
```bash | ```bash | ||
| Line 14: | Line 14: | ||
 |  | ||
== Creating a Workflow using Dolibarr Node == | ==Creating a Workflow using Dolibarr Node== | ||
When you have signed in, you can create you first Workflow and selected the Dolibarr node. | When you have signed in, you can create you first Workflow and selected the Dolibarr node. | ||
To do that you just have to click on | To do that you just have to click on '''Add Workflow''' to create one and click on the '''+''' to add a node to your Workflow. It will open a search bar in which you can search '''dolibarr''' to find it. | ||
<br /> | |||
[[File:Dolibarr node.png|center|thumb|Dolibarr Node]] | |||
== Explanation of the different functionnalities == | ==Explanation of the different functionnalities== | ||
[[File:Different scenarios.png|center|thumb|Different scenarios]] | |||
Here are the different Dolibarr functionnalities we have implemented in n8n. | Here are the different Dolibarr functionnalities we have implemented in n8n. | ||
=== General informations === | ===General informations=== | ||
==== Credentials ==== | ====Credentials==== | ||
For every Dolibarr node you will have to setup up your credentials in order to connect your Dolibarr instance to n8n. | For every Dolibarr node you will have to setup up your credentials in order to connect your Dolibarr instance to n8n. | ||
You can connect to your Dolibarr from the | You can connect to your Dolibarr from the '''Credentials''' tab or directly from a Dolibarr node. | ||
[[File:Credentials.png|center|thumb|Credentials]] | |||
You have to indicate you base URL which is your instance URL. | You have to indicate you base URL which is your instance URL. | ||
| Line 40: | Line 42: | ||
And your API key that you can find in your account parameters when connecting in Dolibarr. | And your API key that you can find in your account parameters when connecting in Dolibarr. | ||
==== Fields in every node ==== | ====Fields in every node==== | ||
[[File:Add event n8n.png|center|thumb|Add event n8n]] | |||
For every Dolibarr node there will be some fields that will be the same. | For every Dolibarr node there will be some fields that will be the same. | ||
These fiels are the first three one on the picture below : | These fiels are the first three one on the picture below : | ||
=== Creating a Calendar Event === | * '''Credential''' to connect with : this is where you can set your `credentials` as explained just before, | ||
* '''Resource''' : this is where you just which module of Dolibarr it will affect, there are 4 options : Calendar, Task, Document and Custom API Call (use this one only if you know what you are doing), | |||
* '''Operation''' : this is in this field where you select this kind of operation you want to do on this specific resource, for now it only support creation operations. | |||
===Creating a Calendar Event=== | |||
The first node is used to create an event in the calendar in Dolibarr. | The first node is used to create an event in the calendar in Dolibarr. | ||
 |  | ||
If you have selected the `Create an Event` and have alreary set your credentials the first three fields will be already completed. | If you have selected the `Create an Event` and have alreary set your credentials the first three fields will be already completed. | ||
| Line 70: | Line 75: | ||
<br /> | <br /> | ||
==== Creating an event in Calendar when an event is created in Google Calendar ==== | ====Creating an event in Calendar when an event is created in Google Calendar==== | ||
To produce this use case you will have to connect a `Google Calendar Trigger node` on the `Dolibarr node`. | To produce this use case you will have to connect a `Google Calendar Trigger node` on the `Dolibarr node`. | ||
| Line 95: | Line 100: | ||
- `{{$json.start.dateTime }}` correspond to the ending time of the Google Calendar event. | - `{{$json.start.dateTime }}` correspond to the ending time of the Google Calendar event. | ||
==== Creating an event in Calendar when an email is received ==== | ====Creating an event in Calendar when an email is received==== | ||
To produce this use case you will have to connect an `Email Trigger node` on the `Dolibarr node`, for example the `Email Trigger (IMAP) node` or the `Gmail Trigger node`. | To produce this use case you will have to connect an `Email Trigger node` on the `Dolibarr node`, for example the `Email Trigger (IMAP) node` or the `Gmail Trigger node`. | ||
| Line 120: | Line 125: | ||
The second screenshot correspond to a possible configuration of the `Dolibarr Create an event Node` with the `Email Trigger (IMAP) node` when the `Email From` and `Email Subject` fields will be implemented in the Dolibarr interface in future updates. | The second screenshot correspond to a possible configuration of the `Dolibarr Create an event Node` with the `Email Trigger (IMAP) node` when the `Email From` and `Email Subject` fields will be implemented in the Dolibarr interface in future updates. | ||
=== Creating a document === | ===Creating a document=== | ||
The second node is used to create create a document on a specific Dolibarr module.  | The second node is used to create create a document on a specific Dolibarr module.  | ||
| Line 141: | Line 146: | ||
- `Create Subdirectories if Necessary ?` is an additionnal field that when activated creates a Subdirectory for your file if this is necessery (this field is optional). | - `Create Subdirectories if Necessary ?` is an additionnal field that when activated creates a Subdirectory for your file if this is necessery (this field is optional). | ||
==== Add a document in Dolibarr Document Gestion containing Zoom meeting information ==== | ====Add a document in Dolibarr Document Gestion containing Zoom meeting information==== | ||
To produce this use case you will have to connect an `Zoom Get Meeting node` on the `Dolibarr node` with a `n8n Trigger node` at the beggining og the workflow. | To produce this use case you will have to connect an `Zoom Get Meeting node` on the `Dolibarr node` with a `n8n Trigger node` at the beggining og the workflow. | ||
| Line 170: | Line 175: | ||
Finally, the additional Field `Overwrite File If Already Exists` is activated to be able ot overwrite the file with more or different informations from the Zoom meeting if wanted. | Finally, the additional Field `Overwrite File If Already Exists` is activated to be able ot overwrite the file with more or different informations from the Zoom meeting if wanted. | ||
=== Creating a Project Task === | ===Creating a Project Task=== | ||
 |  | ||
| Line 193: | Line 198: | ||
A possible configuration for creating a document having zoom meeting inf | A possible configuration for creating a document having zoom meeting inf | ||
==== Creating a Task in Dolibarr when a Github issue is received ==== | ====Creating a Task in Dolibarr when a Github issue is received==== | ||
To produce this use case you will have to connect a `Github Trigger node` on the `Dolibarr node`. | To produce this use case you will have to connect a `Github Trigger node` on the `Dolibarr node`. | ||
| Line 226: | Line 231: | ||
- `{{$json.body.issue.created_at }}` correspond to creation date of the issue. | - `{{$json.body.issue.created_at }}` correspond to creation date of the issue. | ||
=== Conclusion === | ===Conclusion=== | ||
This tutorial helped you understand how to configure a Dolibarr node in n8n and how they work in order to make you build the example use cases or custom use cases using already existing Dolibarr node functionnalities. | This tutorial helped you understand how to configure a Dolibarr node in n8n and how they work in order to make you build the example use cases or custom use cases using already existing Dolibarr node functionnalities. | ||
edits