29
edits
Integration of Dolibarr to the Zapier automation platform: Difference between revisions
Integration of Dolibarr to the Zapier automation platform (view source)
Revision as of 10:05, 14 May 2023
, 3 years agoFixing code files and licence
(Fixing images) Tag: 2017 source edit |
(Fixing code files and licence) Tag: 2017 source edit |
||
| Line 2: | Line 2: | ||
= Integration of Dolibarr to the Zapier automation platform = | = Integration of Dolibarr to the Zapier automation platform = | ||
[ | [https://creativecommons.org/licenses/by-sa/4.0/ License CC-BY-SA 4.0] | ||
<span id="preamble"></span> | <span id="preamble"></span> | ||
| Line 185: | Line 185: | ||
All you have to do is click on the “Save & Finish” button to complete the authentication configuration. | All you have to do is click on the “Save & Finish” button to complete the authentication configuration. | ||
The different authentication configuration data is available in the file [ | The different authentication configuration data is available in the file [https://github.com/Dolibarr/dolibarr-integration-resources/blob/main/zapier/code/authentication.js code/authentication.js], exported from Zapier CLI. | ||
<span id="create-a-trigger"></span> | <span id="create-a-trigger"></span> | ||
| Line 430: | Line 430: | ||
<blockquote>'''Note:''' Some services like Gmail or Google Drive cannot be used in a Zapier scenario until the integration is published and validated. So you will be able to test your scenario, but when publishing you will get an error message. To work around this problem, you can for example use the “Code by Zapier” > “Run Javascript” action before the Dolibarr action, simply returning the trigger data to make it available in the Dolibarr action. Alternatively, you can publish your integration and have it validated. | <blockquote>'''Note:''' Some services like Gmail or Google Drive cannot be used in a Zapier scenario until the integration is published and validated. So you will be able to test your scenario, but when publishing you will get an error message. To work around this problem, you can for example use the “Code by Zapier” > “Run Javascript” action before the Dolibarr action, simply returning the trigger data to make it available in the Dolibarr action. Alternatively, you can publish your integration and have it validated. | ||
</blockquote> | </blockquote> | ||
The different action configuration data is available in the file [ | The different action configuration data is available in the file [https://github.com/Dolibarr/dolibarr-integration-resources/blob/main/zapier/code/creates/create_event.js code/creates/create_event.js], exported from Zapier CLI. Similarly, you will find other sample actions in the [https://github.com/Dolibarr/dolibarr-integration-resources/tree/main/zapier/code/creates code/creates] folder. | ||
<span id="validate-and-publish-the-integration"></span> | <span id="validate-and-publish-the-integration"></span> | ||
| Line 459: | Line 459: | ||
This tutorial is licensed under a [http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]. | This tutorial is licensed under a [http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]. | ||
[ | [https://creativecommons.org/licenses/by-sa/4.0/ License CC-BY-SA 4.0] | ||