diff --git a/.vale.ini b/.vale.ini index d2dce89ab..540df51be 100644 --- a/.vale.ini +++ b/.vale.ini @@ -5,4 +5,4 @@ Vocab = default BasedOnStyles = from-alex, from-write-good, n8n-styles, from-microsoft, Vale Vale.Terms = NO from-alex.Profanity = NO -TokenIgnores = (\-\-8\<\-\- \".*\"), (-only), (\*\*.*\*\*), (\**Release date:\**.*), (\[\[\%.*\%\]\]), (\[.*\]\(.*\)\{:target=_blank .external-link\}), (\[\[.*\]\]) +TokenIgnores = (\-\-8\<\-\- \".*\"), (-only), (\*\*.*\*\*), (\**Release date:\**.*), (\[\[\%.*\%\]\]), (\[.*\]\(.*\)\{:target=_blank .external-link\}), (\[\[.*\]\]), (Rocket\.Chat) diff --git a/docs/_images/integrations/builtin/app-nodes/deepl/deepl_node.png b/docs/_images/integrations/builtin/app-nodes/deepl/deepl_node.png deleted file mode 100644 index c510407d2..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/deepl/deepl_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/deepl/httprequest_node.png b/docs/_images/integrations/builtin/app-nodes/deepl/httprequest_node.png deleted file mode 100644 index 4b95898a7..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/deepl/httprequest_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/deepl/workflow.png b/docs/_images/integrations/builtin/app-nodes/deepl/workflow.png deleted file mode 100644 index b0162561c..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/deepl/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/demio/demio_node.png b/docs/_images/integrations/builtin/app-nodes/demio/demio_node.png deleted file mode 100644 index 164461539..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/demio/demio_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/demio/typeformtrigger_node.png b/docs/_images/integrations/builtin/app-nodes/demio/typeformtrigger_node.png deleted file mode 100644 index b37b2837a..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/demio/typeformtrigger_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/demio/workflow.png b/docs/_images/integrations/builtin/app-nodes/demio/workflow.png deleted file mode 100644 index 4ecf461be..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/demio/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/discourse/discourse1_node.png b/docs/_images/integrations/builtin/app-nodes/discourse/discourse1_node.png deleted file mode 100644 index b34d15548..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/discourse/discourse1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/discourse/discourse2_node.png b/docs/_images/integrations/builtin/app-nodes/discourse/discourse2_node.png deleted file mode 100644 index b39626f96..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/discourse/discourse2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/discourse/discourse_node.png b/docs/_images/integrations/builtin/app-nodes/discourse/discourse_node.png deleted file mode 100644 index 7fcc6dc74..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/discourse/discourse_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/discourse/workflow.png b/docs/_images/integrations/builtin/app-nodes/discourse/workflow.png deleted file mode 100644 index 509dfb39e..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/discourse/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/dropcontact/dropcontact_node.png b/docs/_images/integrations/builtin/app-nodes/dropcontact/dropcontact_node.png deleted file mode 100644 index a59c92b87..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/dropcontact/dropcontact_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/dropcontact/googlesheet_node.png b/docs/_images/integrations/builtin/app-nodes/dropcontact/googlesheet_node.png deleted file mode 100644 index bac75e35d..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/dropcontact/googlesheet_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/dropcontact/lemlist_node.png b/docs/_images/integrations/builtin/app-nodes/dropcontact/lemlist_node.png deleted file mode 100644 index 7f8acef41..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/dropcontact/lemlist_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/dropcontact/workflow.png b/docs/_images/integrations/builtin/app-nodes/dropcontact/workflow.png deleted file mode 100644 index fd345e8ea..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/dropcontact/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/egoi/e-goi1_node.png b/docs/_images/integrations/builtin/app-nodes/egoi/e-goi1_node.png deleted file mode 100644 index 376b55d1f..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/egoi/e-goi1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/egoi/e-goi2_node.png b/docs/_images/integrations/builtin/app-nodes/egoi/e-goi2_node.png deleted file mode 100644 index 8d6ef5c18..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/egoi/e-goi2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/egoi/e-goi_node.png b/docs/_images/integrations/builtin/app-nodes/egoi/e-goi_node.png deleted file mode 100644 index ab6b8b582..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/egoi/e-goi_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/egoi/workflow.png b/docs/_images/integrations/builtin/app-nodes/egoi/workflow.png deleted file mode 100644 index c8027f157..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/egoi/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/emelia/emelia1_node.png b/docs/_images/integrations/builtin/app-nodes/emelia/emelia1_node.png deleted file mode 100644 index 72fc880a2..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/emelia/emelia1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/emelia/emelia2_node.png b/docs/_images/integrations/builtin/app-nodes/emelia/emelia2_node.png deleted file mode 100644 index 593076f9a..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/emelia/emelia2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/emelia/emelia_node.png b/docs/_images/integrations/builtin/app-nodes/emelia/emelia_node.png deleted file mode 100644 index d1d8e510e..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/emelia/emelia_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/emelia/workflow.png b/docs/_images/integrations/builtin/app-nodes/emelia/workflow.png deleted file mode 100644 index 11560e982..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/emelia/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googlebooks/googlebooks1_node.png b/docs/_images/integrations/builtin/app-nodes/googlebooks/googlebooks1_node.png deleted file mode 100644 index 3909c6053..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googlebooks/googlebooks1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googlebooks/googlebooks2_node.png b/docs/_images/integrations/builtin/app-nodes/googlebooks/googlebooks2_node.png deleted file mode 100644 index 33af0102d..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googlebooks/googlebooks2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googlebooks/googlebooks_node.png b/docs/_images/integrations/builtin/app-nodes/googlebooks/googlebooks_node.png deleted file mode 100644 index 1beb5591e..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googlebooks/googlebooks_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googlebooks/workflow.png b/docs/_images/integrations/builtin/app-nodes/googlebooks/workflow.png deleted file mode 100644 index 53832dc43..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googlebooks/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googlecontacts/googlecontacts1_node.png b/docs/_images/integrations/builtin/app-nodes/googlecontacts/googlecontacts1_node.png deleted file mode 100644 index 21a99f7fe..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googlecontacts/googlecontacts1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googlecontacts/googlecontacts2_node.png b/docs/_images/integrations/builtin/app-nodes/googlecontacts/googlecontacts2_node.png deleted file mode 100644 index 78e17f424..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googlecontacts/googlecontacts2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googlecontacts/googlecontacts_node.png b/docs/_images/integrations/builtin/app-nodes/googlecontacts/googlecontacts_node.png deleted file mode 100644 index 8a0f406fe..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googlecontacts/googlecontacts_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googlecontacts/workflow.png b/docs/_images/integrations/builtin/app-nodes/googlecontacts/workflow.png deleted file mode 100644 index 05b1420a9..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googlecontacts/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googledocs/googledocs1_node.png b/docs/_images/integrations/builtin/app-nodes/googledocs/googledocs1_node.png deleted file mode 100644 index 55115193e..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googledocs/googledocs1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googledocs/googledocs_node.png b/docs/_images/integrations/builtin/app-nodes/googledocs/googledocs_node.png deleted file mode 100644 index af46974ba..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googledocs/googledocs_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googledocs/workflow.png b/docs/_images/integrations/builtin/app-nodes/googledocs/workflow.png deleted file mode 100644 index 5e3c00bef..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googledocs/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googledrive/workflow.png b/docs/_images/integrations/builtin/app-nodes/googledrive/workflow.png deleted file mode 100644 index 918853101..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googledrive/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googleslides/googleslides1_node.png b/docs/_images/integrations/builtin/app-nodes/googleslides/googleslides1_node.png deleted file mode 100644 index fe5094176..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googleslides/googleslides1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googleslides/googleslides_node.png b/docs/_images/integrations/builtin/app-nodes/googleslides/googleslides_node.png deleted file mode 100644 index e93fd2ffd..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googleslides/googleslides_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/googleslides/workflow.png b/docs/_images/integrations/builtin/app-nodes/googleslides/workflow.png deleted file mode 100644 index fd50979d0..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/googleslides/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/halopsa/halopsa-client-create.png b/docs/_images/integrations/builtin/app-nodes/halopsa/halopsa-client-create.png deleted file mode 100644 index 1b775722c..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/halopsa/halopsa-client-create.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/halopsa/workflow.png b/docs/_images/integrations/builtin/app-nodes/halopsa/workflow.png deleted file mode 100644 index ce6cb7a24..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/halopsa/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/iterable/iterable1_node.png b/docs/_images/integrations/builtin/app-nodes/iterable/iterable1_node.png deleted file mode 100644 index 6f314a760..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/iterable/iterable1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/iterable/iterable2_node.png b/docs/_images/integrations/builtin/app-nodes/iterable/iterable2_node.png deleted file mode 100644 index 7726a82c4..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/iterable/iterable2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/iterable/iterable_node.png b/docs/_images/integrations/builtin/app-nodes/iterable/iterable_node.png deleted file mode 100644 index 9a2196a35..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/iterable/iterable_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/iterable/workflow.png b/docs/_images/integrations/builtin/app-nodes/iterable/workflow.png deleted file mode 100644 index 97eabac84..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/iterable/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/jenkins/workflow.png b/docs/_images/integrations/builtin/app-nodes/jenkins/workflow.png deleted file mode 100644 index 27007cb7a..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/jenkins/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/kitemaker/kitemaker1_node.png b/docs/_images/integrations/builtin/app-nodes/kitemaker/kitemaker1_node.png deleted file mode 100644 index 68fda012b..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/kitemaker/kitemaker1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/kitemaker/kitemaker2_node.png b/docs/_images/integrations/builtin/app-nodes/kitemaker/kitemaker2_node.png deleted file mode 100644 index f0eb5c3fe..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/kitemaker/kitemaker2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/kitemaker/kitemaker_node.png b/docs/_images/integrations/builtin/app-nodes/kitemaker/kitemaker_node.png deleted file mode 100644 index 2f259cbb8..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/kitemaker/kitemaker_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/kitemaker/workflow.png b/docs/_images/integrations/builtin/app-nodes/kitemaker/workflow.png deleted file mode 100644 index f9e3f56e4..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/kitemaker/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/lemlist/airtable_node.png b/docs/_images/integrations/builtin/app-nodes/lemlist/airtable_node.png deleted file mode 100644 index 831140630..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/lemlist/airtable_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/lemlist/lemlist1_node.png b/docs/_images/integrations/builtin/app-nodes/lemlist/lemlist1_node.png deleted file mode 100644 index 1bbb8860e..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/lemlist/lemlist1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/lemlist/lemlist_node.png b/docs/_images/integrations/builtin/app-nodes/lemlist/lemlist_node.png deleted file mode 100644 index 1889790c8..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/lemlist/lemlist_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/lemlist/workflow.png b/docs/_images/integrations/builtin/app-nodes/lemlist/workflow.png deleted file mode 100644 index fa8d5c2fa..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/lemlist/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/lingvanex/httprequest_node.png b/docs/_images/integrations/builtin/app-nodes/lingvanex/httprequest_node.png deleted file mode 100644 index d45777ad5..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/lingvanex/httprequest_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/lingvanex/lingvanex_node.png b/docs/_images/integrations/builtin/app-nodes/lingvanex/lingvanex_node.png deleted file mode 100644 index 561ee39c0..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/lingvanex/lingvanex_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/lingvanex/workflow.png b/docs/_images/integrations/builtin/app-nodes/lingvanex/workflow.png deleted file mode 100644 index 77640ebf0..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/lingvanex/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/mailerlite/mailerlite1_node.png b/docs/_images/integrations/builtin/app-nodes/mailerlite/mailerlite1_node.png deleted file mode 100644 index 64b9c70e2..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/mailerlite/mailerlite1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/mailerlite/mailerlite2_node.png b/docs/_images/integrations/builtin/app-nodes/mailerlite/mailerlite2_node.png deleted file mode 100644 index 7517d2fee..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/mailerlite/mailerlite2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/mailerlite/mailerlite_node.png b/docs/_images/integrations/builtin/app-nodes/mailerlite/mailerlite_node.png deleted file mode 100644 index bad060cfe..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/mailerlite/mailerlite_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/mailerlite/workflow.png b/docs/_images/integrations/builtin/app-nodes/mailerlite/workflow.png deleted file mode 100644 index ff4c74661..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/mailerlite/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/medium/workflow.png b/docs/_images/integrations/builtin/app-nodes/medium/workflow.png deleted file mode 100644 index baace17b5..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/medium/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/microsoftteams/microsoftteams1_node.png b/docs/_images/integrations/builtin/app-nodes/microsoftteams/microsoftteams1_node.png deleted file mode 100644 index 9b05a5006..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/microsoftteams/microsoftteams1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/microsoftteams/microsoftteams2_node.png b/docs/_images/integrations/builtin/app-nodes/microsoftteams/microsoftteams2_node.png deleted file mode 100644 index 6e3822ea0..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/microsoftteams/microsoftteams2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/microsoftteams/microsoftteams_node.png b/docs/_images/integrations/builtin/app-nodes/microsoftteams/microsoftteams_node.png deleted file mode 100644 index e0837214d..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/microsoftteams/microsoftteams_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/microsoftteams/workflow.png b/docs/_images/integrations/builtin/app-nodes/microsoftteams/workflow.png deleted file mode 100644 index a5a9727d3..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/microsoftteams/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/microsofttodo/microsofttodo1_node.png b/docs/_images/integrations/builtin/app-nodes/microsofttodo/microsofttodo1_node.png deleted file mode 100644 index 44691513d..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/microsofttodo/microsofttodo1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/microsofttodo/microsofttodo2_node.png b/docs/_images/integrations/builtin/app-nodes/microsofttodo/microsofttodo2_node.png deleted file mode 100644 index 27df37bd8..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/microsofttodo/microsofttodo2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/microsofttodo/microsofttodo_node.png b/docs/_images/integrations/builtin/app-nodes/microsofttodo/microsofttodo_node.png deleted file mode 100644 index 9c39fc3ea..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/microsofttodo/microsofttodo_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/microsofttodo/workflow.png b/docs/_images/integrations/builtin/app-nodes/microsofttodo/workflow.png deleted file mode 100644 index 5c4fa4f0b..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/microsofttodo/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/mindee/httprequest_node.png b/docs/_images/integrations/builtin/app-nodes/mindee/httprequest_node.png deleted file mode 100644 index 08ebea872..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/mindee/httprequest_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/mindee/mindee_node.png b/docs/_images/integrations/builtin/app-nodes/mindee/mindee_node.png deleted file mode 100644 index 3653d920f..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/mindee/mindee_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/mindee/workflow.png b/docs/_images/integrations/builtin/app-nodes/mindee/workflow.png deleted file mode 100644 index b259ff4c9..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/mindee/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/orbit/orbit1_node.png b/docs/_images/integrations/builtin/app-nodes/orbit/orbit1_node.png deleted file mode 100644 index d2e2c9930..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/orbit/orbit1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/orbit/orbit2_node.png b/docs/_images/integrations/builtin/app-nodes/orbit/orbit2_node.png deleted file mode 100644 index 430f86148..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/orbit/orbit2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/orbit/orbit3_node.png b/docs/_images/integrations/builtin/app-nodes/orbit/orbit3_node.png deleted file mode 100644 index 21f7c5319..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/orbit/orbit3_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/orbit/orbit_node.png b/docs/_images/integrations/builtin/app-nodes/orbit/orbit_node.png deleted file mode 100644 index fa0657d06..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/orbit/orbit_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/orbit/workflow.png b/docs/_images/integrations/builtin/app-nodes/orbit/workflow.png deleted file mode 100644 index 6e0a70c27..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/orbit/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/paddle/paddle_node.png b/docs/_images/integrations/builtin/app-nodes/paddle/paddle_node.png deleted file mode 100644 index 15e4281f0..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/paddle/paddle_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/paddle/workflow.png b/docs/_images/integrations/builtin/app-nodes/paddle/workflow.png deleted file mode 100644 index e6ddf1702..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/paddle/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/pagerduty/pagerduty1_node.png b/docs/_images/integrations/builtin/app-nodes/pagerduty/pagerduty1_node.png deleted file mode 100644 index afcb31433..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/pagerduty/pagerduty1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/pagerduty/pagerduty2_node.png b/docs/_images/integrations/builtin/app-nodes/pagerduty/pagerduty2_node.png deleted file mode 100644 index 456cbb342..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/pagerduty/pagerduty2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/pagerduty/pagerduty_node.png b/docs/_images/integrations/builtin/app-nodes/pagerduty/pagerduty_node.png deleted file mode 100644 index 2e3de2792..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/pagerduty/pagerduty_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/pagerduty/workflow.png b/docs/_images/integrations/builtin/app-nodes/pagerduty/workflow.png deleted file mode 100644 index 8e2d90d23..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/pagerduty/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/peekalink/if_node.png b/docs/_images/integrations/builtin/app-nodes/peekalink/if_node.png deleted file mode 100644 index 361fd776b..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/peekalink/if_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/peekalink/noop_node.png b/docs/_images/integrations/builtin/app-nodes/peekalink/noop_node.png deleted file mode 100644 index 5a19f49af..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/peekalink/noop_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/peekalink/peekalink1_node.png b/docs/_images/integrations/builtin/app-nodes/peekalink/peekalink1_node.png deleted file mode 100644 index ec6af25cc..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/peekalink/peekalink1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/peekalink/peekalink_node.png b/docs/_images/integrations/builtin/app-nodes/peekalink/peekalink_node.png deleted file mode 100644 index 3c2409cc6..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/peekalink/peekalink_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/peekalink/workflow.png b/docs/_images/integrations/builtin/app-nodes/peekalink/workflow.png deleted file mode 100644 index dc8ddef57..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/peekalink/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/philipshue/workflow.png b/docs/_images/integrations/builtin/app-nodes/philipshue/workflow.png deleted file mode 100644 index 59d0cff8c..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/philipshue/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/posthog/posthog_node.png b/docs/_images/integrations/builtin/app-nodes/posthog/posthog_node.png deleted file mode 100644 index d242f0620..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/posthog/posthog_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/posthog/webhook_node.png b/docs/_images/integrations/builtin/app-nodes/posthog/webhook_node.png deleted file mode 100644 index 5591f0d0e..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/posthog/webhook_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/posthog/workflow.png b/docs/_images/integrations/builtin/app-nodes/posthog/workflow.png deleted file mode 100644 index f1445b2f4..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/posthog/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/raindrop/raindrop1_node.png b/docs/_images/integrations/builtin/app-nodes/raindrop/raindrop1_node.png deleted file mode 100644 index 704c2f734..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/raindrop/raindrop1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/raindrop/raindrop2_node.png b/docs/_images/integrations/builtin/app-nodes/raindrop/raindrop2_node.png deleted file mode 100644 index 11f5dab6b..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/raindrop/raindrop2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/raindrop/raindrop3_node.png b/docs/_images/integrations/builtin/app-nodes/raindrop/raindrop3_node.png deleted file mode 100644 index ab0cdadd2..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/raindrop/raindrop3_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/raindrop/raindrop_node.png b/docs/_images/integrations/builtin/app-nodes/raindrop/raindrop_node.png deleted file mode 100644 index b626b5787..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/raindrop/raindrop_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/raindrop/workflow.png b/docs/_images/integrations/builtin/app-nodes/raindrop/workflow.png deleted file mode 100644 index f0984b90d..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/raindrop/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/reddit/reddit1_node.png b/docs/_images/integrations/builtin/app-nodes/reddit/reddit1_node.png deleted file mode 100644 index fa942b708..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/reddit/reddit1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/reddit/reddit2_node.png b/docs/_images/integrations/builtin/app-nodes/reddit/reddit2_node.png deleted file mode 100644 index a9b265884..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/reddit/reddit2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/reddit/reddit_node.png b/docs/_images/integrations/builtin/app-nodes/reddit/reddit_node.png deleted file mode 100644 index d94429dba..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/reddit/reddit_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/reddit/workflow.png b/docs/_images/integrations/builtin/app-nodes/reddit/workflow.png deleted file mode 100644 index fb5c242a1..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/reddit/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/rocketchat/workflow.png b/docs/_images/integrations/builtin/app-nodes/rocketchat/workflow.png deleted file mode 100644 index 253d2753b..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/rocketchat/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/salesforce/salesforce1_node.png b/docs/_images/integrations/builtin/app-nodes/salesforce/salesforce1_node.png deleted file mode 100644 index dde1c0f7f..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/salesforce/salesforce1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/salesforce/salesforce2_node.png b/docs/_images/integrations/builtin/app-nodes/salesforce/salesforce2_node.png deleted file mode 100644 index 6902a8ea6..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/salesforce/salesforce2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/salesforce/salesforce_node.png b/docs/_images/integrations/builtin/app-nodes/salesforce/salesforce_node.png deleted file mode 100644 index 68190c209..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/salesforce/salesforce_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/salesforce/workflow.png b/docs/_images/integrations/builtin/app-nodes/salesforce/workflow.png deleted file mode 100644 index 088fcd914..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/salesforce/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/sendy/sendy1_node.png b/docs/_images/integrations/builtin/app-nodes/sendy/sendy1_node.png deleted file mode 100644 index 1bad98c13..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/sendy/sendy1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/sendy/sendy_node.png b/docs/_images/integrations/builtin/app-nodes/sendy/sendy_node.png deleted file mode 100644 index fdf0279e6..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/sendy/sendy_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/sendy/workflow.png b/docs/_images/integrations/builtin/app-nodes/sendy/workflow.png deleted file mode 100644 index 06c5f10d2..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/sendy/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/storyblok/storyblok1_node.png b/docs/_images/integrations/builtin/app-nodes/storyblok/storyblok1_node.png deleted file mode 100644 index 0cc24bd6e..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/storyblok/storyblok1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/storyblok/storyblok_node.png b/docs/_images/integrations/builtin/app-nodes/storyblok/storyblok_node.png deleted file mode 100644 index fe722cfa3..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/storyblok/storyblok_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/storyblok/workflow.png b/docs/_images/integrations/builtin/app-nodes/storyblok/workflow.png deleted file mode 100644 index 50b12ab9a..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/storyblok/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/taiga/taiga1_node.png b/docs/_images/integrations/builtin/app-nodes/taiga/taiga1_node.png deleted file mode 100644 index 27a8e07ea..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/taiga/taiga1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/taiga/taiga2_node.png b/docs/_images/integrations/builtin/app-nodes/taiga/taiga2_node.png deleted file mode 100644 index c69510be7..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/taiga/taiga2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/taiga/taiga_node.png b/docs/_images/integrations/builtin/app-nodes/taiga/taiga_node.png deleted file mode 100644 index da6626cea..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/taiga/taiga_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/taiga/workflow.png b/docs/_images/integrations/builtin/app-nodes/taiga/workflow.png deleted file mode 100644 index 0dc535cac..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/taiga/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/travisci/travisci_node.png b/docs/_images/integrations/builtin/app-nodes/travisci/travisci_node.png deleted file mode 100644 index 1f88fb57b..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/travisci/travisci_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/travisci/workflow.png b/docs/_images/integrations/builtin/app-nodes/travisci/workflow.png deleted file mode 100644 index f7b433595..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/travisci/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/twist/twist1_node.png b/docs/_images/integrations/builtin/app-nodes/twist/twist1_node.png deleted file mode 100644 index 10013f46d..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/twist/twist1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/twist/twist2_node.png b/docs/_images/integrations/builtin/app-nodes/twist/twist2_node.png deleted file mode 100644 index 0b2584b2a..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/twist/twist2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/twist/twist_node.png b/docs/_images/integrations/builtin/app-nodes/twist/twist_node.png deleted file mode 100644 index 4f0de5fff..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/twist/twist_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/twist/workflow.png b/docs/_images/integrations/builtin/app-nodes/twist/workflow.png deleted file mode 100644 index 113e41c84..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/twist/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/uptimerobot/uptimerobot1_node.png b/docs/_images/integrations/builtin/app-nodes/uptimerobot/uptimerobot1_node.png deleted file mode 100644 index c206391a8..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/uptimerobot/uptimerobot1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/uptimerobot/uptimerobot2_node.png b/docs/_images/integrations/builtin/app-nodes/uptimerobot/uptimerobot2_node.png deleted file mode 100644 index f1d676f90..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/uptimerobot/uptimerobot2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/uptimerobot/uptimerobot_node.png b/docs/_images/integrations/builtin/app-nodes/uptimerobot/uptimerobot_node.png deleted file mode 100644 index 17fbc7f1f..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/uptimerobot/uptimerobot_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/uptimerobot/workflow.png b/docs/_images/integrations/builtin/app-nodes/uptimerobot/workflow.png deleted file mode 100644 index cfce2aa9d..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/uptimerobot/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/vero/workflow.png b/docs/_images/integrations/builtin/app-nodes/vero/workflow.png deleted file mode 100644 index 21c430501..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/vero/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/webflow/webflow1_node.png b/docs/_images/integrations/builtin/app-nodes/webflow/webflow1_node.png deleted file mode 100644 index e5c907221..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/webflow/webflow1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/webflow/webflow2_node.png b/docs/_images/integrations/builtin/app-nodes/webflow/webflow2_node.png deleted file mode 100644 index 35cad817e..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/webflow/webflow2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/webflow/webflow_node.png b/docs/_images/integrations/builtin/app-nodes/webflow/webflow_node.png deleted file mode 100644 index a44f1a2c5..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/webflow/webflow_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/webflow/workflow.png b/docs/_images/integrations/builtin/app-nodes/webflow/workflow.png deleted file mode 100644 index 233f0bf05..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/webflow/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/wise/wise1_node.png b/docs/_images/integrations/builtin/app-nodes/wise/wise1_node.png deleted file mode 100644 index c4443ece5..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/wise/wise1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/wise/wise2_node.png b/docs/_images/integrations/builtin/app-nodes/wise/wise2_node.png deleted file mode 100644 index f28bf4ad8..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/wise/wise2_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/wise/wise3_node.png b/docs/_images/integrations/builtin/app-nodes/wise/wise3_node.png deleted file mode 100644 index 87e164fe5..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/wise/wise3_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/wise/wise_node.png b/docs/_images/integrations/builtin/app-nodes/wise/wise_node.png deleted file mode 100644 index 9d05ef178..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/wise/wise_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/wise/workflow.png b/docs/_images/integrations/builtin/app-nodes/wise/workflow.png deleted file mode 100644 index 95d119710..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/wise/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/wordpress/wordpress1_node.png b/docs/_images/integrations/builtin/app-nodes/wordpress/wordpress1_node.png deleted file mode 100644 index c815f1619..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/wordpress/wordpress1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/wordpress/wordpress_node.png b/docs/_images/integrations/builtin/app-nodes/wordpress/wordpress_node.png deleted file mode 100644 index e12d0b39d..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/wordpress/wordpress_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/wordpress/workflow.png b/docs/_images/integrations/builtin/app-nodes/wordpress/workflow.png deleted file mode 100644 index e168fc9df..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/wordpress/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/yourls/workflow.png b/docs/_images/integrations/builtin/app-nodes/yourls/workflow.png deleted file mode 100644 index 76907a213..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/yourls/workflow.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/yourls/yourls1_node.png b/docs/_images/integrations/builtin/app-nodes/yourls/yourls1_node.png deleted file mode 100644 index 63362b2a7..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/yourls/yourls1_node.png and /dev/null differ diff --git a/docs/_images/integrations/builtin/app-nodes/yourls/yourls_node.png b/docs/_images/integrations/builtin/app-nodes/yourls/yourls_node.png deleted file mode 100644 index 4b10a65fd..000000000 Binary files a/docs/_images/integrations/builtin/app-nodes/yourls/yourls_node.png and /dev/null differ diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.deepl.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.deepl.md index f27023380..29611335c 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.deepl.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.deepl.md @@ -23,44 +23,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Language * Translate data -## Example Usage - -This workflow allows you to translate cocktail instructions to French. You can also find the [workflow](https://n8n.io/workflows/998) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) -- [DeepL]() - -The final workflow should look like the following image. - -![A workflow with the DeepL node](/_images/integrations/builtin/app-nodes/deepl/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. HTTP Request node (GET) - -This node will make a GET request to the API `https://www.thecocktaildb.com/api/json/v1/1/random.php` to fetch a random cocktail. This information gets passed on to the next node in the workflow. - -1. Enter `https://www.thecocktaildb.com/api/json/v1/1/random.php` in the ***URL*** field. -2. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node makes a GET request to the API and returns information about a random cocktail. - -![Using the HTTP Request node to get the information about a random cocktail](/_images/integrations/builtin/app-nodes/deepl/httprequest_node.png) - -### 3. DeepL node (translate: language) - -This node will translate the cocktail instructions that we got from the previous node to French. To translate the instructions in your language, select your language instead. - -1. First of all, you'll have to enter credentials for the DeepL node. You can find out how to do that [here](/integrations/builtin/credentials/deepl/). - -2. Click on the gears icon next to the ***Text*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Current Nodes > Input Data > JSON > drinks > [item: 0] > strInstructions. You can also add the following expression: `{{$json["drinks"][0]["strInstructions"]}}`. -4. Select 'French' from the ***Target Language*** dropdown list. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node translates the instructions of the cocktail to French. - -![Using the DeepL node to translate the instructions to French](/_images/integrations/builtin/app-nodes/deepl/deepl_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.demio.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.demio.md index a57f0d252..3a3467c15 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.demio.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.demio.md @@ -26,54 +26,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Report * Get an event report -## Example Usage - -This workflow allows you to register your audience to an event on Demio using a Typeform submission. You can also find the [workflow](https://n8n.io/workflows/947) on n8n.io. This example usage workflow uses the following nodes. -- [Typeform Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.typeformtrigger/) -- [Demio]() - -The final workflow should look like the following image. - -![A workflow with the Demio node](/_images/integrations/builtin/app-nodes/demio/workflow.png) - -### 1. Typeform Trigger node - -This node will trigger the workflow when a form response is submitted. - -This example workflow uses a Typeform to collect name and email address. Create a form exactly like [this](https://n8ndocsburner.typeform.com/to/dpr2kxSL) for the example workflow. Below are the questions and their question types for the form. - -|Question | Type | -|---------|-------| -|Let's start with your name. | Short Text | -|What's your email address? | Email | - -1. First of all, you'll have to enter credentials for the Typeform Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/typeform/). -2. Select your form from the ***Form*** dropdown list. -3. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that the Typeform Trigger node triggers the workflow and returns the response submitted by a user. - -![Using the Typeform Trigger node to trigger the workflow](/_images/integrations/builtin/app-nodes/demio/typeformtrigger_node.png) - -### 2. Demio node (register: event) - -This node will use the information from the previous node to register the user for an event on Demio. If you don't have an event on Demio, make sure to create one. - -1. First of all, you'll have to enter credentials for the Demio node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/demio/). -2. Select 'Register' from the ***Operation*** dropdown list. -3. Select the event from the ***Event ID*** dropdown list. -4. Click on the gears icon next to the ***First Name*** field and click on ***Add Expression***. - -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > Let's start with your name. You can also add the following expression: `{{$json["Let's start with your name."]}}`. -6. Click on the gears icon next to the ***Email*** field and click on ***Add Expression***. -7. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > What's your email address? You can also add the following expression: `{{$json["What's your email address?"]}}`. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node registers the user for an event on Demio. - -![Using the Demio node to register a user for an event](/_images/integrations/builtin/app-nodes/demio/demio_node.png) - -/// note | Activate workflow for production -This example workflow uses the Typeform Trigger node. You'll need to save the workflow and then click on the Activate toggle on the top right of the screen to activate the workflow. Your workflow will then be triggered when a new form is submitted. -/// - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.discourse.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.discourse.md index 0a4d94d35..227c5c70c 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.discourse.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.discourse.md @@ -42,61 +42,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Create a user to group * Remove user from group -## Example Usage - -This workflow allows you to create, update, and get a post using the Discourse node. You can also find the [workflow](https://n8n.io/workflows/930) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Discourse]() - -The final workflow should look like the following image. - -![A workflow with the Discourse node](/_images/integrations/builtin/app-nodes/discourse/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Discourse node (create: post) - -This node will create a post under the `Lounge` category. If you want to create a post under a different category, select that category instead. - -1. First of all, you'll have to enter credentials for the Discourse node. You can find out how to do that [here](/integrations/builtin/credentials/discourse/). -2. Enter a title for the post in the ***Title*** field. -3. Enter the content of the post in the ***Content*** field. -4. Click on ***Add Field*** and select 'Category ID' from the dropdown list. -5. Select 'Lounge' from the ***Category ID*** dropdown list. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new topic under the category `Lounge`. - -![Using the Discourse node to create a topic](/_images/integrations/builtin/app-nodes/discourse/discourse_node.png) - -### 3. Discourse1 node (update: post) - -This node will update the content of the post that we created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Update' from the ***Operations*** dropdown list. -3. Click on the gears icon next to the ***Post ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`. -5. Enter the updated content in the ***Content*** field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node updates the content of the post that we created in the previous node. - -![Using the Discourse node to update a post](/_images/integrations/builtin/app-nodes/discourse/discourse1_node.png) - -### 4. Discourse2 node (get: post) - -This node will retrieve the post that we updated previously. - -1. Select the credentials that you entered in the previous node. -2. Select 'Get' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Post ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you notice that the node retrieves the post that we created earlier. - -![Using the Discourse node to get a post](/_images/integrations/builtin/app-nodes/discourse/discourse2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.dropcontact.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.dropcontact.md index 55fbf41be..26753dd16 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.dropcontact.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.dropcontact.md @@ -25,88 +25,4 @@ For usage examples and templates to help you get started, take a look at n8n's [ -## Example Usage - -This workflow allows you to find email and enrich your contact from a Google Sheet and add them to Lemlist. You can also find the [workflow](https://n8n.io/workflows/1304) on n8n.io. - -This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Google Sheets node](/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/) -- [Dropcontact node]() -- [Lemlist node](/integrations/builtin/app-nodes/n8n-nodes-base.lemlist/) - -![A workflow with the GetResponse node](/_images/integrations/builtin/app-nodes/dropcontact/workflow.png) - -### 1. Start Node -The start node exists by default when you create a new workflow. - -### 2. Google Sheet node - -This node will list all the records from Google Sheet. Create a sheet like [this](https://docs.google.com/spreadsheets/d/1jCyGrz01b7wdoujEHHZvw-JD5zszTMFqn8cvvSnLPrE/edit#gid=0) in your Google Drive. - -1. First of all, you'll have to enter credentials for the Google Sheet node. You can find out how to do that [here](/integrations/builtin/credentials/google/). - -2. Select the 'Sheet' option from the ***Ressource*** dropdown list. -3. Select the 'Read' option from the ***Operation*** dropdown list. -4. Enter the Sheet ID in the ***Sheet ID*** field. Your Google Sheet ID is available in the URL `https://docs.google.com/spreadsheets/d/{spreadsheetId}/edit` -5. In the ***Range*** field, enter `A:K`. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns the information of the leads. - -![Using the Google Sheet](/_images/integrations/builtin/app-nodes/dropcontact/googlesheet_node.png) - -### 3. Dropontact node - -This node will find the verified email address and enrich the contact. - -1. First of all, you'll have to enter credentials for the Dropcontact node. You can find out how to do that [here](/integrations/builtin/credentials/dropcontact/). - -2. Select 'Contact' from the ***Resource*** dropdown list. -3. Select 'Enrich' from the ***Operation*** dropdown list. -4. Click on ***Add Field*** and select 'Company Name'. -5. Click on the gears icon next to the ***Company Name*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Node > Input Data > JSON > fields > companyName . You can also add the following expression: `{{$json["fields"]["companyName"]}}`. -7. Click on ***Add Field*** and select 'First Name'. -8. Click on the gears icon next to the ***First Name*** field and click on ***Add Expression***. -9. Select the following in the ***Variable Selector*** section: Node > Input Data > JSON > fields > firstName . You can also add the following expression: `{{$json["fields"]["firstName"]}}`. -10. Click on ***Add Field*** and select 'Full Name'. -11. Click on the gears icon next to the ***Full Name*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Node > Input Data > JSON > fields > fullName . You can also add the following expression: `{{$json["fields"]["fullName"]}}`. -13. Click on ***Add Field*** and select 'Last Name'. -14. Click on the gears icon next to the ***Last Name*** field and click on ***Add Expression***. -15. Select the following in the ***Variable Selector*** section: Node > Input Data > JSON > fields > lastName . You can also add the following expression: `{{$json["fields"]["lastName"]}}`. -16. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Dropcontact node has enriched your data. - -![Using the Dropcontact node](/_images/integrations/builtin/app-nodes/dropcontact/dropcontact_node.png) - -### 4. Lemlist node - -This node will create new leads for a campaign in Lemlist. - -1. First of all, you'll have to enter credentials for the Lemlist node. You can find out how to do that [here](/integrations/builtin/credentials/lemlist/). -2. Select 'Lead' from the ***Resource*** dropdown list. -3. Select a campaign from the ***Campaign ID*** dropdown list. -4. Click on the gears icon next to the ***Email*** field and click on 'Add Expression'. - -5. Select the following in the ***Variable Selector*** section: Dropcontact > Input Data > JSON > fields > email > [Item: 0] > email. You can also add the following expression: `{{$json["email"][0]["email"]}}` -6. Click on the ***Add Field*** button and select 'First Name'. -7. Click on the gears icon next to the ***First Name*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Node > Input Data > JSON > fields > first_name . You can also add the following expression: `{{$json["fields"]["first_name"]}}`. -9. Click on the ***Add Field*** button and select 'Last Name'. -10. Click on the gears icon next to the ***Last Name*** field and click on ***Add Expression***. -11. Select the following in the ***Variable Selector*** section: Node > Input Data > JSON > fields > last_name . You can also add the following expression: `{{$json["fields"]["last_name"]}}`. -12. Click on the ***Add Field*** button and select 'Company Name'. -13. Click on the gears icon next to the ***Company Name*** field and click on ***Add Expression***. -14. Select the following in the ***Variable Selector*** section: Node > Input Data > JSON > fields > company_name . You can also add the following expression: `{{$json["fields"]["company_name"]}}`. -15. Click on the ***Add Field*** button and select 'Deduplicate'. -16. Toggle ***Deduplicate*** to `true`. -17. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates new enriched leads in Lemlist. - -![Using the Lemlist node](/_images/integrations/builtin/app-nodes/dropcontact/lemlist_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.egoi.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.egoi.md index bf4b1f3bd..3c44c9c24 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.egoi.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.egoi.md @@ -26,69 +26,4 @@ For usage examples and templates to help you get started, take a look at n8n's [ - Update a member -## Example Usage - -This workflow allows you to create, update, and get a contact using the E-goi node. You can also find the [workflow](https://n8n.io/workflows/852) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [E-goi]() - -The final workflow should look like the following image. - -![A workflow with the E-goi node](/_images/integrations/builtin/app-nodes/egoi/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. E-goi node (create: contact) - -This node will create a new contact in E-goi. We will add the first name of the contact along with their email. - -1. First of all, you'll have to enter credentials for the E-goi node. You can find out how to do that [here](/integrations/builtin/credentials/egoi/). -2. Select a list from the ***List ID*** field. -3. Enter the email address in the ***Email*** field. -3. Click on the ***Add Field*** button and select 'First Name' from the dropdown list. -4. Enter the name of the contact in the ***First Name*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new contact with their first name and email. - -![Using the E-goi node to create a new contact](/_images/integrations/builtin/app-nodes/egoi/e-goi_node.png) - -### 3. E-goi1 node (update: contact) - -This node will update the information of the contact that we created in the previous node. We will update the first name of the contact using this node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***List ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > E-goi > Parameters > list. You can also add the following expression: `{{$node["E-goi"].parameter["list"]}}`. -5. Click on the gears icon next to the ***Contact ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > E-goi > Output Data > JSON > base > contact_id. You can also add the following expression: `{{$node["E-goi"].json["base"]["contact_id"]}}`. -7. Click on the ***Add Field*** button and select 'First Name' from the dropdown list. -8. Enter the first name of the contact in the ***First Name*** field. -9. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node updates the information of the contact that we created in the previous node. Here, the node has updated the first name of the contact. - -![Using the E-goi node to update the contact](/_images/integrations/builtin/app-nodes/egoi/e-goi1_node.png) - -### 3. E-goi2 node (get: contact) - -This node will return the information of the contact that we created using the E-goi node. - - -1. Select the credentials that you entered in the previous node. -2. Select 'Get' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***List ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > E-goi1 > Parameters > list. You can also add the following expression: `{{$node["E-goi1"].parameter["list"]}}`. -5. Click on the gears icon next to the ***Contact ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > E-goi1 > Output Data > JSON > base > contact_id. You can also add the following expression: `{{$node["E-goi"].json["base"]["contact_id"]}}`. -5. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns the information of the contact that we created using the E-goi node. - -![Using the E-goi node to get the information of the contact](/_images/integrations/builtin/app-nodes/egoi/e-goi2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.emelia.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.emelia.md index 51ab0d4db..a2f2c169e 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.emelia.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.emelia.md @@ -30,61 +30,5 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Add * Get All -## Example Usage - -This workflow allows you to create a campaign, add a contact, and get the campaign from Emelia. You can also find the [workflow](https://n8n.io/workflows/961) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Emelia]() - -The final workflow should look like the following image. - -![A workflow with the Emelia node](/_images/integrations/builtin/app-nodes/emelia/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Emelia node (campaign: create) - -This node will create a new campaign in Emelia. - -1. First of all, you'll have to enter credentials for the Emelia node. You can find out how to do that [here](/integrations/builtin/credentials/emelia/). -2. Select 'Create' from the ***Operation*** dropdown list. -3. Enter the campaign name in the ***Campaign Name*** field. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new campaign. - -![Using the Emelia node to create a new campaign](/_images/integrations/builtin/app-nodes/emelia/emelia_node.png) - -### 3. Emelia1 node (campaign: addContact) - -This node will add a contact to the campaign that we created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Add Contact' from the ***Operation*** dropdown list. -3. Select the campaign from the ***Campaign ID*** dropdown list. -4. Enter the contact's email address in the ***Contact Email*** field. -5. Click on the ***Add Field*** button and select 'First Name'. -6. Enter the first name in the ***First Name*** field. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node adds the contact to the campaign that we created in the previous node. - -![Using the Emelia node to add a contact to a campaign](/_images/integrations/builtin/app-nodes/emelia/emelia1_node.png) - -### 4. Emelia2 node (campaign: get) - -This node will get the information about the campaign that we created earlier. - -1. Select the credentials that you entered in the previous node. -2. Select 'Get' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Campaign ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > Emelia > Output Data > JSON > _id. You can also add the following expression: `{{$node["Emelia"].json["_id"]}}`. -6. Click on ***Execute Node*** to run the node. -In the screenshot below, you will notice that the node returns the information of the campaign. - -![Using the Emelia node to return the information a campaign](/_images/integrations/builtin/app-nodes/emelia/emelia2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.erpnext.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.erpnext.md index c0e7a1405..fbf072de0 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.erpnext.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.erpnext.md @@ -27,73 +27,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ - Update a document -## Example Usage - -This workflow allows you to create, update, and retrieve a document from ERPNext. You can also find the [workflow](https://n8n.io/workflows/961) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [ERPNext]() - -The final workflow should look like the following image. - -![A workflow with the ERPNext node](/_images/integrations/builtin/app-nodes/erpnext/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. ERPNext node (document: create) - -This node will create a new document in ERPNext. - -1. First of all, you'll have to enter credentials for the ERPNext node. You can find out how to do that [here](/integrations/builtin/credentials/erpnext/). -2. Select 'Item' from the ***DocType*** dropdown list. -3. Click on the ***Add Property*** button. -4. Select 'Item Name' from the ***Field*** dropdown list. -5. Enter `item 1` in the ***Value*** field. -6. Click on the ***Add Property*** button. -7. Select 'Item Code' from the ***Field*** dropdown list. -8. Enter `item-1` in the ***Value*** field. -9. Click on the ***Add Property*** button. -10. Select 'Item Group' from the ***Field*** dropdown list. -11. Enter `Products` in the ***Value*** field. -**Note:** Make sure that the item group exists in your ERPNext account. -12. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new item with the name `item 1`. - -![Using the ERPNext node to create a new item](/_images/integrations/builtin/app-nodes/erpnext/erpnext_node.png) - -### 3. ERPNext1 node (document: addContact) - -This node will add the `Item Tax` property to the item that we created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Select 'Item' from the ***DocType*** dropdown list. -4. Click on the gears icon next to the ***Item Name*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > name. You can also add the following expression: `{{$json["name"]}}`. -6. Click on the ***Add Property*** button. -7. Select 'Item Tax' from the ***Field*** dropdown list. -8. Enter `5` in the ***Value*** field. -10. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node adds the Item Tax property to the item that we created in the previous node. - -![Using the ERPNext node to update an item](/_images/integrations/builtin/app-nodes/erpnext/erpnext1_node.png) - -### 4. ERPNext2 node (document: get) - -This node will get the information about the item that we created earlier. - -1. Select the credentials that you entered in the previous node. -2. Select 'Get' from the ***Operation*** dropdown list. -3. Select 'Item' from the ***DocType*** dropdown list. -4. Click on the gears icon next to the ***Item Name*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > name. You can also add the following expression: `{{$json["name"]}}`. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns the information of the item. - -![Using the ERPNext node to return the information an item](/_images/integrations/builtin/app-nodes/erpnext/erpnext2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.filemaker.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.filemaker.md index 782ea0b97..3f6365db1 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.filemaker.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.filemaker.md @@ -28,72 +28,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ - Duplicate Record - Delete Record -## Example Usage - -This workflow allows you to create, update, and retrieve a record from FileMaker. You can also find the [workflow](https://n8n.io/workflows/1068) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [FileMaker]() - -The final workflow should look like the following image. - -![A workflow with the FileMaker node](/_images/integrations/builtin/app-nodes/filemaker/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. FileMaker node - -This node will create a new record in FileMaker. - -1. First of all, you'll have to enter credentials for the FileMaker node. You can find out how to do that [here](/integrations/builtin/credentials/filemaker/). -2. Select 'Create Record' from the ***Action*** dropdown list. -3. Select a layout from the ***Layout*** dropdown list. -4. Click on the ***Add Field*** button. -5. Select a field from the ***Field*** dropdown list. -6. Enter a value in the ***Value*** field. -7. Click on the ***Add field*** button. -8. Select a field from the ***Field*** dropdown list. -9. Enter a value in the ***Value*** field. -10. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new record in FileMaker. - -![Using the FileMaker node to create a new record](/_images/integrations/builtin/app-nodes/filemaker/filemaker_node.png) - -### 3. FileMaker1 node - -This node will add a new field to the record that we created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Edit Record' from the ***Action*** dropdown list. -3. Select a layout from the ***Layout*** dropdown list. -4. Click on the gears icon next to the ***Record Id*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > response > recordId. You can also add the following expression: `{{$json["response"]["recordId"]}}`. -6. Click on the gears icon next to the ***Mod Id*** field and click on ***Add Expression***. -7. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > response > modId. You can also add the following expression: `{{$json["response"]["modId"]}}`. -8. Click on the ***Add field*** button. -9. Select a field from the ***Field*** dropdown list. -10. Enter a value in the ***Value*** field. -11. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node adds the `address_country` field to the record that we created in the previous node. - -![Using the FileMaker node to update a record](/_images/integrations/builtin/app-nodes/filemaker/filemaker1_node.png) - -### 4. FileMaker2 node - -This node will get the information about the record that we created earlier. - -1. Select the credentials that you entered in the previous node. -2. Select 'Get Records by Id' from the ***Action*** dropdown list. -3. Select a layout from the ***Layout*** dropdown list. -4. Click on the gears icon next to the ***Record Id*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > FileMaker > Output Data > JSON > response > recordId. You can also add the following expression: `{{$node["FileMaker"].json["response"]["recordId"]}}`. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns the information of the record. - -![Using the FileMaker node to return the information a record](/_images/integrations/builtin/app-nodes/filemaker/filemaker2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.getresponse.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.getresponse.md index c8d0e9f50..8c03ee771 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.getresponse.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.getresponse.md @@ -27,73 +27,4 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get all contacts * Update contact properties -## Example Usage - -This workflow allows you to get all the contacts from GetResponse and check if they belong to a specific campaign. If they don't belong to the specified campaign, the workflow updates the campaign ID of the contacts using the GetResponse node. You can also find the [workflow](https://n8n.io/workflows/778) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [GetResponse]() -- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/) -- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noop/) - -The final workflow should look like the following image. - -![A workflow with the GetResponse node](/_images/integrations/builtin/app-nodes/getresponse/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. GetResponse node (getAll: contact) - -This node will retrieve all the contacts from GetResponse. - -1. First of all, you'll have to enter credentials for the GetResponse node. You can find out how to do that [here](/integrations/builtin/credentials/getresponse/). -2. Select 'GetAll' from the ***Operation*** dropdown list. -3. Toggle ***Return All*** to true. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node retrieves all the contacts from GetResponse. - -![Using the GetResponse node to retrieve all the contacts](/_images/integrations/builtin/app-nodes/getresponse/getresponse_node.png) - -### 3. IF node - -This node will check if a contact belongs to the `n8n` campaign or not. If a contact doesn'tbelong to the `n8n` campaign, it will return true otherwise false. Create a campaign in GetResponse if you don't already have one. - -1. Click on ***Add Condition*** and select 'String'. -2. Click on the gears icon next to the ***Value 1*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Nodes > GetResponse > Output Data > JSON > campaign > name. You can also add the following expression: `{{$node["GetResponse"].json["campaign"]["name"]}}`. -4. Select 'Not Equal' from the ***Operation*** dropdown list. -5. Enter `n8n` in the ***Value 2*** field. If you have a campaign with a different name, use that name instead. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns all the contacts that do not belong to the `n8n` campaign. - -![Using the IF node to check if a contact belongs to the n8n campaign or not](/_images/integrations/builtin/app-nodes/getresponse/if_node.png) - -### 4. GetResponse1 node (update: contact) - -This node will update the campaign ID of all the contacts that we get from the true branch of the previous node. - -1. Create a GetResponse node connected to the 'true' output of the IF node. -2. Select the credentials that you entered in the previous GetResponse node. -3. Select 'Update' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Contact ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > IF > Output Data > JSON > contactId. You can also add the following expression: `{{$node["IF"].json["contactId"]}}`. -6. Click on ***Add Field*** and select 'Campaign ID' from the dropdown list. -7. Select `n8n` from the ***Campaign ID*** dropdown list. If you have a campaign with a different name, select that instead. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you notice that the node updates the campaign ID of all the contacts that do not belong to the `n8n` campaign. - -![Using the GetResponse node to update the campaign of the contacts](/_images/integrations/builtin/app-nodes/getresponse/getresponse1_node.png) - -### 5. NoOp node - -Adding this node here is optional, as the absence of this node won't make a difference to the functioning of the workflow. - -1. Create a ***NoOp*** node connected to the 'false' output of the IF node. -2. Click on ***Execute Node*** to run the node. - -![Using the NoOp node](/_images/integrations/builtin/app-nodes/getresponse/noop_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.ghost.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.ghost.md index f0544f740..6440f2ddb 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.ghost.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.ghost.md @@ -36,66 +36,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ - Get all posts -## Example Usage - -This workflow allows you to create, update, and get a post in Ghost. You can also find the [workflow](https://n8n.io/workflows/825) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Ghost]() - -The final workflow should look like the following image. - -![A workflow with the Ghost node](/_images/integrations/builtin/app-nodes/ghost/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Ghost node (create: post) - -This node will create a new post with the title `Running ghost with n8n!`. If you want to create a post with a different title, use that instead. - -1. Select 'Admin API' from the ***Source*** dropdown list. -2. You'll have to enter credentials for the Ghost node. You can find out how to do that [here](/integrations/builtin/credentials/ghost/). -3. Select 'Create' from the ***Operation*** dropdown list. -4. Enter `Running ghost with n8n!` in the ***Title*** field. -5. Enter the HTML content in the ***Content*** field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new post. - -![Using the Ghost node to create a new post and publish it](/_images/integrations/builtin/app-nodes/ghost/ghost_node.png) - -### 3. Ghost1 node (update: post) - -This node will update the status of the post that we created in the previous node. We will change the status of the post to `Published`. - -1. Select 'Admin API' from the ***Source*** dropdown list. -2. Select the credentials that you entered in the previous node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Post ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Ghost > Output Data > JSON > id. You can also add the following expression: `{{$node["Ghost"].json["id"]}}`. -5. Click on ***Add Field*** and select 'Status'. -6. Select 'Published' from the ***Status*** dropdown list. -7. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node updates the status of the post that we created in the previous node. - -![Using the Ghost node to update the status of a post](/_images/integrations/builtin/app-nodes/ghost/ghost1_node.png) - -### 4. Ghost2 node (get: post) - -This node returns information about the post that we created using the Ghost node. In this node, we are using the ***Admin API***. You can also use the ***Content API*** to get the information about the post. - -1. Select 'Admin API' from the ***Source*** dropdown list. -2. Select the credentials that you entered in the previous node. -3. Select 'ID' from the ***By*** dropdown list. -4. Click on the gears icon next to the ***Identifier*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > Ghost > Output Data > JSON > id. You can also add the following expression: `{{$node["Ghost"].json["id"]}}`. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns information about the post that we specified. - -![Using the Ghost node to get information of a post](/_images/integrations/builtin/app-nodes/ghost/ghost2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.github.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.github.md index bf0070d56..c56c0a32d 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.github.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.github.md @@ -37,7 +37,7 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Returns issues of a repository. * Get the community profile of a repository with metrics, health score, description, license, etc. * Get the top 10 popular content paths over the last 14 days. - * Get the top 10 referrering domains over the last 14 days. + * Get the top 10 referring domains over the last 14 days. * Release * Creates a new release. * Get a release. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googlebooks.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googlebooks.md index 59e9daf74..00305d146 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googlebooks.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googlebooks.md @@ -33,64 +33,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get a volume resource based on ID * Get all volumes filtered by query -## Example Usage - -This workflow allows you to get a volume and add it to your bookshelf using the Google Books node. You can also find the [workflow](https://n8n.io/workflows/771) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Google Books]() - -The final workflow should look like the following image. - -![A workflow with the Google Books node](/_images/integrations/builtin/app-nodes/googlebooks/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Google Books node (get: volume) - -This node will retrieve a volume from Google Books. - -1. Select 'OAuth2' from the ***Authentication*** dropdown list. -2. Enter credentials for the Google Books node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/google/). -3. Enter the ID of a volume in the ***Volume ID*** field. -4. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will observe that the node retrieves the information of the volume that we specify. - -![Using the Google Books node to retrieve information of a volume](/_images/integrations/builtin/app-nodes/googlebooks/googlebooks_node.png) - -### 3. Google Books1 node (add: bookshelfVolume) - -This node will add the volume that we got from the previous node to a bookshelf in Google Books. - -1. Select 'OAuth2' in the ***Authentication*** field. -2. Select the credentials that you entered in the previous Google Books node. -3. Select 'Bookshelf Volume' from the ***Resource*** dropdown list. -4. Select 'Add' from the ***Operation*** dropdown list. -5. Enter a bookshelf id in the ***ID*** field. -6. Click on the gears icon next to the ***Volume ID*** field and click on ***Add Expression***. -7. Select the following in the ***Variable Selector*** section: Nodes > Google Books > Output Data > JSON > id. You can also add the following expression: `{{$node["Google Books"].json["id"]}}`. -8. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that this node adds the volume that we got from the previous node to a bookshelf that we specified. - -![Using the Google Books node to add a volume to a bookshelf volume](/_images/integrations/builtin/app-nodes/googlebooks/googlebooks1_node.png) - -### 4. Google Books2 node (getAll: bookshelfVolume) - -This node will return all the volumes in a bookshelf. - -1. Select 'OAuth2' in the ***Authentication*** field. -2. Select the credentials that you entered in the previous Google Books node. -3. Select 'Bookshelf Volume' from the ***Resource*** dropdown list. -4. Select 'Get All' from the ***Operation*** dropdown list. -5. Toggle ***My Library*** to true. This will return the information for your account. -6. Click on the gears icon next to the ***Bookshelf ID*** field and click on ***Add Expression***. -7. Select the following in the ***Variable Selector*** section: Nodes > Google Books1 > Parameters > shelfId. You can also add the following expression: `{{$node["Google Books1"].parameter["shelfId"]}}`. -8. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that this node returns all the volumes in the bookshelf that we specified. - -![Using the Google Books node to get all the volumes in a bookshelf](/_images/integrations/builtin/app-nodes/googlebooks/googlebooks2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googlecontacts.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googlecontacts.md index edfd493d4..4a0312167 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googlecontacts.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googlecontacts.md @@ -26,62 +26,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get a contact * Retrieve all contacts * Update a contact - -## Example Usage - -This workflow allows you to create, update, and get a contact from Google Contacts. You can also find the [workflow](https://n8n.io/workflows/637) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Google Contacts]() - -The final workflow should look like the following image. - -![A workflow with the Google Contacts node](/_images/integrations/builtin/app-nodes/googlecontacts/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. Google Contacts node (create: contact) - -1. First of all, you'll have to enter credentials for the Google Contacts node. You can find out how to do that [here](/integrations/builtin/credentials/google/). -2. Enter the family name in the ***Family Name*** field. -3. Enter the given name in the ***Given Name*** field. -4. Click on ***Execute Node*** to run the node. - -![Using the Google Contacts node to create a contact](/_images/integrations/builtin/app-nodes/googlecontacts/googlecontacts_node.png) - - - -### 3. Google Contacts1 node (update: contact) - -1. Select the credentials that you entered in the previous node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Contact ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Google Contacts > Output Data > JSON > contactId. You can also add the following expression: `{{$node["Google Contacts"].json["contactId"]}}`. -5. Select `*` from the ***Fields*** dropdown list. -6. Click on the ***Add Field*** button and select ***Company***. -7. Click on the ***Add Company*** button. -8. Toggle the value to true for the ***Current*** field. -9. Enter the company's domain in the ***Domain*** field. -10. Enter the company's name in the ***Name*** field. -11. Enter the title in the ***Title*** field. -12. Click on ***Execute Node*** to run the node. - - -![Using the Google Contact node to update the contact](/_images/integrations/builtin/app-nodes/googlecontacts/googlecontacts1_node.png) - - - -### 4. Google Contacts2 node (get: contact) - -1. Select the credentials that you entered in the previous node. -2. Select 'Get' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Contact ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Google Contacts > Output Data > JSON > contactId. You can also add the following expression: `{{$node["Google Contacts"].json["contactId"]}}`. -5. Select 'Organizations' from the ***Fields*** dropdown list. -6. Click on ***Execute Node*** to run the node. - - -![Using the Google Contacts node to get the contact](/_images/integrations/builtin/app-nodes/googlecontacts/googlecontacts2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googledocs.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googledocs.md index 1ff210293..86e82ad0f 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googledocs.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googledocs.md @@ -24,44 +24,3 @@ Fo usage examples and templates to help you get started, take a look at n8n's [G * Get * Update -## Example usage - -This workflow allows you to create a new Google Doc and add your desired text to it. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Google Docs]() - -The final workflow should look like the following image. - -![A workflow with the Google Docs node](/_images/integrations/builtin/app-nodes/googledocs/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Google Docs node: create - -The **Document** resource is selected by default. Configure the remaining parameters as follows: - -1. From the **Authentication** dropdown select your desired method and the corresponding [**Credentials**](/integrations/builtin/credentials/google/). -2. From the **Operation** dropdown select **Create**. -3. From the **Drive** dropdown select which of your drives this file will be created in. My Drive is selected by default. -4. From the **Folder** dropdown select which of you drive folders this file will be created in. The root folder (`/`) is selected by default. -5. In the **Title** field enter the name of your new Google Doc. - -![Creating a file with the Google Docs node](/_images/integrations/builtin/app-nodes/googledocs/googledocs_node.png) - -### 3. Google Docs node: update - -The **Document** resource is selected by default. Configure the remaining parameters as follows: - -1. From the **Operation** dropdown select **Update**. -2. In the **Doc ID or URL** field, enter the document ID or URL of the file created by the previous node. -3. From **Actions**, configure the fields as follows: - - **Object:** Select the object of the action. Here we use 'Text'. - - **Action:** Select the action to be performed on the object. Here we use 'Insert'. - - **Insert Segment:** Select where in the document the action should be performed. Here we use 'Body'. - - **Insert Location:** Select the location within the selected Segment. Here we use 'At end of specific location'. - - **Text:** Enter the text to be inserted. - -![Updating text in a file with the Google Docs node](/_images/integrations/builtin/app-nodes/googledocs/googledocs1_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googledrive.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googledrive.md index 3e20ef951..7dfa6375e 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googledrive.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googledrive.md @@ -38,44 +38,6 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Delete a folder * Share a folder -## Example Usage - -This workflow allows you to download a file from Google Drive. You can also find the [workflow](https://n8n.io/workflows/515) on the website. This example usage workflow uses the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Google Drive]() -- [Write Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.writebinaryfile/) - -The final workflow should look like the following image. - -![A workflow with the Google Drive node](/_images/integrations/builtin/app-nodes/googledrive/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Google Sheets node - -1. First of all, you'll have to enter credentials for the Google Drive node. You can find out how to do that [here](/integrations/builtin/credentials/google/), in the section 'Google Drive / Sheets API'. -2. Select the authentication method you plan to use from the *Authentication* dropdown list. -3. Select 'Download' from the *Operation* dropdown list. -4. Copy the string of characters located between `/d/` and `/edit` in your Google Drive URL. Paste that string in the *File ID* field. - -### 3. Write Binary File node - -1. Enter the destination file path in the *File Name* field. -2. Click on *Execute Node* to run the workflow. - -## FAQs - -### How do I list all files/folders within a folder? - -To list all the files and folders within a folder, follow the steps mentioned below. - -1. Toggle ***Use Query String*** to `true`. -2. Copy the string of characters located after `https://drive.google.com/drive/u/0/folders/`. This string is the folder ID. -3. Enter `'FOLDER_ID' in parents` in the ***Query String*** field. Replace `FOLDER_ID` with the folder ID you copied in the previous step. - -There are several additional options available to fine grain the listed results. Refer to [Search for files and folders: Querystring](https://developers.google.com/drive/api/v3/search-files#query_string_examples) for more information. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleslides.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleslides.md index b89cbbea7..00f04d7aa 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleslides.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleslides.md @@ -29,58 +29,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get presentation slides * Replace text in a presentation -## Example Usage - -This workflow allows you to get all the slides from a presentation and get the thumbnails for the pages. You can also find the [workflow](https://n8n.io/workflows/1035) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Google Slides]() - -The final workflow should look like the following image. - -![A workflow with the Google Slides node](/_images/integrations/builtin/app-nodes/googleslides/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Google Slides node (getSlides: presentation) - -#### Get Presentation ID - -1. Open a Google Slides presentation. -2. Copy the string of characters located between `/d/` and `/edit` in your presentation URL. This string is the Presentation ID, which we will use in the Google Slides node. - -#### Configure the Google Slides node - -This Google Slides node will get all the slides from a presentation. - -1. Select 'OAuth2' from the ***Authentication*** dropdown list. -2. First of all, you'll have to enter credentials for the Google Slides node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/google/). -3. Select 'Get Slides' from the ***Operation*** dropdown list. -4. Paste the Presentation ID you copied in the previous step, in the ***Presentation ID*** field. -5. Toggle ***Return All*** to `true`. -6. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that the node returns all the slides from the presentation. - -![Using the Google Slides node to get slides from a presentation](/_images/integrations/builtin/app-nodes/googleslides/googleslides_node.png) - -### 3. Google Slides1 node (getThumbnail: page) - -This node will return thumbnails of the pages that were returned by the previous node. - -1. Select 'OAuth2' from the ***Authentication*** dropdown list. -2. Select the credentials that you entered in the previous Google Slides node. -3. Select 'Page' from the ***Resource*** dropdown list. -4. Select 'Get Thumbnail' from the ***Operation*** dropdown list. -5. Click on the gears icon next to the ***Presentation ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Google Slides > Parameters > presentationId. You can also add the following expression: `{{$node["Google Slides"].parameter["presentationId"]}}`. -7. Click on the gears icon next to the ***Page Object ID*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > Google Slides > Output Data > JSON > objectId. You can also add the following expression: `{{$json["objectId"]}}`. -9. Toggle ***Download*** to `true`. -10. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that the node returns thumbnails of the pages that were returned by the previous node. - -![Using the Google Slides node to get thumbnails of the slides](/_images/integrations/builtin/app-nodes/googleslides/googleslides1_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googletasks.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googletasks.md index bec1938a9..eac8e7235 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googletasks.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googletasks.md @@ -20,10 +20,10 @@ For usage examples and templates to help you get started, take a look at n8n's [ ## Basic Operations * Task - * Add a task to tasklist + * Add a task to task list * Delete a task * Retrieve a task - * Retrieve all tasks from a tasklist + * Retrieve all tasks from a task list * Update a task ## Example Usage diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.gotowebinar.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.gotowebinar.md index fd8d81d03..bda8eea14 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.gotowebinar.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.gotowebinar.md @@ -27,12 +27,12 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Create * Delete * Get All - * Reinvite + * Re-invite * Panelist * Create * Delete * Get All - * Reinvite + * Re-invite * Registrant * Create * Delete diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.halopsa.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.halopsa.md index 59fa43104..443e9b01e 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.halopsa.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.halopsa.md @@ -44,29 +44,4 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get all users * Update a user -## Example Usage - -This workflow allows you to create a client in HaloPSA. This example workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [HaloPSA]() - -![A workflow with the Harvest node](/_images/integrations/builtin/app-nodes/halopsa/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. HaloPSA node (resource: client) - -This node will create a new client in HaloPSA. - -1. First of all, you'll have to enter credentials for the HaloPSA node. You can find out how to do that [here](/integrations/builtin/credentials/halopsa/). -2. Select 'Client' in the ***Resource*** field. -3. Select 'Create' in the ***Operation*** field. -4. Enter the client name in the ***Name*** field. -5. Add additional fields such as ***VIP*** or ***Website*** by clicking ***Add Field***. - -In the below screenshot you can see how the node creates a new client in HaloPSA. - -![Using the HaloPSA node to create a client](/_images/integrations/builtin/app-nodes/halopsa/halopsa-client-create.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.homeassistant.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.homeassistant.md index a98325e10..975e3de3d 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.homeassistant.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.homeassistant.md @@ -6,7 +6,7 @@ contentType: integration # Home Assistant -Use the Home Assistant node to automate work in Home Assistant, and integrate Home Assistant with other applications. n8n has built-in support for a wide range of Home Assistant features, including getting, creating, and checking camera proxies, configs, logs, services, and templates. +Use the Home Assistant node to automate work in Home Assistant, and integrate Home Assistant with other applications. n8n has built-in support for a wide range of Home Assistant features, including getting, creating, and checking camera proxies, configurations, logs, services, and templates. On this page, you'll find a list of operations the Home Assistant node supports and links to more resources. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.iterable.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.iterable.md index 209d06579..5ca15c156 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.iterable.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.iterable.md @@ -29,67 +29,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Add user to list * Remove a user from a list -## Example Usage - -This workflow allows you to create, update, and get a user from Iterable. You can also find the [workflow](https://n8n.io/workflows/813) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Iterable]() - -The final workflow should look like the following image. - -![A workflow with the Iterable node](/_images/integrations/builtin/app-nodes/iterable/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. Iterable node (upsert: user) - -This node will create a new user in Iterable. - -1. First of all, you'll have to enter credentials for the Iterable node. You can find out how to do that [here](/integrations/builtin/credentials/iterable/). -2. Select 'Email' in the ***Identifier*** field. -3. Enter the email address in the ***Value*** field. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new user in Iterable. - -![Using the Iterable node to create a user](/_images/integrations/builtin/app-nodes/iterable/iterable_node.png) - -### 3. Iterable1 node (upsert: user) - -This node will update the information of the user that we created in the previous node. - - -1. Select the credentials that you entered in the previous node. -2. Select 'Email' in the ***Identifier*** field. -3. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Iterable > Parameters > value. You can also add the following expression: `{{$node["Iterable"].parameter["value"]}}`. -5. Click on the ***Add Field*** button and select ***Data Fields***. -6. Click on the ***Add Data Field*** button. -7. Enter `Name` in the ***Key*** field. -8. Enter the name of the user in the ***Value*** field. -9. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node updates the information of the user that we created in the previous node. - -![Using the Iterable node to update the user information](/_images/integrations/builtin/app-nodes/iterable/iterable1_node.png) - - - -### 4. Iterable2 node (get: user) - -This node will get the information of the user that we created using the Iterable node. - - -1. Select the credentials that you entered in the previous node. -2. Select 'Get' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Iterable > Parameters > value. You can also add the following expression: `{{$node["Iterable"].parameter["value"]}}`. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node gets the information of the user that we created using the Iterable node. - -![Using the Iterable node to get the user's information](/_images/integrations/builtin/app-nodes/iterable/iterable2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.jenkins.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.jenkins.md index 1701d0cc6..89ae0349d 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.jenkins.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.jenkins.md @@ -34,25 +34,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Trigger a specific job * Trigger a specific job -## Example Usage - -This workflow allows you to get list of builds in Jenkins. You can also find the [workflow](https://n8n.io/workflows/454) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Jenkins]() - -The final workflow should look like the following image. - -![A workflow with the CircleCI node](/_images/integrations/builtin/app-nodes/jenkins/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. CircleCI node - -1. First of all, you'll have to enter credentials for the Jenkins node. You can find out how to do that [here](/integrations/builtin/credentials/jenkins/). -2. Select the *Build* from the dropdown in the *Resources* field. -3. *Get All Builds* isn't selected in *Operations* dropdown. -4. Adjust the *depth* or add optional parameter by clickin *Add Field* button -5. Click on *Execute Node* to run the workflow. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.kitemaker.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.kitemaker.md index dc3b4a40a..02780b23a 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.kitemaker.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.kitemaker.md @@ -31,63 +31,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get All * Update -## Example Usage - -This workflow allows you to create, update, and get a work item from Kitemaker. You can also find the [workflow](https://n8n.io/workflows/1048) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Kitemaker]() - -The final workflow should look like the following image. - -![A workflow with the Kitemaker node](/_images/integrations/builtin/app-nodes/kitemaker/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Kitemaker node (workItem: create) - -This node will create a work item in Kitemaker. - -1. First of all, you'll have to enter credentials for the Kitemaker node. You can find out how to do that [here](/integrations/builtin/credentials/kitemaker/). -2. Select 'Create' from the ***Operation*** dropdown list. -3. Enter a title in the ***Title*** field. -4. Select 'In progress' from the ***Status ID*** dropdown list. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new work item in Kitemaker. - -![Using the Kitemaker node to create a new work item](/_images/integrations/builtin/app-nodes/kitemaker/kitemaker_node.png) - - -### 3. Kitemaker1 node (workItem: update) - -This node will update the status of the item that we created using the previous node. - -1. Select the credentials that you entered in the previous Kitemaker node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Work Item ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`. -5. Click on the ***Add Field*** button and select 'Status ID' from the dropdown list. -6. Select 'Done' from the ***Status ID*** dropdown list. -7. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node updates the status of the item that got created previously. - -![Using the Kitemaker node to update a work item](/_images/integrations/builtin/app-nodes/kitemaker/kitemaker1_node.png) - -### 4. Kitemaker2 node (workItem: get) - -This node will retrieve the information about the item that we created earlier. - - -1. Select the credentials that you entered in the previous Kitemaker node. -2. Click on the gears icon next to the ***Work Item ID*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node retrieves the information of the work item that we created earlier. - -![Using the Kitemaker node to retrieve the information of a work item](/_images/integrations/builtin/app-nodes/kitemaker/kitemaker2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.lemlist.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.lemlist.md index 39372b9a8..b9d159d05 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.lemlist.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.lemlist.md @@ -35,67 +35,4 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Delete * Get All -## Example Usage - -This workflow allows you to list emails from Airtable and create corresponding leads in Lemlist. You can also find the [workflow](https://n8n.io/workflows/983) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Airtable]/integrations/builtin/app-nodes/n8n-nodes-base.airtable/) -- [Lemlist]() - -The final workflow should look like the following image. - -![A workflow with the Lemlist node](/_images/integrations/builtin/app-nodes/lemlist/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Airtable node (List) - -This node will list all the records from Airtable. Create a table like [this](https://airtable.com/shruiCc4kttDVsTsD) in your Airtable base. - -1. First of all, you'll have to enter credentials for the Airtable node. You can find out how to do that [here](/integrations/builtin/credentials/airtable/). -2. Select the 'List' option from the ***Operation*** dropdown list. -3. Enter the Base ID in the ***Base ID*** field. For obtaining the Base ID, head over to their [API page](https://airtable.com/api) and select the correct base. You'll find the Base ID there. -4. Enter the name of your table in the ***Table*** field. -5. Click on the gears icon next to the ***Table*** field and click on ***Add Expression***. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the information of the leads. - -![Using the Airtable node to list data from an Airtable table](/_images/integrations/builtin/app-nodes/lemlist/airtable_node.png) - -### 3. Lemlist node (create: lead) - -This node will create new leads for a campaign in Lemlist. - -1. First of all, you'll have to enter credentials for the Lemlist node. You can find out how to do that [here](/integrations/builtin/credentials/lemlist/). -2. Select 'Lead' from the ***Resource*** dropdown list. -3. Select a campaign from the ***Campaign ID*** dropdown list. -4. Click on the gears icon next to the ***Email*** field and click on ***Add Expression***. - -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > fields > Email. You can also add the following expression: `{{$json["fields"]["Email"]}}`. -6. Click on the ***Add Field*** button and select 'First Name'. -7. Click on the gears icon next to the ***First Name*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > fields > Name. You can also add the following expression: `{{$json["fields"]["Name"]}}`. -9. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates new leads in Lemlist. - -![Using the Lemlist node to create a new lead](/_images/integrations/builtin/app-nodes/lemlist/lemlist_node.png) - -### 4. Lemlist node (get: lead) - -This node will return the information of the leads that we created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Lead' from the ***Resource*** dropdown list. -3. Select 'Get' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Email*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > Airtable > Output Data > JSON > fields > Email. You can also add the following expression: `{{$node["Airtable"].json["fields"]["Email"]}}`. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the information about the leads we created in the previous node. - -![Using the Lemlist node to get information about the leads](/_images/integrations/builtin/app-nodes/lemlist/lemlist1_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.lingvanex.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.lingvanex.md index 457dead44..63aeb453c 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.lingvanex.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.lingvanex.md @@ -21,48 +21,5 @@ For usage examples and templates to help you get started, take a look at n8n's [ - Translate data -## Example Usage - -This workflow allows you to translate cocktail instructions to Italian. You can also find the [workflow](https://n8n.io/workflows/797) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) -- [LingvaNex]() - -The final workflow should look like the following image. - -![A workflow with the LingvaNex node](/_images/integrations/builtin/app-nodes/lingvanex/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. HTTP Request node (GET) - -This node will make a GET request to the API `https://www.thecocktaildb.com/api/json/v1/1/random.php` to fetch a random cocktail. This information gets passed on to the next node in the workflow. - -1. Enter `https://www.thecocktaildb.com/api/json/v1/1/random.php` in the ***URL*** field. -2. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node makes a GET request to the API and returns information about a random cocktail. - -![Using the HTTP Request node to get the information about a random cocktail](/_images/integrations/builtin/app-nodes/lingvanex/httprequest_node.png) - -### 3. LingvaNex node - -This node will translate the cocktail instructions that we got from the previous node to Italian. To translate the instructions in your language, select your language instead. - -1. First of all, you'll have to enter credentials for the LingvaNex node. You can find out how to do that [here](/integrations/builtin/credentials/lingvanex/). - -2. Click on the gears icon next to the ***Text*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > drinks > [item: 0] > strInstructions. You can also add the following expression: `{{$node["HTTP Request"].json["drinks"][0]["strInstructions"]}}`. -4. Select 'Italian' from the ***Translate To*** dropdown list. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node translates the instructions of the cocktail to Italian. - -![Using the LingvaNex node to translate the instructions to Italian](/_images/integrations/builtin/app-nodes/lingvanex/lingvanex_node.png) - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.magento2.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.magento2.md index 589598dc0..e666bf216 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.magento2.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.magento2.md @@ -36,6 +36,6 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Create a product * Delete a product * Get a product - * Get all producs + * Get all products * Update a product diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailerlite.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailerlite.md index 9ff7ca028..fffd0b120 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailerlite.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailerlite.md @@ -25,68 +25,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get all subscribers * Update an subscriber -## Example Usage - -This workflow allows you to create, update, and get a subscriber using the MailerLite node. You can also find the [workflow](https://n8n.io/workflows/751) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [MailerLite]() - -The final workflow should look like the following image. - -![A workflow with the MailerLite node](/_images/integrations/builtin/app-nodes/mailerlite/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. MailerLite node (create: subscriber) - -This node will create a new subscriber in MailerLite. We will add the name of the subscriber along with their email. - -1. First of all, you'll have to enter credentials for the MailerLite node. You can find out how to do that [here](/integrations/builtin/credentials/mailerlite/). - -2. Enter the email address in the ***Email*** field. -3. Click on the ***Add Field*** button and select 'Name' from the dropdown list. -4. Enter the name of the subscriber in the ***Name*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new subscriber with their name and email. - -![Using the MailerLite node to create a room](/_images/integrations/builtin/app-nodes/mailerlite/mailerlite_node.png) - -### 3. MailerLite1 node (update: subscriber) - -This node will update the information of the subscriber that we created in the previous node. We will add the information about the city of the subscriber using this node. - - -1. Select the credentials that you entered in the previous node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Subscriber Email*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > MailerLite > Output Data > JSON > email. You can also add the following expression: `{{$node["MailerLite"].json["email"]}}`. -5. Click on the ***Add Field*** button and select 'Custom Fields' from the dropdown list. -6. Click on the ***Add Custom Field*** button. -7. Select 'city' from the ***Field ID*** dropdown list. -8. Enter the name of the city in the ***Value*** field. -9. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node updates the information of the subscriber that we created in the previous node. Here, the node has added information about the city of the subscriber. - -![Using the MailerLite node to update the subscriber](/_images/integrations/builtin/app-nodes/mailerlite/mailerlite1_node.png) - -### 3. MailerLite2 node (get: subscriber) - -This node will return the information of the subscriber that we created using the MailerLite node. - - -1. Select the credentials that you entered in the previous node. -2. Select 'Get' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Subscriber Email*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > MailerLite > Output Data > JSON > email. You can also add the following expression: `{{$node["MailerLite"].json["email"]}}`. -5. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns the information of the subscriber that we created using the MailerLite node. - -![Using the MailerLite node to get the information of the subscriber](/_images/integrations/builtin/app-nodes/mailerlite/mailerlite2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailjet.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailjet.md index 77823e6bb..20b500028 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailjet.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailjet.md @@ -6,7 +6,7 @@ contentType: integration # Mailjet -Use the Mailjet node to automate work in Mailjet, and integrate Mailjet with other applications. n8n has built-in support for a wide range of Mailjet features, including sending emails, and sms. +Use the Mailjet node to automate work in Mailjet, and integrate Mailjet with other applications. n8n has built-in support for a wide range of Mailjet features, including sending emails, and SMS. On this page, you'll find a list of operations the Mailjet node supports and links to more resources. @@ -20,10 +20,10 @@ For usage examples and templates to help you get started, take a look at n8n's [ ## Basic Operations * Email - * Send a email - * Send a email template + * Send an email + * Send an email template * SMS - * Send a sms + * Send an SMS ## Example Usage diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.marketstack.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.marketstack.md index eaba62ce6..86792e811 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.marketstack.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.marketstack.md @@ -1,20 +1,20 @@ --- -title: Marketstack -description: Documentation for the Marketstack node in n8n, a workflow automation platform. Includes details of operations and configuration, and links to examples and credentials information. +title: marketstack +description: Documentation for the marketstack node in n8n, a workflow automation platform. Includes details of operations and configuration, and links to examples and credentials information. contentType: integration --- + +# marketstack -# Marketstack +Use the marketstack node to automate work in marketstack, and integrate marketstack with other applications. n8n has built-in support for a wide range of marketstack features, including getting exchanges, end-of-day data, and tickers. -Use the Marketstack node to automate work in Marketstack, and integrate Marketstack with other applications. n8n has built-in support for a wide range of Marketstack features, including getting exchanges, end-of-day data, and tickers. - -On this page, you'll find a list of operations the Marketstack node supports and links to more resources. +On this page, you'll find a list of operations the marketstack node supports and links to more resources. /// note | Credentials -Refer to [Marketstack credentials](/integrations/builtin/credentials/marketstack/) for guidance on setting up authentication. +Refer to [marketstack credentials](/integrations/builtin/credentials/marketstack/) for guidance on setting up authentication. /// /// note | Examples and templates -For usage examples and templates to help you get started, take a look at n8n's [Marketstack integrations](https://n8n.io/integrations/marketstack/){:target="_blank" .external-link} list. +For usage examples and templates to help you get started, take a look at n8n's [marketstack integrations](https://n8n.io/integrations/marketstack/){:target="_blank" .external-link} list. /// ## Basic operations @@ -31,19 +31,19 @@ For usage examples and templates to help you get started, take a look at n8n's [ This workflow allows you to get the past week's end of day data for a desired stock symbol. This example usage workflow uses the following two nodes. - [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Marketstack]() +- [marketstack]() The final workflow should look like the following image. -![A workflow with the Marketstack node](/_images/integrations/builtin/app-nodes/marketstack/workflow.png) +![A workflow with the marketstack node](/_images/integrations/builtin/app-nodes/marketstack/workflow.png) ### 1. Start node The start node exists by default when you create a new workflow. -### 2. Marketstack node +### 2. marketstack node -1. First enter your credentials for the Marketstack node. You can find out how to do that [here](/integrations/builtin/credentials/marketstack/). +1. First enter your credentials for the marketstack node. You can find out how to do that [here](/integrations/builtin/credentials/marketstack/). 2. Select **End-of-Day Data** from the *Resource* dropdown. 3. The **Get All** *Operation* is selected by default. 4. Enter your desired ticker symbol, `AI` in our example. @@ -51,5 +51,5 @@ The start node exists by default when you create a new workflow. 6. Click the **Add Filter** button and select **Timeframe End Date > Today**. 3. Click on **Execute Node** to run the workflow. -![The Marketstack node](/_images/integrations/builtin/app-nodes/marketstack/marketstack_node.png) +![The marketstack node](/_images/integrations/builtin/app-nodes/marketstack/marketstack_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mautic.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mautic.md index fedf8391e..362e6e127 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mautic.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mautic.md @@ -6,7 +6,7 @@ contentType: integration # Mautic -Use the Mautic node to automate work in Mautic, and integrate Mautic with other applications. n8n has built-in support for a wide range of Mautic features, including creating, updating, deleting, and getting companies, and contacts, as well as adding and removing campagin contacts. +Use the Mautic node to automate work in Mautic, and integrate Mautic with other applications. n8n has built-in support for a wide range of Mautic features, including creating, updating, deleting, and getting companies, and contacts, as well as adding and removing campaign contacts. On this page, you'll find a list of operations the Mautic node supports and links to more resources. @@ -35,7 +35,7 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Create a new contact * Delete a contact * Edit contact's points - * Add/remove contacts from/to the do not contact list + * Add/remove contacts from/to the don't contact list * Get data of a contact * Get data of all contacts * Send email to contact diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.medium.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.medium.md index de9828fb1..8c82d0075 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.medium.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.medium.md @@ -25,30 +25,6 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get all publications -## Example Usage - -This workflow allows you to post an article to a publication on Medium. You can also find the [workflow](https://n8n.io/workflows/594) on the website. This example usage workflow uses the following two nodes. - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Medium]() - -The final workflow should look like the following image. - -![A workflow with the Medium node](/_images/integrations/builtin/app-nodes/medium/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Medium node - -1. First of all, you'll have to enter credentials for the Medium node. You can find out how to do that [here](/integrations/builtin/credentials/medium/). -2. Toggle ***Publication*** to true. -3. Select the publication from the ***Publication ID*** dropdown list. -4. Enter the title in the ***Title*** field. -5. Select the format from the ***Content Format*** dropdown list. -6. Enter conent of the post in the ***Content*** field. -7. Click on ***Execute Node*** to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftexcel.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftexcel.md index 554dd4d77..6d7d49cd9 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftexcel.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftexcel.md @@ -22,8 +22,8 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Table * Adds rows to the end of the table - * Retrieve a list of tablecolumns - * Retrieve a list of tablerows + * Retrieve a list of table columns + * Retrieve a list of table rows * Looks for a specific column value and then returns the matching row * Workbook * Adds a new worksheet to the workbook. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftonedrive.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftonedrive.md index e6429b623..935738712 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftonedrive.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftonedrive.md @@ -49,7 +49,7 @@ View [example workflows and related content](https://n8n.io/integrations/microso To perform operations on folders, you need to supply the ID. You can find this: * In the URL of the folder -* By searching for it using the node. You need to do this if using MS 365 (where OneDrive uses Sharepoint behind the scenes): +* By searching for it using the node. You need to do this if using MS 365 (where OneDrive uses SharePoint behind the scenes): 1. Select **Resource** > **Folder**. 2. Select **Operation** > **Search**. 3. In **Query**, enter the folder name. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftteams.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftteams.md index 339e8b875..236463606 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftteams.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftteams.md @@ -35,58 +35,4 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get all tasks * Update a task -## Example Usage - -This workflow allows you to create, update and send a message to a channel in Microsoft Teams. You can also find the [workflow](https://n8n.io/workflows/680) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Microsoft Teams]() - -The final workflow should look like the following image. - -![A workflow with the Microsoft Teams node](/_images/integrations/builtin/app-nodes/microsoftteams/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Microsoft Teams node (create: channel) - -1. First of all, you'll have to enter credentials for the Microsoft Teams node. You can find out how to do that [here](/integrations/builtin/credentials/microsoft/). -2. Select the team that you want to use from the ***Team ID*** dropdown list. -3. Enter a name for the channel in the ***Name*** field. -4. Click on ***Execute Node*** to run the node. - -![Create a channel with the Microsoft Teams node](/_images/integrations/builtin/app-nodes/microsoftteams/microsoftteams_node.png) - - -### 3. Microsoft Teams1 node (update: channel) - -1. Select the credentials that you entered in the previous node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Team ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Microsoft Teams > Parameters > teamId. You can also add the following expression: `{{$node["Microsoft Teams"].parameter["teamId"]}}` -5. Click on the gears icon next to the ***Channel ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Microsoft Teams > Output > JSON > id. You can also add the following expression: `{{$node["Microsoft Teams"].json["id"]}}` -7. Click on the ***Add Field*** button and select 'Name' from the dropdown list. -8. Enter a new channel name in the ***Name*** field. -9. Click on ***Execute Node*** to run the node. - -![Update a Channel with the Microsoft Teams node](/_images/integrations/builtin/app-nodes/microsoftteams/microsoftteams1_node.png) - - - -### 4. Microsoft Teams2 node (create: channelMessage) - -1. Select the credentials that you entered in the previous node. -2. Select 'Channel Message (Beta)' from the ***Resource*** dropdown list. -3. Click on the gears icon next to the ***Team ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Microsoft Teams > Parameters > teamId. You can also add the following expression: `{{$node["Microsoft Teams"].parameter["teamId"]}}` -5. Click on the gears icon next to the ***Channel ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Microsoft Teams > Output > JSON > id. You can also add the following expression: `{{$node["Microsoft Teams"].json["id"]}}` -7. Select 'Text' from the ***Message Type*** dropdown list. -8. Enter a message in the ***Message*** field. -9. Click on ***Execute Node*** to run the node. - -![Send a message with the Microsoft Teams node](/_images/integrations/builtin/app-nodes/microsoftteams/microsoftteams2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsofttodo.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsofttodo.md index 6f7381db3..ea83649e9 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsofttodo.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsofttodo.md @@ -39,70 +39,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get All * Update -## Example Usage - -This workflow allows you to create, update and get a task in Microsoft To Do. You can also find the [workflow](https://n8n.io/workflows/1114) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Microsoft To Do]() - -The final workflow should look like the following image. - -![A workflow with the Microsoft To Do node](/_images/integrations/builtin/app-nodes/microsofttodo/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Microsoft To Do node (create: task) - -This node will create a task with the importance level `High` in the Tasks list. You can select a different list and the importance level. - -1. First of all, you'll have to enter credentials for the Microsoft To Do node. You can find out how to do that [here](/integrations/builtin/credentials/microsoft/). -2. Select 'Create' from the ***Operation*** dropdown list. -3. Select a list from the ***List ID*** dropdown list. -4. Enter a subject in the ***Subject*** field. -5. Click on ***Add Field*** and select 'Importance' from the dropdown list. -6. Select 'High' from the ***Importance*** dropdown list. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new task in Microsoft To Do. - -![Create a task with the Microsoft To Do node](/_images/integrations/builtin/app-nodes/microsofttodo/microsofttodo_node.png) - -### 3. Microsoft To Do1 node (update: task) - -This node will update the status of the task that we created in the previous node. - - -1. Select the credentials that you entered in the previous node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***List ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Microsoft To Do > Parameters > taskListId. You can also add the following expression: `{{$node["Microsoft To Do"].parameter["taskListId"]}}`. -5. Click on the gears icon next to the ***Task ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Current Node > Input > JSON > id. You can also add the following expression: `{{$json["id"]}}`. -7. Click on the ***Add Field*** button and select 'Status' from the dropdown list. -8. Select 'In progress' from the ***Status*** dropdown list. -9. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node updates the status of the task that we created in the previous node. - -![Update the status of a task using the Microsoft To Do node](/_images/integrations/builtin/app-nodes/microsofttodo/microsofttodo1_node.png) - -### 4. Microsoft To Do2 node (get: task) - -This node will get the task that we created earlier. - - -1. Select the credentials that you entered in the previous node. -2. Click on the gears icon next to the ***List ID*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Nodes > Microsoft To Do > Parameters > taskListId. You can also add the following expression: `{{$node["Microsoft To Do"].parameter["taskListId"]}}`. -4. Click on the gears icon next to the ***Task ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Current Node > Input > JSON > id. You can also add the following expression: `{{$json["id"]}}`. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node fetches the information of the task that we created earlier. - -![Retrieve the information of tasks using the Microsoft To Do node](/_images/integrations/builtin/app-nodes/microsofttodo/microsofttodo2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mindee.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mindee.md index 90aab4c4a..30419119c 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mindee.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mindee.md @@ -27,47 +27,6 @@ For usage examples and templates to help you get started, take a look at n8n's [ - Predict -## Example Usage - -This workflow allows you to extract information from an image of a receipt using the Mindee node. You can also find the [workflow](https://n8n.io/workflows/702) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) -- [Mindee]() - -The final workflow should look like the following image. - -![A workflow with the Mindee node](/_images/integrations/builtin/app-nodes/mindee/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - - -### 2. HTTP Request (GET) - -This example workflow uses the HTTP Request node to make a GET request to download the image of a receipt. You can also use other nodes, for example, the [Box](/integrations/builtin/app-nodes/n8n-nodes-base.box/) node, to get the images of the receipts you want to use. - -1. Enter the URL of the image in the ***URL*** field. For example, `https://miro.medium.com/max/1400/0*1T9GkAb93w5NSMsf`. -2. Select 'File' from the ***Response Format*** dropdown list. -3. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the HTTP Request node downloads the image from the URL. This image (binary data) can now be used by the other nodes in the workflow. - -![Using the HTTP Request node to get the file](/_images/integrations/builtin/app-nodes/mindee/httprequest_node.png) - - -### 3. Mindee node (predict: receipt) - -This node will get the image of the receipt (binary data) from the HTTP Request node and extract the information from it. -1. Select 'Receipt' from the ***Resource*** dropdown list. -2. You'll have to enter credentials for the Mindee node. You can find out how to do that [here](/integrations/builtin/credentials/mindee/). -3. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that the node extracts the information from the image that it got from the HTTP Request node. - -![Using the Mindee node to extract information from receipt](/_images/integrations/builtin/app-nodes/mindee/mindee_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.msg91.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.msg91.md index 7a1cf33d5..1631ddb94 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.msg91.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.msg91.md @@ -49,6 +49,6 @@ The start node exists by default when you create a new workflow. ### How do I find my Sender ID? -1. Log in to your MSG91 dasboard and click on 'Sender Id' in the left panel. +1. Log in to your MSG91 dashboard and click on 'Sender Id' in the left panel. 2. If you don't already have one, click on *Add Sender Id +*, fill in the details, and click on the *Save Sender Id* button. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.onesimpleapi.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.onesimpleapi.md index faa7f58ac..7b6d5c666 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.onesimpleapi.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.onesimpleapi.md @@ -3,7 +3,8 @@ title: One Simple API description: Documentation for the One Simple API node in n8n, a workflow automation platform. Includes details of operations and configuration, and links to examples and credentials information. contentType: integration --- - + + # One Simple API Use the One Simple API node to automate work in One Simple API, and integrate One Simple API with other applications. n8n has built-in support for a wide range of One Simple API features, including getting profiles, retrieving information, and generating utilities. @@ -34,3 +35,4 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get SEO information from website * Create a screenshot from a webpage + \ No newline at end of file diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.orbit.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.orbit.md index 25806ee83..8ef5bd6b9 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.orbit.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.orbit.md @@ -38,90 +38,6 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get all posts * Delete a post -## Example Usage - -This workflow allows you to create a new member and update their information in Orbit using the Orbit node. It also allows you to create a note and a post for the new member in Orbit. You can also find the [workflow](https://n8n.io/workflows/765) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Orbit]() - -The final workflow should look like the following image. - -![A workflow with the Orbit node](/_images/integrations/builtin/app-nodes/orbit/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - - -### 2. Orbit node (upsert: member) - -This node will create a new member in a workspace in Orbit. We will use the GitHub identity to create a new member. - -1. First of all, you'll have to enter credentials for the Orbit node. You can find out how to do that [here](/integrations/builtin/credentials/orbit/). -2. Select 'Upsert' from the ***Operation*** dropdown list. -3. Select the workspace where you want to create a new member from the ***Workspace*** dropdown list. -4. Click on the ***Add Identity*** button. -5. Select 'GitHub' from the ***Source*** dropdown list. -6. Select 'Username' from the ***Search By*** dropdown list. -7. Enter the GitHub username of the member in the ***Username*** field. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new member in a workspace in Orbit using the GitHub identity. - -![Using the Orbit node to create a new member in a workspace in Orbit](/_images/integrations/builtin/app-nodes/orbit/orbit_node.png) - -### 3. Orbit1 node (update: member) - -This node will update the tags of the member that we created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Workspace*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Orbit > Parameters > workspaceId. You can also add the following expression: `{{$node["Orbit"].parameter["workspaceId"]}}`. -5. Click on the gears icon next to the ***Member ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Orbit > Output Data > JSON > id. You can also add the following expression: `{{$node["Orbit"].json["id"]}}`. -7. Click on the ***Add Field*** button and select 'Tags to Add'. -8. Enter the tags in the ***Tags to Add*** field. You can add multiple tags by separating them with a comma. -9. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node updates the information of the new member that we created in the previous node. The node adds the tags `n8nConf` and `MLH` to the new member. - -![Using the Orbit node to add tags to a member](/_images/integrations/builtin/app-nodes/orbit/orbit1_node.png) - -### 4. Orbit2 node (create: note) - -This node will create a note for the member that we created using the Orbit node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Note' from the ***Resource*** dropdown list. -3. Click on the gears icon next to the ***Workspace*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Orbit > Parameters > workspaceId. You can also add the following expression: `{{$node["Orbit"].parameter["workspaceId"]}}`. -5. Click on the gears icon next to the ***Member ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Orbit > Output Data > JSON > id. You can also add the following expression: `{{$node["Orbit"].json["id"]}}`. -7. Enter a note in the ***Note*** field. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a note for the member that we created using the Orbit node. - -![Using the Orbit node to create a note for a member](/_images/integrations/builtin/app-nodes/orbit/orbit2_node.png) - -### 5. Orbit3 node (create: post) - -This node will create a post for the member that we created using the Orbit node. - - -1. Select the credentials that you entered in the previous node. -2. Select 'Post' from the ***Resource*** dropdown list. -3. Click on the gears icon next to the ***Workspace*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Orbit > Parameters > workspaceId. You can also add the following expression: `{{$node["Orbit"].parameter["workspaceId"]}}`. -5. Click on the gears icon next to the ***Member ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Orbit > Output Data > JSON > id. You can also add the following expression: `{{$node["Orbit"].json["id"]}}`. -7. Enter a URL for the post in the ***URL*** field. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a post for the member that we created using the Orbit node. - -![Using the Orbit node to create a post for a member](/_images/integrations/builtin/app-nodes/orbit/orbit3_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.paddle.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.paddle.md index dd560f8c2..0b7e86c8e 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.paddle.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.paddle.md @@ -35,28 +35,5 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get all users -## Example Usage - -This workflow allows you to create a coupon on Paddle. You can also find the [workflow](https://n8n.io/workflows/659) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Paddle]() - -The final workflow should look like the following image. - -![A workflow with the Paddle node](/_images/integrations/builtin/app-nodes/paddle/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. -### 2. Paddle node (create: coupon) - -1. First of all, you'll have to enter credentials for the Paddle node. You can find out how to do that [here](/integrations/builtin/credentials/paddle/). -2. Enter the discount amount in the ***Discount Amount*** field. -3. Click on the ***Add Field*** button and select 'Coupon Code' from the dropdown list. -4. Enter the coupon code in the ***Coupon Code*** field. -5. Click on ***Execute Node*** to run the node. - -![Using the Paddle node to create a coupon](/_images/integrations/builtin/app-nodes/paddle/paddle_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.pagerduty.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.pagerduty.md index 4b605a66d..2bf76f5e1 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.pagerduty.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.pagerduty.md @@ -34,62 +34,6 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get a user -## Example Usage - -This workflow allows you to create, update, and get an incident on PagerDuty. You can also find the [workflow](https://n8n.io/workflows/411) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [PagerDuty]() - -The final workflow should look like the following image. - -![A workflow with the PagerDuty node](/_images/integrations/builtin/app-nodes/pagerduty/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. PagerDuty node (create: incident) - -1. First of all, you'll have to enter credentials for the PagerDuty node. You can find out how to do that [here](/integrations/builtin/credentials/pagerduty/). -2. Enter the title of the incident in the ***Title*** field. -3. Select the ***Service ID*** from the dropdown list. -4. Enter your email in the ***Email*** field. -5. Click on ***Execute Node*** to run the node. - -![Using the PagerDuty node to create an incident](/_images/integrations/builtin/app-nodes/pagerduty/pagerduty_node.png) - - - -### 3. PagerDuty1 node (update: incident) - -1. Select the credentials that you entered in the previous node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Incident ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > PagerDuty > Output Data > JSON > id. You can also add the following expression: `{{$node["PagerDuty"].json["id"]}}`. -5. Click on the gears icon next to the ***Email*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > PagerDuty > Parameters > email. You can also add the following expression: `{{$node["PagerDuty"].parameter["email"]}}`. -7. Click on the ***Add Field*** button and click on ***Title***. -8. Enter the name of the updated title in the ***Title*** field. -9. Click on ***Execute Node*** to run the node. - - -![Using the PagerDuty node to update an incident](/_images/integrations/builtin/app-nodes/pagerduty/pagerduty1_node.png) - - - -### 4. PagerDuty2 node (get: incident) - -1. Select the credentials that you entered in the previous node. -2. Select 'Get' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Incident ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > PagerDuty > Output Data > JSON > id. You can also add the following expression: `{{$node["PagerDuty"].json["id"]}}`. -5. Click on ***Execute Node*** to run the node. - - -![Using the PagerDuty node to get an incident](/_images/integrations/builtin/app-nodes/pagerduty/pagerduty2_node.png) - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.paypal.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.paypal.md index 1a1c600b1..95510cda9 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.paypal.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.paypal.md @@ -6,7 +6,7 @@ contentType: integration # PayPal -Use the PayPal node to automate work in PayPal, and integrate PayPal with other applications. n8n has built-in support for a wide range of PayPal features, including including creating a batch payout and canceling unclaimed payout items. +Use the PayPal node to automate work in PayPal, and integrate PayPal with other applications. n8n has built-in support for a wide range of PayPal features, including creating a batch payout and canceling unclaimed payout items. On this page, you'll find a list of operations the PayPal node supports and links to more resources. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.peekalink.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.peekalink.md index 4ddb30609..298aaecd0 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.peekalink.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.peekalink.md @@ -22,74 +22,5 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Check whether preview for a given link is available * Return the preview for a link -## Example Usage - -This workflow allows you to check if preview for a link is available and return the link preview. You can also find the [workflow](https://n8n.io/workflows/935) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Peekalink]() -- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/) -- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noop/) - -The final workflow should look like the following image. - -![A workflow with the Peekalink node](/_images/integrations/builtin/app-nodes/peekalink/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Peekalink node (create: room) - -This node will check whether a preview for the specified link is available. - -1. First of all, you'll have to enter credentials for the Peekalink node. You can find out how to do that [here](/integrations/builtin/credentials/peekalink/). -2. Select 'Is available' from the ***Operation*** dropdown list. -3. Enter a URL in the ***URL*** field. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns information about whether a preview for the specified link is available. - -![Using the Peekalink node to check whether preview for a given link is available](/_images/integrations/builtin/app-nodes/peekalink/peekalink_node.png) - -### 3. IF node - -This node will check the response from the previous node. If the previous node returned `true`, the IF node will also return `true`, otherwise the IF node will return `false`. -1. Click on ***Add Condition*** and select 'Boolean'. -2. Click on the gears icon next to the ***Value 1*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > isAvailable. You can also add the following expression: `{{$json["isAvailable"]}}`. -4. Toggle ***Value 2*** to `true`. -5. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns the data from the previous node for the `true` branch. - -![Using the IF node to check the response from the previous node](/_images/integrations/builtin/app-nodes/peekalink/if_node.png) - -### 4. Peekalink node (preview) - -This node will return the preview of the URL that you specified in the Peekalink node. - - -1. Connect the node to the 'true' output of the IF node -2. Select the credentials that you entered in the previous Peekalink node. -3. Click on the gears icon next to the ***URL*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Peekalink > Parameters > url. You can also add the following expression: `{{$node["Peekalink"].parameter["url"]}}`. -5. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns the preview of the URL that you specified in the Peekalink node. - -![Using the Peekalink node to get the preview of a URL](/_images/integrations/builtin/app-nodes/peekalink/peekalink1_node.png) - -### 5. NoOp node -Adding this node here is optional, as the absence of this node won't make a difference to the functioning of the workflow. We've added this as it can sometimes help others with a better understanding of the workflow, visually. - - -1. Create a ***NoOp*** node connected to the 'false' output of the IF node. -2. Click on ***Execute Node*** to run the node. - - -![Using the NoOp node](/_images/integrations/builtin/app-nodes/peekalink/noop_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.philipshue.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.philipshue.md index e8fe873d7..63b95b18e 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.philipshue.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.philipshue.md @@ -26,25 +26,5 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Update a light -## Example Usage -This workflow allows you to turn on a light and set its brightness using the Philips Hue node. You can also find the [workflow](https://n8n.io/workflows/666) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Philips Hue]() - -The final workflow should look like the following image. - -![A workflow with the Philips Hue node](/_images/integrations/builtin/app-nodes/philipshue/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Philips Hue node (update: light) - -1. First of all, you'll have to enter credentials for the Philips Hue node. You can find out how to do that [here](/integrations/builtin/credentials/philipshue/). -2. Enter the light id in the ***Light ID*** field. -3. Click on ***Add Field*** and select 'Brightness' from the dropdown list. -4. Enter a value between 1 and 254 for the brightness in the ***Brightness*** field. -5. Click on ***Execute Node*** to run the node. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.posthog.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.posthog.md index 88097bfc4..1879d7ec9 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.posthog.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.posthog.md @@ -29,48 +29,4 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Track a page * Track a screen -## Example Usage - -This workflow allows you to create an event in PostHog when a request is made to a webhook URL. You can also find the [workflow](https://n8n.io/workflows/968) on n8n.io. This example usage workflow uses the following nodes. -- [Webhook](/integrations/builtin/core-nodes/n8n-nodes-base.webhook/) -- [PostHog]() - -The final workflow should look like the following image. - -![A workflow with the PostHog node](/_images/integrations/builtin/app-nodes/posthog/workflow.png) - -### 1. Webhook node - -This node will trigger the workflow. We will make a GET request to the test webhook URL and pass on a query parameter called `event`. - -1. Click on ***Webhook URLs*** and select the 'Test' tab. -2. Copy the displayed URL. We will make a GET request to this URL later on. -3. Save the workflow to register the webhook. -4. Click on ***Execute Node*** to run the node. -5. In a new browser tab, paste the URL that you copied in the previous step and append `?event=login` to it. Your URL should look similar to the following URL:`https://your-n8n.url/webhook/path?event=login`. Here, we are passing a query parameter called `event` and assigning the value `login` to it. -6. Press Enter (or Return) to make a request to the test webhook URL. - -In the screenshot below, you will notice that the node triggers the workflow and receives a query parameter. We will use the value of the query parameter in the next node in the workflow. - -![Using the Webhook node to trigger the workflow](/_images/integrations/builtin/app-nodes/posthog/webhook_node.png) - -### 2. PostHog node (create:customer) - -This node will create a new event in PostHog. - -1. First of all, you'll have to enter credentials for the PostHog node. You can find out how to do that [here](/integrations/builtin/credentials/posthog/). -2. Click on the gears icon next to the ***Event*** field and click on ***Add Expression***. - -3. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > query > event. You can also add the following expression: `{{$json["query"]["event"]}}`. - -4. Enter a distinct id in the ***Distinct ID*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new event in PostHog. - -![Using the PostHog node to create a new event](/_images/integrations/builtin/app-nodes/posthog/posthog_node.png) - -/// note | Activate workflow for production -This example workflow uses the Webhook node, which is a Trigger node. You'll need to save the workflow and then click on the Activate toggle on the top right of the screen to activate the workflow. Your workflow will then be triggered every time a GET request is sent to the ***Production*** webhook URL. -/// diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.profitwell.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.profitwell.md index 5ee1e8846..57e2b0d81 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.profitwell.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.profitwell.md @@ -20,6 +20,6 @@ For usage examples and templates to help you get started, take a look at n8n's [ ## Operations * Company - * Get your companys ProfitWell account settings + * Get your company's ProfitWell account settings * Metric * Retrieve financial metric broken down by day for either the current month or the last diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.raindrop.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.raindrop.md index f52e6bd55..a63c54a22 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.raindrop.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.raindrop.md @@ -37,82 +37,4 @@ For usage examples and templates to help you get started, take a look at n8n's [ * User * Get -## Example Usage - -This workflow allows you to create a collection and create, update, and get a bookmark in Raindrop. You can also find the [workflow](https://n8n.io/workflows/959) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Raindrop]() - -The final workflow should look like the following image. - -![A workflow with the Raindrop node](/_images/integrations/builtin/app-nodes/raindrop/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Raindrop node (create: collection) - -This node will create a new collection in Raindrop. - -1. First of all, you'll have to enter credentials for the Raindrop node. You can find out how to do that [here](/integrations/builtin/credentials/raindrop/). -2. Select 'Create' from the ***Operation*** dropdown list. -3. Enter a title in the ***Title*** field. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new collection with the title `n8n-docs`. - -![Using the Raindrop node to create a new collection](/_images/integrations/builtin/app-nodes/raindrop/raindrop_node.png) - -### 3. Raindrop1 node (create: bookmark) - -This node will create a new bookmark and add it to the collection that we created in the previous node. - - -1. Select the credentials that you entered in the previous node. -2. Select 'Bookmark' from the ***Resource*** dropdown list. -3. Select 'Create' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Collection*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > _id. You can also add the following expression: `{{$json["_id"]}}`. -6. Enter `https://docs.n8n.io` in the ***Link*** field. -7. Click on ***Add Field*** and select 'Title' from the dropdown list. -8. Enter `Documentation` in the ***Title*** field. -9. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new bookmark with the title `Documentation`. - -![Using the Raindrop node to create a new bookmark](/_images/integrations/builtin/app-nodes/raindrop/raindrop1_node.png) - -### 4. Raindrop2 node (update: bookmark) - -This node will update the bookmark that we created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Bookmark' from the ***Resource*** dropdown list. -3. Select 'Update' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Bookmark ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > _id. You can also add the following expression: `{{$json["_id"]}}`. -6. Click on ***Add Field*** and select 'Title' from the dropdown list. -7. Enter `n8n Documentation` in the ***Title*** field. -8. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node updates the title of the bookmark that we created in the previous node. - -![Using the Raindrop node to update a bookmark](/_images/integrations/builtin/app-nodes/raindrop/raindrop2_node.png) - -### 5. Raindrop3 node (get: bookmark) - -This node will return the information about the bookmark that we created earlier. - -1. Select the credentials that you entered in the previous node. -2. Select 'Bookmark' from the ***Resource*** dropdown list. -3. Click on the gears icon next to the ***Bookmark ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > _id. You can also add the following expression: `{{$json["_id"]}}`. -5. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns the information on the bookmark that we created earlier. - -![Using the Raindrop node to get a bookmark](/_images/integrations/builtin/app-nodes/raindrop/raindrop3_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.reddit.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.reddit.md index 8c49af4e3..c4acfaac1 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.reddit.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.reddit.md @@ -38,62 +38,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * User * Get -## Example Usage - -This workflow allows you to create a post a Reddit and add a comment to that post. You can also find the [workflow](https://n8n.io/workflows/928) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Reddit]() - -The final workflow should look like the following image. - -![A workflow with the Reddit node](/_images/integrations/builtin/app-nodes/reddit/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Reddit node (create: post) - -This node will create a post under the subreddit `n8n`. If you want to create a post under a different subreddit, enter the name of that subreddit instead. - -1. First of all, you'll have to enter credentials for the Reddit node. You can find out how to do that [here](/integrations/builtin/credentials/reddit/). -2. Enter `n8n` in the ***Subreddit*** field. -3. Enter a title in the ***Title*** field. -4. Enter the content of the post in the ***Text*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new post under the subreddit `n8n`. - -![Using the Reddit node to create a post](/_images/integrations/builtin/app-nodes/reddit/reddit_node.png) - -### 3. Reddit1 node (get: post) - -This node will retrieve the post that we created using the previous node. - -1. Select the credentials you entered in the previous node. -2. Select 'Get' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Subreddit*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Reddit > Parameters > subreddit. You can also add the following expression: `{{$node["Reddit"].parameter["subreddit"]}}`. -5. Click on the gears icon next to the ***Post ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the information of the post that we created in the previous node. - -![Using the Reddit node to get a post](/_images/integrations/builtin/app-nodes/reddit/reddit1_node.png) - -### 4. Reddit node (create: postComment) - -This node will add a comment to the post that we created earlier. - -1. Select the credentials you entered in the previous node. -2. Select 'Post Comment' from the ***Resource*** dropdown list. -3. Click on the gears icon next to the ***Post ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`. -5. Enter your comment in the ***Comment Text*** field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node comments on the post that we created earlier. - -![Using the Reddit node to create a comment](/_images/integrations/builtin/app-nodes/reddit/reddit2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.redis.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.redis.md index f7da536ee..f41bd647f 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.redis.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.redis.md @@ -6,7 +6,7 @@ contentType: integration # Redis -Use the Redis node to automate work in Redis, and integrate Redis with other applications. n8n has built-in support for a wide range of Redis features, including deleting keys, getting key values, setting key value, and publishing messages to theRedischannel. +Use the Redis node to automate work in Redis, and integrate Redis with other applications. n8n has built-in support for a wide range of Redis features, including deleting keys, getting key values, setting key value, and publishing messages to the Redis channel. On this page, you'll find a list of operations the Redis node supports and links to more resources. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.rocketchat.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.rocketchat.md index 524d799ef..3b3d6b5d3 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.rocketchat.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.rocketchat.md @@ -22,26 +22,6 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Chat * Post a message to a channel or a direct message -## Example Usage - -This workflow allows you to post a message to a channel in Rocket.Chat. You can also find the [workflow](https://n8n.io/workflows/462) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Rocket.Chat]() - -The final workflow should look like the following image. - -![A workflow with the Rocket.Chat node](/_images/integrations/builtin/app-nodes/rocketchat/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Rocket.Chat node - -1. First of all, you'll have to enter credentials for the Rocket.Chat node. You can find out how to do that [here](/integrations/builtin/credentials/rocketchat/). -2. Enter the name of the channel where you want to post the message in the *Channel* field. For example, `#general`. -3. Enter the message in the *Text* field. -5. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.salesforce.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.salesforce.md index 14b23a582..cc8371576 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.salesforce.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.salesforce.md @@ -6,7 +6,7 @@ contentType: integration # Salesforce -Use the Salesforce node to automate work in Salesforce, and integrate Salesforce with other applications. n8n has built-in support for a wide range of Salesforce features, including creating, updating, deleting, and getting accounts, attachements, cases, and leads, as well as uploading documents. +Use the Salesforce node to automate work in Salesforce, and integrate Salesforce with other applications. n8n has built-in support for a wide range of Salesforce features, including creating, updating, deleting, and getting accounts, attachments, cases, and leads, as well as uploading documents. On this page, you'll find a list of operations the Salesforce node supports and links to more resources. @@ -106,53 +106,6 @@ To add custom fields to your request: You can then find and add your custom fields. -## Example Usage - -This workflow allows you to create, update, and add a note to a lead in Salesforce. You can also find the [workflow](https://n8n.io/workflows/664) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Salesforce]() - -The final workflow should look like the following image. - -![A workflow with the Salesforce node](/_images/integrations/builtin/app-nodes/salesforce/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Salesforce node (create: lead) - -1. First of all, you'll have to enter credentials for the Salesforce node. You can find out how to do that [here](/integrations/builtin/credentials/salesforce/). -2. Enter the name of the company in the ***Company*** field. -3. Enter the last name of the contact person in the ***Last Name*** field. -4. Click on ***Execute Node*** to run the node. - -![Create a lead with the Salesforce node](/_images/integrations/builtin/app-nodes/salesforce/salesforce_node.png) - - -### 3. Salesforce1 node (update: lead) - -1. Select the credentials that you entered in the previous node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Lead ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Salesforce > Output Data > JSON > id. You can also add the following expression: `{{$node["Salesforce"].json["id"]}}` -5. Click on the ***Add Field*** button and select 'City' from the dropdown list. -6. Enter a city name in the ***City*** field. -7. Click on ***Execute Node*** to run the node. - -![Update a lead with the Salesforce node](/_images/integrations/builtin/app-nodes/salesforce/salesforce1_node.png) -### 4. Salesforce2 node (addNote: lead) - -1. Select the credentials that you entered in the previous node. -2. Select ***Add Note*** from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Lead ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Salesforce > Output Data > JSON > id. You can also add the following expression: `{{$node["Salesforce"].json["id"]}}` -5. Enter the note in the ***Title*** field. -6. Click on ***Execute Node*** to run the node. - -![Add a note to a lead with the Salesforce node](/_images/integrations/builtin/app-nodes/salesforce/salesforce2_node.png) - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.securityscorecard.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.securityscorecard.md index f3b8da0f2..bf91a1d03 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.securityscorecard.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.securityscorecard.md @@ -45,62 +45,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Generate a report * Get list of recently generated report -## Example Usage - -This workflow allows you to generate, retrieve, and download a report using the SecurityScorecard node. You can also find the [workflow](https://n8n.io/workflows/920) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [SecurityScorecard]() - -The final workflow should look like the following image. - -![A workflow with the SecurityScorecard node](/_images/integrations/builtin/app-nodes/securityscorecard/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. SecurityScorecard node (generate: report) - -This node will generate a full scorecard report for a company that we specify. - -1. First of all, you'll have to enter credentials for the SecurityScorecard node. You can find out how to do that [here](/integrations/builtin/credentials/securityscorecard/). -2. Select 'Report' from the ***Resource*** dropdown list. -3. Select 'Generate' from the ***Operation*** dropdown list. -4. Select 'Full Scorecard' from the ***Report*** dropdown list. -5. Enter the domain of the company in the ***Scorecard Identifier*** field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node generates a full scorecard report of `n8n.io`. - -![Using the SecurityScorecard node to create full scorecard report](/_images/integrations/builtin/app-nodes/securityscorecard/securityscorecard_node.png) - -### 3. SecurityScorecard1 node (getAll: report) - -This node will return a report from SecurityScorecard. - -1. Select the credentials that you entered in the previous node. -2. Select 'Report' from the ***Resource*** dropdown list. -3. Select 'Get All' from the ***Operation*** dropdown list. -4. Enter `1` in the ***Limit*** field. By setting it to one, the node will return a single report. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns a report from SecurityScroecard. - -![Using the SecurityScorecard node to get a report](/_images/integrations/builtin/app-nodes/securityscorecard/securityscorecard1_node.png) - -### 4. SecurityScorecard2 node (download: report) - -This node will download the report that got returned by the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Report' from the ***Resource*** dropdown list. -3. Select 'Download' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Report URL*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > download_url. You can also add the following expression: `{{$json["download_url"]}}`. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node downloads the report that was returned by the previous node. - -![Using the SecurityScorecard node to download a report](/_images/integrations/builtin/app-nodes/securityscorecard/securityscorecard2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.sendy.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.sendy.md index e6f02ec2c..dd5edf3e6 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.sendy.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.sendy.md @@ -28,55 +28,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Unsubscribe user from a list * Get the status of subscriber -## Example Usage - -This workflow allows you to add a subscriber to a list and create and send a campaign using the Sendy node. You can also find the [workflow](https://n8n.io/workflows/727) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Sendy]() - -The final workflow should look like the following image. - -![A workflow with the Sendy node](/_images/integrations/builtin/app-nodes/sendy/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - - -### 2. Sendy node (add: subscriber) - -This node will add a subscriber to a list in Sendy. If you don't already have a list in Sendy, make sure to create one. - -1. First of all, you'll have to enter credentials for the Sendy node. You can find out how to do that [here](/integrations/builtin/credentials/sendy/). -2. Enter the subscriber's email address in the ***Email*** field. -3. In your Sendy dashboard, click on 'View all lists' and copy the ID of the list to which you want to add the subscriber. Paste this list ID in the List ID field in n8n. -4. Click on the ***Add Field*** button and select 'Name'. -5. Enter the name of the subscriber in the ***Name*** field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node adds a subscriber with their name to the list that we specify. - -![Using the Sendy node to add a subscriber to a list](/_images/integrations/builtin/app-nodes/sendy/sendy_node.png) - -### 3. Sendy1 node (create: campaign) - -This node will create a campaign with the title 'Welcome to n8n' and send it to the subscribers of the list that we specify. - -1. Select the credentials that you entered in the previous node. -2. Select 'Campaign' from the ***Resource*** dropdown list. -3. Enter the name of the sender in the ***From Name*** field. -4. Enter the email address of the sender in the ***From Email*** field. -5. Enter the email address where the subscribers can reply to in the ***Reply To*** field. -6. Enter the title of the campaign in the ***Title*** field. -7. Enter the subject of the email in the ***Subject*** field. -8. Enter the HTML snippet of the email campaign in the ***HTML Text*** field. -9. Toggle ***Send Campaign*** to true. -10. Click on the ***Add Field*** button and select 'List IDs'. -11. Click on the gears icon next to the ***List IDs*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Nodes > Sendy > Parameters > listId. You can also add the following expression: `{{$node["Sendy"].parameter["listId"]}}`. -13. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates the campaign with the title `Welcome to n8n` and sends it to the list that we specify. - -![Using the Sendy node to create and send a campaign to a list](/_images/integrations/builtin/app-nodes/sendy/sendy1_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.storyblok.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.storyblok.md index c54d22dee..2c166cc07 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.storyblok.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.storyblok.md @@ -34,53 +34,5 @@ For usage examples and templates to help you get started, take a look at n8n's [ - Unpublish a story -## Example Usage - -This workflow allows you to get all the stories that have the slug starting with `release` and publish them using the Storyblok node. You can also find the [workflow](https://n8n.io/workflows/768) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Storyblok]() - -The final workflow should look like the following image. - -![A workflow with the Storyblok node](/_images/integrations/builtin/app-nodes/storyblok/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Storyblok node (getAll: story) - -This node will get all the stories that have a slug starting with `release`. - -1. Select 'Management API' from the ***Source*** dropdown list. -2. You'll have to enter credentials for the Storyblok node. You can find out how to do that [here](/integrations/builtin/credentials/storyblok/). -3. Select 'Get All' from the ***Operation*** dropdown list. -4. Select a space from the ***Space ID*** dropdown list. -5. Click on the ***Add Filter*** button. -6. Enter `release` in the ***Starts With*** field. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns all the stories that have a slug starting with `release`. - -![Using the Storyblok node to get filtered stories](/_images/integrations/builtin/app-nodes/storyblok/storyblok_node.png) - -### 3. Storyblok1 node (publish: story) - -This node will publish the stories that were returned by the previous node. - -1. Select 'Management API' from the ***Source*** dropdown list. -2. Select the credentials that you entered in the previous node. -3. Select 'Publish' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Space ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > Storyblok > Parameters > space. You can also add the following expression: `{{$node["Storyblok"].parameter["space"]}}`. -6. Click on the gears icon next to the ***Story ID*** field and click on ***Add Expression***. -7. Select the following in the ***Variable Selector*** section: Nodes > Storyblok > Output Data > JSON > id. You can also add the following expression: `{{$node["Storyblok"].json["id"]}}`. -8. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node publishes the stories that were returned by the previous node. - -![Using the Storyblok node to publish stories](/_images/integrations/builtin/app-nodes/storyblok/storyblok1_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.taiga.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.taiga.md index c3bc48c64..1776ca447 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.taiga.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.taiga.md @@ -28,57 +28,5 @@ For usage examples and templates to help you get started, take a look at n8n's [ -## Example Usage - -This workflow allows you to create, update, and get an issue on Taiga. You can also find the [workflow](https://n8n.io/workflows/685) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Taiga]() - -The final workflow should look like the following image. - -![A workflow with the Taiga node](/_images/integrations/builtin/app-nodes/taiga/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. -### 2. Taiga node (create: issue) - -1. First of all, you'll have to enter credentials for the Taiga node. You can find out how to do that [here](/integrations/builtin/credentials/taiga/). -2. Select the project ID from the ***Project ID*** dropdown list. -3. Enter the subject of the issue in the ***Subject*** field. -4. Click on ***Execute Node*** to run the node. - -![Using the Taiga node to create an issue](/_images/integrations/builtin/app-nodes/taiga/taiga_node.png) - - - -### 3. Taiga1 node (update: issue) - -1. Select the credentials that you entered in the previous node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Project ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Taiga > Output Data > JSON > project. You can also add the following expression: `{{$node["Taiga"].json["project"]}}`. -5. Click on the gears icon next to the ***Issue ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Taiga > Output Data > JSON > id. You can also add the following expression: `{{$node["Taiga"].json["id"]}}`. -7. Click on the ***Add Field*** button and select 'Description' from the dropdown list. -8. Enter the description of the issue in the ***Description*** field. -9. Click on ***Execute Node*** to run the node. - - -![Using the Taiga node to update an issue](/_images/integrations/builtin/app-nodes/taiga/taiga1_node.png) - - - -### 4. Taiga2 node (get: issue) - -1. Select the credentials that you entered in the previous node. -2. Select 'Get' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Issue ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Taiga > Output Data > JSON > id. You can also add the following expression: `{{$node["Taiga"].json["id"]}}`. -5. Click on ***Execute Node*** to run the node. - - -![Using the Taiga node to get an issue](/_images/integrations/builtin/app-nodes/taiga/taiga2_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.travisci.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.travisci.md index 0d45ab5a3..b3433ce31 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.travisci.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.travisci.md @@ -26,28 +26,4 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Restart a build * Trigger a build -## Example Usage - -This workflow allows you to trigger a build using the Travis CI node. You can also find the [workflow](https://n8n.io/workflows/658) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Travis CI]() - -The final workflow should look like the following image. - -![A workflow with the Travis CI node](/_images/integrations/builtin/app-nodes/travisci/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. Travis CI node (trigger: build) - -1. First of all, you'll have to enter credentials for the Travis CI node. You can find out how to do that [here](/integrations/builtin/credentials/travisci/). -2. Select 'Trigger' from the ***Operation*** dropdown list. -3. Enter the repository name in the ***Slug*** field in the `ownerName/repositoryName` format. -4. Enter the branch name in the ***Branch*** field. -5. Click on ***Execute Node*** to run the node. - -![Using the Travis CI node to trigger a build](/_images/integrations/builtin/app-nodes/travisci/travisci_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.twist.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.twist.md index 8e61acb70..1125aea3f 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.twist.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.twist.md @@ -46,81 +46,6 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get all threads * Update a thread -## Example Usage - -This workflow allows you to create and update a channel as well as send a message on Twist. You can also find the [workflow](https://n8n.io/workflows/826) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Twist]() - -The final workflow should look like the following image. - -![A workflow with the Twist node](/_images/integrations/builtin/app-nodes/twist/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. Twist node (create: channel) - -This node will create a channel `n8n-docs` and add a user to the channel. -1. First of all, you'll have to enter credentials for the Twist node. You can find out how to do that [here](/integrations/builtin/credentials/twist/). - -2. Select 'Channel' from the ***Resource*** dropdown list. -3. Select a workspace from the ***Workspace ID*** dropdown list. -4. Enter `n8n-docs` in the ***Name*** field. If you want to create a channel with a different name, enter that name instead. -5. Click on ***Add Field*** and select 'User IDs' from the dropdown list. -6. Select the users from the ***User IDs*** dropdown list. The users you select will be added to the channel. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new channel named `n8n-docs`, and adds a user to the channel. - -![Using the Twist node to create a channel](/_images/integrations/builtin/app-nodes/twist/twist_node.png) - -### 3. Twist1 node (update: channel) - -This node will update the description of the channel that we created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Channel' from the ***Resource*** dropdown list. -3. Select 'Update' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Channel ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > Twist > Output Data > JSON > id. You can also add the following expression: `{{$node["Twist"].json["id"]}}`. -6. Click on ***Add Field*** and select 'Description' from the dropdown list. -7. Enter a description in the ***Description*** field. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node adds a description to the channel that we created in the previous node. - -![Using the Twist node to update the description of a channel](/_images/integrations/builtin/app-nodes/twist/twist1_node.png) - -### 4. Twist2 node (create: messageConversation) - -This node will send a message to the General conversation on Twist. The message contains an action button that navigates to `https://docs.n8n.io`. - -1. Select the credentials that you entered in the previous node. -2. Select a workspace from the ***Workspace ID*** dropdown list. -3. Select 'General' from the ***Conversation ID*** dropdown list. If you want to send a message to a different conversation, select that conversation instead. -4. Click on the gears icon next to the ***Channel ID*** field and click on ***Add Expression***. -5. Enter the following text in the ***Content*** field: -``` -Hey [Harshil](twist-mention://475370)! -You have been added to the {{$node["Twist"].json["name"]}} channel. -Click on the button below to quickly navigate to the documentation website. -``` -The above message mentions the user `Harshil`. To mention a user in your workspace you need to use their User ID. Refer to the [FAQs](#where-can-i-get-the-user-id) to learn how to get a User ID. - -6. Click on ***Add options*** and select 'Actions' from the dropdown list. -7. Click on the ***Add Action*** button. -8. Select 'Open URL' from the ***Action*** dropdown list. -9. Enter `Documentation site` in the ***Button Text*** field. -10. Select 'Action' from the ***Type*** dropdown list. -11. Enter `https://docs.n8n.io` in the ***URL*** field. -12. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends a message to the General conversation and mentions the user. - -![Using the Twist node to send a message](/_images/integrations/builtin/app-nodes/twist/twist2_node.png) ## FAQs diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.uptimerobot.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.uptimerobot.md index 8ccd8c8d1..102d6185a 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.uptimerobot.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.uptimerobot.md @@ -46,67 +46,4 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get a public status page * Get all a public status pages -## Example Usage - -This workflow allows you to create, update, and get a monitor using the UptimeRobot node. You can also find the [workflow](https://n8n.io/workflows/1112) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [UptimeRobot]() - -The final workflow should look like the following image. - -![A workflow with the UptimeRobot node](/_images/integrations/builtin/app-nodes/uptimerobot/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. UptimeRobot node (create: monitor) - -This node will create a new monitor of the type `HTTP(S)`. - -1. First of all, you'll have to enter credentials for the OpenWeatherMap node. You can find out how to do that [here](/integrations/builtin/credentials/openweathermap/). -2. Select 'Monitor' from the ***Resource*** dropdown list. -3. Select 'Create' from the ***Operation*** dropdown list. -4. Enter `n8n` in the ***Friendly Name*** field. -5. Select 'HTTP(S)' from the ***Type*** dropdown list. -6. Enter `https://n8n.io` in the ***URL*** field. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns data about the current weather in Berlin. - -![Using the OpenWeatherMap node to get weather updates for Berlin](/_images/integrations/builtin/app-nodes/uptimerobot/uptimerobot_node.png) - -### 3. UptimeRobot node (update: monitor) - -This node will update the monitor that we created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Monitor' from the ***Resource*** dropdown list. -3. Select 'Update' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`. -6. Click on ***Add Field*** and select 'Friendly Name' from the dropdown list. -7. Enter `n8n website` in the ***Friendly Name*** field. -8. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node updates the friendly name of the monitor that we created in the previous node. - -![Using the UptimeRobot node to update a monitor](/_images/integrations/builtin/app-nodes/uptimerobot/uptimerobot1_node.png) - -### 4. UptimeRobot node (get: monitor) - -This node will get the information of the monitor that we created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Monitor' from the ***Resource*** dropdown list. -3. Select 'Update' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns the information of the monitor that we created earlier. - -![Using the UptimeRobot node to retrieve information of a monitor](/_images/integrations/builtin/app-nodes/uptimerobot/uptimerobot2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectcloud.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectcloud.md index 410906bcc..4c097e41f 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectcloud.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectcloud.md @@ -36,7 +36,7 @@ Refer to [Venafi's REST API documentation](https://docs.venafi.cloud/api/vaas-re View [example workflows and related content](https://n8n.io/integrations/venafi-tls-protect-cloud/){:target=_blank .external-link} on n8n's website. n8n also provides: - + * A [trigger node](/integrations/builtin/trigger-nodes/n8n-nodes-base.venafitlsprotectcloudtrigger/) for Venafi TLS Protect Cloud. * A [node](/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectdatacenter/) for Venafi TLS Protect Datacenter. - + diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectdatacenter.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectdatacenter.md index f2c3f7713..280343357 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectdatacenter.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectdatacenter.md @@ -3,7 +3,8 @@ title: Venafi TLS Protect Datacenter description: Documentation for the Venafi TLS Protect Datacenter node in n8n, a workflow automation platform. Includes details of operations and configuration, and links to examples and credentials information. contentType: integration --- - + + # Venafi TLS Protect Datacenter Use the Venafi TLS Protect Datacenter node to automate work in Venafi TLS Protect Datacenter, and integrate Venafi TLS Protect Datacenter with other applications. n8n has built-in support for a wide range of Venafi TLS Protect Datacenter features, including creating, deleting, and getting certificates. @@ -36,3 +37,4 @@ n8n also provides: * A [node](/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectcloud/) and [trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.venafitlsprotectcloudtrigger/) node for Venafi TLS Protect Cloud. + \ No newline at end of file diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.vero.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.vero.md index 746690ab8..84dd908bf 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.vero.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.vero.md @@ -1,20 +1,20 @@ --- -title: Vero -description: Documentation for the Vero node in n8n, a workflow automation platform. Includes details of operations and configuration, and links to examples and credentials information. +title: VERO +description: Documentation for the VERO node in n8n, a workflow automation platform. Includes details of operations and configuration, and links to examples and credentials information. contentType: integration --- -# Vero +# VERO -Use the Vero node to automate work in Vero, and integrate Vero with other applications. n8n has built-in support for a wide range of Vero features, including creating and deleting users. +Use the VERO node to automate work in VERO, and integrate VERO with other applications. n8n has built-in support for a wide range of VERO features, including creating and deleting users. -On this page, you'll find a list of operations the Vero node supports and links to more resources. +On this page, you'll find a list of operations the VERO node supports and links to more resources. /// note | Credentials -Refer to [Vero credentials](/integrations/builtin/credentials/vero/) for guidance on setting up authentication. +Refer to [VERO credentials](/integrations/builtin/credentials/vero/) for guidance on setting up authentication. /// /// note | Examples and templates -For usage examples and templates to help you get started, take a look at n8n's [Vero integrations](https://n8n.io/integrations/vero/){:target="_blank" .external-link} list. +For usage examples and templates to help you get started, take a look at n8n's [VERO integrations](https://n8n.io/integrations/vero/){:target="_blank" .external-link} list. /// ## Basic Operations @@ -31,23 +31,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Track an event for a specific customer -## Example Usage - -This workflow allows you to create a user profile in Vero. You can also find the [workflow](https://n8n.io/workflows/499) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Vero]() - -The final workflow should look like the following image. - -![A workflow with the Vero node](/_images/integrations/builtin/app-nodes/vero/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Vero node - -1. First of all, you'll have to enter credentials for the Vero node. You can find out how to do that [here](/integrations/builtin/credentials/vero/). -2. Enter the unique identifier of the user in the *ID* field. -3. Click on *Execute Node* to run the workflow. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.webflow.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.webflow.md index 7f84ae8fe..fd41d4fc4 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.webflow.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.webflow.md @@ -26,97 +26,4 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get All * Update -## Example Usage - -This workflow allows you to create, update, and get an item from Webflow. You can also find the [workflow](https://n8n.io/workflows/1048) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Webflow]() - -The final workflow should look like the following image. - -![A workflow with the Webflow node](/_images/integrations/builtin/app-nodes/webflow/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Webflow node (create: item) - -This node will create a new collection of the type `Team Members` in Webflow. If you want to create a collection with a different type, use that type instead. - -1. First of all, you'll have to enter credentials for the Webflow node. You can find out how to do that [here](/integrations/builtin/credentials/webflow/). -2. Select 'Create' from the ***Operation*** dropdown list. -3. Select your site from the ***Site ID*** dropdown list. -4. Select 'Team Members' from the ***Collection ID*** dropdown list. -5. Click on the ***Add Field*** button. -6. Select 'Name (PlainText) (required)' from the ***Field ID*** dropdown list. If you're using a different collection type, select the field present in that collection. -7. Enter `n8n` in the ***Field Value*** field. -8. Click on the ***Add Field*** button. -9. Select 'Slug (PlainText) (required)' from the ***Field ID*** dropdown list. If you're using a different collection type, select the field present in that collection. -10. Enter `n8n` in the ***Field Value*** field. -11. Click on the ***Add Field*** button. -12. Select 'Archived (Bool) (required)' from the ***Field ID*** dropdown list. If you're using a different collection type, select the field present in that collection. -13. Enter `false` in the ***Field Value*** field. -14. Click on the ***Add Field*** button. -15. Select 'Draft (Bool) (required)' from the ***Field ID*** dropdown list. If you're using a different collection type, select the field present in that collection. -16. Enter `false` in the ***Field Value*** field. -17. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new item for the collection type `Team Members` in Webflow. - -![Using the Webflow node to create a new item](/_images/integrations/builtin/app-nodes/webflow/webflow_node.png) - - -### 3. Webflow1 node (update: item) - -This node will update the item that we created using the previous node. - -1. Select the credentials that you entered in the previous Webflow node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Select your site from the ***Site ID*** dropdown list. -4. Select 'Team Members' from the ***Collection ID*** dropdown list. -5. Click on the gears icon next to the ***Item ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > _id. You can also add the following expression: `{{$json["_id"]}}`. -7. Click on the ***Add Property*** button. -Click on the ***Add Field*** button. -8. Select 'Name (PlainText) (required)' from the ***Field ID*** dropdown list. If you're using a different collection type, select the field present in that collection. -9. Click on the gears icon next to the ***Field Value*** field and click on ***Add Expression***. -10. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > name. You can also add the following expression: `{{$json["name"]}}`. -11. Click on the ***Add Field*** button. -12. Select 'Slug (PlainText) (required)' from the ***Field ID*** dropdown list. If you're using a different collection type, select the field present in that collection. -13. Click on the gears icon next to the ***Field Value*** field and click on ***Add Expression***. -14. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > slug. You can also add the following expression: `{{$json["slug"]}}`. -15. Click on the ***Add Field*** button. -16. Select 'Archived (Bool) (required)' from the ***Field ID*** dropdown list. If you're using a different collection type, select the field present in that collection. -17. Click on the gears icon next to the ***Field Value*** field and click on ***Add Expression***. -18. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > _archived. You can also add the following expression: `{{$json["_archived"]}}`. -19. Click on the ***Add Field*** button. -20. Select 'Draft (Bool) (required)' from the ***Field ID*** dropdown list. If you're using a different collection type, select the field present in that collection. -21. Click on the gears icon next to the ***Field Value*** field and click on ***Add Expression***. -22. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > _draft. You can also add the following expression: `{{$json["_draft"]}}`. -23. Click on the ***Add Field*** button. -24. Select 'Avatar (ImageRef)' from the ***Field ID*** dropdown list. If you're using a different collection type, select the field present in that collection. -25. Enter `https://n8n.io/n8n-logo.png` in the ***Value*** field. -26. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node updates the item that got created previously. - -![Using the Webflow node to update an item](/_images/integrations/builtin/app-nodes/webflow/webflow1_node.png) - -### 4. Webflow2 node (get: item) - -This node will retrieve the information about the item that we created earlier. - - -1. Select the credentials that you entered in the previous Webflow node. -2. Select your site from the ***Site ID*** dropdown list. -3. Select 'Team Members' from the ***Collection ID*** dropdown list. -4. Click on the gears icon next to the ***Item ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > _id. You can also add the following expression: `{{$json["_id"]}}`. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node retrieves the information of the item that we created earlier. - -![Using the Webflow node to retrieve the information of an item](/_images/integrations/builtin/app-nodes/webflow/webflow2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.wise.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.wise.md index 3f1d0ae50..fd0f69853 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.wise.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.wise.md @@ -40,84 +40,3 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get * Get All -## Example Usage - -This workflow allows you to create a quote and a transfer, execute the transfer, and get the information of the transfer using the Wise node. You can also find the [workflow](https://n8n.io/workflows/992) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Wise]() - -The final workflow should look like the following image. - -![A workflow with the Wise node](/_images/integrations/builtin/app-nodes/wise/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Wise node (create: quote) - -This node will create a new quote in Wise. - -1. First of all, you'll have to enter credentials for the Wise node. You can find out how to do that [here](/integrations/builtin/credentials/wise/). -2. Select 'Quote' from the ***Resource*** dropdown list. -3. Select 'Create' from the ***Operation*** dropdown list. -4. Select a profile from the ***Profile ID*** dropdown list. -5. Select a target account from the ***Target Account ID*** dropdown list. -6. Enter an amount in the ***Amount*** field. -7. Enter the source currency in the ***Source Currency*** field. -8. Enter the target currency in the ***Target Currency*** field. -9. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new quote. - -![Using the Wise node to create a new quote](/_images/integrations/builtin/app-nodes/wise/wise_node.png) - -### 3. Wise1 node (create: transfer) - -This node will create a new transfer for the quote that we created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Transfer' from the ***Resource*** dropdown list. -3. Select a profile from the ***Profile ID*** dropdown list. -4. Click on the gears icon next to the ***Quote ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`. -6. Select the target account from the ***Target Account ID*** dropdown list. -7. Click on the ***Add Field*** button. -8. Enter a description in the ***Reference*** field. -9. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new transfer for the quote that we created in the previous node. - -![Using the Wise node to create a new transfer](/_images/integrations/builtin/app-nodes/wise/wise1_node.png) - -### 4. Wise2 node (execute: transfer) - -This node will execute the transfer that we created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Transfer' from the ***Resource*** dropdown list. -3. Select 'Execute' from the ***Operation*** dropdown list. -4. Select a profile from the ***Profile ID*** dropdown list. -5. Click on the gears icon next to the ***Transfer ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the executes the transfer that we created in the previous node. - -![Using the Wise node to execute a transfer](/_images/integrations/builtin/app-nodes/wise/wise2_node.png) - -### 5. Wise3 node (get: transfer) - -This node will return the information of the transfer that we executed in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Transfer' from the ***Resource*** dropdown list. -3. Select 'Get' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Transfer ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > Wise1 > Output Data > JSON > id. You can also add the following expression: `{{$node["Wise1"].json["id"]}}`. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the information about the transfer that we executed in the previous node. - -![Using the Wise node to get a transfer](/_images/integrations/builtin/app-nodes/wise/wise3_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.wordpress.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.wordpress.md index dddbadab2..d995d7d1f 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.wordpress.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.wordpress.md @@ -30,39 +30,5 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Get all users * Update a user -## Example Usage - -This workflow allows you to create and update a post in WordPress. You can also find the [workflow](https://n8n.io/workflows/668) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [WordPress]() - -The final workflow should look like the following image. - -![A workflow with the WordPress node](/_images/integrations/builtin/app-nodes/wordpress/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. WordPress node (create: post) - -1. First of all, you'll have to enter credentials for the WordPress node. You can find out how to do that [here](/integrations/builtin/credentials/wordpress/). -2. Enter the title in the ***Title*** field. -3. Click on ***Execute Node*** to run the workflow. - -![Using the WordPress node to create a new post](/_images/integrations/builtin/app-nodes/wordpress/wordpress_node.png) -### 3. WordPress1 node (update: post) - -1. Select the credentials that you entered in the previous node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Post ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > WordPress > Output Data > JSON > id. You can also add the following expression: `{{$node["Wordpress"].json["id"]}}`. -5. Click on the ***Add Field*** button and select 'Content' from the dropdown list. -6. Enter the content in the ***Content*** filed. -7. Click on ***Execute Node*** to run the workflow. - - -![Using the WordPress node to update the post](/_images/integrations/builtin/app-nodes/wordpress/wordpress1_node.png) - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.yourls.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.yourls.md index f551d323b..3eec8d992 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.yourls.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.yourls.md @@ -24,45 +24,5 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Shorten a URL * Get stats about one short URL -## Example Usage -This workflow allows you to create a short URL and get the statistics of the URL. You can also find the [workflow](https://n8n.io/workflows/815) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Yourls]() - -The final workflow should look like the following image. - -![A workflow with the Yourls node](/_images/integrations/builtin/app-nodes/yourls/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Yourls node (shorten: url) - -This node will create a short URL for the link we specify. - -1. First of all, you'll have to enter credentials for the Yourls node. You can find out how to do that [here](/integrations/builtin/credentials/yourls/). -2. Enter the URL that you want to shorten in the ***URL*** field. -3. Click on ***Add Field*** and select 'Title'. -4. Enter a title in the ***Title*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a short URL for the URL you specified. - -![Using the Yourls node to create short URL](/_images/integrations/builtin/app-nodes/yourls/yourls_node.png) - -### 3. Yourls1 node (stats: url) - -This node will give us the statistics of the short URL that we specify. We will get the statistics for the URL that we created in the previous step. - -1. Select the credentials that you entered in the previous node. -2. Select 'Stats' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Short URL*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Yourls > Output Data > JSON > shorturl. You can also add the following expression: `{{$node["Yourls"].json["shorturl"]}}`. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node gives us the statistics of the short URL that we created in the previous node. - -![Using the Yourls node to get the statistics of a short URL](/_images/integrations/builtin/app-nodes/yourls/yourls1_node.png) diff --git a/styles/Vocab/default/accept.txt b/styles/Vocab/default/accept.txt index caa82c06b..e16eb29b4 100644 --- a/styles/Vocab/default/accept.txt +++ b/styles/Vocab/default/accept.txt @@ -34,6 +34,8 @@ Bitwarden blockquote Boolean boolean +Borderless +borderless Brandfetch Brevo buildpack @@ -61,12 +63,15 @@ crypto Datastore Demio disabled +Disqus Dockerfile +Dropcontact eksctl Emelia Entra Enum enum +ERPNext Erroring erroring ESLint @@ -82,6 +87,8 @@ Firestore Formhub Fortinet Freshdesk +Freshservice +Freshworks gcloud geocoded geocodes @@ -89,6 +96,7 @@ Geospatial geospatial GIMP Gotify +Grafana Hetzner Homeserver HubSpot @@ -101,8 +109,10 @@ Iterable iterable Jira JMESPath +Keap Keycloak Kibana +Kitemaker kubectl Kafka Lemlist @@ -112,7 +122,13 @@ linter LLM Luhn Luxon +Magnetopause +magnetopause +Mailcheck Mailchimp +Mailgun +Mailjet +marketstack Mattermost Mautic Maximum @@ -126,20 +142,24 @@ millicore Mindee Minimum minimum +Mocean Motorhead Multiple multiple n8n namespace NASA +Netlify Nextcloud Nodelinter npm npx OAuth +Odoo Okta Ollama onboarding +Onfleet Oura Peekalink PhantomBuster @@ -164,13 +184,16 @@ Quickstarts quickstarts Realtime Rekognition +requester Rundeck +Salesmate Sekoia Sendy Serverless serverless Shopify shopify +Splunk Spontit Spotify Stackby @@ -182,6 +205,8 @@ strikethrough Subfolder subfolder sublist +Subreddit +subreddit Subtask subtask Supabase @@ -205,10 +230,15 @@ Twilio Typeahead typeahead Typeform +Unarchive +unarchive Unformatted unformatted +Unpublish +unpublish Unshare unshare +Untrash UpLead uProc Upsert @@ -219,6 +249,7 @@ URI URIs URL Venafi +VERO VM Vonage Vuex @@ -231,6 +262,8 @@ WordPress Wufoo Xata Xero +Zammad Zendesk Zep +Zoho Zscaler