diff --git a/docs/_redirects b/docs/_redirects index b8f4377a9..2ce9a2bb6 100644 --- a/docs/_redirects +++ b/docs/_redirects @@ -105,120 +105,120 @@ /nodes/node-basics/ /integrations/ /nodes/creating-nodes/ /integrations/creating-nodes/ /nodes/credentials/ /integrations/builtin/credentials/ -/nodes/n8n-nodes-base.actionNetwork/ /integrations/builtin/app-nodes/n8n-nodes-base.actionNetwork/ -/nodes/n8n-nodes-base.actionnetwork/ /integrations/builtin/app-nodes/n8n-nodes-base.actionNetwork/ -/nodes/n8n-nodes-base.activationTrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.activationTrigger/ -/nodes/n8n-nodes-base.activationtrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.activationTrigger/ -/nodes/n8n-nodes-base.activeCampaign/ /integrations/builtin/app-nodes/n8n-nodes-base.activeCampaign/ -/nodes/n8n-nodes-base.activecampaign/ /integrations/builtin/app-nodes/n8n-nodes-base.activeCampaign/ -/nodes/n8n-nodes-base.activeCampaignTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.activeCampaignTrigger/ -/nodes/n8n-nodes-base.activecampaigntrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.activeCampaignTrigger/ -/nodes/n8n-nodes-base.acuitySchedulingTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.acuitySchedulingTrigger/ -/nodes/n8n-nodes-base.acuityschedulingtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.acuitySchedulingTrigger/ +/nodes/n8n-nodes-base.actionNetwork/ /integrations/builtin/app-nodes/n8n-nodes-base.actionnetwork/ +/nodes/n8n-nodes-base.actionnetwork/ /integrations/builtin/app-nodes/n8n-nodes-base.actionnetwork/ +/nodes/n8n-nodes-base.activationTrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.activationtrigger/ +/nodes/n8n-nodes-base.activationtrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.activationtrigger/ +/nodes/n8n-nodes-base.activeCampaign/ /integrations/builtin/app-nodes/n8n-nodes-base.activecampaign/ +/nodes/n8n-nodes-base.activecampaign/ /integrations/builtin/app-nodes/n8n-nodes-base.activecampaign/ +/nodes/n8n-nodes-base.activeCampaignTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.activecampaigntrigger/ +/nodes/n8n-nodes-base.activecampaigntrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.activecampaigntrigger/ +/nodes/n8n-nodes-base.acuitySchedulingTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.acuityschedulingtrigger/ +/nodes/n8n-nodes-base.acuityschedulingtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.acuityschedulingtrigger/ /nodes/n8n-nodes-base.adalo/ /integrations/builtin/app-nodes.n8n-nodes-base.adalo/ /nodes/n8n-nodes-base.affinity/ /integrations/builtin/app-nodes/n8n-nodes-base.affinity/ -/nodes/n8n-nodes-base.affinityTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.affinityTrigger/ -/nodes/n8n-nodes-base.affinitytrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.affinityTrigger/ -/nodes/n8n-nodes-base.agileCrm/ /integrations/builtin/app-nodes/n8n-nodes-base.agileCrm/ +/nodes/n8n-nodes-base.affinityTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.affinitytrigger/ +/nodes/n8n-nodes-base.affinitytrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.affinitytrigger/ /nodes/n8n-nodes-base.agilecrm/ /integrations/builtin/app-nodes/n8n-nodes-base.agileCrm/ +/nodes/n8n-nodes-base.agilecrm/ /integrations/builtin/app-nodes/n8n-nodes-base.agilecrm/ /nodes/n8n-nodes-base.airtable/ /integrations/builtin/app-nodes/n8n-nodes-base.airtable/ -/nodes/n8n-nodes-base.airtableTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.airtableTrigger/ -/nodes/n8n-nodes-base.airtabletrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.airtableTrigger/ +/nodes/n8n-nodes-base.airtableTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.airtabletrigger/ +/nodes/n8n-nodes-base.airtabletrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.airtabletrigger/ /nodes/n8n-nodes-base.amqp/ /integrations/builtin/app-nodes/n8n-nodes-base.amqp/ -/nodes/n8n-nodes-base.amqpTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.amqpTrigger/ -/nodes/n8n-nodes-base.amqptrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.amqpTrigger/ -/nodes/n8n-nodes-base.apiTemplateIo/ /integrations/builtin/app-nodes/n8n-nodes-base.apiTemplateIo/ -/nodes/n8n-nodes-base.apitemplateio/ /integrations/builtin/app-nodes/n8n-nodes-base.apiTemplateIo/ +/nodes/n8n-nodes-base.amqpTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.amqptrigger/ +/nodes/n8n-nodes-base.amqptrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.amqptrigger/ +/nodes/n8n-nodes-base.apiTemplateIo/ /integrations/builtin/app-nodes/n8n-nodes-base.apitemplateio/ +/nodes/n8n-nodes-base.apitemplateio/ /integrations/builtin/app-nodes/n8n-nodes-base.apitemplateio/ /nodes/n8n-nodes-base.asana/ /integrations/builtin/app-nodes/n8n-nodes-base.asana/ -/nodes/n8n-nodes-base.asanaTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.asanaTrigger/ -/nodes/n8n-nodes-base.asanatrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.asanaTrigger/ +/nodes/n8n-nodes-base.asanaTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.asanatrigger/ +/nodes/n8n-nodes-base.asanatrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.asanatrigger/ /nodes/n8n-nodes-base.automizy/ /integrations/builtin/app-nodes/n8n-nodes-base.automizy/ /nodes/n8n-nodes-base.autopilot/ /integrations/builtin/app-nodes/n8n-nodes-base.autopilot/ -/nodes/n8n-nodes-base.autopilotTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.autopilotTrigger/ -/nodes/n8n-nodes-base.autopilottrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.autopilotTrigger/ -/nodes/n8n-nodes-base.awsComprehend/ /integrations/builtin/app-nodes/n8n-nodes-base.awsComprehend/ -/nodes/n8n-nodes-base.awscomprehend/ /integrations/builtin/app-nodes/n8n-nodes-base.awsComprehend/ -/nodes/n8n-nodes-base.awsDynamoDb/ /integrations/builtin/app-nodes/n8n-nodes-base.awsDynamoDb/ -/nodes/n8n-nodes-base.awsdynamodb/ /integrations/builtin/app-nodes/n8n-nodes-base.awsDynamoDb/ -/nodes/n8n-nodes-base.awsLambda/ /integrations/builtin/app-nodes/n8n-nodes-base.awsLambda/ -/nodes/n8n-nodes-base.awslambda/ /integrations/builtin/app-nodes/n8n-nodes-base.awsLambda/ -/nodes/n8n-nodes-base.awsRekognition/ /integrations/builtin/app-nodes/n8n-nodes-base.awsRekognition/ -/nodes/n8n-nodes-base.awsrekognition/ /integrations/builtin/app-nodes/n8n-nodes-base.awsRekognition/ -/nodes/n8n-nodes-base.awsS3/ /integrations/builtin/app-nodes/n8n-nodes-base.awsS3/ -/nodes/n8n-nodes-base.aws3/ /integrations/builtin/app-nodes/n8n-nodes-base.awsS3/ -/nodes/n8n-nodes-base.awsSes/ /integrations/builtin/app-nodes/n8n-nodes-base.awsSes/ -/nodes/n8n-nodes-base.awsses/ /integrations/builtin/app-nodes/n8n-nodes-base.awsSes/ -/nodes/n8n-nodes-base.awsSns/ /integrations/builtin/app-nodes/n8n-nodes-base.awsSns/ -/nodes/n8n-nodes-base.awssns/ /integrations/builtin/app-nodes/n8n-nodes-base.awsSns/ -/nodes/n8n-nodes-base.awsSnsTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.awsSnsTrigger/ -/nodes/n8n-nodes-base.awssnstrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.awsSnsTrigger/ -/nodes/n8n-nodes-base.awsSqs/ /integrations/builtin/app-nodes/n8n-nodes-base.awsSqs/ -/nodes/n8n-nodes-base.awssqs/ /integrations/builtin/app-nodes/n8n-nodes-base.awsSqs/ -/nodes/n8n-nodes-base.awsTextract/ /integrations/builtin/app-nodes/n8n-nodes-base.awsTextract/ -/nodes/n8n-nodes-base.awstextract/ /integrations/builtin/app-nodes/n8n-nodes-base.awsTextract/ -/nodes/n8n-nodes-base.awsTranscribe/ /integrations/builtin/app-nodes/n8n-nodes-base.awsTranscribe/ -/nodes/n8n-nodes-base.awstranscribe/ /integrations/builtin/app-nodes/n8n-nodes-base.awsTranscribe/ -/nodes/n8n-nodes-base.bambooHr/ /integrations/builtin/app-nodes/n8n-nodes-base.bambooHr/ -/nodes/n8n-nodes-base.bamboohr/ /integrations/builtin/app-nodes/n8n-nodes-base.bambooHr/ +/nodes/n8n-nodes-base.autopilotTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.autopilottrigger/ +/nodes/n8n-nodes-base.autopilottrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.autopilottrigger/ +/nodes/n8n-nodes-base.awsComprehend/ /integrations/builtin/app-nodes/n8n-nodes-base.awscomprehend/ +/nodes/n8n-nodes-base.awscomprehend/ /integrations/builtin/app-nodes/n8n-nodes-base.awscomprehend/ +/nodes/n8n-nodes-base.awsDynamoDb/ /integrations/builtin/app-nodes/n8n-nodes-base.awsdynamodb/ +/nodes/n8n-nodes-base.awsdynamodb/ /integrations/builtin/app-nodes/n8n-nodes-base.awsdynamodb/ +/nodes/n8n-nodes-base.awsLambda/ /integrations/builtin/app-nodes/n8n-nodes-base.awslambda/ +/nodes/n8n-nodes-base.awslambda/ /integrations/builtin/app-nodes/n8n-nodes-base.awslambda/ +/nodes/n8n-nodes-base.awsRekognition/ /integrations/builtin/app-nodes/n8n-nodes-base.awsrekognition/ +/nodes/n8n-nodes-base.awsrekognition/ /integrations/builtin/app-nodes/n8n-nodes-base.awsrekognition/ +/nodes/n8n-nodes-base.awsS3/ /integrations/builtin/app-nodes/n8n-nodes-base.awss3/ +/nodes/n8n-nodes-base.aws3/ /integrations/builtin/app-nodes/n8n-nodes-base.awss3/ +/nodes/n8n-nodes-base.awsSes/ /integrations/builtin/app-nodes/n8n-nodes-base.awsses/ +/nodes/n8n-nodes-base.awsses/ /integrations/builtin/app-nodes/n8n-nodes-base.awsses/ +/nodes/n8n-nodes-base.awsSns/ /integrations/builtin/app-nodes/n8n-nodes-base.awssns/ +/nodes/n8n-nodes-base.awssns/ /integrations/builtin/app-nodes/n8n-nodes-base.awssns/ +/nodes/n8n-nodes-base.awsSnsTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.awssnstrigger/ +/nodes/n8n-nodes-base.awssnstrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.awssnstrigger/ +/nodes/n8n-nodes-base.awsSqs/ /integrations/builtin/app-nodes/n8n-nodes-base.awssqs/ +/nodes/n8n-nodes-base.awssqs/ /integrations/builtin/app-nodes/n8n-nodes-base.awssqs/ +/nodes/n8n-nodes-base.awsTextract/ /integrations/builtin/app-nodes/n8n-nodes-base.awstextract/ +/nodes/n8n-nodes-base.awstextract/ /integrations/builtin/app-nodes/n8n-nodes-base.awstextract/ +/nodes/n8n-nodes-base.awsTranscribe/ /integrations/builtin/app-nodes/n8n-nodes-base.awstranscribe/ +/nodes/n8n-nodes-base.awstranscribe/ /integrations/builtin/app-nodes/n8n-nodes-base.awstranscribe/ +/nodes/n8n-nodes-base.bambooHr/ /integrations/builtin/app-nodes/n8n-nodes-base.bamboohr/ +/nodes/n8n-nodes-base.bamboohr/ /integrations/builtin/app-nodes/n8n-nodes-base.bamboohr/ /nodes/n8n-nodes-base.bannerbear/ /integrations/builtin/app-nodes/n8n-nodes-base.bannerbear/ /nodes/n8n-nodes-base.baserow/ /integrations/builtin/app-nodes/n8n-nodes-base.baserow/ /nodes/n8n-nodes-base.beeminder/ /integrations/builtin/app-nodes/n8n-nodes-base.beeminder/ -/nodes/n8n-nodes-base.bitbucketTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.bitbucketTrigger/ -/nodes/n8n-nodes-base.bitbuckettrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.bitbucketTrigger/ +/nodes/n8n-nodes-base.bitbucketTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.bitbuckettrigger/ +/nodes/n8n-nodes-base.bitbuckettrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.bitbuckettrigger/ /nodes/n8n-nodes-base.bitly/ /integrations/builtin/app-nodes/n8n-nodes-base.bitly/ /nodes/n8n-nodes-base.bitwarden/ /integrations/builtin/app-nodes/n8n-nodes-base.bitwarden/ /nodes/n8n-nodes-base.box/ /integrations/builtin/app-nodes/n8n-nodes-base.box/ -/nodes/n8n-nodes-base.boxTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.boxTrigger/ -/nodes/n8n-nodes-base.boxtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.boxTrigger/ -/nodes/n8n-nodes-base.Brandfetch/ /integrations/builtin/app-nodes/n8n-nodes-base.Brandfetch/ -/nodes/n8n-nodes-base.brandfetch/ /integrations/builtin/app-nodes/n8n-nodes-base.Brandfetch/ +/nodes/n8n-nodes-base.boxTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.boxtrigger/ +/nodes/n8n-nodes-base.boxtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.boxtrigger/ +/nodes/n8n-nodes-base.Brandfetch/ /integrations/builtin/app-nodes/n8n-nodes-base.brandfetch/ +/nodes/n8n-nodes-base.brandfetch/ /integrations/builtin/app-nodes/n8n-nodes-base.brandfetch/ /nodes/n8n-nodes-base.bubble/ /integrations/builtin/app-nodes/n8n-nodes-base.bubble/ -/nodes/n8n-nodes-base/calTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.calTrigger/ +/nodes/n8n-nodes-base/calTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.caltrigger/ /nodes/n8n-nodes-base/caltrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.caltrigger/ -/nodes/n8n-nodes-base.calendlyTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.calendlyTrigger/ -/nodes/n8n-nodes-base.calendlytrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.calendlyTrigger/ +/nodes/n8n-nodes-base.calendlyTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.calendlytrigger/ +/nodes/n8n-nodes-base.calendlytrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.calendlytrigger/ /nodes/n8n-nodes-base.chargebee/ /integrations/builtin/app-nodes/n8n-nodes-base.chargebee/ -/nodes/n8n-nodes-base.chargebeeTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.chargebeeTrigger/ -/nodes/n8n-nodes-base.chargebeetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.chargebeeTrigger/ -/nodes/n8n-nodes-base.circleCi/ /integrations/builtin/app-nodes/n8n-nodes-base.circleCi/ -/nodes/n8n-nodes-base.circleci/ /integrations/builtin/app-nodes/n8n-nodes-base.circleCi/ -/nodes/n8n-nodes-base.ciscoWebex/ /integrations/builtin/app-nodes/n8n-nodes-base.ciscoWebex/ -/nodes/n8n-nodes-base.ciscoWebexTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.ciscoWebexTrigger/ -/nodes/n8n-nodes-base.ciscoWebextrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.ciscoWebexTrigger/ +/nodes/n8n-nodes-base.chargebeeTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.chargebeetrigger/ +/nodes/n8n-nodes-base.chargebeetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.chargebeetrigger/ +/nodes/n8n-nodes-base.circleCi/ /integrations/builtin/app-nodes/n8n-nodes-base.circleci/ +/nodes/n8n-nodes-base.circleci/ /integrations/builtin/app-nodes/n8n-nodes-base.circleci/ +/nodes/n8n-nodes-base.ciscoWebex/ /integrations/builtin/app-nodes/n8n-nodes-base.ciscowebex/ +/nodes/n8n-nodes-base.ciscoWebexTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.ciscowebextrigger/ +/nodes/n8n-nodes-base.ciscoWebextrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.ciscowebextrigger/ /nodes/n8n-nodes-base.clearbit/ /integrations/builtin/app-nodes/n8n-nodes-base.clearbit/ -/nodes/n8n-nodes-base.clickUp/ /integrations/builtin/app-nodes/n8n-nodes-base.clickUp/ -/nodes/n8n-nodes-base.clickup/ /integrations/builtin/app-nodes/n8n-nodes-base.clickUp/ -/nodes/n8n-nodes-base.clickUpTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.clickUpTrigger/ -/nodes/n8n-nodes-base.clickUptrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.clickUpTrigger/ +/nodes/n8n-nodes-base.clickUp/ /integrations/builtin/app-nodes/n8n-nodes-base.clickup/ +/nodes/n8n-nodes-base.clickup/ /integrations/builtin/app-nodes/n8n-nodes-base.clickup/ +/nodes/n8n-nodes-base.clickUpTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.clickuptrigger/ +/nodes/n8n-nodes-base.clickUptrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.clickuptrigger/ /nodes/n8n-nodes-base.clockify/ /integrations/builtin/app-nodes/n8n-nodes-base.clockify/ -/nodes/n8n-nodes-base.clockifyTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.clockifyTrigger/ -/nodes/n8n-nodes-base.clockifytrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.clockifyTrigger/ +/nodes/n8n-nodes-base.clockifyTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.clockifytrigger/ +/nodes/n8n-nodes-base.clockifytrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.clockifytrigger/ /nodes/n8n-nodes-base.cockpit/ /integrations/builtin/app-nodes/n8n-nodes-base.cockpit/ /nodes/n8n-nodes-base.coda/ /integrations/builtin/app-nodes/n8n-nodes-base.coda/ -/nodes/n8n-nodes-base.coinGecko/ /integrations/builtin/app-nodes/n8n-nodes-base.coinGecko/ -/nodes/n8n-nodes-base.coingecko/ /integrations/builtin/app-nodes/n8n-nodes-base.coinGecko/ +/nodes/n8n-nodes-base.coinGecko/ /integrations/builtin/app-nodes/n8n-nodes-base.coingecko/ +/nodes/n8n-nodes-base.coingecko/ /integrations/builtin/app-nodes/n8n-nodes-base.coingecko/ /nodes/n8n-nodes-base.compression/ /integrations/builtin/core-nodes/n8n-nodes-base.compression/ /nodes/n8n-nodes-base.contentful/ /integrations/builtin/app-nodes/n8n-nodes-base.contentful/ -/nodes/n8n-nodes-base.convertKit/ /integrations/builtin/app-nodes/n8n-nodes-base.convertKit/ -/nodes/n8n-nodes-base.convertkit/ /integrations/builtin/app-nodes/n8n-nodes-base.convertKit/ -/nodes/n8n-nodes-base.convertKitTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.convertKitTrigger/ -/nodes/n8n-nodes-base.convertkittrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.convertKitTrigger/ +/nodes/n8n-nodes-base.convertKit/ /integrations/builtin/app-nodes/n8n-nodes-base.convertkit/ +/nodes/n8n-nodes-base.convertkit/ /integrations/builtin/app-nodes/n8n-nodes-base.convertkit/ +/nodes/n8n-nodes-base.convertKitTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.convertkittrigger/ +/nodes/n8n-nodes-base.convertkittrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.convertkittrigger/ /nodes/n8n-nodes-base.copper/ /integrations/builtin/app-nodes/n8n-nodes-base.copper/ -/nodes/n8n-nodes-base.copperTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.copperTrigger/ -/nodes/n8n-nodes-base.coppertrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.copperTrigger/ +/nodes/n8n-nodes-base.copperTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.coppertrigger/ +/nodes/n8n-nodes-base.coppertrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.coppertrigger/ /nodes/n8n-nodes-base.cortex/ /integrations/builtin/app-nodes/n8n-nodes-base.cortex/ -/nodes/n8n-nodes-base.crateDb/ /integrations/builtin/app-nodes/n8n-nodes-base.crateDb/ -/nodes/n8n-nodes-base.cratedb/ /integrations/builtin/app-nodes/n8n-nodes-base.crateDb/ +/nodes/n8n-nodes-base.crateDb/ /integrations/builtin/app-nodes/n8n-nodes-base.cratedb/ +/nodes/n8n-nodes-base.cratedb/ /integrations/builtin/app-nodes/n8n-nodes-base.cratedb/ /nodes/n8n-nodes-base.cron/ /integrations/builtin/core-nodes/n8n-nodes-base.cron/ /nodes/n8n-nodes-base.crypto/ /integrations/builtin/core-nodes/n8n-nodes-base.crypto/ -/nodes/n8n-nodes-base.customerIo/ /integrations/builtin/app-nodes/n8n-nodes-base.customerIo/ -/nodes/n8n-nodes-base.customerio/ /integrations/builtin/app-nodes/n8n-nodes-base.customerIo/ -/nodes/n8n-nodes-base.customerIoTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.customerIoTrigger/ -/nodes/n8n-nodes-base.customeriotrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.customerIoTrigger/ -/nodes/n8n-nodes-base.dateTime/ /integrations/builtin/core-nodes/n8n-nodes-base.dateTime/ -/nodes/n8n-nodes-base.datetime/ /integrations/builtin/app-nodes/n8n-nodes-base.dateTime/ -/nodes/n8n-nodes-base.deepL/ /integrations/builtin/app-nodes/n8n-nodes-base.deepL/ -/nodes/n8n-nodes-base.deepl/ /integrations/builtin/app-nodes/n8n-nodes-base.deepL/ +/nodes/n8n-nodes-base.customerIo/ /integrations/builtin/app-nodes/n8n-nodes-base.customerio/ +/nodes/n8n-nodes-base.customerio/ /integrations/builtin/app-nodes/n8n-nodes-base.customerio/ +/nodes/n8n-nodes-base.customerIoTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.customeriotrigger/ +/nodes/n8n-nodes-base.customeriotrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.customeriotrigger/ +/nodes/n8n-nodes-base.dateTime/ /integrations/builtin/core-nodes/n8n-nodes-base.datetime/ +/nodes/n8n-nodes-base.datetime/ /integrations/builtin/app-nodes/n8n-nodes-base.datetime/ +/nodes/n8n-nodes-base.deepL/ /integrations/builtin/app-nodes/n8n-nodes-base.deepl/ +/nodes/n8n-nodes-base.deepl/ /integrations/builtin/app-nodes/n8n-nodes-base.deepl/ /nodes/n8n-nodes-base.demio/ /integrations/builtin/app-nodes/n8n-nodes-base.demio/ /nodes/n8n-nodes-base.dhl/ /integrations/builtin/app-nodes/n8n-nodes-base.dhl/ /nodes/n8n-nodes-base.discord/ /integrations/builtin/app-nodes/n8n-nodes-base.discord/ @@ -227,447 +227,447 @@ /nodes/n8n-nodes-base.drift/ /integrations/builtin/app-nodes/n8n-nodes-base.drift/ /nodes/n8n-nodes-base.dropbox/ /integrations/builtin/app-nodes/n8n-nodes-base.dropbox/ /nodes/n8n-nodes-base.dropcontact/ /integrations/builtin/app-nodes/n8n-nodes-base.dropcontact/ -/nodes/n8n-nodes-base.editImage/ /integrations/builtin/core-nodes/n8n-nodes-base.editImage/ +/nodes/n8n-nodes-base.editImage/ /integrations/builtin/core-nodes/n8n-nodes-base.editimage/ /nodes/n8n-nodes-base.egoi/ /integrations/builtin/app-nodes/n8n-nodes-base.egoi/ /nodes/n8n-nodes-base.elasticsearch/ /integrations/builtin/app-nodes/n8n-nodes-base.elasticsearch/ -/nodes/n8n-nodes-base.elasticSecurity/ /integrations/builtin/app-nodes/n8n-nodes-base.elasticSecurity/ -/nodes/n8n-nodes-base.elasticsecurity/ /integrations/builtin/app-nodes/n8n-nodes-base.elasticSecurity/ +/nodes/n8n-nodes-base.elasticSecurity/ /integrations/builtin/app-nodes/n8n-nodes-base.elasticsecurity/ +/nodes/n8n-nodes-base.elasticsecurity/ /integrations/builtin/app-nodes/n8n-nodes-base.elasticsecurity/ /nodes/n8n-nodes-base.emailReadImap/ /integrations/builtin/core-nodes/n8n-nodes-base.emailimap/ /nodes/n8n-nodes-base.emailreadimap/ /integrations/builtin/core-nodes/n8n-nodes-base.emailimap/ -/nodes/n8n-nodes-base.emailSend/ /integrations/builtin/core-nodes/n8n-nodes-base.sendEmail/ -/nodes/n8n-nodes-base.emailsend/ /integrations/builtin/core-nodes/n8n-nodes-base.sendEmail/ +/nodes/n8n-nodes-base.emailSend/ /integrations/builtin/core-nodes/n8n-nodes-base.sendemail/ +/nodes/n8n-nodes-base.emailsend/ /integrations/builtin/core-nodes/n8n-nodes-base.sendemail/ /nodes/n8n-nodes-base.emelia/ /integrations/builtin/app-nodes/n8n-nodes-base.emelia/ -/nodes/n8n-nodes-base.emeliaTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.emeliaTrigger/ -/nodes/n8n-nodes-base.emeliatrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.emeliaTrigger/ -/nodes/n8n-nodes-base.erpNext/ /integrations/builtin/app-nodes/n8n-nodes-base.erpNext/ -/nodes/n8n-nodes-base.errorTrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.errorTrigger/ -/nodes/n8n-nodes-base.errortrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.errorTrigger/ -/nodes/n8n-nodes-base.eventbriteTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.eventbriteTrigger/ -/nodes/n8n-nodes-base.eventbritetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.eventbriteTrigger/ -/nodes/n8n-nodes-base.executeCommand/ /integrations/builtin/core-nodes/n8n-nodes-base.executeCommand/ -/nodes/n8n-nodes-base.executecommand/ /integrations/builtin/core-nodes/n8n-nodes-base.executeCommand/ -/nodes/n8n-nodes-base.executeWorkflow/ /integrations/builtin/core-nodes/n8n-nodes-base.executeWorkflow/ -/nodes/n8n-nodes-base.executeworkflow/ /integrations/builtin/core-nodes/n8n-nodes-base.executeWorkflow/ -/nodes/n8n-nodes-base.facebookGraphApi/ /integrations/builtin/app-nodes/n8n-nodes-base.facebookGraphAPI/ -/nodes/n8n-nodes-base.facebookgraphapi/ /integrations/builtin/app-nodes/n8n-nodes-base.facebookGraphAPI/ -/nodes/n8n-nodes-base.facebookTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.facebookTrigger/ -/nodes/n8n-nodes-base.facebooktrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.facebookTrigger/ -/nodes/n8n-nodes-base.figmaTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.figmaTrigger/ -/nodes/n8n-nodes-base.figmatrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.figmaTrigger/ +/nodes/n8n-nodes-base.emeliaTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.emeliatrigger/ +/nodes/n8n-nodes-base.emeliatrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.emeliatrigger/ +/nodes/n8n-nodes-base.erpNext/ /integrations/builtin/app-nodes/n8n-nodes-base.erpnext/ +/nodes/n8n-nodes-base.errorTrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.errortrigger/ +/nodes/n8n-nodes-base.errortrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.errortrigger/ +/nodes/n8n-nodes-base.eventbriteTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.eventbritetrigger/ +/nodes/n8n-nodes-base.eventbritetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.eventbritetrigger/ +/nodes/n8n-nodes-base.executeCommand/ /integrations/builtin/core-nodes/n8n-nodes-base.executecommand/ +/nodes/n8n-nodes-base.executecommand/ /integrations/builtin/core-nodes/n8n-nodes-base.executecommand/ +/nodes/n8n-nodes-base.executeWorkflow/ /integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/ +/nodes/n8n-nodes-base.executeworkflow/ /integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/ +/nodes/n8n-nodes-base.facebookGraphApi/ /integrations/builtin/app-nodes/n8n-nodes-base.facebookgraphapi/ +/nodes/n8n-nodes-base.facebookgraphapi/ /integrations/builtin/app-nodes/n8n-nodes-base.facebookgraphapi/ +/nodes/n8n-nodes-base.facebookTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.facebooktrigger/ +/nodes/n8n-nodes-base.facebooktrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.facebooktrigger/ +/nodes/n8n-nodes-base.figmaTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.figmatrigger/ +/nodes/n8n-nodes-base.figmatrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.figmatrigger/ /nodes/n8n-nodes-base.filemaker/ /integrations/builtin/app-nodes/n8n-nodes-base.filemaker/ /nodes/n8n-nodes-base.flow/ /integrations/builtin/app-nodes/n8n-nodes-base.flow/ -/nodes/n8n-nodes-base.flowTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.flowTrigger/ -/nodes/n8n-nodes-base.flowtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.flowTrigger/ -/nodes/n8n-nodes-base.formIoTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.formIoTrigger/ -/nodes/n8n-nodes-base.formiotrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.formIoTrigger/ -/nodes/n8n-nodes-base.formstackTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.formstackTrigger/ -/nodes/n8n-nodes-base.formstacktrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.formstackTrigger/ +/nodes/n8n-nodes-base.flowtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.flowtrigger/ +/nodes/n8n-nodes-base.flowtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.flowtrigger/ +/nodes/n8n-nodes-base.formIotrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.formiotrigger/ +/nodes/n8n-nodes-base.formiotrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.formiotrigger/ +/nodes/n8n-nodes-base.formstackTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.formstacktrigger/ +/nodes/n8n-nodes-base.formstacktrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.formstacktrigger/ /nodes/n8n-nodes-base.freshdesk/ /integrations/builtin/app-nodes/n8n-nodes-base.freshdesk/ /nodes/n8n-nodes-base.freshservice/ /integrations/builtin/app-nodes/n8n-nodes-base.freshservice/ -/nodes/n8n-nodes-base.freshworksCrm/ /integrations/builtin/app-nodes/n8n-nodes-base.freshworksCrm/ -/nodes/n8n-nodes-base.freshworkscrm/ /integrations/builtin/app-nodes/n8n-nodes-base.freshworksCrm/ +/nodes/n8n-nodes-base.freshworksCrm/ /integrations/builtin/app-nodes/n8n-nodes-base.freshworkscrm/ +/nodes/n8n-nodes-base.freshworkscrm/ /integrations/builtin/app-nodes/n8n-nodes-base.freshworkscrm/ /nodes/n8n-nodes-base.ftp/ /integrations/builtin/core-nodes/n8n-nodes-base.ftp/ /nodes/n8n-nodes-base.function/ /integrations/builtin/core-nodes/n8n-nodes-base.code/ /nodes/n8n-nodes-base.functionItem/ /integrations/builtin/core-nodes/n8n-nodes-base.code/ /nodes/n8n-nodes-base.functionitem/ /integrations/builtin/core-nodes/n8n-nodes-base.code/ -/nodes/n8n-nodes-base.getResponse/ /integrations/builtin/app-nodes/n8n-nodes-base.getResponse/ -/nodes/n8n-nodes-base.getresponse/ /integrations/builtin/app-nodes/n8n-nodes-base.getResponse/ -/nodes/n8n-nodes-base.getResponseTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.getResponseTrigger/ -/nodes/n8n-nodes-base.getresponsetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.getResponseTrigger/ +/nodes/n8n-nodes-base.getResponse/ /integrations/builtin/app-nodes/n8n-nodes-base.getresponse/ +/nodes/n8n-nodes-base.getresponse/ /integrations/builtin/app-nodes/n8n-nodes-base.getresponse/ +/nodes/n8n-nodes-base.getResponseTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.getresponsetrigger/ +/nodes/n8n-nodes-base.getresponsetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.getresponsetrigger/ /nodes/n8n-nodes-base.ghost/ /integrations/builtin/app-nodes/n8n-nodes-base.ghost/ /nodes/n8n-nodes-base.git/ /integrations/builtin/core-nodes/n8n-nodes-base.git/ /nodes/n8n-nodes-base.github/ /integrations/builtin/app-nodes/n8n-nodes-base.github/ -/nodes/n8n-nodes-base.githubTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.githubTrigger/ -/nodes/n8n-nodes-base.githubtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.githubTrigger/ +/nodes/n8n-nodes-base.githubTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.githubtrigger/ +/nodes/n8n-nodes-base.githubtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.githubtrigger/ /nodes/n8n-nodes-base.gitlab/ /integrations/builtin/app-nodes/n8n-nodes-base.gitlab/ -/nodes/n8n-nodes-base.gitlabTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.gitlabTrigger/ -/nodes/n8n-nodes-base.gitlabtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.gitlabTrigger/ +/nodes/n8n-nodes-base.gitlabTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.gitlabtrigger/ +/nodes/n8n-nodes-base.gitlabtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.gitlabtrigger/ /nodes/n8n-nodes-base.gmail/ /integrations/builtin/app-nodes/n8n-nodes-base.gmail/ /nodes/n8n-nodes-base.gmailTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.gmailtrigger/ -/nodes/n8n-nodes-base.googleAds/ /integrations/builtin/app-nodes/n8n-nodes-base.googleAds/ -/nodes/n8n-nodes-base.googleads/ /integrations/builtin/app-nodes/n8n-nodes-base.googleAds/ -/nodes/n8n-nodes-base.googleAnalytics/ /integrations/builtin/app-nodes/n8n-nodes-base.googleAnalytics/ -/nodes/n8n-nodes-base.googleanalytics/ /integrations/builtin/app-nodes/n8n-nodes-base.googleAnalytics/ -/nodes/n8n-nodes-base.googleBigQuery/ /integrations/builtin/app-nodes/n8n-nodes-base.googleBigQuery/ -/nodes/n8n-nodes-base.googlebigquery/ /integrations/builtin/app-nodes/n8n-nodes-base.googleBigQuery/ -/nodes/n8n-nodes-base.googleBooks/ /integrations/builtin/app-nodes/n8n-nodes-base.googleBooks/ -/nodes/n8n-nodes-base.googlebooks/ /integrations/builtin/app-nodes/n8n-nodes-base.googleBooks/ -/nodes/n8n-nodes-base.googleCalendar/ /integrations/builtin/app-nodes/n8n-nodes-base.googleCalendar/ -/nodes/n8n-nodes-base.googlecalendar/ /integrations/builtin/app-nodes/n8n-nodes-base.googleCalendar/ -/nodes/n8n-nodes-base.googleCalendarTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.googleCalendarTrigger/ -/nodes/n8n-nodes-base.googlecalendartrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.googleCalendarTrigger/ +/nodes/n8n-nodes-base.googleAds/ /integrations/builtin/app-nodes/n8n-nodes-base.googleads/ +/nodes/n8n-nodes-base.googleads/ /integrations/builtin/app-nodes/n8n-nodes-base.googleads/ +/nodes/n8n-nodes-base.googleAnalytics/ /integrations/builtin/app-nodes/n8n-nodes-base.googleanalytics/ +/nodes/n8n-nodes-base.googleanalytics/ /integrations/builtin/app-nodes/n8n-nodes-base.googleanalytics/ +/nodes/n8n-nodes-base.googleBigQuery/ /integrations/builtin/app-nodes/n8n-nodes-base.googlebigquery/ +/nodes/n8n-nodes-base.googlebigquery/ /integrations/builtin/app-nodes/n8n-nodes-base.googlebigquery/ +/nodes/n8n-nodes-base.googleBooks/ /integrations/builtin/app-nodes/n8n-nodes-base.googlebooks/ +/nodes/n8n-nodes-base.googlebooks/ /integrations/builtin/app-nodes/n8n-nodes-base.googlebooks/ +/nodes/n8n-nodes-base.googleCalendar/ /integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/ +/nodes/n8n-nodes-base.googlecalendar/ /integrations/builtin/app-nodes/n8n-nodes-base.googlecalendar/ +/nodes/n8n-nodes-base.googleCalendarTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.googlecalendartrigger/ +/nodes/n8n-nodes-base.googlecalendartrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.googlecalendartrigger/ /nodes/n8n-nodes-base.googleCloudStorage/ /integrations/builtin/app-nodes/n8n-nodes-base.googlecloudstorage/ -/nodes/n8n-nodes-base.googleChat/ /integrations/builtin/app-nodes/n8n-nodes-base.googleChat/ -/nodes/n8n-nodes-base.googlechat/ /integrations/builtin/app-nodes/n8n-nodes-base.googleChat/ -/nodes/n8n-nodes-base.googleCloudNaturalLanguage/ /integrations/builtin/app-nodes/n8n-nodes-base.googleCloudNaturalLanguage/ -/nodes/n8n-nodes-base.googlecloudnaturallanguage/ /integrations/builtin/app-nodes/n8n-nodes-base.googleCloudNaturalLanguage/ -/nodes/n8n-nodes-base.googleContacts/ /integrations/builtin/app-nodes/n8n-nodes-base.googleContacts/ -/nodes/n8n-nodes-base.googlecontacts/ /integrations/builtin/app-nodes/n8n-nodes-base.googleContacts/ -/nodes/n8n-nodes-base.googleDocs/ /integrations/builtin/app-nodes/n8n-nodes-base.googleDocs/ -/nodes/n8n-nodes-base.googledocs/ /integrations/builtin/app-nodes/n8n-nodes-base.googleDocs/ -/nodes/n8n-nodes-base.googleDrive/ /integrations/builtin/app-nodes/n8n-nodes-base.googleDrive/ -/nodes/n8n-nodes-base.googledrive/ /integrations/builtin/app-nodes/n8n-nodes-base.googleDrive/ -/nodes/n8n-nodes-base.googleDriveTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.googleDriveTrigger/ -/nodes/n8n-nodes-base.googledrivetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.googleDriveTrigger/ -/nodes/n8n-nodes-base.googleFirebaseCloudFirestore/ /integrations/builtin/app-nodes/n8n-nodes-base.googleCloudFirestore/ -/nodes/n8n-nodes-base.googlefirebasecloudfirestore/ /integrations/builtin/app-nodes/n8n-nodes-base.googleCloudFirestore/ -/nodes/n8n-nodes-base.googleFirebaseRealtimeDatabase/ /integrations/builtin/app-nodes/n8n-nodes-base.googleCloudRealtimeDatabase/ -/nodes/n8n-nodes-base.googlefirebaserealtimedatabase/ /integrations/builtin/app-nodes/n8n-nodes-base.googleFirebaseRealtimeDatabase/ -/nodes/n8n-nodes-base.googlePerspective/ /integrations/builtin/app-nodes/n8n-nodes-base.googlePerspective/ -/nodes/n8n-nodes-base.googleperspective/ /integrations/builtin/app-nodes/n8n-nodes-base.googlePerspective/ -/nodes/n8n-nodes-base.googleSheets/ /integrations/builtin/app-nodes/n8n-nodes-base.googleSheets/ -/nodes/n8n-nodes-base.googlesheets/ /integrations/builtin/app-nodes/n8n-nodes-base.googleSheets/ -/nodes/n8n-nodes-base.googleSlides/ /integrations/builtin/app-nodes/n8n-nodes-base.googleSlides/ -/nodes/n8n-nodes-base.googleslides/ /integrations/builtin/app-nodes/n8n-nodes-base.googleSlides/ -/nodes/n8n-nodes-base.googleTasks/ /integrations/builtin/app-nodes/n8n-nodes-base.googleTasks/ -/nodes/n8n-nodes-base.googletasks/ /integrations/builtin/app-nodes/n8n-nodes-base.googleTasks/ -/nodes/n8n-nodes-base.googleTranslate/ /integrations/builtin/app-nodes/n8n-nodes-base.googleTranslate/ -/nodes/n8n-nodes-base.googletranslate/ /integrations/builtin/app-nodes/n8n-nodes-base.googleTranslate/ +/nodes/n8n-nodes-base.googleChat/ /integrations/builtin/app-nodes/n8n-nodes-base.googlechat/ +/nodes/n8n-nodes-base.googlechat/ /integrations/builtin/app-nodes/n8n-nodes-base.googlechat/ +/nodes/n8n-nodes-base.googleCloudNaturalLanguage/ /integrations/builtin/app-nodes/n8n-nodes-base.googlecloudnaturallanguage/ +/nodes/n8n-nodes-base.googlecloudnaturallanguage/ /integrations/builtin/app-nodes/n8n-nodes-base.googlecloudnaturallanguage/ +/nodes/n8n-nodes-base.googleContacts/ /integrations/builtin/app-nodes/n8n-nodes-base.googlecontacts/ +/nodes/n8n-nodes-base.googlecontacts/ /integrations/builtin/app-nodes/n8n-nodes-base.googlecontacts/ +/nodes/n8n-nodes-base.googleDocs/ /integrations/builtin/app-nodes/n8n-nodes-base.googledocs/ +/nodes/n8n-nodes-base.googledocs/ /integrations/builtin/app-nodes/n8n-nodes-base.googledocs/ +/nodes/n8n-nodes-base.googleDrive/ /integrations/builtin/app-nodes/n8n-nodes-base.googledrive/ +/nodes/n8n-nodes-base.googledrive/ /integrations/builtin/app-nodes/n8n-nodes-base.googledrive/ +/nodes/n8n-nodes-base.googleDriveTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.googledrivetrigger/ +/nodes/n8n-nodes-base.googledrivetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.googledrivetrigger/ +/nodes/n8n-nodes-base.googleFirebaseCloudFirestore/ /integrations/builtin/app-nodes/n8n-nodes-base.googlecloudfirestore/ +/nodes/n8n-nodes-base.googlefirebasecloudfirestore/ /integrations/builtin/app-nodes/n8n-nodes-base.googlecloudfirestore/ +/nodes/n8n-nodes-base.googleFirebaseRealtimeDatabase/ /integrations/builtin/app-nodes/n8n-nodes-base.googlecloudrealtimedatabase/ +/nodes/n8n-nodes-base.googlefirebaserealtimedatabase/ /integrations/builtin/app-nodes/n8n-nodes-base.googlefirebaserealtimedatabase/ +/nodes/n8n-nodes-base.googlePerspective/ /integrations/builtin/app-nodes/n8n-nodes-base.googleperspective/ +/nodes/n8n-nodes-base.googleperspective/ /integrations/builtin/app-nodes/n8n-nodes-base.googleperspective/ +/nodes/n8n-nodes-base.googleSheets/ /integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/ +/nodes/n8n-nodes-base.googlesheets/ /integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/ +/nodes/n8n-nodes-base.googleSlides/ /integrations/builtin/app-nodes/n8n-nodes-base.googleslides/ +/nodes/n8n-nodes-base.googleslides/ /integrations/builtin/app-nodes/n8n-nodes-base.googleslides/ +/nodes/n8n-nodes-base.googleTasks/ /integrations/builtin/app-nodes/n8n-nodes-base.googletasks/ +/nodes/n8n-nodes-base.googletasks/ /integrations/builtin/app-nodes/n8n-nodes-base.googletasks/ +/nodes/n8n-nodes-base.googleTranslate/ /integrations/builtin/app-nodes/n8n-nodes-base.googletranslate/ +/nodes/n8n-nodes-base.googletranslate/ /integrations/builtin/app-nodes/n8n-nodes-base.googletranslate/ /nodes/n8n-nodes-base.gotify/ /integrations/builtin/app-nodes/n8n-nodes-base.gotify/ -/nodes/n8n-nodes-base.goToWebinar/ /integrations/builtin/app-nodes/n8n-nodes-base.goToWebinar/ -/nodes/n8n-nodes-base.gotowebinar/ /integrations/builtin/app-nodes/n8n-nodes-base.goToWebinar/ +/nodes/n8n-nodes-base.goToWebinar/ /integrations/builtin/app-nodes/n8n-nodes-base.gotowebinar/ +/nodes/n8n-nodes-base.gotowebinar/ /integrations/builtin/app-nodes/n8n-nodes-base.gotowebinar/ /nodes/n8n-nodes-base.grafana/ /integrations/builtin/app-nodes/n8n-nodes-base.grafana/ /nodes/n8n-nodes-base.graphql/ /integrations/builtin/core-nodes/n8n-nodes-base.graphql/ /nodes/n8n-nodes-base.grist/ /integrations/builtin/app-nodes/n8n-nodes-base.grist/ -/nodes/n8n-nodes-base.gSuiteAdmin/ /integrations/builtin/app-nodes/n8n-nodes-base.gSuiteAdmin/ -/nodes/n8n-nodes-base.gsuiteadmin/ /integrations/builtin/app-nodes/n8n-nodes-base.gSuiteAdmin/ -/nodes/n8n-nodes-base.gumroadTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.gumroadTrigger/ -/nodes/n8n-nodes-base.gumroadtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.gumroadTrigger/ -/nodes/n8n-nodes-base.hackerNews/ /integrations/builtin/app-nodes/n8n-nodes-base.hackerNews/ -/nodes/n8n-nodes-base.hackernews/ /integrations/builtin/app-nodes/n8n-nodes-base.hackerNews/ -/nodes/n8n-nodes-base.haloPSA/ /integrations/builtin/app-nodes/n8n-nodes-base.haloPSA/ -/nodes/n8n-nodes-base.halopsa/ /integrations/builtin/app-nodes/n8n-nodes-base.haloPSA/ +/nodes/n8n-nodes-base.gSuiteAdmin/ /integrations/builtin/app-nodes/n8n-nodes-base.gsuiteadmin/ +/nodes/n8n-nodes-base.gsuiteadmin/ /integrations/builtin/app-nodes/n8n-nodes-base.gsuiteadmin/ +/nodes/n8n-nodes-base.gumroadTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.gumroadtrigger/ +/nodes/n8n-nodes-base.gumroadtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.gumroadtrigger/ +/nodes/n8n-nodes-base.hackerNews/ /integrations/builtin/app-nodes/n8n-nodes-base.hackernews/ +/nodes/n8n-nodes-base.hackernews/ /integrations/builtin/app-nodes/n8n-nodes-base.hackernews/ +/nodes/n8n-nodes-base.haloPSA/ /integrations/builtin/app-nodes/n8n-nodes-base.halopsa/ +/nodes/n8n-nodes-base.halopsa/ /integrations/builtin/app-nodes/n8n-nodes-base.halopsa/ /nodes/n8n-nodes-base.harvest/ /integrations/builtin/app-nodes/n8n-nodes-base.harvest/ -/nodes/n8n-nodes-base.helpScout/ /integrations/builtin/app-nodes/n8n-nodes-base.helpScout/ -/nodes/n8n-nodes-base.helpscout/ /integrations/builtin/app-nodes/n8n-nodes-base.helpScout/ -/nodes/n8n-nodes-base.helpScoutTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.helpScoutTrigger/ -/nodes/n8n-nodes-base.helpscouttrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.helpScoutTrigger/ -/nodes/n8n-nodes-base.highLevel/ /integrations/builtin/app-nodes/n8n-nodes-base.highLevel/ +/nodes/n8n-nodes-base.helpScout/ /integrations/builtin/app-nodes/n8n-nodes-base.helpscout/ +/nodes/n8n-nodes-base.helpscout/ /integrations/builtin/app-nodes/n8n-nodes-base.helpscout/ +/nodes/n8n-nodes-base.helpScoutTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.helpscouttrigger/ +/nodes/n8n-nodes-base.helpscouttrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.helpscouttrigger/ +/nodes/n8n-nodes-base.highLevel/ /integrations/builtin/app-nodes/n8n-nodes-base.highlevel/ /nodes/n8n-nodes-base.highlevel/ /integrations/builtin/app-nodes/n8n-nodes-base.highlevel/ -/nodes/n8n-nodes-base.homeAssistant/ /integrations/builtin/app-nodes/n8n-nodes-base.homeAssistant/ -/nodes/n8n-nodes-base.homeassistant/ /integrations/builtin/app-nodes/n8n-nodes-base.homeAssistant/ -/nodes/n8n-nodes-base.htmlExtract/ /integrations/builtin/core-nodes/n8n-nodes-base.htmlExtract/ -/nodes/n8n-nodes-base.htmlextract/ /integrations/builtin/core-nodes/n8n-nodes-base.htmlExtract/ -/nodes/n8n-nodes-base.httpRequest/ /integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/ -/nodes/n8n-nodes-base.httprequest/ /integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/ +/nodes/n8n-nodes-base.homeAssistant/ /integrations/builtin/app-nodes/n8n-nodes-base.homeassistant/ +/nodes/n8n-nodes-base.homeassistant/ /integrations/builtin/app-nodes/n8n-nodes-base.homeassistant/ +/nodes/n8n-nodes-base.htmlExtract/ /integrations/builtin/core-nodes/n8n-nodes-base.htmlextract/ +/nodes/n8n-nodes-base.htmlextract/ /integrations/builtin/core-nodes/n8n-nodes-base.htmlextract/ +/nodes/n8n-nodes-base.httpRequest/ /integrations/builtin/core-nodes/n8n-nodes-base.httprequest/ +/nodes/n8n-nodes-base.httprequest/ /integrations/builtin/core-nodes/n8n-nodes-base.httprequest/ /nodes/n8n-nodes-base.hubspot/ /integrations/builtin/app-nodes/n8n-nodes-base.hubspot/ -/nodes/n8n-nodes-base.hubspotTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.hubspotTrigger/ -/nodes/n8n-nodes-base.hubspottrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.hubspotTrigger/ -/nodes/n8n-nodes-base.humanticAi/ /integrations/builtin/app-nodes/n8n-nodes-base.humanticAi/ -/nodes/n8n-nodes-base.humanticai/ /integrations/builtin/app-nodes/n8n-nodes-base.humanticAi/ +/nodes/n8n-nodes-base.hubspotTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.hubspottrigger/ +/nodes/n8n-nodes-base.hubspottrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.hubspottrigger/ +/nodes/n8n-nodes-base.humanticAi/ /integrations/builtin/app-nodes/n8n-nodes-base.humanticai/ +/nodes/n8n-nodes-base.humanticai/ /integrations/builtin/app-nodes/n8n-nodes-base.humanticai/ /nodes/n8n-nodes-base.hunter/ /integrations/builtin/app-nodes/n8n-nodes-base.hunter/ -/nodes/n8n-nodes-base.iCal/ /integrations/builtin/core-nodes/n8n-nodes-base.iCal/ +/nodes/n8n-nodes-base.iCal/ /integrations/builtin/core-nodes/n8n-nodes-base.ical/ /nodes/n8n-nodes-base.if/ /integrations/builtin/core-nodes/n8n-nodes-base.if/ /nodes/n8n-nodes-base.intercom/ /integrations/builtin/app-nodes/n8n-nodes-base.intercom/ /nodes/n8n-nodes-base.interval/ /integrations/builtin/core-nodes/n8n-nodes-base.interval/ -/nodes/n8n-nodes-base.invoiceNinja/ /integrations/builtin/app-nodes/n8n-nodes-base.invoiceNinja/ -/nodes/n8n-nodes-base.invoiceninja/ /integrations/builtin/app-nodes/n8n-nodes-base.invoiceNinja/ -/nodes/n8n-nodes-base.invoiceNinjaTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.invoiceNinjaTrigger/ -/nodes/n8n-nodes-base.invoiceninjatrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.invoiceNinjaTrigger/ -/nodes/n8n-nodes-base.itemLists/ /integrations/builtin/core-nodes/n8n-nodes-base.itemLists/ -/nodes/n8n-nodes-base.itemlists/ /integrations/builtin/core-nodes/n8n-nodes-base.itemLists/ +/nodes/n8n-nodes-base.invoiceNinja/ /integrations/builtin/app-nodes/n8n-nodes-base.invoiceninja/ +/nodes/n8n-nodes-base.invoiceninja/ /integrations/builtin/app-nodes/n8n-nodes-base.invoiceninja/ +/nodes/n8n-nodes-base.invoiceNinjaTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.invoiceninjatrigger/ +/nodes/n8n-nodes-base.invoiceninjatrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.invoiceninjatrigger/ +/nodes/n8n-nodes-base.itemLists/ /integrations/builtin/core-nodes/n8n-nodes-base.itemlists/ +/nodes/n8n-nodes-base.itemlists/ /integrations/builtin/core-nodes/n8n-nodes-base.itemlists/ /nodes/n8n-nodes-base.iterable/ /integrations/builtin/app-nodes/n8n-nodes-base.iterable/ /nodes/n8n-nodes-base.jenkins/ /integrations/builtin/app-nodes/n8n-nodes-base.jenkins/ /nodes/n8n-nodes-base.jira/ /integrations/builtin/app-nodes/n8n-nodes-base.jira/ -/nodes/n8n-nodes-base.jiraTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.jiraTrigger/ -/nodes/n8n-nodes-base.jiratrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.jiraTrigger/ -/nodes/n8n-nodes-base.jotFormTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.jotFormTrigger/ -/nodes/n8n-nodes-base.jotFormtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.jotFormTrigger/ +/nodes/n8n-nodes-base.jiraTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.jiratrigger/ +/nodes/n8n-nodes-base.jiratrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.jiratrigger/ +/nodes/n8n-nodes-base.jotFormTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.jotformtrigger/ +/nodes/n8n-nodes-base.jotformtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.jotformtrigger/ /nodes/n8n-nodes-base.kafka/ /integrations/builtin/app-nodes/n8n-nodes-base.kafka/ -/nodes/n8n-nodes-base.kafkaTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.kafkaTrigger/ -/nodes/n8n-nodes-base.kafkatrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.kafkaTrigger/ +/nodes/n8n-nodes-base.kafkaTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.kafkatrigger/ +/nodes/n8n-nodes-base.kafkatrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.kafkatrigger/ /nodes/n8n-nodes-base.keap/ /integrations/builtin/app-nodes/n8n-nodes-base.keap/ -/nodes/n8n-nodes-base.keapTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.keapTrigger/ -/nodes/n8n-nodes-base.keaptrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.keapTrigger/ +/nodes/n8n-nodes-base.keapTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.keaptrigger/ +/nodes/n8n-nodes-base.keaptrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.keaptrigger/ /nodes/n8n-nodes-base.kitemaker/ /integrations/builtin/app-nodes/n8n-nodes-base.kitemaker/ -/nodes/n8n-nodes-base.koBoToolbox/ /integrations/builtin/app-nodes/n8n-nodes-base.koBoToolbox/ -/nodes/n8n-nodes-base.kobotoolbox/ /integrations/builtin/app-nodes/n8n-nodes-base.koBoToolbox/ -/nodes/n8n-nodes-base.koBoToolboxTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.koBoToolboxTrigger/ -/nodes/n8n-nodes-base.kobotoolboxtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.koBoToolboxTrigger/ +/nodes/n8n-nodes-base.koBoToolbox/ /integrations/builtin/app-nodes/n8n-nodes-base.kobotoolbox/ +/nodes/n8n-nodes-base.kobotoolbox/ /integrations/builtin/app-nodes/n8n-nodes-base.kobotoolbox/ +/nodes/n8n-nodes-base.koBoToolboxTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.kobotoolboxtrigger/ +/nodes/n8n-nodes-base.kobotoolboxtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.kobotoolboxtrigger/ /nodes/n8n-nodes-base.lemlist/ /integrations/builtin/app-nodes/n8n-nodes-base.lemlist/ -/nodes/n8n-nodes-base.lemlistTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.lemlistTrigger/ -/nodes/n8n-nodes-base.lemlisttrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.lemlistTrigger/ +/nodes/n8n-nodes-base.lemlistTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.lemlisttrigger/ +/nodes/n8n-nodes-base.lemlisttrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.lemlisttrigger/ /nodes/n8n-nodes-base.line/ /integrations/builtin/app-nodes/n8n-nodes-base.line/ /nodes/n8n-nodes-base.linear/ /integrations/builtin/app-nodes/n8n-nodes-base.linear/ -/nodes/n8n-nodes-base.linearTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.linearTrigger/ -/nodes/n8n-nodes-base.lineartrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.linearTrigger/ -/nodes/n8n-nodes-base.lingvaNex/ /integrations/builtin/app-nodes/n8n-nodes-base.lingvaNex/ -/nodes/n8n-nodes-base.lingvanex/ /integrations/builtin/app-nodes/n8n-nodes-base.lingvaNex/ -/nodes/n8n-nodes-base.linkedIn/ /integrations/builtin/app-nodes/n8n-nodes-base.linkedIn/ -/nodes/n8n-nodes-base.linkedin/ /integrations/builtin/app-nodes/n8n-nodes-base.linkedIn/ -/nodes/n8n-nodes-base.localFileTrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.localFileTrigger/ -/nodes/n8n-nodes-base.localfiletrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.localFileTrigger/ +/nodes/n8n-nodes-base.linearTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.lineartrigger/ +/nodes/n8n-nodes-base.lineartrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.lineartrigger/ +/nodes/n8n-nodes-base.lingvaNex/ /integrations/builtin/app-nodes/n8n-nodes-base.lingvanex/ +/nodes/n8n-nodes-base.lingvanex/ /integrations/builtin/app-nodes/n8n-nodes-base.lingvanex/ +/nodes/n8n-nodes-base.linkedIn/ /integrations/builtin/app-nodes/n8n-nodes-base.linkedin/ +/nodes/n8n-nodes-base.linkedin/ /integrations/builtin/app-nodes/n8n-nodes-base.linkedin/ +/nodes/n8n-nodes-base.localFileTrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.localfiletrigger/ +/nodes/n8n-nodes-base.localfiletrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.localfiletrigger/ /nodes/n8n-nodes-base.magento2/ /integrations/builtin/app-nodes/n8n-nodes-base.magento2/ /nodes/n8n-nodes-base.mailcheck/ /integrations/builtin/app-nodes/n8n-nodes-base.mailcheck/ /nodes/n8n-nodes-base.mailchimp/ /integrations/builtin/app-nodes/n8n-nodes-base.mailchimp/ -/nodes/n8n-nodes-base.mailchimpTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mailchimpTrigger/ -/nodes/n8n-nodes-base.mailchimptrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mailchimpTrigger/ -/nodes/n8n-nodes-base.mailerLite/ /integrations/builtin/app-nodes/n8n-nodes-base.mailerLite/ -/nodes/n8n-nodes-base.mailerlite/ /integrations/builtin/app-nodes/n8n-nodes-base.mailerLite/ -/nodes/n8n-nodes-base.mailerLiteTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mailerLiteTrigger/ -/nodes/n8n-nodes-base.mailerlitetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mailerLiteTrigger/ +/nodes/n8n-nodes-base.mailchimpTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mailchimptrigger/ +/nodes/n8n-nodes-base.mailchimptrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mailchimptrigger/ +/nodes/n8n-nodes-base.mailerLite/ /integrations/builtin/app-nodes/n8n-nodes-base.mailerlite/ +/nodes/n8n-nodes-base.mailerlite/ /integrations/builtin/app-nodes/n8n-nodes-base.mailerlite/ +/nodes/n8n-nodes-base.mailerLiteTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mailerlitetrigger/ +/nodes/n8n-nodes-base.mailerlitetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mailerlitetrigger/ /nodes/n8n-nodes-base.mailgun/ /integrations/builtin/app-nodes/n8n-nodes-base.mailgun/ /nodes/n8n-nodes-base.mailjet/ /integrations/builtin/app-nodes/n8n-nodes-base.mailjet/ -/nodes/n8n-nodes-base.mailjetTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mailjetTrigger/ -/nodes/n8n-nodes-base.mailjettrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mailjetTrigger/ +/nodes/n8n-nodes-base.mailjetTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mailjettrigger/ +/nodes/n8n-nodes-base.mailjettrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mailjettrigger/ /nodes/n8n-nodes-base.mandrill/ /integrations/builtin/app-nodes/n8n-nodes-base.mandrill/ /nodes/n8n-nodes-base.markdown/ /integrations/builtin/core-nodes/n8n-nodes-base.markdown/ /nodes/n8n-nodes-base.marketstack/ /integrations/builtin/app-nodes/n8n-nodes-base.marketstack/ /nodes/n8n-nodes-base.matrix/ /integrations/builtin/app-nodes/n8n-nodes-base.matrix/ /nodes/n8n-nodes-base.mattermost/ /integrations/builtin/app-nodes/n8n-nodes-base.mattermost/ /nodes/n8n-nodes-base.mautic/ /integrations/builtin/app-nodes/n8n-nodes-base.mautic/ -/nodes/n8n-nodes-base.mauticTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mauticTrigger/ -/nodes/n8n-nodes-base.mautictrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mauticTrigger/ +/nodes/n8n-nodes-base.mauticTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mautictrigger/ +/nodes/n8n-nodes-base.mautictrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mautictrigger/ /nodes/n8n-nodes-base.medium/ /integrations/builtin/app-nodes/n8n-nodes-base.medium/ /nodes/n8n-nodes-base.merge/ /integrations/builtin/core-nodes/n8n-nodes-base.merge/ -/nodes/n8n-nodes-base.messageBird/ /integrations/builtin/app-nodes/n8n-nodes-base.messageBird/ -/nodes/n8n-nodes-base.messagebird/ /integrations/builtin/app-nodes/n8n-nodes-base.messageBird/ +/nodes/n8n-nodes-base.messageBird/ /integrations/builtin/app-nodes/n8n-nodes-base.messagebird/ +/nodes/n8n-nodes-base.messagebird/ /integrations/builtin/app-nodes/n8n-nodes-base.messagebird/ /nodes/n8n-nodes-base.metabase/ /integrations/builtin/app-nodes/n8n-nodes-base.metabase/ -/nodes/n8n-nodes-base.microsoftDynamicsCrm/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftDynamicsCrm/ -/nodes/n8n-nodes-base.microsoftdynamicscrm/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftDynamicsCrm/ -/nodes/n8n-nodes-base.microsoftExcel/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftExcel/ -/nodes/n8n-nodes-base.microsoftexcel/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftExcel/ -/nodes/n8n-nodes-base.microsoftGraphSecurity/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftGraphSecurity/ -/nodes/n8n-nodes-base.microsoftgraphsecurity/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftGraphSecurity/ -/nodes/n8n-nodes-base.microsoftOneDrive/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftOneDrive/ -/nodes/n8n-nodes-base.microsoftonedrive/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftOneDrive/ -/nodes/n8n-nodes-base.microsoftOutlook/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftOutlook/ -/nodes/n8n-nodes-base.microsoftoutlook/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftOutlook/ -/nodes/n8n-nodes-base.microsoftSql/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftSql/ -/nodes/n8n-nodes-base.microsoftsql/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftSql/ -/nodes/n8n-nodes-base.microsoftTeams/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftTeams/ -/nodes/n8n-nodes-base.microsoftteams/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftTeams/ -/nodes/n8n-nodes-base.microsoftToDo/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftToDo/ -/nodes/n8n-nodes-base.microsofttodo/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftToDo/ +/nodes/n8n-nodes-base.microsoftDynamicsCrm/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftdynamicscrm/ +/nodes/n8n-nodes-base.microsoftdynamicscrm/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftdynamicscrm/ +/nodes/n8n-nodes-base.microsoftExcel/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftexcel/ +/nodes/n8n-nodes-base.microsoftexcel/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftexcel/ +/nodes/n8n-nodes-base.microsoftGraphSecurity/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftgraphsecurity/ +/nodes/n8n-nodes-base.microsoftgraphsecurity/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftgraphsecurity/ +/nodes/n8n-nodes-base.microsoftOneDrive/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftonedrive/ +/nodes/n8n-nodes-base.microsoftonedrive/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftonedrive/ +/nodes/n8n-nodes-base.microsoftOutlook/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftoutlook/ +/nodes/n8n-nodes-base.microsoftoutlook/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftoutlook/ +/nodes/n8n-nodes-base.microsoftSql/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftsql/ +/nodes/n8n-nodes-base.microsoftsql/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftsql/ +/nodes/n8n-nodes-base.microsoftTeams/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftteams/ +/nodes/n8n-nodes-base.microsoftteams/ /integrations/builtin/app-nodes/n8n-nodes-base.microsoftteams/ +/nodes/n8n-nodes-base.microsoftToDo/ /integrations/builtin/app-nodes/n8n-nodes-base.microsofttodo/ +/nodes/n8n-nodes-base.microsofttodo/ /integrations/builtin/app-nodes/n8n-nodes-base.microsofttodo/ /nodes/n8n-nodes-base.mindee/ /integrations/builtin/app-nodes/n8n-nodes-base.mindee/ /nodes/n8n-nodes-base.misp/ /integrations/builtin/app-nodes/n8n-nodes-base.misp/ /nodes/n8n-nodes-base.mocean/ /integrations/builtin/app-nodes/n8n-nodes-base.mocean/ -/nodes/n8n-nodes-base.mondayCom/ /integrations/builtin/app-nodes/n8n-nodes-base.mondayCom/ -/nodes/n8n-nodes-base.mondaycom/ /integrations/builtin/app-nodes/n8n-nodes-base.mondayCom/ -/nodes/n8n-nodes-base.mongoDb/ /integrations/builtin/app-nodes/n8n-nodes-base.mongoDb/ -/nodes/n8n-nodes-base.mongodb/ /integrations/builtin/app-nodes/n8n-nodes-base.mongoDb/ -/nodes/n8n-nodes-base.monicaCrm/ /integrations/builtin/app-nodes/n8n-nodes-base.monicaCrm/ -/nodes/n8n-nodes-base.monicacrm/ /integrations/builtin/app-nodes/n8n-nodes-base.monicaCrm/ -/nodes/n8n-nodes-base.moveBinaryData/ /integrations/builtin/core-nodes/n8n-nodes-base.moveBinaryData/ -/nodes/n8n-nodes-base.movebinarydata/ /integrations/builtin/core-nodes/n8n-nodes-base.moveBinaryData/ +/nodes/n8n-nodes-base.mondayCom/ /integrations/builtin/app-nodes/n8n-nodes-base.mondaycom/ +/nodes/n8n-nodes-base.mondaycom/ /integrations/builtin/app-nodes/n8n-nodes-base.mondaycom/ +/nodes/n8n-nodes-base.mongoDb/ /integrations/builtin/app-nodes/n8n-nodes-base.mongodb/ +/nodes/n8n-nodes-base.mongodb/ /integrations/builtin/app-nodes/n8n-nodes-base.mongodb/ +/nodes/n8n-nodes-base.monicaCrm/ /integrations/builtin/app-nodes/n8n-nodes-base.monicacrm/ +/nodes/n8n-nodes-base.monicacrm/ /integrations/builtin/app-nodes/n8n-nodes-base.monicacrm/ +/nodes/n8n-nodes-base.moveBinaryData/ /integrations/builtin/core-nodes/n8n-nodes-base.movebinarydata/ +/nodes/n8n-nodes-base.movebinarydata/ /integrations/builtin/core-nodes/n8n-nodes-base.movebinarydata/ /nodes/n8n-nodes-base.mqtt/ /integrations/builtin/app-nodes/n8n-nodes-base.mqtt/ -/nodes/n8n-nodes-base.mqttTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mqttTrigger/ -/nodes/n8n-nodes-base.mqtttrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mqttTrigger/ +/nodes/n8n-nodes-base.mqttTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mqtttrigger/ +/nodes/n8n-nodes-base.mqtttrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mqtttrigger/ /nodes/n8n-nodes-base.msg91/ /integrations/builtin/app-nodes/n8n-nodes-base.msg91/ -/nodes/n8n-nodes-base.mySql/ /integrations/builtin/app-nodes/n8n-nodes-base.mySql/ -/nodes/n8n-nodes-base.mysql/ /integrations/builtin/app-nodes/n8n-nodes-base.mySql/ -/nodes/n8n-nodes-base.n8nTrainingCustomerMessenger/ /integrations/builtin/app-nodes/n8n-nodes-base.n8nTrainingCustomerMessenger/ -/nodes/n8n-nodes-base.n8ntrainingcustomermessenger/ /integrations/builtin/app-nodes/n8n-nodes-base.n8nTrainingCustomerMessenger/ -/nodes/n8n-nodes-base.n8nTrainingCustomerDatastore/ /integrations/builtin/app-nodes/n8n-nodes-base.n8nTrainingCustomerDatastore/ -/nodes/n8n-nodes-base.n8ntrainingcustomercatastore/ /integrations/builtin/app-nodes/n8n-nodes-base.n8nTrainingCustomerDatastore/ -/nodes/n8n-nodes-base.n8nTrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.n8nTrigger/ -/nodes/n8n-nodes-base.n8ntrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.n8nTrigger/ +/nodes/n8n-nodes-base.mySql/ /integrations/builtin/app-nodes/n8n-nodes-base.mysql/ +/nodes/n8n-nodes-base.mysql/ /integrations/builtin/app-nodes/n8n-nodes-base.mysql/ +/nodes/n8n-nodes-base.n8nTrainingCustomerMessenger/ /integrations/builtin/app-nodes/n8n-nodes-base.n8ntrainingcustomermessenger/ +/nodes/n8n-nodes-base.n8ntrainingcustomermessenger/ /integrations/builtin/app-nodes/n8n-nodes-base.n8ntrainingcustomermessenger/ +/nodes/n8n-nodes-base.n8nTrainingCustomerDatastore/ /integrations/builtin/app-nodes/n8n-nodes-base.n8ntrainingcustomerdatastore/ +/nodes/n8n-nodes-base.n8ntrainingcustomercatastore/ /integrations/builtin/app-nodes/n8n-nodes-base.n8ntrainingcustomerdatastore/ +/nodes/n8n-nodes-base.n8nTrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.n8ntrigger/ +/nodes/n8n-nodes-base.n8ntrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.n8ntrigger/ /nodes/n8n-nodes-base.nasa/ /integrations/builtin/app-nodes/n8n-nodes-base.nasa/ /nodes/n8n-nodes-base.netlify/ /integrations/builtin/app-nodes/n8n-nodes-base.netlify/ -/nodes/n8n-nodes-base.netlifyTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.netlifyTrigger/ -/nodes/n8n-nodes-base.netlifytrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.netlifyTrigger/ -/nodes/n8n-nodes-base.nextCloud/ /integrations/builtin/app-nodes/n8n-nodes-base.nextCloud/ -/nodes/n8n-nodes-base.nextcloud/ /integrations/builtin/app-nodes/n8n-nodes-base.nextCloud/ -/nodes/n8n-nodes-base.nocoDb/ /integrations/builtin/app-nodes/n8n-nodes-base.nocoDb/ -/nodes/n8n-nodes-base.nocodb/ /integrations/builtin/app-nodes/n8n-nodes-base.nocoDb/ -/nodes/n8n-nodes-base.noOp/ /integrations/builtin/core-nodes/n8n-nodes-base.noOp/ -/nodes/n8n-nodes-base.noop/ /integrations/builtin/core-nodes/n8n-nodes-base.noOp/ +/nodes/n8n-nodes-base.netlifyTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.netlifytrigger/ +/nodes/n8n-nodes-base.netlifytrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.netlifytrigger/ +/nodes/n8n-nodes-base.nextCloud/ /integrations/builtin/app-nodes/n8n-nodes-base.nextcloud/ +/nodes/n8n-nodes-base.nextcloud/ /integrations/builtin/app-nodes/n8n-nodes-base.nextcloud/ +/nodes/n8n-nodes-base.nocoDb/ /integrations/builtin/app-nodes/n8n-nodes-base.nocodb/ +/nodes/n8n-nodes-base.nocodb/ /integrations/builtin/app-nodes/n8n-nodes-base.nocodb/ +/nodes/n8n-nodes-base.noOp/ /integrations/builtin/core-nodes/n8n-nodes-base.noop/ +/nodes/n8n-nodes-base.noop/ /integrations/builtin/core-nodes/n8n-nodes-base.noop/ /nodes/n8n-nodes-base.notion/ /integrations/builtin/app-nodes/n8n-nodes-base.notion/ -/nodes/n8n-nodes-base.notionTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.notionTrigger/ -/nodes/n8n-nodes-base.notiontrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.notionTrigger/ +/nodes/n8n-nodes-base.notionTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.notiontrigger/ +/nodes/n8n-nodes-base.notiontrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.notiontrigger/ /nodes/n8n-nodes-base.odoo/ /integrations/builtin/app-nodes/n8n-nodes-base.odoo/ -/nodes/n8n-nodes-base.oneSimpleApi/ /integrations/builtin/app-nodes/n8n-nodes-base.oneSimpleApi/ -/nodes/n8n-nodes-base.onesimpleapi/ /integrations/builtin/app-nodes/n8n-nodes-base.oneSimpleApi/ +/nodes/n8n-nodes-base.oneSimpleApi/ /integrations/builtin/app-nodes/n8n-nodes-base.onesimpleapi/ +/nodes/n8n-nodes-base.onesimpleapi/ /integrations/builtin/app-nodes/n8n-nodes-base.onesimpleapi/ /nodes/n8n-nodes-base.onfleet/ /integrations/builtin/app-nodes/n8n-nodes-base.onfleet/ -/nodes/n8n-nodes-base.onfleetTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.onfleetTrigger/ -/nodes/n8n-nodes-base.onfleettrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.onfleetTrigger/ -/nodes/n8n-nodes-base.openThesaurus/ /integrations/builtin/app-nodes/n8n-nodes-base.openThesaurus/ -/nodes/n8n-nodes-base.openthesaurus/ /integrations/builtin/app-nodes/n8n-nodes-base.openThesaurus/ -/nodes/n8n-nodes-base.openWeatherMap/ /integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/ -/nodes/n8n-nodes-base.openweathermap/ /integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/ +/nodes/n8n-nodes-base.onfleetTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.onfleettrigger/ +/nodes/n8n-nodes-base.onfleettrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.onfleettrigger/ +/nodes/n8n-nodes-base.openThesaurus/ /integrations/builtin/app-nodes/n8n-nodes-base.openthesaurus/ +/nodes/n8n-nodes-base.openthesaurus/ /integrations/builtin/app-nodes/n8n-nodes-base.openthesaurus/ +/nodes/n8n-nodes-base.openWeatherMap/ /integrations/builtin/app-nodes/n8n-nodes-base.openweathermap/ +/nodes/n8n-nodes-base.openweathermap/ /integrations/builtin/app-nodes/n8n-nodes-base.openweathermap/ /nodes/n8n-nodes-base.orbit/ /integrations/builtin/app-nodes/n8n-nodes-base.orbit/ /nodes/n8n-nodes-base.oura/ /integrations/builtin/app-nodes/n8n-nodes-base.oura/ /nodes/n8n-nodes-base.paddle/ /integrations/builtin/app-nodes/n8n-nodes-base.paddle/ -/nodes/n8n-nodes-base.pagerDuty/ /integrations/builtin/app-nodes/n8n-nodes-base.pagerDuty/ -/nodes/n8n-nodes-base.pagerduty/ /integrations/builtin/app-nodes/n8n-nodes-base.pagerDuty/ -/nodes/n8n-nodes-base.payPal/ /integrations/builtin/app-nodes/n8n-nodes-base.payPal/ -/nodes/n8n-nodes-base.paypal/ /integrations/builtin/app-nodes/n8n-nodes-base.payPal/ -/nodes/n8n-nodes-base.payPalTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.payPalTrigger/ -/nodes/n8n-nodes-base.paypaltrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.payPalTrigger/ +/nodes/n8n-nodes-base.pagerDuty/ /integrations/builtin/app-nodes/n8n-nodes-base.pagerduty/ +/nodes/n8n-nodes-base.pagerduty/ /integrations/builtin/app-nodes/n8n-nodes-base.pagerduty/ +/nodes/n8n-nodes-base.payPal/ /integrations/builtin/app-nodes/n8n-nodes-base.paypal/ +/nodes/n8n-nodes-base.paypal/ /integrations/builtin/app-nodes/n8n-nodes-base.paypal/ +/nodes/n8n-nodes-base.payPalTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.paypaltrigger/ +/nodes/n8n-nodes-base.paypaltrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.paypaltrigger/ /nodes/n8n-nodes-base.peekalink/ /integrations/builtin/app-nodes/n8n-nodes-base.peekalink/ /nodes/n8n-nodes-base.phantombuster/ /integrations/builtin/app-nodes/n8n-nodes-base.phantombuster/ -/nodes/n8n-nodes-base.philipsHue/ /integrations/builtin/app-nodes/n8n-nodes-base.philipsHue/ -/nodes/n8n-nodes-base.philipsHue/ /integrations/builtin/app-nodes/n8n-nodes-base.philipsHue/ +/nodes/n8n-nodes-base.philipsHue/ /integrations/builtin/app-nodes/n8n-nodes-base.philipshue/ +/nodes/n8n-nodes-base.philipsHue/ /integrations/builtin/app-nodes/n8n-nodes-base.philipshue/ /nodes/n8n-nodes-base.pipedrive/ /integrations/builtin/app-nodes/n8n-nodes-base.pipedrive/ -/nodes/n8n-nodes-base.pipedriveTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.pipedriveTrigger/ -/nodes/n8n-nodes-base.pipedrivetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.pipedriveTrigger/ +/nodes/n8n-nodes-base.pipedriveTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.pipedrivetrigger/ +/nodes/n8n-nodes-base.pipedrivetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.pipedrivetrigger/ /nodes/n8n-nodes-base.plivo/ /integrations/builtin/app-nodes/n8n-nodes-base.plivo/ /nodes/n8n-nodes-base.postbin/ /integrations/builtin/app-nodes/n8n-nodes-base.postbin/ /nodes/n8n-nodes-base.postgres/ /integrations/builtin/app-nodes/n8n-nodes-base.postgres/ -/nodes/n8n-nodes-base.postHog/ /integrations/builtin/app-nodes/n8n-nodes-base.postHog/ -/nodes/n8n-nodes-base.postmarkTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.postmarkTrigger/ -/nodes/n8n-nodes-base.postmarktrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.postmarkTrigger/ -/nodes/n8n-nodes-base.profitWell/ /integrations/builtin/app-nodes/n8n-nodes-base.profitWell/ -/nodes/n8n-nodes-base.profitwell/ /integrations/builtin/app-nodes/n8n-nodes-base.profitWell/ +/nodes/n8n-nodes-base.postHog/ /integrations/builtin/app-nodes/n8n-nodes-base.posthog/ +/nodes/n8n-nodes-base.postmarkTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.postmarktrigger/ +/nodes/n8n-nodes-base.postmarktrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.postmarktrigger/ +/nodes/n8n-nodes-base.profitWell/ /integrations/builtin/app-nodes/n8n-nodes-base.profitwell/ +/nodes/n8n-nodes-base.profitwell/ /integrations/builtin/app-nodes/n8n-nodes-base.profitwell/ /nodes/n8n-nodes-base.pushbullet/ /integrations/builtin/app-nodes/n8n-nodes-base.pushbullet/ /nodes/n8n-nodes-base.pushcut/ /integrations/builtin/app-nodes/n8n-nodes-base.pushcut/ -/nodes/n8n-nodes-base.pushcutTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.pushcutTrigger/ -/nodes/n8n-nodes-base.pushcuttrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.pushcutTrigger/ +/nodes/n8n-nodes-base.pushcutTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.pushcuttrigger/ +/nodes/n8n-nodes-base.pushcuttrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.pushcuttrigger/ /nodes/n8n-nodes-base.pushover/ /integrations/builtin/app-nodes/n8n-nodes-base.pushover/ -/nodes/n8n-nodes-base.questDb/ /integrations/builtin/app-nodes/n8n-nodes-base.questDb/ -/nodes/n8n-nodes-base.questdb/ /integrations/builtin/app-nodes/n8n-nodes-base.questDb/ +/nodes/n8n-nodes-base.questDb/ /integrations/builtin/app-nodes/n8n-nodes-base.questdb/ +/nodes/n8n-nodes-base.questdb/ /integrations/builtin/app-nodes/n8n-nodes-base.questdb/ /nodes/n8n-nodes-base.quickbase/ /integrations/builtin/app-nodes/n8n-nodes-base.quickbase/ /nodes/n8n-nodes-base.quickbooks/ /integrations/builtin/app-nodes/n8n-nodes-base.quickbooks/ /nodes/n8n-nodes-base.rabbitmq/ /integrations/builtin/app-nodes/n8n-nodes-base.rabbitmq/ -/nodes/n8n-nodes-base.rabbitmqTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.rabbitmqTrigger/ -/nodes/n8n-nodes-base.rabbitmqtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.rabbitmqTrigger/ +/nodes/n8n-nodes-base.rabbitmqTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.rabbitmqtrigger/ +/nodes/n8n-nodes-base.rabbitmqtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.rabbitmqtrigger/ /nodes/n8n-nodes-base.raindrop/ /integrations/builtin/app-nodes/n8n-nodes-base.raindrop/ -/nodes/n8n-nodes-base.readBinaryFile/ /integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/ -/nodes/n8n-nodes-base.readbinaryfile/ /integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/ -/nodes/n8n-nodes-base.readBinaryFiles/ /integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFiles/ -/nodes/n8n-nodes-base.readbinaryfiles/ /integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFiles/ -/nodes/n8n-nodes-base.readPDF/ /integrations/builtin/core-nodes/n8n-nodes-base.readPDF/ -/nodes/n8n-nodes-base.readpdf/ /integrations/builtin/core-nodes/n8n-nodes-base.readPDF/ +/nodes/n8n-nodes-base.readBinaryFile/ /integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/ +/nodes/n8n-nodes-base.readbinaryfile/ /integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/ +/nodes/n8n-nodes-base.readBinaryFiles/ /integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfiles/ +/nodes/n8n-nodes-base.readbinaryfiles/ /integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfiles/ +/nodes/n8n-nodes-base.readPDF/ /integrations/builtin/core-nodes/n8n-nodes-base.readpdf/ +/nodes/n8n-nodes-base.readpdf/ /integrations/builtin/core-nodes/n8n-nodes-base.readpdf/ /nodes/n8n-nodes-base.reddit/ /integrations/builtin/app-nodes/n8n-nodes-base.reddit/ /nodes/n8n-nodes-base.redis/ /integrations/builtin/app-nodes/n8n-nodes-base.redis/ -/nodes/n8n-nodes-base.redisTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.redisTrigger/ -/nodes/n8n-nodes-base.redistrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.redisTrigger/ -/nodes/n8n-nodes-base.renameKeys/ /integrations/builtin/core-nodes/n8n-nodes-base.renameKeys/ -/nodes/n8n-nodes-base.renamekeys/ /integrations/builtin/core-nodes/n8n-nodes-base.renameKeys/ -/nodes/n8n-nodes-base.respondToWebhook/ /integrations/builtin/core-nodes/n8n-nodes-base.respondToWebhook/ -/nodes/n8n-nodes-base.respondtowebhook/ /integrations/builtin/core-nodes/n8n-nodes-base.respondToWebhook/ +/nodes/n8n-nodes-base.redisTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.redistrigger/ +/nodes/n8n-nodes-base.redistrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.redistrigger/ +/nodes/n8n-nodes-base.renameKeys/ /integrations/builtin/core-nodes/n8n-nodes-base.renamekeys/ +/nodes/n8n-nodes-base.renamekeys/ /integrations/builtin/core-nodes/n8n-nodes-base.renamekeys/ +/nodes/n8n-nodes-base.respondToWebhook/ /integrations/builtin/core-nodes/n8n-nodes-base.respondtowebhook/ +/nodes/n8n-nodes-base.respondtowebhook/ /integrations/builtin/core-nodes/n8n-nodes-base.respondtowebhook/ /nodes/n8n-nodes-base.rocketchat/ /integrations/builtin/app-nodes/n8n-nodes-base.rocketchat/ -/nodes/n8n-nodes-base.rssFeedRead/ /integrations/builtin/core-nodes/n8n-nodes-base.rssFeedRead/ -/nodes/n8n-nodes-base.rssfeedread/ /integrations/builtin/core-nodes/n8n-nodes-base.rssFeedRead/ +/nodes/n8n-nodes-base.rssFeedRead/ /integrations/builtin/core-nodes/n8n-nodes-base.rssfeedread/ +/nodes/n8n-nodes-base.rssfeedread/ /integrations/builtin/core-nodes/n8n-nodes-base.rssfeedread/ /nodes/n8n-nodes-base.rundeck/ /integrations/builtin/app-nodes/n8n-nodes-base.rundeck/ /nodes/n8n-nodes-base.s3/ /integrations/builtin/app-nodes/n8n-nodes-base.s3/ /nodes/n8n-nodes-base.salesforce/ /integrations/builtin/app-nodes/n8n-nodes-base.salesforce/ /nodes/n8n-nodes-base.salesmate/ /integrations/builtin/app-nodes/n8n-nodes-base.salesmate/ -/nodes/n8n-nodes-base.seaTable/ /integrations/builtin/app-nodes/n8n-nodes-base.seaTable/ -/nodes/n8n-nodes-base.seatable/ /integrations/builtin/app-nodes/n8n-nodes-base.seaTable/ -/nodes/n8n-nodes-base.seaTableTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.seaTableTrigger/ -/nodes/n8n-nodes-base.seatabletrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.seaTableTrigger/ -/nodes/n8n-nodes-base.securityScorecard/ /integrations/builtin/app-nodes/n8n-nodes-base.securityScorecard/ -/nodes/n8n-nodes-base.securityscorecard/ /integrations/builtin/app-nodes/n8n-nodes-base.securityScorecard/ +/nodes/n8n-nodes-base.seaTable/ /integrations/builtin/app-nodes/n8n-nodes-base.seatable/ +/nodes/n8n-nodes-base.seatable/ /integrations/builtin/app-nodes/n8n-nodes-base.seatable/ +/nodes/n8n-nodes-base.seaTableTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.seatabletrigger/ +/nodes/n8n-nodes-base.seatabletrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.seatabletrigger/ +/nodes/n8n-nodes-base.securityScorecard/ /integrations/builtin/app-nodes/n8n-nodes-base.securityscorecard/ +/nodes/n8n-nodes-base.securityscorecard/ /integrations/builtin/app-nodes/n8n-nodes-base.securityscorecard/ /nodes/n8n-nodes-base.segment/ /integrations/builtin/app-nodes/n8n-nodes-base.segment/ -/nodes/n8n-nodes-base.sendGrid/ /integrations/builtin/app-nodes/n8n-nodes-base.sendGrid/ -/nodes/n8n-nodes-base.sendgrid/ /integrations/builtin/app-nodes/n8n-nodes-base.sendGrid/ -/nodes/n8n--nodes-base.sendInBlue/ /integrations/builtin/app-nodes/n8n-nodes-base.sendInBlue/ +/nodes/n8n-nodes-base.sendGrid/ /integrations/builtin/app-nodes/n8n-nodes-base.sendgrid/ +/nodes/n8n-nodes-base.sendgrid/ /integrations/builtin/app-nodes/n8n-nodes-base.sendgrid/ +/nodes/n8n--nodes-base.sendInBlue/ /integrations/builtin/app-nodes/n8n-nodes-base.sendinblue/ /nodes/n8n--nodes-base.sendinblue/ /integrations/builtin/app-nodes/n8n-nodes-base.sendinblue/ -/nodes/n8n--nodes-base.sendInBlue/ /integrations/builtin/trigger-nodes/n8n-nodes-base.sendInBlueTrigger/ -/nodes/n8n--nodes-base.sendinblue/ /integrations/builtin/trigger-nodes/n8n-nodes-base.sendinbluetrigger/ +/nodes/n8n--nodes-base.sendInBlueTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.sendinbluetrigger/ +/nodes/n8n--nodes-base.sendinbluetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.sendinbluetrigger/ /nodes/n8n-nodes-base.sendy/ /integrations/builtin/app-nodes/n8n-nodes-base.sendy/ -/nodes/n8n-nodes-base.sentryIo/ /integrations/builtin/app-nodes/n8n-nodes-base.sentryIo/ -/nodes/n8n-nodes-base.sentryio/ /integrations/builtin/app-nodes/n8n-nodes-base.sentryIo/ -/nodes/n8n-nodes-base.serviceNow/ /integrations/builtin/app-nodes/n8n-nodes-base.serviceNow/ -/nodes/n8n-nodes-base.servicenow/ /integrations/builtin/app-nodes/n8n-nodes-base.serviceNow/ +/nodes/n8n-nodes-base.sentryIo/ /integrations/builtin/app-nodes/n8n-nodes-base.sentryio/ +/nodes/n8n-nodes-base.sentryio/ /integrations/builtin/app-nodes/n8n-nodes-base.sentryio/ +/nodes/n8n-nodes-base.serviceNow/ /integrations/builtin/app-nodes/n8n-nodes-base.servicenow/ +/nodes/n8n-nodes-base.servicenow/ /integrations/builtin/app-nodes/n8n-nodes-base.servicenow/ /nodes/n8n-nodes-base.set/ /integrations/builtin/core-nodes/n8n-nodes-base.set/ /nodes/n8n-nodes-base.shopify/ /integrations/builtin/app-nodes/n8n-nodes-base.shopify/ -/nodes/n8n-nodes-base.shopifyTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.shopifyTrigger/ -/nodes/n8n-nodes-base.shopifytrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.shopifyTrigger/ +/nodes/n8n-nodes-base.shopifyTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.shopifytrigger/ +/nodes/n8n-nodes-base.shopifytrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.shopifytrigger/ /nodes/n8n-nodes-base.signl4/ /integrations/builtin/app-nodes/n8n-nodes-base.signl4/ /nodes/n8n-nodes-base.slack/ /integrations/builtin/app-nodes/n8n-nodes-base.slack/ /nodes/n8n-nodes-base.sms77/ /integrations/builtin/app-nodes/n8n-nodes-base.sms77/ /nodes/n8n-nodes-base.snowflake/ /integrations/builtin/app-nodes/n8n-nodes-base.snowflake/ -/nodes/n8n-nodes-base.splitInBatches/ /integrations/builtin/core-nodes/n8n-nodes-base.splitInBatches/ -/nodes/n8n-nodes-base.splitinbatches/ /integrations/builtin/core-nodes/n8n-nodes-base.splitInBatches/ +/nodes/n8n-nodes-base.splitInBatches/ /integrations/builtin/core-nodes/n8n-nodes-base.splitinbatches/ +/nodes/n8n-nodes-base.splitinbatches/ /integrations/builtin/core-nodes/n8n-nodes-base.splitinbatches/ /nodes/n8n-nodes-base.splunk/ /integrations/builtin/app-nodes/n8n-nodes-base.splunk/ /nodes/n8n-nodes-base.spontit/ /integrations/builtin/app-nodes/n8n-nodes-base.spontit/ /nodes/n8n-nodes-base.spotify/ /integrations/builtin/app-nodes/n8n-nodes-base.spotify/ -/nodes/n8n-nodes-base.spreadsheetFile/ /integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetFile/ -/nodes/n8n-nodes-base.spreadsheetfile/ /integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetFile/ -/nodes/n8n-nodes-base.sseTrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.sseTrigger/ -/nodes/n8n-nodes-base.ssetrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.sseTrigger/ +/nodes/n8n-nodes-base.spreadsheetFile/ /integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetfile/ +/nodes/n8n-nodes-base.spreadsheetfile/ /integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetfile/ +/nodes/n8n-nodes-base.sseTrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.ssetrigger/ +/nodes/n8n-nodes-base.ssetrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.ssetrigger/ /nodes/n8n-nodes-base.ssh/ /integrations/builtin/core-nodes/n8n-nodes-base.ssh/ /nodes/n8n-nodes-base.stackby/ /integrations/builtin/app-nodes/n8n-nodes-base.stackby/ /nodes/n8n-nodes-base.start/ /integrations/builtin/core-nodes/n8n-nodes-base.start/ -/nodes/n8n-nodes-base.stopAndError/ /integrations/builtin/core-nodes/n8n-nodes-base.stopAndError/ -/nodes/n8n-nodes-base.stopanderror/ /integrations/builtin/core-nodes/n8n-nodes-base.stopAndError/ +/nodes/n8n-nodes-base.stopAndError/ /integrations/builtin/core-nodes/n8n-nodes-base.stopanderror/ +/nodes/n8n-nodes-base.stopanderror/ /integrations/builtin/core-nodes/n8n-nodes-base.stopanderror/ /nodes/n8n-nodes-base.storyblok/ /integrations/builtin/app-nodes/n8n-nodes-base.storyblok/ /nodes/n8n-nodes-base.strapi/ /integrations/builtin/app-nodes/n8n-nodes-base.strapi/ /nodes/n8n-nodes-base.strava/ /integrations/builtin/app-nodes/n8n-nodes-base.strava/ -/nodes/n8n-nodes-base.stravaTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.stravaTrigger/ -/nodes/n8n-nodes-base.stravatrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.stravaTrigger/ +/nodes/n8n-nodes-base.stravaTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.stravatrigger/ +/nodes/n8n-nodes-base.stravatrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.stravatrigger/ /nodes/n8n-nodes-base.stripe/ /integrations/builtin/app-nodes/n8n-nodes-base.stripe/ -/nodes/n8n-nodes-base.stripeTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.stripeTrigger/ -/nodes/n8n-nodes-base.stripetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.stripeTrigger/ +/nodes/n8n-nodes-base.stripeTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.stripetrigger/ +/nodes/n8n-nodes-base.stripetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.stripetrigger/ /nodes/n8n-nodes-base.supabase/ /integrations/builtin/app-nodes/n8n-nodes-base.supabase/ -/nodes/n8n-nodes-base.surveyMonkeyTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.surveyMonkeyTrigger/ -/nodes/n8n-nodes-base.surveymonkeytrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.surveyMonkeyTrigger/ +/nodes/n8n-nodes-base.surveyMonkeyTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.surveymonkeytrigger/ +/nodes/n8n-nodes-base.surveymonkeytrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.surveymonkeytrigger/ /nodes/n8n-nodes-base.switch/ /integrations/builtin/core-nodes/n8n-nodes-base.switch/ -/nodes/n8n-nodes-base.syncroMsp/ /integrations/builtin/app-nodes/n8n-nodes-base.syncroMsp/ -/nodes/n8n-nodes-base.syncromsp/ /integrations/builtin/app-nodes/n8n-nodes-base.syncroMsp/ +/nodes/n8n-nodes-base.syncroMsp/ /integrations/builtin/app-nodes/n8n-nodes-base.syncromsp/ +/nodes/n8n-nodes-base.syncromsp/ /integrations/builtin/app-nodes/n8n-nodes-base.syncromsp/ /nodes/n8n-nodes-base.taiga/ /integrations/builtin/app-nodes/n8n-nodes-base.taiga/ -/nodes/n8n-nodes-base.taigaTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.taigaTrigger/ -/nodes/n8n-nodes-base.taigatrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.taigaTrigger/ +/nodes/n8n-nodes-base.taigaTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.taigatrigger/ +/nodes/n8n-nodes-base.taigatrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.taigatrigger/ /nodes/n8n-nodes-base.tapfiliate/ /integrations/builtin/app-nodes/n8n-nodes-base.tapfiliate/ /nodes/n8n-nodes-base.telegram/ /integrations/builtin/app-nodes/n8n-nodes-base.telegram/ -/nodes/n8n-nodes-base.telegramTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.telegramTrigger/ -/nodes/n8n-nodes-base.telegramtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.telegramTrigger/ -/nodes/n8n-nodes-base.theHive/ /integrations/builtin/app-nodes/n8n-nodes-base.theHive/ -/nodes/n8n-nodes-base.thehive/ /integrations/builtin/app-nodes/n8n-nodes-base.theHive/ -/nodes/n8n-nodes-base.theHiveTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.theHiveTrigger/ -/nodes/n8n-nodes-base.thehivetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.theHiveTrigger/ -/nodes/n8n-nodes-base.timescaleDb/ /integrations/builtin/app-nodes/n8n-nodes-base.timescaleDb/ -/nodes/n8n-nodes-base.timescaledb/ /integrations/builtin/app-nodes/n8n-nodes-base.timescaleDb/ +/nodes/n8n-nodes-base.telegramTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.telegramtrigger/ +/nodes/n8n-nodes-base.telegramtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.telegramtrigger/ +/nodes/n8n-nodes-base.theHive/ /integrations/builtin/app-nodes/n8n-nodes-base.thehive/ +/nodes/n8n-nodes-base.thehive/ /integrations/builtin/app-nodes/n8n-nodes-base.thehive/ +/nodes/n8n-nodes-base.theHiveTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.thehivetrigger/ +/nodes/n8n-nodes-base.thehivetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.thehivetrigger/ +/nodes/n8n-nodes-base.timescaleDb/ /integrations/builtin/app-nodes/n8n-nodes-base.timescaledb/ +/nodes/n8n-nodes-base.timescaledb/ /integrations/builtin/app-nodes/n8n-nodes-base.timescaledb/ /nodes/n8n-nodes-base.todoist/ /integrations/builtin/app-nodes/n8n-nodes-base.todoist/ -/nodes/n8n-nodes-base.togglTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.togglTrigger/ -/nodes/n8n-nodes-base.toggltrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.togglTrigger/ -/nodes/n8n-nodes-base.travisCi/ /integrations/builtin/app-nodes/n8n-nodes-base.travisCi/ -/nodes/n8n-nodes-base.travisci/ /integrations/builtin/app-nodes/n8n-nodes-base.travisCi/ +/nodes/n8n-nodes-base.togglTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.toggltrigger/ +/nodes/n8n-nodes-base.toggltrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.toggltrigger/ +/nodes/n8n-nodes-base.travisCi/ /integrations/builtin/app-nodes/n8n-nodes-base.travisci/ +/nodes/n8n-nodes-base.travisci/ /integrations/builtin/app-nodes/n8n-nodes-base.travisci/ /nodes/n8n-nodes-base.trello/ /integrations/builtin/app-nodes/n8n-nodes-base.trello/ -/nodes/n8n-nodes-base.trelloTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.trelloTrigger/ -/nodes/n8n-nodes-base.trellotrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.trelloTrigger/ +/nodes/n8n-nodes-base.trelloTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.trellotrigger/ +/nodes/n8n-nodes-base.trellotrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.trellotrigger/ /nodes/n8n-nodes-base.twake/ /integrations/builtin/app-nodes/n8n-nodes-base.twake/ /nodes/n8n-nodes-base.twilio/ /integrations/builtin/app-nodes/n8n-nodes-base.twilio/ /nodes/n8n-nodes-base.twist/ /integrations/builtin/app-nodes/n8n-nodes-base.twist/ /nodes/n8n-nodes-base.twitter/ /integrations/builtin/app-nodes/n8n-nodes-base.twitter/ -/nodes/n8n-nodes-base.typeformTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.typeformTrigger/ -/nodes/n8n-nodes-base.typeformtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.typeformTrigger/ -/nodes/n8n-nodes-base.unleashedSoftware/ /integrations/builtin/app-nodes/n8n-nodes-base.unleashedSoftware/ -/nodes/n8n-nodes-base.unleashedsoftware/ /integrations/builtin/app-nodes/n8n-nodes-base.unleashedSoftware/ +/nodes/n8n-nodes-base.typeformTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.typeformtrigger/ +/nodes/n8n-nodes-base.typeformtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.typeformtrigger/ +/nodes/n8n-nodes-base.unleashedSoftware/ /integrations/builtin/app-nodes/n8n-nodes-base.unleashedsoftware/ +/nodes/n8n-nodes-base.unleashedsoftware/ /integrations/builtin/app-nodes/n8n-nodes-base.unleashedsoftware/ /nodes/n8n-nodes-base.uplead/ /integrations/builtin/app-nodes/n8n-nodes-base.uplead/ /nodes/n8n-nodes-base.uproc/ /integrations/builtin/app-nodes/n8n-nodes-base.uproc/ -/nodes/n8n-nodes-base.uptimeRobot/ /integrations/builtin/app-nodes/n8n-nodes-base.uptimeRobot/ -/nodes/n8n-nodes-base.uptimerobot/ /integrations/builtin/app-nodes/n8n-nodes-base.uptimeRobot/ -/nodes/n8n-nodes-base.urlScanIo/ /integrations/builtin/app-nodes/n8n-nodes-base.urlScanIo/ -/nodes/n8n-nodes-base.urlscanio/ /integrations/builtin/app-nodes/n8n-nodes-base.urlScanIo/ +/nodes/n8n-nodes-base.uptimeRobot/ /integrations/builtin/app-nodes/n8n-nodes-base.uptimerobot/ +/nodes/n8n-nodes-base.uptimerobot/ /integrations/builtin/app-nodes/n8n-nodes-base.uptimerobot/ +/nodes/n8n-nodes-base.urlScanIo/ /integrations/builtin/app-nodes/n8n-nodes-base.urlscanio/ +/nodes/n8n-nodes-base.urlscanio/ /integrations/builtin/app-nodes/n8n-nodes-base.urlscanio/ /nodes/n8n-nodes-base.vero/ /integrations/builtin/app-nodes/n8n-nodes-base.vero/ /nodes/n8n-nodes-base.vonage/ /integrations/builtin/app-nodes/n8n-nodes-base.vonage/ /nodes/n8n-nodes-base.wait/ /integrations/builtin/core-nodes/n8n-nodes-base.wait/ /nodes/n8n-nodes-base.webflow/ /integrations/builtin/app-nodes/n8n-nodes-base.webflow/ -/nodes/n8n-nodes-base.webflowTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.webflowTrigger/ -/nodes/n8n-nodes-base.webflowtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.webflowTrigger/ +/nodes/n8n-nodes-base.webflowTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.webflowtrigger/ +/nodes/n8n-nodes-base.webflowtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.webflowtrigger/ /nodes/n8n-nodes-base.webhook/ /integrations/builtin/core-nodes/n8n-nodes-base.webhook/ /nodes/n8n-nodes-base.wekan/ /integrations/builtin/app-nodes/n8n-nodes-base.wekan/ /nodes/n8n-nodes-base.wise/ /integrations/builtin/app-nodes/n8n-nodes-base.wise/ -/nodes/n8n-nodes-base.wiseTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.wiseTrigger/ -/nodes/n8n-nodes-base.wisetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.wiseTrigger/ -/nodes/n8n-nodes-base.wooCommerce/ /integrations/builtin/app-nodes/n8n-nodes-base.wooCommerce/ -/nodes/n8n-nodes-base.woocommerce/ /integrations/builtin/app-nodes/n8n-nodes-base.wooCommerce/ -/nodes/n8n-nodes-base.wooCommerceTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.wooCommerceTrigger/ -/nodes/n8n-nodes-base.woocommercetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.wooCommerceTrigger/ +/nodes/n8n-nodes-base.wiseTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.wisetrigger/ +/nodes/n8n-nodes-base.wisetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.wisetrigger/ +/nodes/n8n-nodes-base.wooCommerce/ /integrations/builtin/app-nodes/n8n-nodes-base.woocommerce/ +/nodes/n8n-nodes-base.woocommerce/ /integrations/builtin/app-nodes/n8n-nodes-base.woocommerce/ +/nodes/n8n-nodes-base.wooCommerceTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.woocommercetrigger/ +/nodes/n8n-nodes-base.woocommercetrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.woocommercetrigger/ /nodes/n8n-nodes-base.wordpress/ /integrations/builtin/app-nodes/n8n-nodes-base.wordpress/ -/nodes/n8n-nodes-base.workableTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.workableTrigger/ -/nodes/n8n-nodes-base.workabletrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.workableTrigger/ -/nodes/n8n-nodes-base.workflowTrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.workflowTrigger/ -/nodes/n8n-nodes-base.workflowtrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.workflowTrigger/ -/nodes/n8n-nodes-base.Workflowtrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.workflowTrigger/ -/nodes/n8n-nodes-base.writeBinaryFile/ /integrations/builtin/core-nodes/n8n-nodes-base.writeBinaryFile/ -/nodes/n8n-nodes-base.writebinaryfile/ /integrations/builtin/core-nodes/n8n-nodes-base.writeBinaryFile/ -/nodes/n8n-nodes-base.wufooTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.wufooTrigger/ -/nodes/n8n-nodes-base.wufootrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.wufooTrigger/ +/nodes/n8n-nodes-base.workableTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.workabletrigger/ +/nodes/n8n-nodes-base.workabletrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.workabletrigger/ +/nodes/n8n-nodes-base.workflowTrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.workflowtrigger/ +/nodes/n8n-nodes-base.workflowtrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.workflowtrigger/ +/nodes/n8n-nodes-base.Workflowtrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.workflowtrigger/ +/nodes/n8n-nodes-base.writeBinaryFile/ /integrations/builtin/core-nodes/n8n-nodes-base.writebinaryfile/ +/nodes/n8n-nodes-base.writebinaryfile/ /integrations/builtin/core-nodes/n8n-nodes-base.writebinaryfile/ +/nodes/n8n-nodes-base.wufooTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.wufootrigger/ +/nodes/n8n-nodes-base.wufootrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.wufootrigger/ /nodes/n8n-nodes-base.xero/ /integrations/builtin/app-nodes/n8n-nodes-base.xero/ /nodes/n8n-nodes-base.xml/ /integrations/builtin/core-nodes/n8n-nodes-base.xml/ /nodes/n8n-nodes-base.yourls/ /integrations/builtin/app-nodes/n8n-nodes-base.yourls/ -/nodes/n8n-nodes-base.youTube/ /integrations/builtin/app-nodes/n8n-nodes-base.youTube/ -/nodes/n8n-nodes-base.youtube/ /integrations/builtin/app-nodes/n8n-nodes-base.youTube/ +/nodes/n8n-nodes-base.youTube/ /integrations/builtin/app-nodes/n8n-nodes-base.youtube/ +/nodes/n8n-nodes-base.youtube/ /integrations/builtin/app-nodes/n8n-nodes-base.youtube/ /nodes/n8n-nodes-base.zammad/ /integrations/builtin/app-nodes/n8n-nodes-base.zammad/ /nodes/n8n-nodes-base.zendesk/ /integrations/builtin/app-nodes/n8n-nodes-base.zendesk/ -/nodes/n8n-nodes-base.zendeskTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.zendeskTrigger/ -/nodes/n8n-nodes-base.zendesktrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.zendeskTrigger/ -/nodes/n8n-nodes-base.zohoCrm/ /integrations/builtin/app-nodes/n8n-nodes-base.zohoCrm/ -/nodes/n8n-nodes-base.zohocrm/ /integrations/builtin/app-nodes/n8n-nodes-base.zohoCrm/ +/nodes/n8n-nodes-base.zendeskTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.zendesktrigger/ +/nodes/n8n-nodes-base.zendesktrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.zendesktrigger/ +/nodes/n8n-nodes-base.zohoCrm/ /integrations/builtin/app-nodes/n8n-nodes-base.zohocrm/ +/nodes/n8n-nodes-base.zohocrm/ /integrations/builtin/app-nodes/n8n-nodes-base.zohocrm/ /nodes/n8n-nodes-base.zoom/ /integrations/builtin/app-nodes/n8n-nodes-base.zoom/ /nodes/n8n-nodes-base.zulip/ /integrations/builtin/app-nodes/n8n-nodes-base.zulip/ /nodes/nodes-library/ /integrations/ diff --git a/docs/integrations/builtin/app-nodes/index.md b/docs/integrations/builtin/app-nodes/index.md deleted file mode 100644 index 470105543..000000000 --- a/docs/integrations/builtin/app-nodes/index.md +++ /dev/null @@ -1,3 +0,0 @@ -# App nodes library - -This section provides information about n8n's app nodes. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.actionNetwork.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.actionNetwork.md deleted file mode 100644 index 117dbfa8d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.actionNetwork.md +++ /dev/null @@ -1,91 +0,0 @@ -# Action Network - -[Action Network](https://actionnetwork.org/) is an open platform that empowers individuals and groups to organize for progressive causes. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/actionNetwork/). - - -## Basic operations - -* Attendance - * Create - * Get - * Get All -* Event - * Create - * Get - * Get All -* Person - * Create - * Get - * Get All - * Update -* Person Tag - * Add - * Remove -* Petition - * Create - * Get - * Get All - * Update -* Signature - * Create - * Get - * Get All - * Update -* Tag - * Create - * Get - * Get All - -## Example - -This workflow allows you to create a new event in Action Network, then create a new person and mark them as having attended your event. This workflow uses the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [ActiveCampaign]() - -The final workflow should look like the following image. - -![A workflow with the Action Network node](/_images/integrations/builtin/app-nodes/actionnetwork/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Action Network node - -1. First enter your credentials. You can find out how to do that [here](/integrations/builtin/credentials/actionNetwork/). -2. Fill in the remaining parameters as follows: - * **Resource**: Select **Event** from the dropdown list. - * **Operation**: Select **Create** from the dropdown list. - * **Origin System**: Enter where this event originated. n8n.io in our example. - * **Title**: Enter the name of your event, July Meetup in our example here. -3. Enable the **Simple** toggle to return an easier to view response as opposed to the complete raw data. -4. Use the **Additional Fields** to enter any further details about your event. Here we provided the Start Date. - -![Action Network node](/_images/integrations/builtin/app-nodes/actionnetwork/action_network_node.png) - -### 3. Action Network1 node - -1. First enter your credentials. You can find out how to do that [here](/integrations/builtin/credentials/actionNetwork/). -2. Fill in the remaining parameters as follows: - * **Resource**: Select **Person** from the dropdown list. - * **Operation**: Select **Create** from the dropdown list. -3. Enable the **Simple** toggle to return an easier to view response as opposed to the complete raw data. -4. In the **Email Address** section, enter the address and status for this person (here we Subscribe them). -5. Use the **Additional Fields** to enter any further details about this person. Here we provided their given name. - -![Action Network1 node](/_images/integrations/builtin/app-nodes/actionnetwork/action_network_node1.png) - -### 4. Action Network2 node - -1. First enter your credentials. You can find out how to do that [here](/integrations/builtin/credentials/actionNetwork/). -2. Fill in the remaining parameters as follows: - * **Resource**: Select **Attendance** from the dropdown list. - * **Operation**: Select **Create** from the dropdown list. - * **Person ID**: Enter the ID for the person created by the previous node. - * **Event ID**: Enter the ID for the event created in the first node. -3. Enable the **Simple** toggle to return an easier to view response as opposed to the complete raw data. - -![Action Network2 node](/_images/integrations/builtin/app-nodes/actionnetwork/action_network_node2.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.activeCampaign.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.activeCampaign.md deleted file mode 100644 index fe9a8e28f..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.activeCampaign.md +++ /dev/null @@ -1,95 +0,0 @@ -# ActiveCampaign - -[ActiveCampaign](https://www.activecampaign.com/) is a cloud software platform for small-to-mid-sized business. The company offers software for customer experience automation, which combines the email marketing, marketing automation, sales automation, and CRM categories. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/activeCampaign/). - - -## Basic Operations - -* Account - * Create an account - * Delete an account - * Get data of an account - * Get data of all accounts - * Update an account -* Account Contact - * Create an association - * Delete an association - * Update an association -* Contact - * Create a contact - * Delete a contact - * Get data of a contact - * Get data of all contact - * Update a contact -* Contact List - * Add contact to a list - * Remove contact from a list -* Contact Tag - * Add a tag to a contact - * Remove a tag from a contact -* Connection - * Create a connection - * Delete a connection - * Get data of a connection - * Get data of all connections - * Update a connection -* Deal - * Create a deal - * Delete a deal - * Get data of a deal - * Get data of all deals - * Update a deal - * Create a deal note - * Update a deal note -* E-commerce Order - * Create a order - * Delete a order - * Get data of a order - * Get data of all orders - * Update a order -* E-Commerce Customer - * Create a E-commerce Customer - * Delete a E-commerce Customer - * Get data of a E-commerce Customer - * Get data of all E-commerce Customer - * Update a E-commerce Customer -* E-commerce Order Products - * Get data of all order products - * Get data of a ordered product - * Get data of an order's products -* List - * Get all lists -* Tag - * Create a tag - * Delete a tag - * Get data of a tag - * Get data of all tags - * Update a tag - -## Example Usage - -This workflow allows you to create a contact in ActiveCampaign. You can also find the [workflow](https://n8n.io/workflows/412) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [ActiveCampaign]() - -The final workflow should look like the following image. - -![A workflow with the ActiveCampaign node](/_images/integrations/builtin/app-nodes/activecampaign/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. ActiveCampaign node - -1. First of all, you'll have to enter credentials for the ActiveCampaign node. You can find out how to do that [here](/integrations/builtin/credentials/activeCampaign/). -2. Enter the email of the contact in the *Email* field. -3. Toggle the *Update if exists* option to yes. -4. Under the *Additional Fields* section, click on the *Add Field* button and select *First Name*. -5. Enter the first name of the contact in the *First Name* field. -6. Click on *Add Field* again and select *Last Name*. -7. Enter the last name of the contact in the *Last name* field. -8. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.adalo.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.adalo.md deleted file mode 100644 index 8c6d801b8..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.adalo.md +++ /dev/null @@ -1,19 +0,0 @@ -# Adalo - -[Adalo](https://www.adalo.com/){:target=_blank .external-link} is a low code app builder. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/adalo/). - -## Operations - -* Collection - * Create - * Delete - * Get - * Get Many - * Update - -## Related resources - -Refer to [Adalo's documentation](https://help.adalo.com/){:target=_blank .external-link} for more information on using Adalo. Their [External Collections with APIs](https://help.adalo.com/integrations/external-collections-with-apis){:target=_blank .external-link} page gives more detail about what you can do with Adalo collections. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.affinity.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.affinity.md deleted file mode 100644 index 600444c6f..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.affinity.md +++ /dev/null @@ -1,52 +0,0 @@ -# Affinity - -[Affinity](https://www.affinity.co/) is a powerful relationship intelligence platform enabling teams to leverage their network to close the next big deal. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/affinity/). - - -## Basic Operations - -* List - * Get a list - * Get all lists -* List Entry - * Create a list entry - * Delete a list entry - * Get a list entry - * Get all list entries -* Organization - * Create an organization - * Delete an organization - * Get an organization - * Get all organizations - * Update an organization -* Person - * Create a person - * Delete a person - * Get a person - * Get all persons - * Update a person - - -## Example Usage - -This workflow allows you to create an organization in Affinity. You can also find the [workflow](https://n8n.io/workflows/476) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Affinity]() - -The final workflow should look like the following image. - -![A workflow with the Affinity node](/_images/integrations/builtin/app-nodes/affinity/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Affinity node - -1. First of all, you'll have to enter credentials for the Affinity node. You can find out how to do that [here](/integrations/builtin/credentials/affinity/). -2. Enter the name of the organization in the *Name* field. -3. Enter the domain name of the organization in the *Domain* field. -4. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.agileCrm.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.agileCrm.md deleted file mode 100644 index 0af980d17..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.agileCrm.md +++ /dev/null @@ -1,53 +0,0 @@ -# Agile CRM - -[Agile CRM](https://www.agilecrm.com/) is a CRM with Sales, Marketing and Service automation in single platform. It has sales tracking, contact management, marketing automation, web analytics, two-way emails, telephony, and a helpdesk. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/agileCrm/). - - -## Basic Operations - -* Company - * Create a new company - * Delete a company - * Get a company - * Get all companies - * Update company properties -* Contact - * Create a new contact - * Delete a contact - * Get a contact - * Get all contacts - * Update contact properties -* Deal - * Create a new deal - * Delete a deal - * Get a deal - * Get all deals - * Update deal properties - - -## Example Usage - -This workflow allows you to create a new contact in Agile CRM. You can also find the [workflow](https://n8n.io/workflows/474) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Agile CRM]() - -The final workflow should look like the following image. - -![A workflow with the Agile CRM node](/_images/integrations/builtin/app-nodes/agilecrm/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Agile CRM node - -1. First of all, you'll have to enter credentials for the Agile CRM node. You can find out how to do that [here](/integrations/builtin/credentials/agileCrm/). -2. Select the 'Create' option from the *Operation* dropdown list. -3. Under the *Additional Fields* section, click on the *Add Field* button and select *First Name*. -5. Enter the first name of the contact in the *First Name* field. -6. Click on *Add Field* again and select *Last Name*. -7. Enter the last name of the contact in the *Last name* field. -8. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.airtable.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.airtable.md deleted file mode 100644 index 64f059c13..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.airtable.md +++ /dev/null @@ -1,142 +0,0 @@ -# Airtable - -[Airtable](https://airtable.com/) is a spreadsheet-database hybrid, with the features of a database but applied to a spreadsheet. The fields in an Airtable table are similar to cells in a spreadsheet, but have types such as 'checkbox', 'phone number', and 'drop-down list', and can reference file attachments like images. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/airtable/). - - -## Basic Operations - -* Append the data to a table -* Delete data from a table -* List data from a table -* Read data from a table -* Update data in a table - - -## Example Usage - -This workflow allows you to insert and update data from a table in Airtable. You can also find the [workflow](https://n8n.io/workflows/818) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Airtable]() - -The final workflow should look like the following image. - -![A workflow with the Airtable node](/_images/integrations/builtin/app-nodes/airtable/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Set node - -We will use the Set node to set the values for the name and id fields for a new record. - -1. Click on the ***Add Value*** button and select 'Number' from the dropdown list. -2. Enter `ID` in the ***Name*** field. -3. Enter an id in the ***Value*** field. -4. Click on the ***Add Value*** button and select 'String' from the dropdown list. -5. Enter `Name` in the ***Name*** field. -6. Enter a name in the ***Value*** field. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sets the value for `ID` and `Name`. - -![Using the Set node to set data to be inserted by the Airtable node](/_images/integrations/builtin/app-nodes/airtable/set_node.png) - -### 3. Airtable node (Append) - -This node will append the data that we set in the previous node to a table. Create a table like [this](https://airtable.com/shrN2yLZyKEETq1xj) 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 'Append' 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 ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node appends the data that we had set in the previous node. - -![Using the Airtable node to insert data into an Airtable table](/_images/integrations/builtin/app-nodes/airtable/airtable_node.png) - -### 4. Airtable1 node (List) - -This node will list all the records with the name `n8n`. If you want to list records with a different name, use that name instead. - -1. Select the credentials that you entered in the previous node. -2. Select the 'List' option from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Base ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Airtable > Parameters > application. You can also add the following expression: `{{$node["Airtable"].parameter["application"]}}`. -5. Click on the gears icon next to the ***Table*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Airtable > Parameters > table. You can also add the following expression: `{{$node["Airtable"].parameter["table"]}}`. -7. Click on ***Add Option*** and select 'Filter By Formula' from the dropdown list. -8. Enter `Name='n8n'` in the ***Filter By Formula*** field. -9. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node only returns the record with the name `n8n`. - -![Using the Airtable node to read data from an Airtable table](/_images/integrations/builtin/app-nodes/airtable/airtable1_node.png) - -### 5. Set1 node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. We will set the value of `Name` in this node. - -1. Click on the ***Add Value*** button and select 'String' from the dropdown list. -2. Enter `Name` in the ***Name*** field. -3. Enter `nodemation` in the ***Value*** field. -4. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sets the value of `Name`. This value is passed to the next node in the workflow. - -![Using the Set node to set data to be inserted by the Airtable node](/_images/integrations/builtin/app-nodes/airtable/set_node.png) - -### 6. Airtable2 node (Update) - -This node will update the Name field of the record that we received from the previous Airtable node. - -1. Select the credentials that you entered in the previous Airtable node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Base ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Airtable > Parameters > application. You can also add the following expression: `{{$node["Airtable"].parameter["application"]}}`. -5. Click on the gears icon next to the ***Table*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Airtable > Parameters > table. You can also add the following expression: `{{$node["Airtable"].parameter["table"]}}`. -7. Click on the gears icon next to the ***Id*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > Airtable1 > Output Data > JSON > id. You can also add the following expression: `{{$node["Airtable1"].json["id"]}}`. -9. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node updates the Name field. - -![Using the Airtable node to update data of a record](/_images/integrations/builtin/app-nodes/airtable/airtable2_node.png) - -## FAQs - -### How to get the Record ID? - -To fetch data for a particular record, you need the Record ID. There are two ways to get the Record ID. - -**Create a Record ID column in Airtable** - -To create a `Record ID` column in your table, refer to this [article](https://support.airtable.com/hc/en-us/articles/360051564873-Record-ID). You can then use this Record ID in your Airtable node. - -**Use the List operation** - -To get the Record ID of your record, you can use the ***List*** operation of the Airtable node. This operation will return the Record ID along with the fields. You can then use this Record ID in your Airtable node. - -### How to filter records when using the List operation? - -To filter records from your Airtable base, use the ***Filter By Formula*** option. For example, if you want to return all the users that belong to the organization `n8n`, follow the steps mentioned below: -1. Select 'List' from the ***Operation*** dropdown list. -2. Enter the base ID and the table name in the ***Base ID*** and ***Table*** field, respectively. -3. Click on ***Add Option*** and select 'Filter By Formula' from the dropdown list. -4. Enter the following formula in the ***Filter By Formula*** field: `{Organization}='n8n'`. - -Similarly, if you want to return all the users that do not belong to the organization `n8n`, use the following formula: `NOT({Organization}='n8n')`. - -Refer to the Airtable [documentation](https://support.airtable.com/hc/en-us/articles/203255215-Formula-Field-Reference) to learn more about the formulas. - - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.amqp.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.amqp.md deleted file mode 100644 index 5f7a30659..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.amqp.md +++ /dev/null @@ -1,100 +0,0 @@ -# AMQP Sender - -[AMQP](https://www.amqp.org/) is an open standard application layer protocol for message-oriented middleware. The defining features of AMQP are message orientation, queuing, routing, reliability and security. This node supports AMQP 1.0 compatible message brokers. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/amqp/). - - -## Basic Operations - -- Send message - - -## Example Usage - -This workflow allows you to send updates about the position of the ISS every minute to an [ActiveMQ](https://activemq.apache.org/) queue using the AMQP Sender node. You can also find the [workflow](https://n8n.io/workflows/762) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [AMQP Sender]() - -The final workflow should look like the following image. - -![A workflow with the AMQP Sender node](/_images/integrations/builtin/app-nodes/amqp/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow every minute. - -1. Click on ***Add Cron Time***. -2. Select 'Every Minute' from the ***Mode*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every minute. - -![Using the Cron node to trigger the workflow every minute](/_images/integrations/builtin/app-nodes/amqp/cron_node.png) - -### 2. HTTP Request node (GET) - -This node will make a GET request to the API `https://api.wheretheiss.at/v1/satellites/25544/positions` to fetch the position of the ISS. This information gets passed on to the next node in the workflow. - -1. Enter `https://api.wheretheiss.at/v1/satellites/25544/positions` in the ***URL*** field. -2. Click on the ***Add Parameter*** button in the ***Query Parameters*** section. -3. Enter `timestamps` in the ***Name*** field. -4. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -5. Enter the following expression: `{{Date.now()}}`. This expression will return the current timestamp. -6. 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 the information about the location of the ISS. - -![Using the HTTP Request node to get the information about the location of the ISS](/_images/integrations/builtin/app-nodes/amqp/httprequest_node.png) - -### 3. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `Name` in the ***Name*** 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 > HTTP Request > Output Data > JSON > 0 > name. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["name"]}}`. -5. Click on ***Add Value*** and select 'String' from the dropdown list. -6. Enter `Latitude` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > 0 > latitude. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["latitude"]}}`. -9. Click on ***Add Value*** and select 'String' from the dropdown list. -10. Enter `Longitude` in the ***Name*** field. -11. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > 0 > longitude. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["longitude"]}}`. -13. Click on ***Add Value*** and select 'String' from the dropdown list. -14. Enter `Timestamp` in the ***Name*** field. -15. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -16. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > 0 > timpestamp. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["timestamp"]}}`. -17. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -18. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uses the data from the previous node and returns the data that we set for the workflow. - -![Using the Set node to set the data](/_images/integrations/builtin/app-nodes/amqp/set_node.png) - -### 4. AMQP Sender node - -This node will send the data from the previous node to the `iss-position` queue in ActiveMQ. If you have created a queue with a different name in ActiveMQ, you can use that queue instead. - -1. First of all, you'll have to enter credentials for the AMQP Sender node. You can find out how to do that [here](/integrations/builtin/credentials/amqp/). -2. Enter the name of the queue or topic in the ***Queue / Topic*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends the data from the previous node to the `iss-position` queue in ActiveMQ. - -![Using the AMQP Sender node to send the data to a queue](/_images/integrations/builtin/app-nodes/amqp/amqpsender_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. - - - - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.apiTemplateIo.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.apiTemplateIo.md deleted file mode 100644 index 28069a071..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.apiTemplateIo.md +++ /dev/null @@ -1,93 +0,0 @@ -# APITemplate.io - -[APITemplate.io](https://apitemplate.io) allows you to auto-generate images and PDF documents. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/apiTemplateIo/). - - -## Basic Operations - -* Account - * Get -* Image - * Create -* PDF - * Create - -## Example Usage - -This workflow allows you to create an invoice with the information received via a Typeform submission. You can also find the [workflow](https://n8n.io/workflows/989) on n8n.io. This example usage workflow would use the following nodes. -- [Typeform Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.typeformtrigger/) -- [APITemplate.io]() - -The final workflow should look like the following image. - -![A workflow with the APITemplate.io node](/_images/integrations/builtin/app-nodes/apitemplateio/workflow.png) - -### 1. Typeform Trigger node - -This node will trigger the workflow when a form is submitted. Make sure to create a form that collects the following information: - -- Bill To (Short Text) -- Client's Email Address (Email) -- Item Description (Short Text) -- Item Price (Number) -- Item Description (Short Text) -- Item Price (Number) - -1. Select 'Access Token' from the ***Authentication*** dropdown list. -2. Enter the credentials for the Typeform Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/typeform/). -3. Select the invoice form from the ***Form*** dropdown list. -4. Toggle ***Simplify Answers*** to `false`. By setting this option to false, the node returns the values for the fields with duplicate names. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node triggers the workflow when the form is submitted. We will pass this information to the next nodes in the workflow. - -![Using the Typeform Trigger node to trigger the workflow when a form is submitted](/_images/integrations/builtin/app-nodes/apitemplateio/typeformtrigger_node.png) - -### 2. APITemplate.io node (create: pdf) - -This node will generate an invoice using the information from the previous node. Create an invoice template in APITemplate.io, if you don't already have one. - -1. First of all, you'll have to enter credentials for the APITemplate.io node. You can find out how to do that [here](/integrations/builtin/credentials/apiTemplateIo/). -2. Select 'PDF' from the ***Resource*** dropdown list. -3. Select your invoice template from the ***Template ID*** dropdown list. -4. Toggle ***JSON Parameters*** to `true`. By setting this option to true, the node allows us to write custom JSON data. -5. Toggle ***Download*** to `true`. -6. Click on the gears icon next to the ***Properties (JSON)*** field. -7. Enter the following expression in the ***Edit Expression*** field: -```json -{ - "company": "n8n", - "email": "{{$json["1"]["email"]}}", - "invoice_no": "213223444", - "invoice_date": "18-03-2021", - "invoice_due_date": "17-04-2021", - "address": "Berlin, Germany", - "company_bill_to": "{{$json["0"]["text"]}}", - "website": "https://n8n.io", - "document_id": "889856789012", - "items": [ - { - "item_name": "{{$json["2"]["text"]}}", - "price": "EUR {{$json["3"]["number"]}}" - }, - { - "item_name": "{{$json["4"]["text"]}}", - "price": "EUR {{$json["5"]["number"]}}" - } - ] -} -``` -8. Click on the ***Add Field*** button. -9. Enter a file name in the ***File Name*** field. -10. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates an invoice using the data from the previous node. - -![Using the APITemplate.io node to create an invoice](/_images/integrations/builtin/app-nodes/apitemplateio/apitemplate.io_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Typeform Trigger node. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.asana.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.asana.md deleted file mode 100644 index 0a10db80c..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.asana.md +++ /dev/null @@ -1,64 +0,0 @@ -# Asana - -[Asana](https://asana.com/) is a web and mobile application designed to help teams organize, track, and manage their work. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/asana/). - - -## Basic Operations - -* Project - * Create a new project - * Delete a project - * Get a project - * Get all projects - * Update a project -* Subtask - * Create a subtask - * Get all substasks -* Task - * Create a task - * Delete a task - * Get a task - * Get all tasks - * Move a task - * Search for tasks - * Update a task -* Task Comment - * Add a comment to a task - * Remove a comment from a task -* Task Tag - * Add a tag to a task - * Remove a tag from a task -* Task Project - * Add a task to a project - * Remove a task from a project -* User - * Get a user - * Get all users - -## Example Usage - -This workflow allows you to create a new task in Asana. You can also find the [workflow](https://n8n.io/workflows/478) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Asana]() - -The final workflow should look like the following image. - -![A workflow with the Asana node](/_images/integrations/builtin/app-nodes/asana/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Asana node - -1. First of all, you'll have to enter credentials for the Asana node. You can find out how to do that [here](/integrations/builtin/credentials/asana/). -2. Select your workspace from the *Workspace* dropdown list. -3. Enter the name of the task in the *Name* field. -4. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.automizy.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.automizy.md deleted file mode 100644 index 0ab1a467d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.automizy.md +++ /dev/null @@ -1,98 +0,0 @@ -# Automizy - -[Automizy](https://automizy.com/) is an email marketing automation software that offers AI-powered Subject Line Tester, AB testing, and email automation. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/automizy/). - - -## Basic Operations - -* Contact - * Create a contact - * Delete a contact - * Get a contact - * Get all contacts - * Update a contact -* List - * Create a list - * Delete a list - * Get a list - * Get all lists - * Update a list - -## Example Usage - -This workflow allows you to create a new list, add a new contact to that list, update the contact, and get all contacts in the list using the Automizy node. You can also find the [workflow](https://n8n.io/workflows/720) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Automizy]() - -The final workflow should look like the following image. - -![A workflow with the Automizy node](/_images/integrations/builtin/app-nodes/automizy/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - - -### 2. Automizy node (create: list) - -This node will create a new list called `n8n-docs` in Automizy. - -1. First of all, you'll have to enter credentials for the Automizy node. You can find out how to do that [here](/integrations/builtin/credentials/automizy/). -2. Select 'List' from the ***Resource*** dropdown list. -3. Enter `n8n-docs` in the ***Name*** field. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new list with the name `n8n-docs`. - -![Using the Automizy node to create a new list](/_images/integrations/builtin/app-nodes/automizy/automizy_node.png) - -### 3. Automizy1 node (create: contact) - -This node creates a new contact and adds it to the list created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Enter the email address of the contact you want to add to the list in the ***Email*** field. -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 > Automizy > Output Data > JSON > id. You can also add the following expression: `{{$node["Automizy"].json["id"]}}`. -5. Click on ***Add Field*** and select 'Status' from the dropdown list. -6. Select 'Active' from the ***Status*** dropdown list. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new contact with the email address `example@n8n.io` and status `Active` and adds it to the list `n8n-docs` created in the previous node. - -![Using the Automizy node to create a new contact and add it to the list](/_images/integrations/builtin/app-nodes/automizy/automizy1_node.png) - -### 4. Automizy2 node (update: contact) - -This node updates the contact that we created in the previous node by adding the tag `reviewer` to it. Make sure that you create a tag in Automizy. - - -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 ***Email*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Automizy1 > Output Data > JSON > email. You can also add the following expression: `{{$node["Automizy1"].json["email"]}}`. -5. Click on ***Add Field*** and select 'Tags' from the dropdown list. -6. Select a tag from the ***Tags*** dropdown list. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node updates the contact created in the previous node by adding the tag `reviewer` to it. - -![Using the Automizy node to update the contact by adding a tag](/_images/integrations/builtin/app-nodes/automizy/automizy2_node.png) - -### 5. Automizy3 node (getAll: contact) - -This node returns all the contacts of the `n8n-docs` list that we created using the Automizy node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Get All' 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 > Automizy > Output Data > JSON > id. You can also add the following expression: `{{$node["Automizy"].json["id"]}}`. -5. Toggle ***Return All*** to true. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns all the contacts that are present in the list `n8n-docs`. - -![Using the Automizy node to get all the contacts in a list](/_images/integrations/builtin/app-nodes/automizy/automizy3_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.autopilot.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.autopilot.md deleted file mode 100644 index a3ddc4820..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.autopilot.md +++ /dev/null @@ -1,100 +0,0 @@ -# Autopilot - -[Autopilot](https://www.autopilothq.com/) is a visual marketing software that allows you to automate and personalize your marketing across the entire customer journey. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/autopilot/). - - -## Basic Operations - -* Contact - * Create/Update a contact - * Delete a contact - * Get a contact - * Get all contacts -* Contact Journey - * Add contact to list -* Contact List - * Add contact to list. - * Check if contact is on list. - * Get all contacts on list. - * Remove a contact from a list. -* List - * Create a list. - * Get all lists - -## Example Usage - -This workflow allows you to create a new list, add a new contact to that list, update the contact, and get all contacts in the list using the Autopilot node. You can also find the [workflow](https://n8n.io/workflows/990) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Autopilot]() - -The final workflow should look like the following image. - -![A workflow with the Autopilot node](/_images/integrations/builtin/app-nodes/autopilot/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - - -### 2. Autopilot node (create: list) - -This node will create a new list called `n8n-docs` in Autopilot. - -1. First of all, you'll have to enter credentials for the Autopilot node. You can find out how to do that [here](/integrations/builtin/credentials/autopilot/). -2. Select 'List' from the ***Resource*** dropdown list. -3. Enter `n8n-docs` in the ***Name*** field. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new list with the name `n8n-docs`. - -![Using the Autopilot node to create a new list](/_images/integrations/builtin/app-nodes/autopilot/autopilot_node.png) - -### 3. Autopilot1 node (upsert: contact) - -This node creates a new contact and adds it to the list created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Enter the email address of the contact you want to add to the list in the ***Email*** field. -3. Click on ***Add Field*** and select 'List ID' from the dropdown list. -4. Click on the gears icon next to the ***List ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > list_id. You can also add the following expression: `{{$json["list_id"]}}`. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new contact with the email address `harshil@n8n.io` and adds it to the list `n8n-docs` created in the previous node. - -![Using the Autopilot node to create a new contact and add it to the list](/_images/integrations/builtin/app-nodes/autopilot/autopilot1_node.png) - -### 4. Autopilot2 node (update: contact) - -This node updates the information of the contact that we created in the previous node. - - -1. Select the credentials that you entered in the previous node. -2. Click on the gears icon next to the ***Email*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Nodes > Autopilot1 > Parameters > email. You can also add the following expression: `{{$node["Autopilot1"].parameter["email"]}}`. -4. Click on ***Add Field*** and select 'Company' from the dropdown list. -5. Enter `n8n` in the ***Company*** field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node updates the contact created in the previous node by adding the tag `reviewer` to it. - -![Using the Autopilot node to update the contact by adding a tag](/_images/integrations/builtin/app-nodes/autopilot/autopilot2_node.png) - -### 5. Autopilot3 node (getAll: contact) - -This node returns all the contacts of the `n8n-docs` list that we created using the Autopilot node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Contact List' from the ***Resource*** dropdown list. -3. Select 'Get All' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***List ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > Autopilot > Output Data > JSON > list_id. You can also add the following expression: `{{$node["Autopilot"].json["list_id"]}}`. -6. Toggle ***Return All*** to true. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns all the contacts that are present in the list `n8n-docs`. - -![Using the Autopilot node to get all the contacts in a list](/_images/integrations/builtin/app-nodes/autopilot/autopilot3_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsCertificateManager.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsCertificateManager.md deleted file mode 100644 index 0ebc79317..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsCertificateManager.md +++ /dev/null @@ -1,21 +0,0 @@ -# AWS Certificate Manager - -[AWS Certificate Manager](https://aws.amazon.com/certificate-manager/){:target=_blank .external-link} is a service that lets you provision, manage, and deploy public and private Secure Sockets Layer/Transport Layer Security (SSL/TLS) certificates for use with AWS services and your internal connected resources. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/aws/). - -## Operations - -* Certificate - * Delete - * Get - * Get Many - * Get Metadata - * Renew - -## Related resources - -Refer to [AWS Certificate Manager's documentation](https://docs.aws.amazon.com/acm/latest/userguide/acm-overview.html){:target=_blank .external-link} for more information on this service. - -View [example workflows and related content](https://n8n.io/integrations/aws-certificate-manager/){:target=_blank .external-link} on n8n's website. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsComprehend.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsComprehend.md deleted file mode 100644 index 5b041d9a5..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsComprehend.md +++ /dev/null @@ -1,100 +0,0 @@ -# AWS Comprehend - -[AWS Comprehend](https://aws.amazon.com/comprehend/) is a natural language processing (NLP) service that uses machine learning to find insights and relationships in a text. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/aws/). - - -## Basic Operations - -**Text** - -- Identify the dominant language -- Analyse the sentiment of the text - - -## Example Usage - -This workflow allows you to analyze the sentiment of feedback received via a Typeform submission and send a message on Mattermost if that feedback is negative. You can also find the [workflow](https://n8n.io/workflows/965) on n8n.io. This example usage workflow uses the following nodes. -- [Typeform Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.typeformtrigger/) -- [AWS Comprehend]() -- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/) -- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/) -- [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 AWS Comprehend node](/_images/integrations/builtin/app-nodes/awscomprehend/workflow.png) - -### 1. Typeform Trigger node - -This node will trigger the workflow when a feedback form is submitted. Make sure to create a feedback form for your event. - -1. Select 'Access Token' from the ***Authentication*** dropdown list. -2. Enter the credentials for the Typeform Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/typeform/). -3. Select the event feedback form from the ***Form*** dropdown list. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node triggers the workflow when feedback is submitted. We will pass this feedback to the next nodes in the workflow. - -![Using the Typeform Trigger node to trigger the workflow when a feedback form is submitted](/_images/integrations/builtin/app-nodes/awscomprehend/typeformtrigger_node.png) - -### 2. AWS Comprehend node (detectSentiment: text) - -This node will analyze the sentiment of the feedback that we got from the previous node. We will pass the analysis score to the next node in the workflow. - -1. First of all, you'll have to enter credentials for the AWS Comprehend node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/aws/). -2. Select 'Detect Sentiment' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Text*** field and click on ***Add Expression***. - -4. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > What did you think about the event? You can also add the following expression: `{{$json["What did you think about the event?"]}}`. If you want to analyze the sentiment for a different question, select that question instead. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node analyzes the sentiment of the feedback and gives a score based on that. - -![Using the AWS Comprehend node to analyze the sentiment](/_images/integrations/builtin/app-nodes/awscomprehend/awscomprehend_node.png) - - -### 3. IF node - -This node will check if the sentiment we got from the previous node is negative. If the sentiment is negative, it will return true otherwise false. - -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: Current Node > Input Data > JSON > Sentiment. You can also add the following expression: `{{$json["Sentiment"]}}`. -4. Enter `NEGATIVE` in the ***Value 2*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node checks the sentiment that we received from the previous node and returns `true` if the sentiment is negative. - -![Using the IF node to check if the sentiment](/_images/integrations/builtin/app-nodes/awscomprehend/if_node.png) - -### 4. Mattermost node (post: message) - -This node will send the feedback and the analysis score to the `feedback` channel in Mattermost. If you have a different channel, use that instead. - -1. Create a Mattermost node connected to the 'true' output of the IF node. -2. You'll have to enter credentials for the Mattermost node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/mattermost/). -3. Select a channel from the ***Channel ID*** dropdown list. -4. Click on the gears icon next to the ***Message*** field click on ***Add Expression***. - -5. Enter the following message in the ***Expression*** field: `You got new feedback with a score of {{$json["SentimentScore"]["Negative"]}}. Here is what it says:{{$node["Typeform Trigger"].json["What did you think about the event?"]}}`. -6. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that the node sends the feedback and the analysis score to the `feedback` channel in Mattermost. - -![Using the Mattermost node to send the feedback and the analysis score](/_images/integrations/builtin/app-nodes/awscomprehend/mattermost_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/awscomprehend/noop_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.awsDynamoDb.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsDynamoDb.md deleted file mode 100644 index 251b65ac0..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsDynamoDb.md +++ /dev/null @@ -1,56 +0,0 @@ -# AWS DynamoDB - -[AWS DynamoDB](https://aws.amazon.com/DynamoDB/) is a key-value and document database provided by Amazon as a part of Amazon Web Services. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/aws/). - - -## Basic operations - -* Item - * Create a new record, or update the current one if it already exists (upsert/put) - * Delete an item - * Get an item - * Get all items - -## Example usage - -This workflow allows you to insert an item into your DynamoDB database. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Function](/integrations/builtin/core-nodes/n8n-nodes-base.function/) -- [AWS DynamoDB]() - -The final workflow should look like the following image. - -![A workflow with the AWS DynamoDB node](/_images/integrations/builtin/app-nodes/awsdynamodb/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Function node - -The function node will return the item to insert, [properly formatted](https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_AttributeValue.html) for our table structure `id: number`. - -1. Enter the following snippet: - ```js - return [ - { - json: { - id: { - 'N': '1' - } - } - } - ] - ``` - -### 3. AWS DynamoDB node - -1. First enter credentials for the AWS DynamoDB node. You can find out how to do that [here](/integrations/builtin/credentials/aws/). -2. The **Item** ***Resource*** is selected by default. -3. Select the **Create or Update** ***Operation***. -4. Enter the ***Table Name*** where you are inserting data. -5. In ***Data to Send*** select **Define Below for Each Column**. -6. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsElb.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsElb.md deleted file mode 100644 index c835a76b1..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsElb.md +++ /dev/null @@ -1,26 +0,0 @@ -# AWS Elastic Load Balancing - -[AWS Elastic Load Balancing](https://aws.amazon.com/elasticloadbalancing/){:target=_blank .external-link} (ELB) automatically distributes incoming application traffic across multiple targets and virtual appliances in one or more Availability Zones (AZs). - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/aws/). - -## Operations - -* Listener Certificate - * Add - * Get Many - * Remove -* Load Balancer - * Create - * Delete - * Get - * Get Many - -This node supports creating and managing application and network load balancers. It doesn't currently support gateway load balancers. - -## Related resources - -Refer to [AWS ELB's documentation](https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/what-is-load-balancing.html){:target=_blank .external-link} for more information on this service. - -View [example workflows and related content](https://n8n.io/integrations/aws-elb/){:target=_blank .external-link} on n8n's website. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsLambda.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsLambda.md deleted file mode 100644 index 5b61af37c..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsLambda.md +++ /dev/null @@ -1,31 +0,0 @@ -# AWS Lambda - -[AWS Lambda](https://aws.amazon.com/lambda/) is an event-driven, serverless computing platform provided by Amazon as a part of Amazon Web Services. It is a computing service that runs code in response to events and automatically manages the computing resources required by that code. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/aws/). - - -## Basic Operations - -* Invoke a function - -## Example Usage - -This workflow allows you to invoke a function using AWS Lambda. You can also find the [workflow](https://n8n.io/workflows/510) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [AWS Lambda]() - -The final workflow should look like the following image. - -![A workflow with the AWS Lambda node](/_images/integrations/builtin/app-nodes/awslambda/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. AWS Lambda node - -1. First of all, you'll have to enter credentials for the AWS Lambda node. You can find out how to do that [here](/integrations/builtin/credentials/aws/). -2. Select the function that you want to invoke from the *Function* dropdown list. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsRekognition.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsRekognition.md deleted file mode 100644 index c56a37ac0..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsRekognition.md +++ /dev/null @@ -1,55 +0,0 @@ -# AWS Rekognition - -[AWS Rekognition](https://aws.amazon.com/rekognition/) allows you to add image and video analysis to your applications. With AWS Rekognition, you can identify faces, labels, and celebrities in images. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/aws/). - - -## Basic Operations - -**Image** - -- Analyze - - -## Example Usage - -This workflow allows you to detect a face from an image using the AWS Rekognition node. You can also find the [workflow](https://n8n.io/workflows/694) 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/) -- [AWS Rekognition]() - -The final workflow should look like the following image. - -![A workflow with the AWS Rekognition node](/_images/integrations/builtin/app-nodes/awsrekognition/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - - -### 2. HTTP Request node (GET) - -This example workflow uses the HTTP Request node to fetch an image from a URL. You can also use the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node to read an image file from the path you specify. - -1. Enter the URL of the image in the ***URL*** field. For example, `https://n8n.io/_nuxt/img/04c67e5.png`. -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 fetches the image from the URL. This image gets passed on as binary data to the next node in the workflow. - -![Using the HTTP Request node to fetch an image from a URL](/_images/integrations/builtin/app-nodes/awsrekognition/httprequest_node.png) - - -### 3. AWS Rekognition node (analyze: image) - -This node will detect faces in the image that we fetched in the previous node. You can also use this node to analyze an image stored in your AWS Bucket. - -1. First of all, you'll have to enter credentials for the AWS Rekognition node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/aws/). -2. Set ***Binary Data*** to `true`. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will observe that the node detects the face in the image that we got from the HTTP Request node. - -![Using the AWS Rekognition node to detect faces in an image](/_images/integrations/builtin/app-nodes/awsrekognition/awsrekognition_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsS3.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsS3.md deleted file mode 100644 index 65445d8cb..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsS3.md +++ /dev/null @@ -1,50 +0,0 @@ -# AWS S3 - -[AWS S3](https://aws.amazon.com/s3/) is a service offered by Amazon Web Services that provides object storage through a web service interface. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/aws/). - - -## Basic Operations - -* Bucket - * Create a bucket - * Delete a bucket - * Get all buckets - * Search within a bucket -* File - * Copy a file - * Delete a file - * Download a file - * Get all files - * Upload a file -* Folder - * Create a folder - * Delete a folder - * Get all folders - -## Example Usage - -This workflow allows you to create a bucket on AWS S3. You can also find the [workflow](https://n8n.io/workflows/458) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [AWS S3]() - -The final workflow should look like the following image. - -![A workflow with the AWS S3 node](/_images/integrations/builtin/app-nodes/awss3/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. AWS S3 node - -1. First of all, you'll have to enter credentials for the AWS S3 node. You can find out how to do that [here](/integrations/builtin/credentials/aws/). -2. Select 'Bucket' from the *Resource* dropdown list. -3. Enter a name for your bucket in the *Name* field. -4. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsSes.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsSes.md deleted file mode 100644 index 87b026996..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsSes.md +++ /dev/null @@ -1,53 +0,0 @@ -# AWS SES - -[AWS SES](https://aws.amazon.com/ses/) is a cost-effective, flexible, and scalable email service that enables developers to send mail from within any application. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/aws/). - - -## Basic Operations - -* Custom Verification Email - * Create a new custom verification email template - * Delete an existing custom verification email template - * Get the custom email verification template - * Get all the existing custom verification email templates for your account - * Add an email address to the list of identities - * Update an existing custom verification email template. -* Email - * Send - * Send Template -* Template - * Create a template - * Delete a template - * Get a template - * Get all templates - * Update a template - -## Example Usage - -This workflow allows you to send an email using AWS SES. You can also find the [workflow](https://n8n.io/workflows/507) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [AWS SES]() - -The final workflow should look like the following image. - -![A workflow with the AWS SES node](/_images/integrations/builtin/app-nodes/awsses/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. AWS SNS node - -1. First of all, you'll have to enter credentials for the AWS SES node. You can find out how to do that [here](/integrations/builtin/credentials/aws/). -2. Enter a subject for your email in the *Subject* field. -3. Enter your message in the *Body* field. -4. Enter the email address from which you want to send the email in the *From Email* field. -5. Click on the *Add To Email* button and add your recipient email addresses. -6. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsSns.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsSns.md deleted file mode 100644 index 3d9d41222..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsSns.md +++ /dev/null @@ -1,33 +0,0 @@ -# AWS SNS - -[AWS SNS](https://aws.amazon.com/sns/) is a notification service provided as part of Amazon Web Services. It provides a low-cost infrastructure for the mass delivery of messages, predominantly to mobile users. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/aws/). - - -## Basic Operations - -* Publish a message to a topic - -## Example Usage - -This workflow allows you to publish a message using AWS SNS. You can also find the [workflow](https://n8n.io/workflows/501) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [AWS SNS]() - -The final workflow should look like the following image. - -![A workflow with the AWS SNS node](/_images/integrations/builtin/app-nodes/awssns/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. AWS SNS node - -1. First of all, you'll have to enter credentials for the AWS SNS node. You can find out how to do that [here](/integrations/builtin/credentials/aws/). -2. Select the topic in the *Topic* dropdown list. You can find instructions on how to create a new topic in AWS SNS [here](https://docs.aws.amazon.com/sns/latest/dg/sns-tutorial-create-topic.html). -3. Enter a subject for your message in the *Subject* field. -4. Enter your message in the *Message* field. -5. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsSqs.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsSqs.md deleted file mode 100644 index a65cc0c2d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsSqs.md +++ /dev/null @@ -1,92 +0,0 @@ -# AWS SQS - -[AWS SQS](https://aws.amazon.com/sqs/) is a fully managed message queuing service that enables you to decouple and scale microservices, distributed systems, and serverless applications. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/aws/). - - -## Basic Operations - -* Send a message to a queue. - -## Example Usage - -This workflow allows you to send position updates of the ISS every minute to a queue using the AWS SQS node. You can also find the [workflow](https://n8n.io/workflows/1047) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [AWS SQS]() - -The final workflow should look like the following image. - -![A workflow with the AMQP Sender node](/_images/integrations/builtin/app-nodes/awssqs/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow every minute. - -1. Click on ***Add Cron Time***. -2. Select 'Every Minute' from the ***Mode*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every minute. - -![Using the Cron node to trigger the workflow every minute](/_images/integrations/builtin/app-nodes/awssqs/cron_node.png) - -### 2. HTTP Request node (GET) - -This node will make a GET request to the API `https://api.wheretheiss.at/v1/satellites/25544/positions` to fetch the position of the ISS. This information gets passed on to the next node in the workflow. - -1. Enter `https://api.wheretheiss.at/v1/satellites/25544/positions` in the ***URL*** field. -2. Click on the ***Add Parameter*** button in the ***Query Parameters*** section. -3. Enter `timestamps` in the ***Name*** field. -4. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -5. Enter the following expression: `{{Date.now()}}`. This expression will return the current timestamp. -6. 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 the information about the location of the ISS. - -![Using the HTTP Request node to get the information about the location of the ISS](/_images/integrations/builtin/app-nodes/awssqs/httprequest_node.png) - -### 3. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `Name` in the ***Name*** 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 > HTTP Request > Output Data > JSON > 0 > name. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["name"]}}`. -5. Click on ***Add Value*** and select 'Number' from the dropdown list. -6. Enter `Latitude` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > 0 > latitude. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["latitude"]}}`. -9. Click on ***Add Value*** and select 'Number' from the dropdown list. -10. Enter `Longitude` in the ***Name*** field. -11. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > 0 > longitude. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["longitude"]}}`. -13. Click on ***Add Value*** and select 'Number' from the dropdown list. -14. Enter `Timestamp` in the ***Name*** field. -15. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -16. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > 0 > timpestamp. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["timestamp"]}}`. -17. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -18. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uses the data from the previous node and returns the data that we set for the workflow. - -![Using the Set node to set the data](/_images/integrations/builtin/app-nodes/awssqs/set_node.png) - -### 4. AWS SQS node - -This node will send the data from the previous node to the `iss-position` queue. If you have created a queue with a different one, you can use that queue instead. - -1. First of all, you'll have to enter credentials for the AWS SQS node. You can find out how to do that [here](/integrations/builtin/credentials/aws/). -2. Select the queue from the ***Queue*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends the data from the previous node to the `iss-position` queue in ActiveMQ. - -![Using the AWS SQS node to send the data to a queue](/_images/integrations/builtin/app-nodes/awssqs/awssqs_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsTextract.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsTextract.md deleted file mode 100644 index cb2edbf90..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsTextract.md +++ /dev/null @@ -1,50 +0,0 @@ -# AWS Textract - -[AWS Textract](https://aws.amazon.com/textract/) is a service that extracts printed text, handwriting, and data from any document. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/aws/). - - -## Basic Operations - -- Analyze Receipt or Invoice - -## Example Usage - -This workflow allows you to extract data from a an invoice stored in AWS S3. You can also find the [workflow](https://n8n.io/workflows/1282) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [AWS S3](/integrations/builtin/app-nodes/n8n-nodes-base.awsS3/) -- [AWS Textract]() - -The final workflow looks like the following image. - -![A workflow using the AWS S3 and AWS Textract node](/_images/integrations/builtin/app-nodes/awstextract/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. AWS S3 node (download: file) - -This node will retrieve an image file with a receipt from an S3 bucket. - -1. Choose your credentials for the AWS S3 node. See [here](/integrations/builtin/credentials/aws/) for information on how to create these credentials. -2. Enter the bucket name in the ***Bucket Name*** field. -3. Enter the file key in the ***File Key*** field. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below you can see the file returned by the node. - -![Using the AWS S3 node to fetch a file stored in a bucket](/_images/integrations/builtin/app-nodes/awstextract/awss3_node.png) - -### 3. AWS Textract node (analyzeExpense) - -This node will extract data from the receipt returned by the previous node. - -1. Choose your AWS credentials. -2. Click on ***Execute Node*** to run the node. - -In the screenshot below, you can see the receipt data extracted by AWS Textract and returned by the node. - -![Using the AWS Textract node to extract data from a receipt](/_images/integrations/builtin/app-nodes/awstextract/awstextract_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsTranscribe.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsTranscribe.md deleted file mode 100644 index db0d67bfa..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.awsTranscribe.md +++ /dev/null @@ -1,61 +0,0 @@ -# AWS Transcribe - -[AWS Transcribe](https://aws.amazon.com/transcribe/) is a service that recognizes speech in your audio or video and transcribes that speech into text. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/aws/). - - -## Basic Operations - -**Transcription Job** -- Create a transcription job -- Delete a transcription job -- Get a transcription job -- Get all transcriptions job - - -## Example Usage - -This workflow allows you to create transcription jobs for all your audio and video files stored in AWS S3. You can also find the [workflow](https://n8n.io/workflows/1111) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [AWS S3](/integrations/builtin/app-nodes/n8n-nodes-base.awsS3/) -- [AWS Transcribe]() - -The final workflow should look like the following image. - -![A workflow with the AMQP Sender node](/_images/integrations/builtin/app-nodes/awstranscribe/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. AWS S3 node (getAll: file) - -This node will retrieve all the files from an S3 bucket you specify. - -1. First of all, you'll have to enter credentials for the AWS S3 node. You can find out how to do that [here](/integrations/builtin/credentials/aws/). -2. Select 'Get All' from the ***Operation*** dropdown list. -3. Enter the bucket name in the ***Bucket Name*** field. -4. Toggle ***Return All*** to `true`. This option will return information on all the files stored in the S3 bucket. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns information of all the files stored in the bucket you specified. - -![Using the AWS S3 node to fetch information of files stored in a bucket](/_images/integrations/builtin/app-nodes/awstranscribe/awss3_node.png) - -### 3. AWS Transcribe node (create: transcriptionJob) - -This node will create a transcription job for the files that get returned by the previous node. - -1. Select the credentials that you entered in the previous node. -2. Click on the gears icon next to the ***Job Name*** field and click on ***Add Expression***. -3. Enter `{{$json["Key"].replace(/\s/g,'-')}}` in the ***Expression*** field. The code snippet fetches the name of the file and replaces the white-spaces with a hyphen (-). -4. Click on the gears icon next to the ***Media File URI*** field and click on ***Add Expression***. -5. Enter `s3://{{$node["AWS S3"].parameter["bucketName"]}}/{{$json["Key"]}}` in the ***Expression*** field. -6. Toggle ***Detect Language*** to `true`. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a transcription job for the files stored in an S3 bucket. - -![Using the AWS Transcribe node to create a transcription job](/_images/integrations/builtin/app-nodes/awstranscribe/awstranscribe_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.bambooHr.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.bambooHr.md deleted file mode 100644 index f8ef73118..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.bambooHr.md +++ /dev/null @@ -1,29 +0,0 @@ -# BambooHR - -[BambooHR](https://www.bamboohr.com/) provides human resources software as a service. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/bambooHr/). - - -## Basic Operations - -* Company Report - * Get a company report -* Employee - * Create an employee - * Get an employee - * Get all employees - * Update an employee -* Employee Document - * Delete an employee document - * Download an employee document - * Get all employee document - * Update an employee document - * Upload an employee document -* File - * Delete a company file - * Download a company file - * Get all company files - * Update a company file - * Upload a company file diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.bannerbear.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.bannerbear.md deleted file mode 100644 index baa3f2808..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.bannerbear.md +++ /dev/null @@ -1,43 +0,0 @@ -# Bannerbear - -[Bannerbear](https://www.bannerbear.com/) is an API-based image generation service that automatically generates variations of graphic templates. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/bannerbear/). - - -## Basic Operations - -* Image - * Create an image - * Get an image -* Template - * Get a template - * Get all templates - -## Example Usage - -This workflow allows you to create an image using the Bannerbear welcome template. You can also find the [workflow](https://n8n.io/workflows/544) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Bannerbear]() - -The final workflow should look like the following image. - -![A workflow with the Bannerbear node](/_images/integrations/builtin/app-nodes/bannerbear/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Bannerbear node - -1. First of all, you'll have to enter credentials for the Bannerbear node. You can find out how to do that [here](/integrations/builtin/credentials/bannerbear/). -2. Select 'Welcome Template' from the *Template ID* dropdown list. -3. Click on the *Add Field* dropdown, select 'Wait for Image', and set the slider is set to 'on'. -4. Click on the *Add Modification* button and select 'message' from the *Name* dropdown list. -5. Enter the text in the *Text* field. -6. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.baserow.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.baserow.md deleted file mode 100644 index 2a3ab2dce..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.baserow.md +++ /dev/null @@ -1,93 +0,0 @@ -# Baserow - -[Baserow](https://baserow.io/) is an open source no-code database and Airtable alternative. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/baserow/). - - -## Basic operations - -* Row - * Create a row - * Delete a row - * Retrieve a row - * Retrieve all rows - * Update a row - -## Example - -This workflow allows you to create, find, and delete rows in Baserow default Customer table. This example workflow uses the following nodes. - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Baserow]() - -The final workflow should look like the following image: - -![A workflow with the Baserow node](/_images/integrations/builtin/app-nodes/baserow/workflow.png) - -For this workflow you need an account to any Baserow instance with the demo table `Customers`. - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Set node - -We will use the Set node to set the values for the `name` and `id` fields of a new record. - -1. Click on the ***Add Value*** button and select 'String' from the dropdown list. -2. Enter `Name` in the ***Name*** field. -3. Enter a name in the ***Value*** field. -4. Click on the ***Add Value*** button and select 'String' from the dropdown list. -5. Enter `Last name` in the ***Name*** field. -6. Enter a last name in the ***Value*** field. -7. Click on the ***Add Value*** button and select 'Boolean' from the dropdown list. -8. Enter `Active` in the ***Name*** field. -9. Check the value. -10. Click on ***Execute Node*** to run the node. - -### 3. Baserow node (Create) - -This node will create a row in the `Customers` table with the content from the previous node. - -1. Enter your credentials for the Baserow node. You can find out how to create credentials [here](/integrations/builtin/credentials/baserow/). -2. Enter your Baserow instance URL (default value is for official version). -3. Select 'Create' from the ***Operation*** dropdown list. -4. Enter the Table ID in the ***Table ID*** field. For obtaining the Table ID, see the Database API page available from the database menu. -5. Click on ***Execute Node*** to run the node. - -### 4. Baserow node (List) - -This node will list all the rows with the name `Bill`. If you want to list records with a different name, use that name instead. - - -1. Select the credentials that you entered in the previous node. -2. Click on the gears icon next to the ***Host*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: ***Nodes > Baserow > Parameters > Host***. You can also add the following expression: `{{$node["Baserow"].parameter["host"]}}`. -4. Select the 'List' option from the ***Operation*** dropdown list. -5. Click on the gears icon next to the ***Table ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: ***Nodes > Baserow > Parameters > Table***. You can also add the following expression: `{{$node["Baserow"].parameter["table"]}}`. -1. Click on ***Add Option*** and select 'Search' from the dropdown list. -7. Enter `Bill` in the ***Search*** field. -8. Click on ***Execute Node*** to run the node. - - -You will notice that the node only returns the record with a column containing `Bill`. - -### 5. Baserow node (Delete) - -This node will delete all the rows listed from the previous node. - - -1. Select the credentials that you entered in the previous node. -2. Click on the gears icon next to the ***Host*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: ***Nodes > Baserow > Parameters > Host***. You can also add the following expression: `{{$node["Baserow"].parameter["host"]}}`. -4. Select the 'Delete' option from the ***Operation*** dropdown list. -5. Click on the gears icon next to the ***Table ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: ***Nodes > Baserow > Parameters > Table***. You can also add the following expression: `{{$node["Baserow"].parameter["table"]}}`. -5. Click on the gears icon next to the ***Row 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. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.beeminder.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.beeminder.md deleted file mode 100644 index 39c1ba48a..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.beeminder.md +++ /dev/null @@ -1,60 +0,0 @@ -# Beeminder - -[Beeminder](https://www.beeminder.com/) is a service that helps you to self-track and stick to your goals. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/beeminder/). - - - -## Basic Operations - -**Datapoint** -- Create datapoint for a goal -- Delete a datapoint -- Get all datapoints for a goal -- Update a datapoint - - -## Example Usage - -This workflow allows you to add a datapoint to Beeminder when a new activity gets added to Strava. You can also find the [workflow](https://n8n.io/workflows/900) on n8n.io. This example usage workflow would use the following nodes. -- [Strava Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.stravatrigger/) -- [Beeminder]() - -The final workflow should look like the following image. - -![A workflow with the Beeminder node](/_images/integrations/builtin/app-nodes/beeminder/workflow.png) - -### 1. Strava Trigger node - -This node will trigger the workflow whenever a new activity gets added to your Strava account. - -1. First of all, you'll have to enter credentials for the Strava Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/strava/). -2. Select 'created' from the ***Event*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node triggers the workflow when a new activity gets added to Strava. - -![Using the Strava Trigger node to trigger the workflow](/_images/integrations/builtin/app-nodes/beeminder/stravatrigger_node.png) - -### 2. Beeminder node (create: datapoint) - -This node will create a datapoint for the goal `testing`. If you have created a goal with a different name, select that goal instead. - -1. First of all, you'll have to enter credentials for the Beeminder node. You can find out how to do that [here](/integrations/builtin/credentials/beeminder/). -2. Select a goal from the ***Goal Name*** dropdown list. -3. Click on ***Add Field*** and select 'Comment'. -4. Click on the gears icon next to the ***Comment*** field and click on ***Add Expression***. - -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > object_data > name. You can also add the following expression: `{{$json["object_data"]["name"]}}`. - -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a datapoint in Beeminder. - -![Using the Beeminder node to create a datapoint for a goal](/_images/integrations/builtin/app-nodes/beeminder/beeminder_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Strava Trigger node. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.bitly.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.bitly.md deleted file mode 100644 index 14cdb032a..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.bitly.md +++ /dev/null @@ -1,34 +0,0 @@ -# Bitly - -[Bitly](https://bitly.com/) is URL shortening service and a link management platform that allows users to shorten, create and share trusted, powerful links for businesses. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/bitly/). - - -## Basic Operations - -* Link - * Create a link - * Get a link - * Update a link - -## Example Usage - -This workflow shows you how to create a new link. You can also find the [workflow](https://n8n.io/workflows/442) on the website. This example usage workflow uses the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Bitly]() - -The final workflow should look like the following image. - -![A workflow with the Bitly node](/_images/integrations/builtin/app-nodes/bitly/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Bitly node - -1. First of all, you'll have to enter credentials for the Bitly node. You can find out how to do that [here](/integrations/builtin/credentials/bitly/). -2. Enter the URL in the *Long URL* field. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.bitwarden.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.bitwarden.md deleted file mode 100644 index 08388fbf5..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.bitwarden.md +++ /dev/null @@ -1,110 +0,0 @@ -# Bitwarden - -[Bitwarden](https://www.bitwarden.com/) is an open-source password management solution for individuals, teams, and business organizations. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/bitwarden/). - - - -## Basic Operations - -* Collection - * Delete - * Get - * Get All - * Update -* Event - * Get All -* Group - * Create - * Delete - * Get - * Get All - * Get Members - * Update - * Update Members -* Member - * Create - * Delete - * Get - * Get All - * Get Groups - * Update - * Update Groups - -## Example Usage - -This workflow allows you to create a group, add members to the group, and get the members of the group in Bitwarden. You can also find the [workflow](https://n8n.io/workflows/1001) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Bitwarden]() - -The final workflow should look like the following image. - -![A workflow with the Bitwarden node](/_images/integrations/builtin/app-nodes/bitwarden/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Bitwarden node (create: group) - -This node will create a new group called `documentation` in Bitwarden. - -1. First of all, you'll have to enter credentials for the Bitwarden node. You can find out how to do that [here](/integrations/builtin/credentials/bitwarden/). -2. Select 'Group' from the ***Resource*** dropdown list. -3. Select 'Create' from the ***Operation*** dropdown list. -4. Enter `documentation` 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 group in Bitwarden. - -![Using the Bitwarden node to create a new group](/_images/integrations/builtin/app-nodes/bitwarden/bitwarden_node.png) - -### 3. Bitwarden1 node (getAll: member) - -This node will get all the members from Bitwarden. - -1. Select the credentials that you entered in the previous node. -2. Select 'Member' from the ***Resource*** dropdown list. -3. Select 'Get All' from the ***Operation*** dropdown list. -4. 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 members from Bitwarden. - -![Using the Bitwarden node to get all the members](/_images/integrations/builtin/app-nodes/bitwarden/bitwarden1_node.png) - -### 4. Bitwarden2 node (updateMembers: group) - -This node will update all the members in the group that we created earlier. - -1. Select the credentials that you entered in the previous node. -2. Select 'Group' from the ***Resource*** dropdown list. -3. Select 'Update Members' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Group ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > Bitwarden > Output Data > JSON > id. You can also add the following expression: `{{$node["Bitwarden"].json["id"]}}`. -6. Click on the gears icon next to the ***Member IDs*** field and click on ***Add Expression***. -7. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`. -8. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node updates the members of the group. - -![Using the Bitwarden node to update members in a group](/_images/integrations/builtin/app-nodes/bitwarden/bitwarden2_node.png) - -### 5. Bitwarden3 node (getMembers: group) - -This node will get all the members in the group that we created earlier. - -1. Select the credentials that you entered in the previous node. -2. Select 'Group' from the ***Resource*** dropdown list. -3. Select 'Get Members' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Group ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > Bitwarden > Output Data > JSON > id. You can also add the following expression: `{{$node["Bitwarden"].json["id"]}}`. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node retrieves the members in the group. - -![Using the Bitwarden node to get members in a group](/_images/integrations/builtin/app-nodes/bitwarden/bitwarden3_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.box.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.box.md deleted file mode 100644 index aef32ffe5..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.box.md +++ /dev/null @@ -1,46 +0,0 @@ -# Box - -[Box](https://www.box.com/) is a cloud computing company which provides file sharing, collaborating, and other tools for working with files that are uploaded to its servers. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/box/). - - -## Basic Operations - -* File - * Copy a file - * Delete a file - * Download a file - * Get a file - * Search files - * Share a file - * Upload a file -* Folder - * Create a folder - * Get a folder - * Delete a folder - * Search files - * Share a folder - * Update folder - -## Example Usage - -This workflow allows you to create a folder on Box. You can also find the [workflow](https://n8n.io/workflows/559) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Box]() - -The final workflow should look like the following image. - -![A workflow with the Box node](/_images/integrations/builtin/app-nodes/box/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Box node - -1. First of all, you'll have to enter credentials for the Box node. You can find out how to do that [here](/integrations/builtin/credentials/box/). -2. Select the 'Folder' option from the *Resource* dropdown list. -3. Enter the name of the folder in the *Name* field. -4. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.brandfetch.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.brandfetch.md deleted file mode 100644 index 5621792ec..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.brandfetch.md +++ /dev/null @@ -1,95 +0,0 @@ -# Brandfetch - -[Brandfetch](https://www.Brandfetch.com/) is a brand search engine that helps you find logos, colors, fonts, images, and more. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/brandfetch/). - - - -## Basic Operations - -* Return a company's colors -* Return a company's data -* Return a company's fonts -* Return a company's industry -* Return a company's logo & icon - -## Example Usage - -This workflow allows you to get the logo, icon, and information of a company and store it in Airtable. You can also find the [workflow](https://n8n.io/workflows/835) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Brandfetch]() -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Airtable](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/) - -The final workflow should look like the following image. - -![A workflow with the Brandfetch node](/_images/integrations/builtin/app-nodes/brandfetch/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Brandfetch node (logo) - -This node will fetch the URL of the logo and icon of n8n. If you want the logo and icon of a different company, enter the domain name of that company instead. - -1. First of all, you'll have to enter credentials for the Brandfetch node. You can find out how to do that [here](/integrations/builtin/credentials/brandfetch/). -2. Enter `n8n.io` in the ***Domain*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node retrieves the URL of n8n's logo and icon. - -![Using the Brandfetch node to retrieve the URL of the logo and icon of a comapny](/_images/integrations/builtin/app-nodes/brandfetch/brandfetch_node.png) - -### 3. Brandfetch1 node (company) - -This node will fetch company data about n8n. - -1. Select the credentials that you entered in the previous Brandfetch node. -2. Select 'Company' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Domain*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Brandfetch > Parameters > domain. You can also add the following expression: `{{$node["Brandfetch"].parameter["domain"]}}`. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns company data about n8n. - -![Using the Brandfetch node to retrieve the company data](/_images/integrations/builtin/app-nodes/brandfetch/brandfetch1_node.png) - -### 4. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. We will set the value of `Name`, `Icon URL`, and `Logo URL`in this node. - -1. Click on the ***Add Value*** button and select 'String' from the dropdown list. -2. Enter `Name` in the ***Name*** 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 > Brandfetch1 > Output Data > JSON > name. You can also add the following expression: `{{$node["Brandfetch1"].json["name"]}}`. -5. Click on the ***Add Value*** button and select 'String' from the dropdown list. -6. Enter `Icon URL` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > Brandfetch > Output Data > JSON > icon > image. You can also add the following expression: `{{$node["Brandfetch"].json["icon"]["image"]}}`. -9. Click on the ***Add Value*** button and select 'String' from the dropdown list. -10. Enter `Logo URL` in the ***Name*** field. -11. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Nodes > Brandfetch > Output Data > JSON > logo > image. You can also add the following expression: `{{$node["Brandfetch"].json["logo"]["image"]}}`. -13. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -14. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sets the value of `Name`, `Icon URL`, and `Logo URL`. This value is passed to the next node in the workflow. - -![Using the Set node to set data to be inserted by the Airtable node](/_images/integrations/builtin/app-nodes/brandfetch/set_node.png) - -### 5. Airtable node (Append) - -This node will append the data that we set in the previous node to a table. Create a table like [this](https://airtable.com/shrPVVaVZuHofrDVw) 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 'Append' 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 ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node appends the data that we had set in the previous node. - -![Using the Airtable node to insert data into an Airtable table](/_images/integrations/builtin/app-nodes/brandfetch/airtable_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.bubble.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.bubble.md deleted file mode 100644 index 8b3b6dac9..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.bubble.md +++ /dev/null @@ -1,83 +0,0 @@ -# Bubble - -[Bubble](https://www.bubble.io/) lets you create interactive, multi-user apps for desktop and mobile web browsers. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/bubble/). - - -## Basic Operations - -* Object - * Create - * Delete - * Get - * Get All - * Update - -## Example Usage - -This workflow allows you to create, update, and get an object from Bubble. You can also find the [workflow](https://n8n.io/workflows/1041) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Bubble]() - -The final workflow should look like the following image. - -![A workflow with the Bubble node](/_images/integrations/builtin/app-nodes/bubble/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Bubble node (create: object) - -This node will create a new object of the type `Doc` in Bubble. If you want to create an object with a different type, use that type instead. - -1. First of all, you'll have to enter credentials for the Bubble node. You can find out how to do that [here](/integrations/builtin/credentials/bubble/). -2. Select 'Create' from the ***Operation*** dropdown list. -3. Enter `Doc` in the ***Type Name*** field. -4. Click on the ***Add Property*** button. -5. Enter `Name` in the ***Key*** field. If you're using a different type, enter the field name present in the type. -6. Enter `Bubble` in the ***Value*** field. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new object of the type `Doc` in Bubble. - -![Using the Bubble node to create a new object](/_images/integrations/builtin/app-nodes/bubble/bubble_node.png) - - -### 3. Bubble1 node (update: object) - -This node will update the object that we created using the previous node. - -1. Select the credentials that you entered in the previous Bubble node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Type Name*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Bubble > Parameters > typeName. You can also add the following expression: `{{$node["Bubble"].parameter["typeName"]}}`. -5. Click on the gears icon next to the ***Object 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"]}}`. -6. Click on the ***Add Property*** button. -7. Enter `Name` in the ***Key*** field. If you're using a different type, enter the field name present in the type. -8. Enter `Bubble node` 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 object that got created previously. - -![Using the Bubble node to update the information of an object](/_images/integrations/builtin/app-nodes/bubble/bubble1_node.png) - -### 4. Bubble2 node (get: object) - -This node will retrieve the information of the object that we created earlier. - - -1. Select the credentials that you entered in the previous Bubble node. -2. Click on the gears icon next to the ***Type Name*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Nodes > Bubble > Parameters > typeName. You can also add the following expression: `{{$node["Bubble"].parameter["typeName"]}}`. -4. Click on the gears icon next to the ***Object ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > Bubble > Output Data > JSON > id. You can also add the following expression: `{{$node["Bubble"].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 object that we created earlier. - -![Using the Bubble node to retrieve the information of an object](/_images/integrations/builtin/app-nodes/bubble/bubble2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.chargebee.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.chargebee.md deleted file mode 100644 index e0cbbc876..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.chargebee.md +++ /dev/null @@ -1,42 +0,0 @@ -# Chargebee - -[Chargebee](https://www.chargebee.com/) is a billing platform for subscription based SaaS and eCommerce businesses. Chargebee integrates with payment gateways to let you automate recurring payment collection along with invoicing, taxes, accounting, email notifications, SaaS Metrics and customer management. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/chargebee/). - - -## Basic Operations - -* Customer - * Create a customer -* Invoice - * Return the invoices - * Get URL for the invoice PDF -* Subscription - * Cancel a subscription - * Delete a subscription - -## Example Usage - -This workflow allows you to create a new customer in Chargebee. You can also find the [workflow](https://n8n.io/workflows/483) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Chargebee]() - -The final workflow should look like the following image. - -![A workflow with the Chargebee node](/_images/integrations/builtin/app-nodes/chargebee/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Chargebee node - -1. First of all, you'll have to enter credentials for the Chargebee node. You can find out how to do that [here](/integrations/builtin/credentials/chargebee/). -2. Select the 'Customer' option from the *Resource* dropdown list. -3. Under the *Properties* section, click on the *Add Property* button and select *First Name*. -5. Enter the first name of the contact in the *First Name* field. -6. Click on *Add Property* again and select *Last Name*. -7. Enter the last name of the contact in the *Last name* field. -8. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.circleCi.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.circleCi.md deleted file mode 100644 index 112039815..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.circleCi.md +++ /dev/null @@ -1,36 +0,0 @@ -# CircleCI - -[CircleCI](https://circleci.com/) is a continuous integration and delivery platform helps teams release quality code, faster. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/circleCi/). - - -## Basic Operations - -* Pipeline - * Get a pipeline - * Get all pipelines - * Trigger a pipeline - -## Example Usage - -This workflow allows you to get a pipeline in CircleCI. 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/) -- [CircleCI]() - -The final workflow should look like the following image. - -![A workflow with the CircleCI node](/_images/integrations/builtin/app-nodes/circleci/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 CircleCI node. You can find out how to do that [here](/integrations/builtin/credentials/circleCi/). -2. Select the VCS provider from the dropdown in the *Provider* field. -3. Enter the project slug in the *Project Slug* field. -4. Enter the number of the pipeline in CircleCI that you want to get in the *Pipeline Number* field. -5. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.ciscoWebex.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.ciscoWebex.md deleted file mode 100644 index 955401903..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.ciscoWebex.md +++ /dev/null @@ -1,44 +0,0 @@ -# Webex by Cisco - -[Webex by Cisco](https://webex.com/) is a web conferencing and videoconferencing application. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/ciscoWebex/). - - -## Basic operations - -* Meeting - * Create - * Delete - * Get - * Get All - * Update -* Message - * Create - * Delete - * Get - * Get All - * Update - -## Example usage - -This workflow allows you to create a new meeting. This example usage workflow uses the following node: - -- [Webex by Cisco]() - -The final workflow should look like the following image. - -![A workflow with the Webex by Cisco node](/_images/integrations/builtin/app-nodes/ciscowebex/workflow.png) - -### 1. Webex by Cisco node - -1. First enter your credentials for node. You can find out how to do that [here](/integrations/builtin/credentials/ciscoWebex/). -2. Select 'Meeting' from the *Resource* dropdown list. -3. Select 'Create' from the *Operation* dropdown list. -4. Enter a *Title* for your new meeting. -5. Select the *Start* and *End* times for the meeting. -6. Optionally, use the *Additional Fields* menu to add further meeting details, for example an agenda, set the invitees, or a meeting recurrence. -7. Click on *Execute Node* to run the workflow. - -![The Webex by Cisco node](/_images/integrations/builtin/app-nodes/ciscowebex/webex_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.citrixAdc.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.citrixAdc.md deleted file mode 100644 index 0b8254ea5..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.citrixAdc.md +++ /dev/null @@ -1,22 +0,0 @@ -# Citrix ADC - -[Citrix ADC](https://www.citrix.com/en-gb/products/citrix-adc/){:target=_blank .external-link} is an application delivery and load balancing solution for monolithic and microservices-based applications. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/citrixAdc/). - -## Operations - -* Certificate - * Create - * Install -* File - * Delete - * Download - * Upload - -## Related resources - -Refer to [Citrix ADC's documentation](https://docs.citrix.com/en-us/citrix-adc/current-release/){:target=_blank .external-link} for more information about the service. - -View [example workflows and related content](https://n8n.io/integrations/citrix-adc/){:target=_blank .external-link} on n8n's website. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.clearbit.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.clearbit.md deleted file mode 100644 index 5f34cbf4b..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.clearbit.md +++ /dev/null @@ -1,36 +0,0 @@ -# Clearbit - -[Clearbit](https://clearbit.com/) provides powerful products, and data APIs like contact enrichment, lead generation, financial compliance, and more to help businesses grow. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/clearbit/). - - -## Basic Operations - -* Company - * Auto-complete company names and retrieve logo and domain - * Look up person and company data based on an email or domain -* Person - * Look up a person and company data based on an email or domain - -## Example Usage - -This workflow allows you to look up a person using their email in Clearbit. You can also find the [workflow](https://n8n.io/workflows/484) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Clearbit]() - -The final workflow should look like the following image. - -![A workflow with the Clearbit node](/_images/integrations/builtin/app-nodes/clearbit/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Clearbit node - -1. First of all, you'll have to enter credentials for the Clearbit node. You can find out how to do that [here](/integrations/builtin/credentials/clearbit/). -2. Select the 'Person' option from the *Resource* dropdown list. -3. Enter the email of the person you want to look up in the *Email* field. -4. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.clickUp.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.clickUp.md deleted file mode 100644 index 2cb0eb0d6..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.clickUp.md +++ /dev/null @@ -1,109 +0,0 @@ -# ClickUp - -[ClickUp](https://clickup.com/) is a cloud-based collaboration and project management tool suitable for businesses of all sizes and industries. Features include communication and collaboration tools, task assignments and statuses, alerts and a task toolbar. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/clickUp/). - - -## Basic Operations - -* Checklist - * Create a checklist - * Delete a checklist - * Update a checklist -* Checklist Item - * Create a checklist item - * Delete a checklist item - * Update a checklist item -* Comment - * Create a comment - * Delete a comment - * Get all comments - * Update a comment -* Folder - * Create a folder - * Delete a folder - * Get a folder - * Get all folders - * Update a folder -* Goal - * Create a goal - * Delete a goal - * Get a goal - * Get all goals - * Update a goal -* Goal Key Result - * Create a key result - * Delete a key result - * Update a key result -* List - * Create a list - * Retrieve list's custom fields - * Delete a list - * Get a list - * Get all lists - * Get list members - * Update a list -* Space Tag - * Create a space tag - * Delete a space tag - * Get all space tags - * Update a space tag -* Task - * Create a task - * Delete a task - * Get a task - * Get all tasks - * Get task members - * Set a custom field - * Update a task -* Task List - * Add a task to a list - * Remove a task from a list -* Task Tag - * Add a tag to a task - * Remove a tag from a task -* Task Dependency - * Create a task dependency - * Delete a task dependency -* Time Entry - * Create a time entry - * Delete a time entry - * Get a time entry - * Get all time entries - * Start a time entry - * Stop the current running timer - * Update a time Entry -* Time Entry Tag - * Add tag to time entry - * Get all time entry tags - * Remove tag from time entry - -## Example Usage - -This workflow allows you to create a task in ClickUp. You can also find the [workflow](https://n8n.io/workflows/485) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [ClickUp]() - -The final workflow should look like the following image. - -![A workflow with the ClickUp node](/_images/integrations/builtin/app-nodes/clickup/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. ClickUp node - -1. First of all, you'll have to enter credentials for the ClickUp node. You can find out how to do that [here](/integrations/builtin/credentials/clickUp/). -2. Select your team ID from the *Team ID* dropdown list. -3. Select your space ID from the *Space ID* dropdown list. -4. Select your folder ID from the *Folder ID* dropdown list. -5. Select your list ID from the *List ID* dropdown list. -6. Enter the name of the task in the *Name* field. -7. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.clockify.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.clockify.md deleted file mode 100644 index 72c3a9f32..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.clockify.md +++ /dev/null @@ -1,127 +0,0 @@ -# Clockify - -[Clockify](https://clockify.me/) is a free time tracker and timesheet app for tracking work hours across projects. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/clockify/). - - -## Basic Operations - -* Project - * Create a project - * Delete a project - * Get a project - * Get all projects - * Update a project -* Tag - * Create a tag - * Delete a tag - * Get all tags - * Update a tag -* Task - * Create a task - * Delete a task - * Get a task - * Get all tasks - * Update a task -* Time Entry - * Create a time entry - * Delete a time entry - * Get time entrie - * Update a time entry - -## Example Usage - -This workflow allows you to create a project, tag, and time entry in Clockify. It also allows you to update the time entry in Clockify. You can also find the [workflow](https://n8n.io/workflows/701) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Clockify]() - -The final workflow should look like the following image. - -![A workflow with the Clockify node](/_images/integrations/builtin/app-nodes/clockify/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. Clockify node (create: project) - -This node will create a private project with a custom color. It will also add a note to the project in Clockify. - -1. First of all, you'll have to enter credentials for the Clockify node. You can find out how to do that [here](/integrations/builtin/credentials/clockify/). -2. Select the ***Workspace ID*** from the dropdown list. -3. Enter the name of the project in the ***Project Name*** field. -4. Click on ***Add Field*** and select 'Color' from the dropdown list. -5. Select the color from the color-picker or enter the hexadecimal value of the color in the ***Color*** field. -6. Click on ***Add Field*** and select 'Is Public' from the dropdown list. -7. Toggle ***Is Public*** to false. -8. Click on ***Add Field*** and select 'Note' from the dropdown list. -9. Enter the note in the ***Note*** field. -10. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new private project called `n8n-docs`. This project has a custom color `#0000FF` and a note `For n8n-docs`. - -![Using the Clockify node to create project](/_images/integrations/builtin/app-nodes/clockify/clockify_node.png) - - - -### 3. Clockify1 node (create: tag) - -This node will create a new tag in Clockify. - -1. Select the credentials that you entered in the previous node. -2. Select 'Tag' from the ***Resource*** dropdown list. -3. Select the ***Workspace ID*** from the dropdown list. -4. Enter the name of the tag 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 tag called `docs` in the n8n workspace in Clockify. - -![Using the Clockify node to create a tag](/_images/integrations/builtin/app-nodes/clockify/clockify1_node.png) - - - -### 4. Clockify2 node (create: timeEntry) - -This node creates a new time entry in Clockify with a description. It also adds the tag that we created in the previous step to the time entry. - -1. Select the credentials that you entered in the previous node. -2. Select 'Time Entry' from the ***Resource*** dropdown list. -3. Select the ***Workspace ID*** from the dropdown list. -4. Select a start date and time for the ***Start*** field. -5. Click on ***Add Field*** and select 'Description' from the dropdown list. -6. Enter a description in the ***Description*** field. -7. Click on ***Add Field*** and select 'End' from the dropdown list. -8. Select a end date and time for the ***End*** field. -9. Click on ***Add Field*** and select 'Tag IDs' from the dropdown list. -10. Select the tag that you created in the previous step from the ***Tag IDs*** dropdown list. -11. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node creates a new time entry with a description and adds the tag that was created in the previous node. - -![Using the Clockify node to create a time entry](/_images/integrations/builtin/app-nodes/clockify/clockify2_node.png) - - -### 5. Clockify3 node (update: timeEntry) - -This node will add the project to the time entry that was created by the Clockify node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Time Entry' from the ***Resource*** dropdown list. -3. Select 'Update' from the ***Operation*** dropdown list. -4. Select the ***Workspace ID*** from the dropdown list. -5. Click on the gears icon next to the ***Time Entry ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Clockify2 > Output Data > JSON > id. You can also add the following expression: `{{$node["Clockify2"].json["id"]}}`. -7. Click on ***Add Field*** and select 'Project ID' from the dropdown list. -8. Click on the gears icon next to the ***Project ID*** field and click on ***Add Expression***. -9. Select the following in the ***Variable Selector*** section: Nodes > Clockify > Output Data > JSON > id. You can also add the following expression: `{{$node["Clockify"].json["id"]}}`. -10. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node has updated the time entry by adding the project ID we created in the Clockify node. - -![Using the Clockify node to update the time entry](/_images/integrations/builtin/app-nodes/clockify/clockify3_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.cloudflare.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.cloudflare.md deleted file mode 100644 index 604d25436..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.cloudflare.md +++ /dev/null @@ -1,20 +0,0 @@ -# Cloudflare - -[Cloudflare](https://www.cloudflare.com/){:target=_blank .external-link} provides a range of services to manage and protect your websites. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/cloudflare/). - -## Operations - -* Zone Certificate - * Delete - * Get - * Get Many - * Upload - -## Related resources - -Refer to [Cloudflare's API documentation on zone-level authentication](https://api.cloudflare.com/#zone-level-authenticated-origin-pulls-properties){:target=_blank .external-link} for more information on this service. - -View [example workflows and related content](https://n8n.io/integrations/cloudflare/){:target=_blank .external-link} on n8n's website. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.cockpit.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.cockpit.md deleted file mode 100644 index f7a08e3f2..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.cockpit.md +++ /dev/null @@ -1,38 +0,0 @@ -# Cockpit - -[Cockpit](https://getcockpit.com/) is a headless CMS with an API-first approach that puts content first. It is designed to simplify the process of publication by separating content management from content consumption on the client side. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/cockpit/). - - -## Basic Operations - -* Collection - * Create a collection entry - * Get all collection entries - * Update a collection entry -* Form - * Store data from a form submission -* Singleton - * Get a singleton - -## Example Usage - -This workflow allows you to get entries from a collection in Cockpit. You can also find the [workflow](https://n8n.io/workflows/518) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Cockpit]() - -The final workflow should look like the following image. - -![A workflow with the Cockpit node](/_images/integrations/builtin/app-nodes/cockpit/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Cockpit node - -1. First of all, you'll have to enter credentials for the Cockpit node. You can find out how to do that [here](/integrations/builtin/credentials/cockpit/). -2. Select your collection from the *Collection* dropdown list. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.coda.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.coda.md deleted file mode 100644 index b33b02132..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.coda.md +++ /dev/null @@ -1,67 +0,0 @@ -# Coda - -[Coda](https://coda.io/) is a new type of document that blends the flexibility of documents, the power of spreadsheets, and the utility of applications into a single new canvas. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/coda/). - - -## Basic Operations - -* Control - * Get a control - * Get all controls -* Formula - * Get a formula - * Get all formulas -* Table - * Create/Insert a row - * Delete one or multiple rows - * Get all columns - * Get all the rows - * Get a column - * Get a row - * Pushes a button -* View - * Delete view row - * Get a view - * Get all views - * Get all views columns - * Get all views rows - * Update row - * Push view button - -## Example Usage - -This workflow allows you to insert data into a new row for a table in Coda. You can also find the [workflow](https://n8n.io/workflows/482) on the website. This example usage workflow would use the following three nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Coda]() - -The final workflow should look like the following image. - -![A workflow with the Coda node](/_images/integrations/builtin/app-nodes/coda/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Set node - -1. Click on the *Add Value* button and select 'String' from the dropdown list. -2. Enter `Column 1`in the *Name* field. -3. Enter the value for the first column in the *Value* field. -4. Repeat the first three steps of all the columns that you have in your Coda table. - -**Note:** Here, we've used the default table in Coda, which has three columns namely Column 1, Column 2, and Column 3. Please make sure that the column names in the *Name* field matches the names of the table columns in Coda. - -### 3. Coda node - -1. First of all, you'll have to enter credentials for the Coda node. You can find out how to do that [here](/integrations/builtin/credentials/coda/). -2. Select the name of your document from the *Doc* dropdown list. -3. Select the name of your table from the *Table* dropdown list. -4. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.coinGecko.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.coinGecko.md deleted file mode 100644 index 5235fb6b2..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.coinGecko.md +++ /dev/null @@ -1,108 +0,0 @@ -# CoinGecko - -[CoinGecko](https://www.coingecko.com) provides a fundamental analysis of the crypto market. In addition to tracking price, volume and market capitalization, CoinGecko tracks community growth, open-source code development, major events, and on-chain metrics. - -!!! note "Credentials" - The CoinGecko node does not require authentication. - - -## Basic Operations - -* Coin - * Get a candlestick open-high-low-close chart for the selected currency - * Get current data for a coin - * Get all coins - * Get historical data (name, price, market, stats) at a given date for a coin - * Get prices and market related data for all trading pairs that match the selected currency - * Get historical market data include price, market cap, and 24h volume (granularity auto) - * Get the current price of any cryptocurrencies in any other supported currencies that you need - * Get coin tickers -* Event - * Get all events - -## Example Usage - -This workflow allows you to get the price of BTC in EUR using the CoinGecko node and send an SMS when the price is greater than or equal to €9000. You can also find the [workflow](https://n8n.io/workflows/704) on n8n.io. This example usage workflow would use the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [CoinGecko]() -- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/) -- [Twilio](/integrations/builtin/app-nodes/n8n-nodes-base.twilio/) -- [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 CoinGecko node](/_images/integrations/builtin/app-nodes/coingecko/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow every minute. - -1. Click on ***Add Cron Time***. -2. Select 'Every Minute' from the ***Mode*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -![Using the Cron node to trigger the workflow](/_images/integrations/builtin/app-nodes/coingecko/cron_node.png) - -### 2. CoinGecko node (price: coin) - -This node will get the price of BTC in EUR using the CoinGecko API. Feel free to select a different Coin ID and Currency. -1. Select 'Price' from the ***Operation*** dropdown list. -2. Select 'BTC' from the ***Coin IDs*** dropdown list. -3. Select 'EUR' from the ***Currencies*** dropdown list. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node fetches the price of 1 BTC in EUR. This information will be passed on to the next nodes in the workflow. - -![Using the CoinGecko node to get the price](/_images/integrations/builtin/app-nodes/coingecko/coingecko_node.png) - - - -### 3. IF node - -This node will compare the price that we got from the CoinGecko node. If the price is greater than or equal to 9000, it will return true otherwise false. - -1. Click on ***Add Condition*** and select 'Number' from the dropdown list. -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 > CoinGecko > Output Data > JSON > bitcoin > eur. You can also add the following expression: `{{$node["CoinGecko"].json["bitcoin"]["eur"]}}`. -4. Select 'Larger Equal' from the ***Operation*** dropdown list. -5. Set ***Value 2*** to 9000. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns an output for **true** when the price is greater than 9000. - -![Using the IF node to check if the price is larger than 9000](/_images/integrations/builtin/app-nodes/coingecko/if_node.png) - - -### 4. Twilio node (send: sms) - -This node sends an SMS to a number when the price is greater than or equal to 9000. - -1. Connect this node with the **true** output of the IF node. -2. You'll have to enter credentials for the Twilio node. You can find out how to do that [here](/integrations/builtin/credentials/twilio/). -3. Enter the Twilio phone number in the ***From*** field. -4. Enter the receiver's phone number in the ***To*** field. -5. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. - -6. Enter `The price went up! The new price is €{{$node["CoinGecko"].json["bitcoin"]["eur"]}}` in the ***Expression*** field. -7. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends an SMS with the price that we obtained from the CoinGecko node. - -![Using the Twilio node to send an SMS](/_images/integrations/builtin/app-nodes/coingecko/twilio_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. Connect this node with 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/coingecko/noop_node.png) - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.contentful.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.contentful.md deleted file mode 100644 index 4ad6a1307..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.contentful.md +++ /dev/null @@ -1,45 +0,0 @@ -# Contentful - -[Contentful](https://www.contentful.com/) provides a content infrastructure for digital teams to power content in websites, apps, and devices. It offers a central hub for structured content, powerful management and delivery APIs, and a customizable web app. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/contentful/). - - -## Basic Operations - -* Asset - * Get - * Get All -* Content Type - * Get -* Entry - * Get - * Get All -* Locale - * Get All -* Space - * Get - -## Example Usage - -This workflow allows you to get all the entries using the Delivery API of Contentful. You can also find the [workflow](https://n8n.io/workflows/640) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Contentful]() - -The final workflow should look like the following image. - -![A workflow with the Contentful node](/_images/integrations/builtin/app-nodes/contentful/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Contentful node - -1. First of all, you'll have to enter credentials for the Contentful node. You can find out how to do that [here](/integrations/builtin/credentials/contentful/). -2. Select 'Get All' from the ***Operation*** dropdown list. -3. Toggle ***Return All*** to true. -4. Click on ***Execute Node*** to run the node. - -![Using the Contentful node to get all entries](/_images/integrations/builtin/app-nodes/contentful/contentful_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.convertKit.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.convertKit.md deleted file mode 100644 index f660d694b..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.convertKit.md +++ /dev/null @@ -1,80 +0,0 @@ -# ConvertKit - -[ConvertKit](https://www.convertkit.com/) is a fully-featured email marketing platform. ConvertKit can be used to build an email list, send email broadcasts, automate sequences, create segments, and build landing pages. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/convertKit/). - - -## Basic Operations - -* Custom Field - * Create a field - * Delete a field - * Get all fields - * Update a field -* Form - * Add a subscriber - * Get all forms - * List subscriptions to a form including subscriber data -* Sequence - * Add a subscriber - * Get all sequences - * Get all subscriptions to a sequence including subscriber data -* Tag - * Create a tag - * Get all tags -* Tag Subscriber - * Add a tag to a subscriber - * List subscriptions to a tag including subscriber data - * Delete a tag from a subscriber - -## Example Usage - -This workflow allows you to add a subscriber to a form, create a tag and add the subscriber to the tag using the ConvertKit node. You can also find the [workflow](https://n8n.io/workflows/642) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [ConvertKit]() - -The final workflow should look like the following image. - -![A workflow with the ConvertKit node](/_images/integrations/builtin/app-nodes/convertkit/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. ConvertKit node (addSubscriber: form) - -1. First of all, you'll have to enter credentials for the ConvertKit node. You can find out how to do that [here](/integrations/builtin/credentials/convertKit/). -2. Select the form from the ***Form ID*** dropdown list. -3. Enter the email address in the ***Email*** field. -4. Click on ***Execute Node*** to run the node. - -![Using the ConvertKit node to add a subscriber to a form](/_images/integrations/builtin/app-nodes/convertkit/convertkit_node.png) - - - -### 3. ConvertKit1 node (create: tag) - -1. Select the credentials that you entered in the previous ConvertKit node. -2. Select 'Tag' from the ***Resource*** dropdown list. -3. Enter the tag name in the ***Name*** field. -4. Click on ***Execute Node*** to run the node. - - -![Using the ConvertKit node to create a tag](/_images/integrations/builtin/app-nodes/convertkit/convertkit1_node.png) - - - -### 4. ConvertKit2 node (add: tagSubscriber) - -1. Select the credentials that you entered in the previous ConvertKit node. -2. Select 'Tag Subscriber' from the ***Resource*** dropdown list. -3. Select 'Add' from the ***Operation*** dropdown list. -4. Select the tag from the ***Tag ID*** dropdown list. -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 > ConvertKit > Output Data > JSON > subscriber > email_address. You can also add the following expression: `{{$node["ConvertKit"].json["subscriber"]["email_address"]}}`. -7. Click on ***Execute Node*** to run the node. - - -![Using the ConvertKit node to add the subscriber to the tag](/_images/integrations/builtin/app-nodes/convertkit/convertkit2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.copper.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.copper.md deleted file mode 100644 index 9bd4f1000..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.copper.md +++ /dev/null @@ -1,118 +0,0 @@ -# Copper - -[Copper](https://www.copper.com/) is a CRM that focuses on strong integration with Google's G Suite, targeted towards small and medium-sized businesses. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/copper/). - - -## Basic Operations - -* Company - * Create - * Delete - * Get - * Get All - * Update -* Customer Source - * Get All -* Lead - * Create - * Delete - * Get - * Get All - * Update -* Opportunity - * Create - * Delete - * Get - * Get All - * Update -* Person - * Create - * Delete - * Get - * Get All - * Update -* Project - * Create - * Delete - * Get - * Get All - * Update -* Task - * Create - * Delete - * Get - * Get All - * Update -* User - * Get All - -## Example Usage - -This workflow allows you to create, update, and get a person from Copper. You can also find the [workflow](https://n8n.io/workflows/1021) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Copper]() - -The final workflow should look like the following image. - -![A workflow with the Copper node](/_images/integrations/builtin/app-nodes/copper/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Copper node (create: person) - -This node will create a new person in Copper. - -1. First of all, you'll have to enter credentials for the Copper node. You can find out how to do that [here](/integrations/builtin/credentials/copper/). -2. Select 'Person' from the ***Resource*** dropdown list. -3. Enter the name of the lead in the ***Name*** field. -4. Click on the ***Add Field*** button and select 'Emails' from the dropdown list. -5. Click on the ***Add Email*** button. -6. Enter the email in the ***Email*** field. -7. Enter the category of the email in the ***Category*** field. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new person in Copper. - -![Using the Copper node to create a new person](/_images/integrations/builtin/app-nodes/copper/copper_node.png) - - -### 3. Copper1 node (update: person) - -This node will update the information of the person that we created using the previous node. - -1. Select the credentials that you entered in the previous Copper node. -2. Select 'Person' from the ***Resource*** dropdown list. -3. Select 'Update' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Person 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 the ***Add Field*** button and select 'Phone Numbers' from the dropdown list. -7. Click on the ***Add Phone Number*** field. -8. Enter the phone number in the ***Phone Number*** field. -9. Enter the category in the ***Category*** field. -10. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node updates the information of the person that got created previously. - -![Using the Copper node to update the information of a person](/_images/integrations/builtin/app-nodes/copper/copper1_node.png) - -### 4. Copper2 node (get: person) - -This node will retrieve the information of the person that we created earlier. - - -1. Select the credentials that you entered in the previous Copper node. -2. Select 'Person' from the ***Resource*** dropdown list. -3. Select 'Update' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Person 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 person that we created earlier. - -![Using the Copper node to retrieve the information of a person](/_images/integrations/builtin/app-nodes/copper/copper2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.cortex.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.cortex.md deleted file mode 100644 index 1a286757f..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.cortex.md +++ /dev/null @@ -1,59 +0,0 @@ -# Cortex - -[Cortex](https://github.com/TheHive-Project/CortexDocs) offers a powerful observable (URL, file, IP, etc) analysis mechanism. It allows you to analyze collected observables using a single tool, respond to threats, and interact with the constituency and other teams. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/cortex/). - - -## Basic Operations - -* Analyzer - * Execute Analyzer -* Job - * Get job details - * Get job report -* Responder - * Execute Responder - -## Example Usage - -This workflow allows you to analyze a URL and get the job details using the Cortex node. You can also find the [workflow](https://n8n.io/workflows/809) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Cortex]() - -The final workflow should look like the following image. - -![A workflow with the Cortex node](/_images/integrations/builtin/app-nodes/cortex/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Cortex node (analyzer: execute) - -This node will analyze a URL. If you want to analyze a different observable type, select that instead. - -1. First of all, you'll have to enter credentials for the Cortex node. You can find out how to do that [here](/integrations/builtin/credentials/cortex/). -2. Select 'Abuse_Finder_3_0' from the ***Analyzer Type*** dropdown list. -3. Select 'URL' from the ***Observable Type*** dropdown list. -4. Enter the URL you want to analyze in the ***Observable Value*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node starts the analysis of the URL. - -![Using the Cortex node to analyze a URL](/_images/integrations/builtin/app-nodes/cortex/cortex_node.png) - -### 3. Cortex1 node (job: get) - -This node will return the job details for the analysis that we executed in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Job' from the ***Resource*** dropdown list. -3. Click on the gears icon next to the ***Job ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Cortex > Output Data > JSON > _id. You can also add the following expression: `{{$node["Cortex"].json["_id"]}}`. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node starts the analysis of the URL. - -![Using the Cortex node to get job details](/_images/integrations/builtin/app-nodes/cortex/cortex1_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.crateDb.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.crateDb.md deleted file mode 100644 index 22b8206de..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.crateDb.md +++ /dev/null @@ -1,68 +0,0 @@ -# CrateDB - -[CrateDB](https://crate.io/) is an open-source distributed SQL database management system that integrates a fully searchable document-oriented data store based on a shared-nothing architecture, and is designed for high scalability. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/crateDb/). - - -## Basic Operations - -* Execute an SQL query -* Insert rows in database -* Update rows in database - - -## Example Usage - -This workflow allows you to create a table and insert data into it in CrateDB. You can also find the [workflow](https://n8n.io/workflows/597) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [CrateDB]() - -The final workflow should look like the following image. - -![A workflow with the CrateDB node](/_images/integrations/builtin/app-nodes/cratedb/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. CrateDB node (Execute Query) - -1. First of all, you'll have to enter credentials for the CrateDB node. You can find out how to do that [here](/integrations/builtin/credentials/crateDb/). -2. Select 'Execute Query' from the ***Operation*** dropdown list. -3. Enter the following SQL query in the ***Query*** field: `CREATE TABLE test (id INT, name STRING);`. -4. Click on the ***Node*** tab and toggle ***Always Output Data*** to true. -5. Click on ***Execute Node*** to run the node. - -![Using the CreateDB node to create a table](/_images/integrations/builtin/app-nodes/cratedb/cratedb_node.png) - -### 3. Set node - -1. Click on the ***Add Value*** button and select 'Number' from the dropdown list. -2. Enter `id` in the ***Name*** field. -3. Click on the ***Add Value*** button and select 'String' from the dropdown list. -4. Enter `name` in the ***Name*** field. -5. Enter the value for the name in the ***Value*** field. -6. Click on ***Execute Node*** to run the node. - -![Using the Set node to set data to be inserted by the CrateDB node](/_images/integrations/builtin/app-nodes/cratedb/set_node.png) - -### 4. CrateDB1 node (Insert) - -1. Select the credentials that you entered in the previous CrateDB node. -2. Enter `test` in the ***Table*** field. -3. Enter `id, name` in the ***Columns*** field. -4. Click on ***Execute Node*** to run the node. - -![Using the CrateDB node to insert data into a table](/_images/integrations/builtin/app-nodes/cratedb/cratedb1_node.png) - -## FAQs - -### How to specify the data type of a column? -To specify the data type of a column, append the column name with `:type`, where `type` is the data type of that column. For example, if you want to specify the type `int` for the column *id* and type `text` for the column *name*, you can use the following snippet in the ***Columns*** field: `id:init,name:text`. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.customerIo.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.customerIo.md deleted file mode 100644 index 7851696a2..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.customerIo.md +++ /dev/null @@ -1,61 +0,0 @@ -# Customer.io - -[Customer.io](https://customer.io/) enables users to send newsletters to selected segments of customers using their website data. You can send targeted emails, push notifications, and SMS to lower churn, create stronger relationships, and drive subscriptions. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/customerIo/). - - -## Basic Operations - -* Customer - * Create/Update a customer. - * Delete a customer. -* Event - * Track a customer event. - * Track an anonymous event. -* Campaign - * Get - * Get All - * Get Metrics -* Segment - * Add Customer - * Remove Customer - -## Example Usage - -This workflow allows you to create a customer and add them to a segment in Customer.io. You can also find the [workflow](https://n8n.io/workflows/646) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Customer.io]() - -The final workflow should look like the following image. - -![A workflow with the Customer.io node](/_images/integrations/builtin/app-nodes/customerio/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. CustomerIo node (upsert: customer) - -1. First of all, you'll have to enter credentials for the Customer.io node. You can find out how to do that [here](/integrations/builtin/credentials/customerIo/). -2. Enter a customer id in the ***ID*** field. -3. Click on the ***Add Field*** button and select 'Custom Properties' from the dropdown list. -4. Click on the ***Choose Option To Add*** button. -5. Enter `name` in the ***Key*** field. -6. Enter the name of the customer in the ***Value*** field. -7. Click on ***Execute Node*** to run the node. - -![Using the Customer.io node to create a new customer](/_images/integrations/builtin/app-nodes/customerio/customerio_node.png) - - -### 3. CustomerIo1 node (add: segment) - -1. Select the credentials that you entered in the previous Customer.io node. -2. Select 'Segment' from the ***Resource*** field. -3. Click on the gears icon next to the ***Customer IDs*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > CustomerIo > Output Data > JSON > id. You can also add the following expression: `{{$node["CustomerIo"].json["id"]}}`. -4. Click on ***Execute Node*** to run the node. - - -![Using the Customer.io node to add the customer to a segment](/_images/integrations/builtin/app-nodes/customerio/customerio1_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.deepL.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.deepL.md deleted file mode 100644 index 1fcb7417d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.deepL.md +++ /dev/null @@ -1,53 +0,0 @@ -# DeepL - -[DeepL](https://deepL.com) is a machine translation service that allows you to translate text to different languages. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/deepL/). - - -## Basic Operations - -* 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 deleted file mode 100644 index 11fc12828..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.demio.md +++ /dev/null @@ -1,67 +0,0 @@ -# Demio - -[Demio](https://demio.com) provides a simple, no-download webinar experience and all the marketing tools you need to generate better results. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/demio/). - - -## Basic Operations - -* Event - * Get an event - * Get all events - * Register someone to an event -* Report - * Get an event report - -## Example Usage - -This workflow allows you to register your audience to an event on Demio via 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.dhl.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.dhl.md deleted file mode 100644 index e9e611fc6..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.dhl.md +++ /dev/null @@ -1,19 +0,0 @@ -# DHL - -The [DHL Shipment Tracking](https://developer.dhl.com/api-reference/shipment-tracking/) provides shipment status reports for services provided by DPDHL under these brand names: - -- Post & Parcel Germany -- DHL Global Forwarding -- DHL Freight -- DHL Express -- DHL Supply Chain -- DHL eCommerce Solutions (Asia-Pacific, US, Canada, EU) - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/dhl/). - - -## Basic Operations - -* Shipment - * Get Tracking Details diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.discord.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.discord.md deleted file mode 100644 index 2e1ab323c..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.discord.md +++ /dev/null @@ -1,34 +0,0 @@ -# Discord - -[Discord](https://discord.com/) is a voice, video, and text communications platform for groups. Discord allows users to programmatically send messages using webhooks. - -!!! note "Credentials" - The Discord node does not require authentication, but you must have access to a channel's settings to use webhooks. You can find out how to create a webhook in Discord [here](/integrations/builtin/credentials/discord/). - - -## Basic Operations - -- Send messages in a Discord Channel - -## Example Usage - -This workflow allows you to send a message to a Discord channel using webhooks. You can also find the [workflow](https://n8n.io/workflows/410) on this website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Discord]() - -The final workflow should look like the following image. - -![A workflow with the Discord node](/_images/integrations/builtin/app-nodes/discord/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Discord node - -1. First of all, you'll have to create a webhook for the Discord node. You can find out how to do that [here](/integrations/builtin/credentials/discord/). -2. Paste your webhook into the **Webhook URL** field. -5. Enter your message in the **Text** field. -6. Click on **Execute Node** to run the workflow. - -![Sending a message to a Discord channel using the Discord node](/_images/integrations/builtin/app-nodes/discord/discord_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.discourse.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.discourse.md deleted file mode 100644 index 0d70f38d0..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.discourse.md +++ /dev/null @@ -1,90 +0,0 @@ -# Discourse - -[Discourse](https://www.discourse.org/) is an open-source discussion platform that can be used as a mailing list, discussion forum, long-form chat room, and more. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/discourse/). - - - -## Basic Operations - -* Category - * Create a category - * Get all categories - * Update a category -* Group - * Create a group - * Get a group - * Get all groups - * Update a group -* Post - * Create a post - * Get a post - * Get all posts - * Update a post -* User - * Create a user - * Get a user - * Get all users -* User Group - * 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.disqus.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.disqus.md deleted file mode 100644 index a867c8b2f..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.disqus.md +++ /dev/null @@ -1,35 +0,0 @@ -# Disqus - -[Disqus](https://disqus.com/) is a worldwide blog comment hosting service for web sites and online communities that use a networked platform. The company's platform includes various features, such as social integration, social networking, user profiles, spam and moderation tools, analytics, email notifications, and mobile commenting. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/disqus/). - - -## Basic Operations - -* Forum - * Return forum details - * Return a list of categories within a forum - * Return a list of threads within a forum - * Return a list of posts within a forum - -## Example Usage - -This workflow allows you to get details of a forum in Disqus. You can also find the [workflow](https://n8n.io/workflows/493) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Disqus]() - -The final workflow should look like the following image. - -![A workflow with the Disqus node](/_images/integrations/builtin/app-nodes/disqus/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Disqus node - -1. First of all, you'll have to enter credentials for the Disqus node. You can find out how to do that [here](/integrations/builtin/credentials/disqus/). -2. Enter the name of the forum in the *Forum name* field. For example, I entered `hackernoon`. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.drift.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.drift.md deleted file mode 100644 index 0877b048c..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.drift.md +++ /dev/null @@ -1,36 +0,0 @@ -# Drift - -[Drift](https://www.drift.com/) is a tool for managing conversations, engaging with customers, and collaborating with teammates. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/drift/). - - -## Basic Operations - -* Contact - * Create a contact - * Get custom attributes - * Delete a contact - * Get a contact - * Update a contact - -## Example Usage - -This workflow allows you to create a contact in Drift. You can also find the [workflow](https://n8n.io/workflows/497) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Drift]() - -The final workflow should look like the following image. - -![A workflow with the Drift node](/_images/integrations/builtin/app-nodes/drift/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Drift node - -1. First of all, you'll have to enter credentials for the Drift node. You can find out how to do that [here](/integrations/builtin/credentials/drift/). -2. Enter the email of the contact in the *Email* field. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.dropbox.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.dropbox.md deleted file mode 100644 index ded4a3c1a..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.dropbox.md +++ /dev/null @@ -1,75 +0,0 @@ -# Dropbox - -[Dropbox](https://dropbox.com) is a cloud-based file storage and sharing service, accessible through multiple devices. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/dropbox/). - - -## Basic Operations - -* File - * Copy a file - * Delete a file - * Download a file - * Move a file - * Upload a file -* Folder - * Copy a folder - * Create a folder - * Delete a folder - * Return the files and folders in a given folder - * Move a folder -* Search - * Query - -## Example Usage - -This workflow allows you to create a folder in Dropbox, upload a file into that folder, and list the contents of the folder. You can also find the [workflow](https://n8n.io/workflows/615) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Dropbox]() -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) - -The final workflow should look like the following image. - -![A workflow with the Dropbox node](/_images/integrations/builtin/app-nodes/dropbox/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Dropbox node (create: folder) - -1. First of all, you'll have to enter credentials for the Dropbox node. You can find out how to do that [here](/integrations/builtin/credentials/dropbox/). -2. Select 'Folder' from the ***Resource*** dropdown list. -3. Enter the name of the new folder in the ***Folder*** field. -4. Click on ***Execute Node*** to run the workflow. - -![Create a folder in Dropbox using the Dropbox node](/_images/integrations/builtin/app-nodes/dropbox/dropbox_node.png) - -### 3. HTTP Request node (GET) - -1. Enter `https://n8n.io/n8n-logo.png` in the ***URL*** field. -2. Select 'File' from the ***Response Format*** dropdown list. -3. Click on ***Execute Node*** to run the workflow. - -![Get a file to upload in Dropbox using the HTTP Request node](/_images/integrations/builtin/app-nodes/dropbox/httprequest_node.png) - -### 4. Dropbox1 node (upload: file) - -1. Select the credentials that you entered in the Dropbox node. -2. Enter the path of the Dropbox folder you created in the previous steps along with a file name in the ***File Path*** field. -3. Set the ***Binary Data*** toggle to true. -4. Click on ***Execute Node*** to run the node. - -![Upload a file in Dropbox using the Dropbox node](/_images/integrations/builtin/app-nodes/dropbox/dropbox1_node.png) - -### 5. Dropbox2 node (list: folder) - -1. Select the credentials that you entered in the Dropbox node. -2. Select 'Folder' from the ***Resource*** dropdown list. -3. Select 'List' from the ***Operation*** dropdown list. -4. Enter the path of the Dropbox folder you created in the previous steps in the ***Folder Path*** field. -5. Click on ***Execute Node*** to run the node. - -![List the contents of a Dropbox folder using the Dropbox node](/_images/integrations/builtin/app-nodes/dropbox/dropbox2_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 deleted file mode 100644 index 5a8924598..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.dropcontact.md +++ /dev/null @@ -1,102 +0,0 @@ -# Dropcontact - -[Dropcontact](https://www.dropcpontact.com) is an email finder platform that allows you to automatically find, verify and validate nominative emails and enrich your contacts with all efficient information to contact him. - - - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/dropcontact/). - - -## Basic Operations - -**Contact** -- Enrich -- Fetch Request - - - -## 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 deleted file mode 100644 index b39ffc352..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.egoi.md +++ /dev/null @@ -1,82 +0,0 @@ -# E-goi - -[E-goi](https://www.e-goi.com/) is an omnichannel marketing automation platform. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/egoi/). - - -## Basic Operations - -**Contact** -- Create a member -- Get a member -- Get all members -- 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.elasticSecurity.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.elasticSecurity.md deleted file mode 100644 index 2aade7c73..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.elasticSecurity.md +++ /dev/null @@ -1,28 +0,0 @@ -# Elastic Security - -[Elastic Security](https://www.elastic.co/security) helps security teams stop threats and at cloud scale, assisting with prevention, detection, and response. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/elasticSecurity/). - - -## Basic operations - -* Case - * Create a case - * Delete a case - * Get a case - * Retrieve all cases - * Retrieve a summary of all case activity - * Update a case -* Case Comment - * Add a comment to a case - * Get a case comment - * Retrieve all case comments - * Remove a comment from a case - * Update a comment in a case -* Case Tag - * Add a tag to a case - * Remove a tag from a case -* Connector - * Create a connector diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.elasticsearch.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.elasticsearch.md deleted file mode 100644 index 721129e18..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.elasticsearch.md +++ /dev/null @@ -1,45 +0,0 @@ -# Elasticsearch - -[Elasticsearch](https://www.elastic.co/) is a distributed, free and open search and analytics engine for all types of data, including textual, numerical, geospatial, structured, and unstructured. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/elasticsearch/). - - -## Basic operations - -* Document - * Create a document - * Delete a document - * Get a document - * Get all documents - * Update a document -* Index - * Create - * Delete - * Get - * Get All - -## Example usage - -This workflow allows you to get all documents for a selected index. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Elasticsearch]() - -The final workflow should look like the following image. - -![A workflow with the Elasticsearch node](/_images/integrations/builtin/app-nodes/elasticsearch/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Elasticsearch node - -1. First enter credentials for the Elasticsearch node. You can find out how to do that [here](/integrations/builtin/credentials/elasticsearch/). -2. Select **Document** from the ***Resource*** dropdown. -3. Select **Get All** from the ***Operation*** dropdown. -3. Enter the ID of your desired index in the ***Index ID*** field. -4. Click on ***Execute Node*** to run the node. - -![Using the Elasticsearch node ](/_images/integrations/builtin/app-nodes/elasticsearch/elasticsearch_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 deleted file mode 100644 index 41e77d193..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.emelia.md +++ /dev/null @@ -1,78 +0,0 @@ -# Emelia - -[Emelia](https://emelia.io) is a cold-mailing tool. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/emelia/). - - -## Basic Operations - -* Campaign - * Add Contact - * Create - * Get - * Get All - * Pause - * Start -* Contact List - * 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 deleted file mode 100644 index 6be1b6bda..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.erpNext.md +++ /dev/null @@ -1,87 +0,0 @@ -# ERPNext - -[ERPNext](https://erpnext.com) is an open-source integrated Enterprise Resource Planning software. It is a generic ERP software used by manufacturers, distributors, and services companies. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/erpnext/). - - -## Basic Operations - -**Document** -- Create a document -- Delete a document -- Retrieve a document -- Retrieve all documents -- 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.facebookGraphAPI.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.facebookGraphAPI.md deleted file mode 100644 index 81d36f54d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.facebookGraphAPI.md +++ /dev/null @@ -1,60 +0,0 @@ -# Facebook Graph API - -[Facebook](https://www.facebook.com/) is a social networking site that makes it easy to connect and share with family and friends online. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/facebookGraph/). - - -## Basic operations - -**Default** -- GET -- POST -- DELETE - - -**Video Uploads** -- GET -- POST -- DELETE - - -### Parameters - -* **Host URL**: The host URL for the request. The following options are available: - * **Default**: Requests are passed to the `graph.facebook.com` host URL. Used for the majority of requests. - * **Video**: Requests are passed to the `graph-video.facebook.com` host URL. Used for video upload requests only. -* **HTTP Request Method**: The method to be used for this request, from the following options: - * **GET** - * **POST** - * **DELETE** -* **Graph API Version**: The version of the [Facebook Graph API](https://developers.facebook.com/docs/graph-api/changelog) to be used for this request. -* **Node**: The node on which to operate, for example `//feed`. Read more about it in the [official Facebook Developer documentation](https://developers.facebook.com/docs/graph-api/using-graph-api). -* **Edge**: Edge of the node on which to operate. Edges represent collections of objects which are attached to the node. -* **Ignore SSL Issues**: Toggle to still download the response even if SSL certificate validation is not possible. -* **Send Binary Data**: Available for `POST` operations. If enabled binary data is sent as the body. Requires setting the following: - * **Binary Property**: Name of the binary property which contains the data for the file to be uploaded. - -## Example usage - -This workflow allows you to retrieve the first and last name of a profile on Facebook. You can also find the [workflow](https://n8n.io/workflows/514) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Facebook Graph API]() - -The final workflow should look like the following image. - -![A workflow with the Facebook Graph API node](/_images/integrations/builtin/app-nodes/facebookgraphapi/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Facebook Graph API node - -1. First of all, you'll have to enter credentials for the Facebook Graph API node. You can find out how to do that [here](/integrations/builtin/credentials/facebookGraph/). -2. Enter `me` in the *Node* field. -3. Click on the *Add Option* button and select 'Fields' from the dropdown list. -4. Click on the *Add Field* button and enter `first_name` in the *Name* field. -5. Click on the *Add Field* button and enter `last_name` in the *Name* field. -6. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.filemaker.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.filemaker.md deleted file mode 100644 index 3f75ae03d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.filemaker.md +++ /dev/null @@ -1,87 +0,0 @@ -# FileMaker - -[FileMaker](https://www.claris.com/filemaker/) is an integrated Enterprise Resource Planning software. It is a generic ERP software used by manufacturers, distributors, and service companies. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/fileMaker/). - - -## Basic Operations - -- Find Records -- Get Records -- Get Records by Id -- Perform Script -- Create Record -- Edit Record -- 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.flow.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.flow.md deleted file mode 100644 index cdee83e31..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.flow.md +++ /dev/null @@ -1,36 +0,0 @@ -# Flow - -[Flow](https://www.getflow.com/) is modern task and project management software for teams. It brings together tasks, projects, timelines, and conversations, and integrates with a lot of tools. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/flow/). - - -## Basic Operations - -* Task - * Create a new task - * Update a task - * Get a task - * Get all the tasks - -## Example Usage - -This workflow allows you to get all the tasks in Flow. You can also find the [workflow](https://n8n.io/workflows/506) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Flow]() - -The final workflow should look like the following image. - -![A workflow with the Flow node](/_images/integrations/builtin/app-nodes/flow/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Flow node - -1. First of all, you'll have to enter credentials for the Flow node. You can find out how to do that [here](/integrations/builtin/credentials/flow/). -2. Select the 'Get All' option from the *Operation* dropdown list. -3. Toggle the *Return All* slider to true. -4. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.freshdesk.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.freshdesk.md deleted file mode 100644 index 40dad050b..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.freshdesk.md +++ /dev/null @@ -1,44 +0,0 @@ -# Freshdesk - -[Freshdesk](https://freshdesk.com/) is a customer support software also classified as a ticketing software or a helpdesk that allows companies to effectively manage their customer care and support function. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/freshdesk/). - - -## Basic Operations - -* Contact - * Create a new contact - * Delete a contact - * Get a contact - * Get all contacts - * Update a contact -* Ticket - * Create a new ticket - * Delete a ticket - * Get a ticket - * Get all tickets - * Update a ticket - -## Example Usage - -This workflow allows you to create a ticket on Freshdesk. You can also find the [workflow](https://n8n.io/workflows/448) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Freshdesk]() - -The final workflow should look like the following image. - -![A workflow with the Freshdesk node](/_images/integrations/builtin/app-nodes/freshdesk/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Freshdesk node - -1. First of all, you'll have to enter credentials for the Freshdesk node. You can find out how to do that [here](/integrations/builtin/credentials/freshdesk/). -2. Select 'Email' from the *Requester Identification* dropdown. -3. Enter the requester email in the *Value* field. -4. Select 'Open' from the *Status* Dropdown. -5. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.freshservice.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.freshservice.md deleted file mode 100644 index 38bc17a96..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.freshservice.md +++ /dev/null @@ -1,122 +0,0 @@ -# Freshservice - -[Freshservice](https://www.freshservice.com/) is a cloud-based IT Service Management solution. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/freshservice/). - - -## Basic operations - -* Agent - * Create an agent - * Delete an agent - * Retrieve an agent - * Retrieve all agents - * Update an agent -* Agent Group - * Create an agent group - * Delete an agent group - * Retrieve an agent group - * Retrieve all agent groups - * Update an agent group -* Agent Role - * Retrieve an agent role - * Retrieve all agent roles -* Announcement - * Create an announcement - * Delete an announcement - * Retrieve an announcement - * Retrieve all announcements - * Update an announcement -* Asset Type - * Create an asset type - * Delete an asset type - * Retrieve an asset type - * Retrieve all asset types - * Update an asset type -* Change - * Create a change - * Delete a change - * Retrieve a change - * Retrieve all changes - * Update a change -* Department - * Create a department - * Delete a department - * Retrieve a department - * Retrieve all departments - * Update a department -* Location - * Create a location - * Delete a location - * Retrieve a location - * Retrieve all locations - * Update a location -* Problem - * Create a problem - * Delete a problem - * Retrieve a problem - * Retrieve all problems - * Update a problem -* Product - * Create a product - * Delete a product - * Retrieve a product - * Retrieve all products - * Update a product -* Release - * Create a release - * Delete a release - * Retrieve a release - * Retrieve all releases - * Update a release -* Requester - * Create a requester - * Delete a requester - * Retrieve a requester - * Retrieve all requesters - * Update a requester -* Requester Group - * Create a requester group - * Delete a requester group - * Retrieve a requester group - * Retrieve all requester groups - * Update a requester group -* Software - * Create a software application - * Delete a software application - * Retrieve a software application - * Retrieve all software applications - * Update a software application -* Ticket - * Create a ticket - * Delete a ticket - * Retrieve a ticket - * Retrieve all tickets - * Update a ticket - -## Example usage - -This workflow allows you to fetch all Tickets with an Urgent status in Freshservice. This example usage workflow would use the following two nodes: - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Freshservice]() - -The final workflow should look like the following image. - -![A workflow with the Freshservice node](/_images/integrations/builtin/app-nodes/freshservice/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Freshservice node - -1. First enter your credentials for the Freshservice node. You can find out how to do that [here](/integrations/builtin/credentials/freshservice/). -2. Select **Ticket** from the *Resource* dropdown. -3. Select **Get All** from the *Operation* dropdown. -4. Enable the **Return All** toggle. -5. From the *Add Filter* dropdown select **Priority**. -6. From the new *Priority* dropdown select **Urgent**. -5. Click on **Execute Node** to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.freshworksCrm.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.freshworksCrm.md deleted file mode 100644 index 47bc507d3..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.freshworksCrm.md +++ /dev/null @@ -1,72 +0,0 @@ -# Freshworks CRM - -[Freshworks CRM](https://www.freshworks.com/freshsales-crm/) is a cloud-based customer relationship management (CRM) solution that helps businesses manage their interactions with existing and potential customers. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/freshworksCrm/). - - -## Basic operations - -* Account - * Create an account - * Delete an account - * Retrieve an account - * Retrieve all accounts - * Update an account -* Appointment - * Create an appointment - * Delete an appointment - * Retrieve an appointment - * Retrieve all appointments - * Update an appointment -* Contact - * Create a contact - * Delete a contact - * Retrieve a contact - * Retrieve all contacts - * Update a contact -* Deal - * Create a deal - * Delete a deal - * Retrieve a deal - * Retrieve all deals - * Update a deal -* Note - * Create a note - * Delete a note - * Update a note -* Sales Activity - * Retrieve a sales activity - * Retrieve all sales activities -* Task - * Create a task - * Delete a task - * Retrieve a task - * Retrieve all tasks - * Update a task - -## Example usage - -This workflow allows you to fetch all Contacts in Freshworks CRM that you have yet to contact. This example usage workflow would use the following two nodes: - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Freshworks CRM]() - -The final workflow should look like the following image. - -![A workflow with the Freshworks CRM node](/_images/integrations/builtin/app-nodes/freshworkscrm/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Freshworks CRM node - -1. First enter your credentials for the Freshworks CRM node. You can find out how to do that [here](/integrations/builtin/credentials/freshworksCrm/). -2. Select **Contact** from the *Resource* dropdown. -3. Select **Get All** from the *Operation* dropdown. -4. Select **Never Contacted** from the *View* dropdown. -5. Click on **Execute Node** to run the workflow. - -![The Freshworks CRM node](/_images/integrations/builtin/app-nodes/freshworkscrm/freshworkscrm_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.gSuiteAdmin.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.gSuiteAdmin.md deleted file mode 100644 index 7d5843384..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.gSuiteAdmin.md +++ /dev/null @@ -1,101 +0,0 @@ -# G Suite Admin - -[G Suite Admin](https://developers.google.com/admin-sdk) helps you administer domain and app resources, create reports, and manage subscriptions and alerts for your G Suite organization. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -* Group - * Create a group - * Delete a group - * Get a group - * Get all groups - * Update a group -* User - * Create a user - * Delete a user - * Get a user - * Get all users - * Update a user - -## Example Usage - -This workflow allows you to create, update, and get a user using the G Suite Admin node. You can also find the [workflow](https://n8n.io/workflows/710) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [G Suite Admin]() - -The final workflow should look like the following image. - -![A workflow with the Google Sheets node](/_images/integrations/builtin/app-nodes/gsuiteadmin/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. G Suite Admin node (create: user) - -This node will create a user in G Suite with the following information: first name, last name, password, domain, and username. - -1. First of all, you'll have to enter credentials for the G Suite Admin node. You can find out how to do that [here](/integrations/builtin/credentials/google/). -3. Enter the first name of the user in the ***First Name*** field. -4. Enter the last name of the user in the ***Last Name*** field. -5. Enter a password for the user in the ***Password*** field. -6. Select the domain from the ***Domain*** dropdown list. -7. Enter the username for the user in the ***Username*** field. -8. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will observe that the node has created a new user with the first name `Nathan`, last name `Nat`, domain `n8n.io`, username `nat`, and a password, in G Suite. - -![Using the G Suite Admin node to create a user](/_images/integrations/builtin/app-nodes/gsuiteadmin/gsuiteadmin_node.png) - - -### 3. G Suite Admin1 node (update: user) - -This node will get the User ID from the previous node and update the user's last name to `Nate`. - -1. Select the credentials that you entered in the previous G Suite Admin node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***User ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > G Suite Admin > Output Data > JSON > id. You can also add the following expression: `{{$node["G Suite Admin"].json["id"]}}`. -5. Click on the ***Add Field*** button and select 'Last Name' from the dropdown list. -6. Enter the last name in the ***Last Name*** field. -7. Click on ***Execute Node*** to run the workflow. - - -In the screenshot below, you will notice that the node has updated the last name of the user that we created in the previous node. - -![Using the G Suite Admin node to update the last name of the user](/_images/integrations/builtin/app-nodes/gsuiteadmin/gsuiteadmin1_node.png) - - -### 4. G Suite Admin2 (get: user) - -This node will get the information of the user we created in the G Suite Admin node. - -1. Select the credentials that you entered in the previous G Suite Admin node. -2. Select 'Get' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***User ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > G Suite Admin > Output Data > JSON > id. You can also add the following expression: `{{$node["G Suite Admin"].json["id"]}}`. -5. Click on ***Execute Node*** to run the workflow. - - -In the screenshot below, you will notice that the node returns the information of the user we created in the G Suite Admin node. - -![Using the G Suite Admin node to get the information of the user](/_images/integrations/builtin/app-nodes/gsuiteadmin/gsuiteadmin2_node.png) - -## FAQs - -### What are the different ways to project a user's information? - -There are three different ways to project a user's information: - -- ***Basic:*** Does not include any custom fields. -- ***Custom:*** Includes the custom fields from schemas in customField. -- ***Full:*** Include all the fields associated with the user. - -You can include custom fields by following the steps mentioned below. -1. Select 'Custom' from the ***Projection*** dropdown list. -2. Click on the ***Add Options*** button and select 'Custom Schemas' from the dropdown list. -3. Select the schema names you want to include from the ***Custom Schemas*** dropdown list. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.getResponse.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.getResponse.md deleted file mode 100644 index 98286b6a8..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.getResponse.md +++ /dev/null @@ -1,87 +0,0 @@ -# GetResponse - -[GetResponse](https://www.getresponse.com/) is an online platform that offers email marketing software, landing page creator, webinar hosting, and much more. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/getResponse/). - - - -## Basic Operations - -* Contact - * Create a new contact - * Delete a contact - * Get a contact - * 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 does not belong 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 deleted file mode 100644 index 4179563aa..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.ghost.md +++ /dev/null @@ -1,89 +0,0 @@ -# Ghost - -[Ghost](https://www.ghost.org/) is an open-source, professional publishing platform built on a Node.js technology stack. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/ghost/). - - -## Basic Operations - -### Admin API - -**Post** -- Create a post -- Delete a post -- Get a post -- Get all posts -- Update a post - - -### Content API - -**Post** -- Get a post -- 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 deleted file mode 100644 index 0482ec779..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.github.md +++ /dev/null @@ -1,70 +0,0 @@ -# GitHub - -[GitHub](https://github.com/) provides hosting for software development and version control using Git. It offers the distributed version control and source code management (SCM) functionality of Git, access control and several collaboration features such as bug tracking, feature requests, task management, and wikis for every project. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/github/). - - -## Basic Operations - -* File - * Create a new file in repository. - * Delete a file in repository. - * Edit a file in repository. - * Get the data of a single file. - * List contents of a folder. -* Issue - * Create a new issue. - * Create a new comment on an issue. - * Edit an issue. - * Get the data of a single issue. - * Lock an issue. -* Repository - * Get the data of a single repository. - * Returns the contents of the repository's license file, if one is detected. - * 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. -* Release - * Creates a new release. - * Get a release. - * Get all repository releases. - * Delete a release. - * Update a release. -* Review - * Creates a new review. - * Get a review for a pull request. - * Get all reviews for a pull request. - * Update a review. -* User - * Returns the repositories of a user. - * Invites a user to an organization. - -## Example Usage - -This workflow allows you to get the community profile of a GitHub repository. You can also find the [workflow](https://n8n.io/workflows/450) on the website. This example usage workflow uses the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [GitHub]() - -The final workflow should look like the following image. - -![A workflow with the GitHub node](/_images/integrations/builtin/app-nodes/github/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. GitHub node - -1. First of all, you'll have to enter credentials for the GitHub node. You can find out how to do that [here](/integrations/builtin/credentials/github/). -2. Select the 'Repository' option under the *Resource* field. -3. Select the 'Get Profile' option under the *Operation* field. -4. Enter the repository owner in the *Repository Owner* field. -5. Enter the repository name in the *Repository Name* field. -6. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.gitlab.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.gitlab.md deleted file mode 100644 index ce88fdea4..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.gitlab.md +++ /dev/null @@ -1,50 +0,0 @@ -# GitLab - -[GitLab](https://gitlab.com/) is a web-based DevOps lifecycle tool that provides a Git-repository manager providing wiki, issue-tracking, and continuous integration/continuous installation pipeline features. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/gitlab/). - - -## Basic Operations - -* Issue - * Create a new issue - * Create a new comment on an issue - * Edit an issue - * Get the data of a single issue - * Lock an issue -* Repository - * Get the data of a single repository - * Returns issues of a repository -* Release - * Create a new release - * Delete a new release - * Get a new release - * Get all releases - * Update a new release -* User - * Returns the repositories of a user - -## Example Usage - -This workflow allows you to get the details of a GitLab repository. You can also find the [workflow](https://n8n.io/workflows/465) on the website. This example usage workflow uses the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [GitLab]() - -The final workflow should look like the following image. - -![A workflow with the GitLab node](/_images/integrations/builtin/app-nodes/gitlab/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. GitLab node - -1. First of all, you'll have to enter credentials for the GitLab node. You can find out how to do that [here](/integrations/builtin/credentials/gitlab/). -2. Select the 'Repository' option from the *Resource* dropdown list. -3. Select the 'Get' option under the *Operation* field. -4. Enter the project owner in the *Project Owner* field. -5. Enter the project name in the *Project Name* field. -6. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.gmail.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.gmail.md deleted file mode 100644 index 8621e493f..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.gmail.md +++ /dev/null @@ -1,49 +0,0 @@ -# Gmail - -[Gmail](https://www.gmail.com){:target=_blank .external-link} is an email service developed by Google. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Operations - -* Draft - * Create - * Delete - * Get - * Get Many -* Label - * Create - * Delete - * Get - * Get Many -* Message - * Add Label - * Delete - * Get - * Get Many - * Mark as Read - * Mark as Unread - * Remove Label - * Reply - * Send -* Thread - * Add Label - * Delete - * Get - * Get Many - * Remove Label - * reply - * Trash - * Untrash - -## Related resources - -Refer to Google's [Gmail API documentation](https://developers.google.com/gmail/api) for detailed information about the API that this node integrates with. - -n8n provides a trigger node for Gmail. You can find the trigger node docs [here](/integrations/builtin/trigger-nodes/gmailTrigger/). - -View [example workflows and related content](https://n8n.io/integrations/356-gmail/){:target=_blank .external-link} on our website. - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.goToWebinar.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.goToWebinar.md deleted file mode 100644 index 74fbe1b96..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.goToWebinar.md +++ /dev/null @@ -1,103 +0,0 @@ -# GoToWebinar - -[GoToWebinar](https://www.gotomeeting.com/webinar) is a platform that helps you create and deliver online video conferences. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/goToWebinar/). - - -## Basic Operations - -* Attendee - * Get - * Get All - * Get Details -* Co-Organizer - * Create - * Delete - * Get All - * Reinvite -* Panelist - * Create - * Delete - * Get All - * Reinvite -* Registrant - * Create - * Delete - * Get - * Get All -* Session - * Get - * Get All - * Get Details -* Webinar - * Create - * Get - * Get All - * Update - -## Example Usage - -This workflow allows you to create, update, and get a webinar. You can also find the [workflow](https://n8n.io/workflows/960) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [GoToWebinar]() - -The final workflow should look like the following image. - -![A workflow with the GoToWebinar node](/_images/integrations/builtin/app-nodes/gotowebinar/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. GoToWebinar node (create: webinar) - -This node will create a new webinar in GoToWebinar. - -1. First of all, you'll have to enter credentials for the GoToWebinar node. You can find out how to do that [here](/integrations/builtin/credentials/goToWebinar/). -2. Select 'Webinar' from the ***Resource*** dropdown list. -3. Select 'Create' from the ***Operation*** dropdown list. -4. Enter a subject in the ***Subject*** field. -5. Click on the ***Add Time Range*** button. -6. Set the start time in the ***Start Time*** field. -7. Set the end time in the ***End Time*** field. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new webinar. - -![Using the GoToWebinar node to create a new webinar](/_images/integrations/builtin/app-nodes/gotowebinar/gotowebinar_node.png) - -### 3. GoToWebinar1 node (update: webinar) - -This node will update the description of the webinar that we created in the previous node. - - -1. Select the credentials that you entered in the previous node. -2. Select 'Webinar' from the ***Resource*** dropdown list. -3. Select 'Update' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Webinar Key*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > webinarKey. You can also add the following expression: `{{$json["webinarKey"]}}`. -6. Click on the ***Add Field*** button 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 updates the description of the webinar that we created in the previous node. - -![Using the GoToWebinar node to update a webinar](/_images/integrations/builtin/app-nodes/gotowebinar/gotowebinar1_node.png) - -### 4. GoToWebinar2 node (get: webinar) - -This node will get the information about the webinar that we created earlier. - -1. Select the credentials that you entered in the previous node. -2. Select 'Webinar' from the ***Resource*** dropdown list. -3. Select 'Get' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Webinar Key*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > GoToWebinar > Output Data > JSON > webinarKey. You can also add the following expression: `{{$node["GoToWebinar"].json["webinarKey"]}}`. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns the information about the webinar. - -![Using the GoToWebinar node to get information of a webinar](/_images/integrations/builtin/app-nodes/gotowebinar/gotowebinar2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleAds.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleAds.md deleted file mode 100644 index 957e39324..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleAds.md +++ /dev/null @@ -1,12 +0,0 @@ -# Google Ads node - -[Google Ads](https://ads.google.com/){:targe=_blank .external-link} is a digital advertising service. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - -## Basic operations - -* Campaign - * Get all campaigns - * Get a campaign \ No newline at end of file diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleAnalytics.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleAnalytics.md deleted file mode 100644 index 5beb944f4..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleAnalytics.md +++ /dev/null @@ -1,86 +0,0 @@ -# Google Analytics - -[Google Analytics](https://analytics.google.com) is a web analytics service offered by Google that lets you measure your advertising ROI as well as track your Flash, video, and social networking sites and applications. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -* Report - * Return the analytics data -* User Activity - * Return user activity data. - -## Example Usage - -This workflow allows you to get analytical metrics of your website using the Goole Analytics node and store it in Airtable. You can also find the [workflow](https://n8n.io/workflows/892) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Google Analytics]() -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Airtable]/integrations/builtin/app-nodes/n8n-nodes-base.airtable/) - -The final workflow should look like the following image. - -![A workflow with the Google Analytics node](/_images/integrations/builtin/app-nodes/googleanalytics/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Google Analytics node (get: report) - -This node will retrieve the session metrics grouped by country for a given date range. You can select a different dimension, metric, and date range. - -1. First of all, you'll have to enter credentials for the Google Analytics node. You can find out how to do that [here](/integrations/builtin/credentials/google/). -2. Select a view from the ***View ID*** dropdown list. -3. Click on ***Add Field*** and select 'Dimensions'. -4. Click on the ***Add Dimension*** button. -5. Select 'Country' from the ***Name*** field. -6. Click on ***Add Field*** and select 'Date Ranges'. -7. Click on the ***Add Date Range*** button. -8. Select a start date in the ***Start Date*** field. -9. Select an end date in the ***End Date*** field. -10. Click on ***Add Field*** and select 'Metrics'. -11. Click on the ***Add Metrics*** button. -12. Enter `Session` in the ***Alias*** field. -13. Enter `ga:sessions` in the ***Expression*** field. -14. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the information about the sessions grouped by country. - -![Using the Google Analytics node to retrieve analytics of a website](/_images/integrations/builtin/app-nodes/googleanalytics/analytics_node.png) - -### 3. Set node - -We will use the Set node to set the values for the country and metrics. This data gets passed on to the next nodes in the workflow. - -1. Click on the ***Add Value*** button and select 'string' from the dropdown list. -2. Enter `Country` in the ***Name*** 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: Current Nodes > Input Data > JSON > country. You can also add the following expression: `{{$json["ga:country"]}}`. -5. Click on ***Add Value*** and select 'Number' from the dropdown list. -6. Enter `Metric` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Current Nodes > Input Data > JSON > total. You can also add the following expression: `{{$json["total"]}}`. -9. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -10. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sets the value for `Country` and `Metric`. - -![Using the Set node to set data](/_images/integrations/builtin/app-nodes/googleanalytics/set_node.png) - -### 4. Airtable node (Append) - -This node will append the data that we set in the previous node to a table. Create a table like [this](https://airtable.com/shrFIVzFaXgv7LekV) 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 'Append' 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 ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node appends the data that we had set in the previous node. - -![Using the Airtable node to insert data into an Airtable table](/_images/integrations/builtin/app-nodes/googleanalytics/airtable_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleBigQuery.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleBigQuery.md deleted file mode 100644 index 2a0cb53d1..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleBigQuery.md +++ /dev/null @@ -1,101 +0,0 @@ -# Google BigQuery - -[Google BigQuery](https://cloud.google.com/bigquery/) is a fully-managed, serverless data warehouse that enables scalable analysis over petabytes of data. It is a Platform as a Service that supports querying using ANSI SQL. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -**Record** - -- Create a new record -- Retrieve all records - - - -## Example Usage - -This workflow allows you to send position updates of the ISS every minute to a table in Google BigQuery. You can also find the [workflow](https://n8n.io/workflows/1049) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Google BigQuery]() - -The final workflow should look like the following image. - -![A workflow with the Google BigQuery node](/_images/integrations/builtin/app-nodes/googlebigquery/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow every minute. - -1. Click on ***Add Cron Time***. -2. Select 'Every Minute' from the ***Mode*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every minute. - -![Using the Cron node to trigger the workflow every minute](/_images/integrations/builtin/app-nodes/googlebigquery/cron_node.png) - -### 2. HTTP Request node (GET) - -This node will make a GET request to the API `https://api.wheretheiss.at/v1/satellites/25544/positions` to fetch the position of the ISS. This information gets passed on to the next node in the workflow. - -1. Enter `https://api.wheretheiss.at/v1/satellites/25544/positions` in the ***URL*** field. -2. Click on the ***Add Parameter*** button in the ***Query Parameters*** section. -3. Enter `timestamps` in the ***Name*** field. -4. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -5. Enter the following expression: `{{Date.now()}}`. This expression will return the current timestamp. -6. 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 the information about the location of the ISS. - -![Using the HTTP Request node to get the information about the location of the ISS](/_images/integrations/builtin/app-nodes/googlebigquery/httprequest_node.png) - -### 3. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `name` in the ***Name*** 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: Current Node > Input Data > JSON > 0 > name. You can also add the following expression: `{{$json["0"]["name"]}}`. -5. Click on ***Add Value*** and select 'Number' from the dropdown list. -6. Enter `latitude` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > Input Data > JSON > 0 > latitude. You can also add the following expression: `{{$json["0"]["latitude"]}}`. -9. Click on ***Add Value*** and select 'Number' from the dropdown list. -10. Enter `longitude` in the ***Name*** field. -11. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Nodes > Input Data > JSON > 0 > longitude. You can also add the following expression: `{{$json["0"]["longitude"]}}`. -13. Click on ***Add Value*** and select 'Number' from the dropdown list. -14. Enter `timestamp` in the ***Name*** field. -15. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -16. Select the following in the ***Variable Selector*** section: Nodes > Input Data > JSON > 0 > timpestamp. You can also add the following expression: `{{$json["0"]["timestamp"]}}`. -17. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -18. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uses the data from the previous node and returns the data that we set for the workflow. - -![Using the Set node to set the data](/_images/integrations/builtin/app-nodes/googlebigquery/set_node.png) - -### 4. Google BigQuery node (create: record) - -This node will send the data from the previous node to the `position` table in Google BigQuery. If you have created a table with a different name, use that table instead. - -1. First of all, you'll have to enter credentials for the Google BigQuery node. You can find out how to do that [here](/integrations/builtin/credentials/google/). -2. Select a project from the ***Project ID*** dropdown list. -3. Select a dataset from the ***Dataset ID*** dropdown list. -4. Select the table from `position` from the ***Table ID*** dropdown list. If you created a table with a different name, select that table instead. -5. Enter `name, latitude, longitude, timestamp` in the ***Columns*** field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends the data from the previous node to the `position` table in Google BigQuery. - -![Using the Google BigQuery node to create new record](/_images/integrations/builtin/app-nodes/googlebigquery/googlebigquery_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleBooks.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleBooks.md deleted file mode 100644 index 4afee3077..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleBooks.md +++ /dev/null @@ -1,83 +0,0 @@ -# Google Books - -[Google Books](https://books.google.com) is a service from Google to browse, buy, or borrow books online. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -* Bookshelf - * Retrieve a specific bookshelf resource for the specified user - * Get all public bookshelf resource for the specified user -* Bookshelf Volume - * Add a volume to a bookshelf - * Clears all volumes from a bookshelf - * Get all volumes in a specific bookshelf for the specified user - * Moves a volume within a bookshelf - * Removes a volume from a bookshelf -* Volume - * 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.googleCalendar.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleCalendar.md deleted file mode 100644 index 1c26c393d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleCalendar.md +++ /dev/null @@ -1,44 +0,0 @@ -# Google Calendar - -[Google Calendar](https://www.google.com/calendar/) is a time-management and scheduling calendar service developed by Google. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -* Calendar - * If a time-slot is available in a calendar -* Event - * Add a event to calendar - * Delete an event - * Retrieve an event - * Retrieve all events from a calendar - * Update an event - -## Example Usage - -This workflow allows you to add an event to Google Calendar. You can also find the [workflow](https://n8n.io/workflows/427) on the website. This example usage workflow uses the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Google Calendar]() - -The final workflow should look like the following image. - -![A workflow with the Google Calendar node](/_images/integrations/builtin/app-nodes/googlecalendar/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Google Calendar node - -1. First of all, you'll have to enter credentials for the Google Calendar node. You can find out how to do that [here](/integrations/builtin/credentials/google/). -2. Select the *Calendar* from the dropdown list of the user's calendar list. -3. Enter the start date of your event in the *Start* field. -4. Enter the end date of your event in the *End* field. -5. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleChat.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleChat.md deleted file mode 100644 index a8db7e7ae..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleChat.md +++ /dev/null @@ -1,21 +0,0 @@ -# Google Chat - -[Google Chat](https://chat.google.com/) is a messaging platform. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -* Member - * Get a membership - * Get all memberships in a space -* Message - * Create a message - * Delete a message - * Get a message - * Update a message -* Space - * Get a space - * Get all spaces the caller is a member of diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudFirestore.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudFirestore.md deleted file mode 100644 index 8a225a7f1..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudFirestore.md +++ /dev/null @@ -1,122 +0,0 @@ -# Google Cloud Firestore - -[Google Cloud Firestore](https://firebase.google.com/docs/firestore/) is a flexible, scalable database for mobile, web, and server development from Firebase and Google Cloud. It keeps your data in-sync across client apps through real-time listeners and offers offline support for mobile and web. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -* Document - * Create a document - * Create/Update a document - * Delete a document - * Get a document - * Get all documents from a collection - * Runs a query against your documents -* Collection - * Get all root collections - -## Example Usage - -This workflow allows you to create, update, and get a document in the Google Cloud Firestore. You can also find the [workflow](https://n8n.io/workflows/839) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Google Cloud Firestore]() - -The final workflow should look like the following image. - -![A workflow with the Google Cloud Firestore node](/_images/integrations/builtin/app-nodes/googlecloudfirestore/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Set node - -We will use the Set node to set the name and id. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `name` in the ***Name*** field. -3. Enter `n8n` in the ***Value*** field. -4. Click on ***Add Value*** and select 'Number' from the dropdown list. -5. Enter `id` in the ***Name*** field. -6. Enter `1` in the ***Value*** field. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that node sets the value for name and id. - -![Using the Set node to set the data](/_images/integrations/builtin/app-nodes/googlecloudfirestore/set_node.png) - -### 3. Google Cloud Firestore node (document: create) - -This node will create a new document in a collection in Google Cloud Firestore with the data from the previous node. - -1. First of all, you'll have to enter credentials for the Google Cloud Firestore node. You can find out how to do that [here](/integrations/builtin/credentials/google/). -2. Select 'Create' from the ***Operation*** dropdown list. -3. Select a project from the ***Project ID*** dropdown list. -4. Enter the name of your collection in the ***Collection*** field. -5. Enter `id, name` in the ***Columns / attributes*** field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new document using the data from the previous node. - -![Using the Google Cloud Firestore node to create new document](/_images/integrations/builtin/app-nodes/googlecloudfirestore/googlecloudfirestore_node.png) - -### 4. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. We will set a new value for `name`. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `name` in the ***Name*** field. -3. Enter `nodemation` in the ***Value*** field. -4. Click on ***Add Value*** and select 'String' from the dropdown list. -5. Enter `document_id` in the ***Name*** field. -6. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -7. Select the following in the ***Variable Selector*** section: Nodes > Google Cloud Firestore > Output Data > JSON > _id. You can also add the following expression: `{{$node["Google Cloud Firestore"].json["_id"]}}`. -8. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -9. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sets the values of `name` and `document_id`. These values are passed to the next node in the workflow. - -![Using the Set node to set the values for name and document_id](/_images/integrations/builtin/app-nodes/googlecloudfirestore/set1_node.png) - -### 5. Google Cloud Firestore1 node (document: upsert) - -This node will update the value of the `name` field in the document that we created using the Google Cloud Firestore node. - -1. Select the credentials that you entered in the previous Google Cloud Firestore node. -2. Select 'Create/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 > Google Cloud Firestore > Parameters > projectId. You can also add the following expression: `{{$node["Google Cloud Firestore"].parameter["projectId"]}}`. -5. Click on the gears icon next to the ***Collection*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Google Cloud Firestore > Parameters > collection. You can also add the following expression: `{{$node["Google Cloud Firestore"].parameter["collection"]}}`. -7. Enter `document_id` in the ***Update Key*** field. -8. Enter `name` in the ***Column /Attributes*** field. -9. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node updates the value of the `name` field in the document that we created using the Google Cloud Firestore node. - -![Using the Google Cloud Firestore node to update a document](/_images/integrations/builtin/app-nodes/googlecloudfirestore/googlecloudfirestore1_node.png) - -### 6. Google Cloud Firestore node (document: get) - -This node will get the document that we created using the Google Cloud Firestore node. - - -1. Select the credentials that you entered in the previous node. -2. Click on the gears icon next to the ***Project ID*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Nodes > Google Cloud Firestore > Parameters > projectId. You can also add the following expression: `{{$node["Google Cloud Firestore"].parameter["projectId"]}}`. -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: Nodes > Google Cloud Firestore > Parameters > collection. You can also add the following expression: `{{$node["Google Cloud Firestore"].parameter["collection"]}}`. -6. Click on the gears icon next to the ***Document ID*** field and click on ***Add Expression***. -7. Select the following in the ***Variable Selector*** section: Nodes > Set1 > Output Data > JSON > document_id. You can also add the following expression: `{{$node["Set1"].json["document_id"]}}`. -8. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns the document that we created using the Google Cloud Firestore node. - -![Using the Google Cloud Firestore node to get a document](/_images/integrations/builtin/app-nodes/googlecloudfirestore/googlecloudfirestore2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudNaturalLanguage.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudNaturalLanguage.md deleted file mode 100644 index a3c2f8fb0..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudNaturalLanguage.md +++ /dev/null @@ -1,95 +0,0 @@ -# Google Cloud Natural Language - -[Google Cloud Natural Language](https://cloud.google.com/natural-language/) uses machine learning to reveal the structure and meaning of text. You can extract information about people, places, and events, and better understand social media sentiment and customer conversations. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -* Document - * Analyze Sentiment - -## Example Usage - -This workflow allows you to analyze the sentiment of feedback received via a Typeform submission and send a message on Mattermost if that feedback is negative. You can also find the [workflow](https://n8n.io/workflows/786) on n8n.io. This example usage workflow uses the following nodes. -- [Typeform Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.typeformtrigger/) -- [Google Cloud Natural Language]() -- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/) -- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/) -- [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 Google Cloud Natural Language node](/_images/integrations/builtin/app-nodes/googlecloudnaturallanguage/workflow.png) - -### 1. Typeform Trigger node - -This node will trigger the workflow when a feedback form is submitted. Make sure to create a feedback form for your event. - -1. Select 'Access Token' from the ***Authentication*** dropdown list. -2. Enter the credentials for the Typeform Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/typeform/). -3. Select the event feedback form from the ***Form*** dropdown list. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node triggers the workflow when feedback is submitted. We will pass this feedback to the next nodes in the workflow. -![Using the Typeform Trigger node to trigger the workflow when a feedback form is submitted](/_images/integrations/builtin/app-nodes/googlecloudnaturallanguage/typeformtrigger_node.png) - -### 2. Google Cloud Natural Language node (analyzeSentiment: document) - -This node will analyze the sentiment of the feedback that we got from the previous node. We will pass the analysis score to the next node in the workflow. - -1. First of all, you'll have to enter credentials for the Google Cloud Natural Language node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/google/). -2. Click on the gears icon next to the ***Content*** field and click on ***Add Expression***. - -3. Select the following in the ***Variable Selector*** section: Nodes > Typeform Trigger > Output Data > JSON > What did you think about the event? You can also add the following expression: `{{$node["Typeform Trigger"].json["What did you think about the event?"]}}`. If you want to analyze the sentiment for a different question, select that question instead. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node analyzes the sentiment of the feedback and gives a score based on that. - -![Using the Google Cloud Natural Language node to analyze the sentiment](/_images/integrations/builtin/app-nodes/googlecloudnaturallanguage/googlecloudnaturallanguage_node.png) - - -### 3. IF node - -This node will check if the score we got from the previous node is smaller than `0`. If the score is smaller than `0`, it will return true otherwise false. - -1. Click on ***Add Condition*** and select 'Number'. -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 > Google Cloud Natural Language > Output Data > JSON > documentSentiment > score. You can also add the following expression: `{{$node["Google Cloud Natural Language"].json["documentSentiment"]["score"]}}`. -4. Select 'Smaller' from the ***Operation*** dropdown list. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node checks if the score that we received from the previous node is smaller than `0`. - -![Using the IF node to check if the score is smaller than `0` or not](/_images/integrations/builtin/app-nodes/googlecloudnaturallanguage/if_node.png) - -### 4. Mattermost node (post: message) - -This node will send the feedback and the analysis score to the `Feedback` channel in Mattermost. If you have a different channel, use that instead. - -1. Create a Mattermost node connected to the 'true' output of the IF node. -2. You'll have to enter credentials for the Mattermost node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/mattermost/). -3. Select a channel from the ***Channel ID*** dropdown list. -4. Click on the gears icon next to the ***Message*** field click on ***Add Expression***. - -5. Enter the following message in the ***Expression*** field: `You got a new feedback with a score of {{$node["Google Cloud Natural Language"].json["documentSentiment"]["score"]}}. Here is what it says:{{$node["Typeform Trigger"].json["What did you think about the event?"]}}`. -6. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that the node sends the feedback and the analysis score to the `Feedback` channel in Mattermost. - -![Using the Mattermost node to send the feedback and the analysis score](/_images/integrations/builtin/app-nodes/googlecloudnaturallanguage/mattermost_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/googlecloudnaturallanguage/noop_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.googleCloudRealtimeDatabase.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudRealtimeDatabase.md deleted file mode 100644 index 19e8f7f4e..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudRealtimeDatabase.md +++ /dev/null @@ -1,97 +0,0 @@ -# Google Cloud Realtime Database - -[Google Cloud Realtime Database](https://firebase.google.com/docs/database/) is a cloud-hosted database. Data is stored as JSON and synchronized in realtime to every connected client. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -* Write data to a database -* Delete data from a database -* Get a record from a database -* Append to a list of data -* Update item on a database - -## Example Usage - -This workflow allows you to receive updates of the position of the ISS every minute and push it to a database using the Google Cloud Realtime Database node. You can also find the [workflow](https://n8n.io/workflows/787) on n8n.io. This example usage workflow uses the following nodes. - -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Google Cloud Realtime Database]() - -The final workflow should look like the following image. - -![A workflow with the Google Cloud Realtime Database node](/_images/integrations/builtin/app-nodes/googlecloudrealtimedatabase/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow every minute. - -1. Click on ***Add Cron Time***. -2. Select 'Every Minute' from the ***Mode*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every minute. - -![Using the Cron node to trigger the workflow every minute](/_images/integrations/builtin/app-nodes/googlecloudrealtimedatabase/cron_node.png) - -### 2. HTTP Request node (GET) - -This node will make a GET request to the API `https://api.wheretheiss.at/v1/satellites/25544/positions` to fetch the position of the ISS. This information gets passed on to the next node in the workflow. - -1. Enter `https://api.wheretheiss.at/v1/satellites/25544/positions` in the ***URL*** field. -2. Click on the ***Add Parameter*** button in the ***Query Parameters*** section. -3. Enter `timestamps` in the ***Name*** field. -4. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -5. Enter the following expression: `{{Date.now()}}`. This expression will return the current timestamp. -6. 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 the information about the location of the ISS. - -![Using the HTTP Request node to get the information about the location of the ISS](/_images/integrations/builtin/app-nodes/googlecloudrealtimedatabase/httprequest_node.png) - -### 3. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `latitude` in the ***Name*** 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 > HTTP Request > Output Data > JSON > 0 > latitude. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["latitude"]}}`. -5. Click on ***Add Value*** and select 'String' from the dropdown list. -6. Enter `longitude` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > 0 > longitude. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["longitude"]}}`. -9. Click on ***Add Value*** and select 'String' from the dropdown list. -10. Enter `timestamp` in the ***Name*** field. -11. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > 0 > timpestamp. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["timestamp"]}}`. -13. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -14. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uses the data from the previous node and returns the data that we set for the workflow. - -![Using the Set node to set the data](/_images/integrations/builtin/app-nodes/googlecloudrealtimedatabase/set_node.png) - -### 4. Google Cloud Realtime Database node (push) - -This node will push the data from the previous node to the `iss` path in Google Cloud Realtime Database. If you have created a path with a different name, you can use that path instead. - -1. First of all, you'll have to enter credentials for the Google Cloud Realtime Database node. You can find out how to do that [here](/integrations/builtin/credentials/google/). -2. Select a project from the ***Project ID*** dropdown list. -3. Select 'Push' from the ***Operation*** dropdown list. -4. Enter a path in the ***Object Path*** field. -5. Enter `latitude, longitude, timestamp` in the ***Columns / Attributes*** field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node pushes the data from the previous node to the `iss` path in Google Cloud Realtime Database. - -![Using the Google Cloud Realtime Database node to push the data to a path](/_images/integrations/builtin/app-nodes/googlecloudrealtimedatabase/googlecloudrealtimedatabase_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudStorage.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudStorage.md deleted file mode 100644 index 2d81d5e2f..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudStorage.md +++ /dev/null @@ -1,25 +0,0 @@ -# Google Cloud Storage - -[Google Cloud Storage](https://cloud.google.com/storage){:target=_blank .external-link} offers object storage for data, with flexible capacity and retrieval. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - -## Operations - -* Bucket - * Create - * Delete - * Get - * Get Many - * Update -* Object - * Create - * Delete - * Get - * Get Many - * Update - -## Related resources - -Refer to Google's [Cloud Storage API documentation](https://cloud.google.com/storage/docs/apis){:target=_blank .external-link} for detailed information about the API that this node integrates with. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleContacts.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleContacts.md deleted file mode 100644 index 37ade402d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleContacts.md +++ /dev/null @@ -1,75 +0,0 @@ -# Google Contacts - -[Google Contacts](https://contacts.google.com/) is Google's contact management tool that is available in its free email service Gmail, as a standalone service, and as a part of Google's business-oriented suite of web apps Google Apps. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - - -## Basic Operations - -* Contact - * Create a contact - * Delete a contact - * 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 deleted file mode 100644 index 74586c1f8..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleDocs.md +++ /dev/null @@ -1,55 +0,0 @@ -# Google Docs - -[Google Docs](https://docs.google.com) is a web-based word processor that is part of Google's office software suite within its Google Drive service. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic operations - -* Document - * Create - * 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 deleted file mode 100644 index 9fef1ff13..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleDrive.md +++ /dev/null @@ -1,71 +0,0 @@ -# Google Drive - -[Google Drive](https://drive.google.com) is a file storage and synchronization service developed by Google. It allows users to store files on their servers, synchronize files across devices, and share files. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -* Drive - * Create a drive - * Delete a drive - * Get a drive - * List all drives - * Update a drive -* File - * Copy a file - * Delete a file - * Download a file - * List files and folders - * Share a file - * Update a file - * Upload a file -* Folder - * Create a folder - * 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.googlePerspective.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googlePerspective.md deleted file mode 100644 index da1298973..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googlePerspective.md +++ /dev/null @@ -1,37 +0,0 @@ -# Google Perspective - -[Google Perspective](https://www.perspectiveapi.com/) is a free API that uses machine learning to identify "toxic" comments, making it easier to host better conversations online. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic operations - -* Analyze Comment - -## Example usage - -This workflow allows you to analyze a comment for profanity. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Google Perspective]() - -The final workflow should look like the following image. - -![A workflow with the Google Perspective node](/_images/integrations/builtin/app-nodes/googleperspective/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Google Perspective node - -1. First enter credentials for the Google Perspective node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/google/). -2. The **Analyze Comment** ***Operation*** is selected by default. -3. In the ***Text*** field enter the comment to be analyzed. -4. From the ***Properties*** section click **Add Attribute**. - * For ***Attribute Name*** select **Profanity**. - * For ***Score Threshold*** leave the **0.00** default setting to return all scores. -5. Click on **Execute Node** to run the workflow. - -![The Google Perspective node](/_images/integrations/builtin/app-nodes/googleperspective/googleperspective_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleSheets.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleSheets.md deleted file mode 100644 index 5bdca0a35..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleSheets.md +++ /dev/null @@ -1,205 +0,0 @@ -# Google Sheets - -[Google Sheets](https://www.google.com/sheets) is a web-based spreadsheet program that is part of Google's office software suite within its Google Drive service. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -* Spreadsheet - * Create a spreadsheet -* Sheet - * Append data to a sheet - * Clear data from a sheet - * Create a new sheet - * Delete columns and rows from a sheet - * Look up a specific column value and return the matching row - * Read data from a sheet - * Remove a sheet - * Update rows in a sheet - -## Example Usage - -This workflow allows you to append, lookup, update, and read data from Google Sheets. You can also find the [workflow](https://n8n.io/workflows/694) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Google Sheets]() - -The final workflow should look like the following image. - -![A workflow with the Google Sheets node](/_images/integrations/builtin/app-nodes/googlesheets/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - - -### 2. Set node - -This example workflow uses the Set node to generate data that we want to add to Google Sheets. You can also use other nodes, for example, the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node, to get the data you want to add to the Google Sheets. - -1. Click on the ***Add Value*** button and select 'String' from the dropdown list. -2. Enter `Name` in the ***Name*** field. -3. Enter the name for a house in the ***Value*** field. -4. Click on the ***Add Value*** button and select 'String' from the dropdown list. -5. Enter `Rent` in the ***Name*** field. -6. Enter the rent of the house along with the currency in the ***Value*** field. For example, `$1000`. -7. Click on the ***Add Value*** button and select 'String' from the dropdown list. -8. Enter `City` in the ***Name*** field. -9. Enter the name of the city in the ***Value*** field. -10. Click on the ***Add Value*** button and select 'Number' from the dropdown list. -11. Enter `ID` in the ***Name*** field. -12. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -13. Paste the following expression: `{{Math.floor(Math.random()*1000)}}`. This expression will generate a three-digit random number. -14. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the Set node has created data that will be passed to the next nodes in the workflow. Also, the output shows a random three-digit number as the ID, created by the expression. - -![Using the Set node to set data to be inserted in the Google Sheets node](/_images/integrations/builtin/app-nodes/googlesheets/set_node.png) - - -### 3. Google Sheets node (Append) - -#### Creating a Google Sheets spreadsheet - -1. Create a new [Google Sheets](https://sheet.new) spreadsheet. -2. In your spreadsheet, enter `ID`, `Name`, `Rent`, and `City` in the cells A1, B1, C1, and D1, respectively. -3. Copy the string of characters located between `/d/` and `/edit` in your spreadsheet URL. This string is the Spreadsheet ID, which we will use in the Google Sheets node. - -#### Configure the Google Sheets node - -This Google Sheets node will add the data from the Set node in a new row to the Google Sheets that we will specify using the Spreadsheet ID. - -1. Select 'OAuth2' from the ***Authentication*** dropdown list. -2. First of all, you'll have to enter credentials for the Google Sheets node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/google/). -3. Select 'Append' from the ***Operation*** dropdown list. -4. Paste the Spreadsheet ID you copied in the previous step, in the ***Spreadsheet ID*** field. -5. In the ***Range*** field, enter the range of columns to append the data to your spreadsheet. Make sure that your range includes enough columns for all the data in the Set node. For this workflow, enter `A:D` in the ***Range*** field. -6. Click on the ***Add Option*** button and select 'Value Input Mode' from the dropdown list. -7. Select 'User Entered' from the ***Value Input Mode*** dropdown list. Refer to the [FAQs](#how-to-enter-values-with-a-proper-format) for more information on why we used this option. -8. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will observe that the node adds the data from the Set node to the Google Sheets. You will also notice that the values get added in the format they are set. - -![Using the Google Sheets node to insert data into a Google Sheets spreadsheet](/_images/integrations/builtin/app-nodes/googlesheets/googlesheets_node.png) - -### 4. Google Sheets1 node (Lookup) - -This node will return the entries from the Google Sheets that have `Berlin` as the City. Feel free to change the city name to something else but make sure you have at least one record with the city name you look for in your Google Sheets spreadsheet. - -1. Select 'OAuth2' from the ***Authentication*** dropdown list. -2. Select the credentials that you entered in the previous Google Sheets node. -3. Select 'Lookup' from the ***Operation*** dropdown list. -4. In the ***Spreadsheet ID*** field, enter the same string used in the previous Google Sheets node. -5. Enter `City` in the ***Lookup Column*** field. -6. Enter `Berlin` in the ***Lookup Value*** field. -7. Click on the ***Add Option*** button and select 'Return All Matches' from the dropdown list. -8. Toggle ***Return All Matches*** to true. This option returns all the entries that contain `Berlin` as the City. Refer to the [FAQs](#how-to-return-all-the-values-with-the-lookup-operation) for more information. -9. Click on the ***Add Option*** button and select 'Value Render Mode' from the dropdown list. This option determines how the values should render in the output. The 'Unformatted Value' option returns the data without formatting it. Refer to the [FAQs](#what-are-the-various-formats-to-read-the-data-from-the-google-sheets) for more information on why we used this option. -10. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that the node returns all the entries that contain Berlin as the City. The output is unformatted and is passed on to the next nodes in the workflow. - -![Using the Google Sheets node to lookup for data in the Google Sheets spreadsheet](/_images/integrations/builtin/app-nodes/googlesheets/googlesheets1_node.png) - - -### 5. Set1 node - -We will use expressions to get the data from the previous node and increase the rent by $100 for the houses in Berlin. - -1. Click on the ***Add Value*** button and select 'String' from the dropdown list. -2. Enter `Name` in the ***Name*** field. -3. Click on the gears icon next to the ***Value*** field click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Google Sheets1 > Output Data > JSON > Name. You can also add the following expression: `{{$node["Google Sheets1"].json["Name"]}}`. -5. Click on the ***Add Value*** button and select 'String' from the dropdown list. -6. Enter `City` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > Google Sheets1 > Output Data > JSON > City. You can also add the following expression: `{{$node["Google Sheets1"].json["City"]}}`. -9. Click on the ***Add Value*** button and select 'Number' from the dropdown list. -10. Click on the gears icon next to the ***Value*** field click on ***Add Expression***. -11. Paste the following expression: `{{$node["Google Sheets1"].json["Rent"]+100}}`. This expression will increase the rent by $100. -12. Click on the ***Add Value*** button and select 'Number' from the dropdown list. -13. Enter `ID` in the ***Name*** field. -14. Click on the gears icon next to the ***Value*** field click on ***Add Expression***. -15. Select the following in the ***Variable Selector*** section: Nodes > Google Sheets1 > Output Data > JSON > ID. You can also add the following expression: `{{$node["Google Sheets1"].json["ID"]}}`. -16. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node uses an expression to get the data from the previous node and increases the rent of the houses by $100. This new data will be passed to the next nodes in the workflow. - -![Using the Set node to increase the rent](/_images/integrations/builtin/app-nodes/googlesheets/set1_node.png) - -### 6. Google Sheets2 node (Update) - -This node will update the rent for the houses in Berlin with the new rent set in the previous node. - -1. Select 'OAuth2' in the ***Authentication*** field. -2. Select the credentials that you entered in the previous Google Sheets node. -3. Select 'Update' from the ***Operation*** dropdown list. -4. In the ***Spreadsheet ID*** field, enter the same string used in the previous Google Sheets node. -5. In the ***Range*** field, enter the same range used in the previous Google Sheets node. -6. Enter `ID` in the ***Key*** field. -7. Click on the ***Add Option*** button and select 'Value Input Mode' from the dropdown list. -8. Select 'User Entered' from the ***Value Input Mode*** dropdown list. Refer to the [FAQs](#how-to-enter-values-with-a-proper-format) for more information on why we used this option. -9. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that this node updates the rent values of the houses in Berlin based on the ID in the Google Sheets. You will also see that the updated values are in the correct format. - -![Using the Google Sheets node to update the data to the Google Sheets spreadsheet](/_images/integrations/builtin/app-nodes/googlesheets/googlesheets2_node.png) - -### 7. Google Sheets3 node (Read) - -This node will read the data from Google Sheets. - -1. Select 'OAuth2' in the ***Authentication*** field. -2. Select the credentials that you entered in the previous Google Sheets node. -3. Select 'Read' from the ***Operation*** dropdown list. -4. In the ***Spreadsheet ID*** field, enter the same string used in the previous Google Sheets node. -5. In the ***Range*** field, enter the same range used in the previous Google Sheets node. -6. Click on the ***Add Option*** button and select 'Value Render Mode' from the dropdown list. -7. Select 'Formatted Value' from the ***Value Render Mode*** dropdown list. Refer to the [FAQs](#what-are-the-various-formats-to-read-the-data-from-the-google-sheets) for more information on why we used this option. -8. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that this node returns all the values from the Google Sheets in the appropriate format. - -![Using the Google Sheets node to read data from the Google Sheets spreadsheet](/_images/integrations/builtin/app-nodes/googlesheets/googlesheets3_node.png) - -## FAQs - -### What are the various formats to read the data from the Google Sheets? - -There are three different formats to read the data from the Google Sheets. - -- **Unformatted Value:** In this mode, the node calculates the values, but doesn't format them. For example, if cell A1 is 1.23, and cell A2 is =A1, and the format of these cells is currency, then values returned will be of the format number. For cell A1 and A2, the values returned will be 1.23. -- **Formula:** In this mode, the node will return the formula. The node does not calculate the values. For example, if cell A1 is 1.23, and cell A2 is =A1, and the format of these cells is currency, then the value returned will be of the format number. The value returned for cell A2 will be =A1. -- **Formatted Value:** In this mode, the node calculates the values and returns the values with the cells' format. For example, if cell A1 is 1.23, and cell A2 is =A1, and the format of these cells is currency, then the values returned will be $1.23. - -To change the format, click on ***Add Option*** and select 'Value Render Mode' from the dropdown list. Select the appropriate option you want your output to be returned to from the ***Value Render Mode*** dropdown list. - -### How to enter values in the correct format? - -There are two different formats you can use to add/update data in Google Sheets. - -- **Raw:** This is the default format. In this format, the values are stored as-is and not parsed. For example, the node stores the text 2020-10-01 as a string in the Google Sheets. -- **User Entered:** In this format, the node parse the values. It follows the rules that are applied when entering text into the cell via the Google Sheet UI. For example, the node stores the text 2020-10-01 as a date in the Google Sheets. - -To change the format, click on ***Add Option*** and select 'Value Input Mode' from the dropdown list. Select the appropriate option you want your data to be stored in, from the ***Value Input Mode*** dropdown list. - -### How to append an array in the Google Sheets? - -To insert the data in Google Sheets, you have to first convert the data in a valid JSON (key, value) format. You can use the [Function node](/integrations/builtin/core-nodes/n8n-nodes-base.function/) to convert the array into JSON format. - -### How to return all the values with the Lookup operation? - -By default, the Lookup operation returns only the first value that it matches. To return all the values that match, click on ***Add Option*** and select 'Return All Matches'. Toggle ***Return All Matches*** to true. - -### How to specify a sheet? - -By default, the Google Sheets node will operate on the default sheet, `Sheet 1`. If you rename the sheet or want to use a different sheet, you have to specify the name of the sheet. You can do that in the ***Range*** field. For example, if you need to use a sheet named `n8n` for the range `A` to `H`, enter `n8n!A:H` in the ***Range*** field. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleSlides.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleSlides.md deleted file mode 100644 index 65013bcca..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleSlides.md +++ /dev/null @@ -1,73 +0,0 @@ -# Google Slides - -[Google Slides](https://www.google.com/slides) is a web-based presentation program that is part of Google's office software suite within its Google Drive service. It allows you to create, edit, and collaborate. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -* Page - * Get a page - * Get a thumbnail -* Presentation - * Create a presentation - * Get a presentation - * 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 deleted file mode 100644 index 69f0de9f8..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleTasks.md +++ /dev/null @@ -1,37 +0,0 @@ -# Google Tasks - -[Google Tasks](https://tasks.google.com) is a task management service developed by Google. It keeps track of your daily tasks, organize multiple lists, and track important deadlines. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -* Task - * Add a task to tasklist - * Delete a task - * Retrieve a task - * Retrieve all tasks from a tasklist - * Update a task - -## Example Usage - -This workflow allows you to add a task to Google Tasks. You can also find the [workflow](https://n8n.io/workflows/428) on the website. This example usage workflow uses the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Google Tasks]() - -The final workflow should look like the following image. - -![A workflow with the Google Tasks node](/_images/integrations/builtin/app-nodes/googletasks/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Google Tasks node - -1. First of all, you'll have to enter credentials for the Google Tasks node. You can find out how to do that [here](/integrations/builtin/credentials/google/). -2. Select the *TaskList* from the dropdown list of the user's task-lists where a new task needs to be added. -3. Enter a title for the task in the *Title* field. -4. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleTranslate.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleTranslate.md deleted file mode 100644 index e57a724f9..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.googleTranslate.md +++ /dev/null @@ -1,40 +0,0 @@ -# Google Translate - -[Google Translate](https://translate.google.com/) is a free multilingual translation service developed by Google to translate text and websites from one language into another. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -* Language - * Translate data - -## Example Usage - -This workflow allows you to translate text from English to German using the Google Translate node. You can also find the [workflow](https://n8n.io/workflows/743) on the website. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Google Translate]() - -The final workflow should look like the following image. - -![A workflow with the Google Translate node](/_images/integrations/builtin/app-nodes/googletranslate/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Google Translate node (translate:language) - -This node will translate the text `Hello from n8n!` to German. You can enter a different text as well as select another language to translate the text to. - -1. Select 'OAuth2' from the ***Authentication*** dropdown list. -2. Next, you'll have to enter credentials for the Google Translate node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/google/). -3. Enter the text `Hello from n8n!` in the ***Text*** field. -4. Select 'DE' from the ***Translate To*** dropdown list. DE is the language code for German. You can refer to [Language Support](https://cloud.google.com/translate/docs/languages) to view the list of all supported languages and their corresponding language codes. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node translates the text `Hello from n8n!` to German. - -![Using the Google Translate node to translate text in German](/_images/integrations/builtin/app-nodes/googletranslate/googletranslate_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.gotify.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.gotify.md deleted file mode 100644 index 1fce4946f..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.gotify.md +++ /dev/null @@ -1,70 +0,0 @@ -# Gotify - -[Gotify](https://gotify.net/) is a server for sending and receiving messages. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/gotify/). - - -## Basic Operations - -* Message - * Create - * Delete - * Get All - -## Example Usage - -This workflow allows you to send daily weather updates via a message using the Gotify node. You can also find the [workflow](https://n8n.io/workflows/774) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/) -- [Gotify]() - -The final workflow should look like the following image. - -![A workflow with the Gotify node](/_images/integrations/builtin/app-nodes/gotify/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow daily at 9 AM. - -1. Click on ***Add Cron Time***. -2. Set hours to 9 in the ***Hour*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every day at 9 AM. - -![Using the Cron node to trigger the workflow daily at 9 am](/_images/integrations/builtin/app-nodes/gotify/cron_node.png) - -### 2. OpenWeatherMap node (Current Weather) - -This node will return data about the current weather in Berlin. To get the weather updates for your city, you can enter the name of your city instead. - -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. Enter `berlin` in the ***City*** field. -3. 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/gotify/openweathermap_node.png) - -### 3. Gotify node (create: message) - -This node will send a message with the weather update. - -1. First of all, you'll have to enter credentials for the Gotify node. You can find out how to do that [here](/integrations/builtin/credentials/gotify/). -2. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. - -3. Enter the following message in the ***Expression*** field: `Hey! The temperature outside is {{$node["OpenWeatherMap"].json["main"]["temp"]}}°C.`. -4. Click on ***Add Field*** and select 'Title' from the dropdown list. -5. Enter `Today's Weather Update` in the ***Title*** field. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends a message with the weather update. - -![Using the Gotify node to send weather updates via a message](/_images/integrations/builtin/app-nodes/gotify/gotify_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.grafana.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.grafana.md deleted file mode 100644 index 6110abb97..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.grafana.md +++ /dev/null @@ -1,30 +0,0 @@ -# Grafana - -[Grafana](https://grafana.com/) is a multi-platform open source analytics and interactive visualization web application. It provides charts, graphs, and alerts for the web when connected to supported data sources. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/grafana/). - - -## Basic Operations - -* Dashboard - * Create a dashboard - * Delete a dashboard - * Get a dashboard - * Get all dashboards - * Update a dashboard -* Team - * Create a team - * Delete a team - * Get a team - * Retrieve all teams - * Update a team -* Team Member - * Add a member to a team - * Retrieve all team members - * Remove a member from a team -* User - * Delete a user from the current organization - * Retrieve all users in the current organization - * Update a user in the current organization diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.grist.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.grist.md deleted file mode 100644 index f56b37399..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.grist.md +++ /dev/null @@ -1,118 +0,0 @@ -# Grist - -[Grist](https://getgrist.com/) combines the flexibility of a spreadsheet with the robustness of a database to organize your data, your way. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/grist/). - - -## Basic operations - -* Create rows in a table -* Delete rows from a table -* Read rows from a table -* Update rows in a table - -## Example usage - -This workflow allows you to insert and update data from a table in Grist. You can also find the [workflow](https://n8n.io/workflows/818) on n8n.io. This example usage workflow uses the following nodes: - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Grist]() - -The final workflow should look like the following: - -![A workflow with the Grist node](/_images/integrations/builtin/app-nodes/grist/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Grist node (Create) - -This workflow assumes there is a document with a table in your Grist workspace. - -![Table in an example Grist document](/_images/integrations/builtin/app-nodes/grist/table_start.png) - -This node will create a new record in a table. - -1. First enter your credentials for the Grist node. You can find out how to do that [here](/integrations/builtin/credentials/grist/). -2. Select 'Create' from the ***Operation*** dropdown list. -3. Enter that ID of your document into the ***Document ID*** field. -4. Enter the ID of your table in the ***Table ID*** field. -5. Under ***Fields to Send*** click the **Add Field** button twice. -6. For the first field, choose **Name** from the ***Field ID*** dropdown, and type a name in the ***Field Value***. -7. For the second field, choose `Link` from the ***Field ID*** dropdown, and enter a URL in the ***Field Value***. -8. Click on **Execute Node** to run the node. - -Here is an example of how the configuration should look: - -![Using the Grist node to insert data into an Grist table](/_images/integrations/builtin/app-nodes/grist/grist_node.png) - -And here's the result of adding the record to the Grist table: - -![The example table after creating a new record with the Grist node](/_images/integrations/builtin/app-nodes/grist/table_create.png) - -### 3. Grist1 node (Get All) - -This node will list all the records with a particular `Name` value. - -1. Select the credentials that you entered in the previous node. -2. Select the 'Get All' option from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Document ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: **Nodes** > **Grist** > **Parameters** > **docId**. -5. Click on the gears icon next to the ***Table*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: **Nodes** > **Grist** > **Parameters** > **tableId**. -7. Click on ***Add Option*** and select 'Filter' from the dropdown list. -8. Click the ***Add Filter*** button. -9. Select `Name` from the **Column** dropdown. -10. Type a name in the ***Values*** field. -11. Click on ***Execute Node*** to run the node. - -In the screenshot below, the node only returned the record with the name 'Grist': - -![Using the Grist node to read data from an Grist table](/_images/integrations/builtin/app-nodes/grist/grist1_node.png) - -### 4. Grist2 node (Update) - -This node will update the Name field of the record that we received from the previous Grist node. - -1. Select the ***Grist1*** node in your workflow and click 'Duplicate Node'. Now you won't need to specify the credentials, Document ID, and Table ID again. -2. Double click the newly duplicated node (Grist2) to edit it. -3. Select 'Update' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Row ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: **Nodes** > **Grist1** > **Output Data** > **JSON** > **id**. -6. Under ***Fields to Send*** click the ***Add Field*** button. -7. Choose `Name` from the ***Field ID*** dropdown, and type a name in the ***Field Value***. -8. Click on ***Execute Node*** to run the node. - -Here is an example of how the configuration should look: - -![Using the Grist node to update data of a record](/_images/integrations/builtin/app-nodes/grist/grist2_node.png) - -The result is that the Name in the first record changed from 'Grist' to 'Grist Labs': - -![The example table after updating a record with the Grist node](/_images/integrations/builtin/app-nodes/grist/table_update.png) - -## FAQs - -### How to get the Row ID? - -To update or delete a particular record, you need the Row ID. There are two ways to get the Row ID. - -**Create a Row ID column in Grist** - -Create a new column in your Grist table with the formula `$id`. - -**Use the Get All operation** - -The ***Get All*** operation returns the Row ID of each record along with the fields. - -You can obtain it with the expression `{{$node["GristNodeName"].json["id"]}}`. - - -### How to filter records when using the Get All operation? - -- Click on ***Add Option*** and select 'Filter' from the dropdown list. -- You can add filters for any number of columns. The result will only include records which match all the columns. -- For each column, you can enter any number of values separated by commas. The result will include records which match any of the values for that column. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.hackerNews.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.hackerNews.md deleted file mode 100644 index 94ba9e811..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.hackerNews.md +++ /dev/null @@ -1,39 +0,0 @@ -# Hacker News - -[Hacker News](https://news.ycombinator.com/) is a social news website focusing on computer science and entrepreneurship. - -!!! note "Credentials" - The Hacker News node does not require authentication. - - -## Basic Operations - -* All - * Get all items -* Article - * Get a Hacker News article -* User - * Get a Hacker News user - -## Example Usage - -This workflow allows you to get articles from Hacker News. You can also find the [workflow](https://n8n.io/workflows/525) on this website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Hacker News]() - -The final workflow should look like the following image. - -![A workflow with the Hacker News node](/_images/integrations/builtin/app-nodes/hackernews/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Hacker News node - -1. Select the 'All' option from the *Resource* dropdown list. -2. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.haloPSA.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.haloPSA.md deleted file mode 100644 index fdbb15ccf..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.haloPSA.md +++ /dev/null @@ -1,60 +0,0 @@ -# HaloPSA - -[HaloPSA](https://halopsa.com/) is a intuitive PSA software. Standardise your processes and keep your customers at the center of every conversation. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/haloPSA/). - - -## Basic Operations - -* Client - * Create a client - * Delete a client - * Get a client - * Get all clients - * Update a client -* Site - * Create a site - * Delete a site - * Get a site - * Get all sites - * Update a site -* Ticket - * Create a ticket - * Delete a ticket - * Get a ticket - * Get all tickets - * Update a ticket -* User - * Create a user - * Delete a user - * Get a user - * 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.harvest.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.harvest.md deleted file mode 100644 index 6250ca07c..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.harvest.md +++ /dev/null @@ -1,93 +0,0 @@ -# Harvest - -[Harvest](https://www.getharvest.com/) is a web-based time tracking tool that helps with its simple time tracking, fast online invoicing, and powerful reporting software. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/harvest/). - - -## Basic Operations - -* Client - * Create a client - * Delete a client - * Get data of a client - * Get data of all clients - * Update a client -* Company - * Retrieves the company for the currently authenticated user -* Contact - * Create a contact - * Delete a contact - * Get data of a contact - * Get data of all contacts - * Update a contact -* Estimate - * Create an estimate - * Delete an estimate - * Get data of an estimate - * Get data of all estimates - * Update an estimate -* Expense - * Get data of an expense - * Get data of all expenses - * Create an expense - * Update an expense - * Delete an expense -* Invoice - * Get data of an invoice - * Get data of all invoices - * Create an invoice - * Update an invoice - * Delete an invoice -* Project - * Create a project - * Delete a project - * Get data of a project - * Get data of all projects - * Update a project -* Task - * Create a task - * Delete a task - * Get data of a task - * Get data of all tasks - * Update a task -* Time Entries - * Create a time entry via duration - * Create a time entry via start and end time - * Delete a time entry - * Delete a time entry's external reference. - * Get data of a time entry - * Get data of all time entries - * Restart a time entry - * Stop a time entry - * Update a time entry -* User - * Create a user - * Delete a user - * Get data of a user - * Get data of all users - * Get data of authenticated user - * Update a user - -## Example Usage - -This workflow allows you to create a client in Harvest. You can also find the [workflow](https://n8n.io/workflows/494) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Harvest]() - -The final workflow should look like the following image. - -![A workflow with the Harvest node](/_images/integrations/builtin/app-nodes/harvest/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Harvest node - -1. First of all, you'll have to enter credentials for the Harvest node. You can find out how to do that [here](/integrations/builtin/credentials/harvest/). -2. Select the 'Client' option from the *Resource* dropdown list. -3. Select the 'Create' option from the *Operation* dropdown list. -4. Enter the name of the client in the *Name* field. -5. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.helpScout.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.helpScout.md deleted file mode 100644 index b53523e3d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.helpScout.md +++ /dev/null @@ -1,48 +0,0 @@ -# Help Scout - -[Help Scout](https://www.helpscout.com/) is a help desk software that provides an email-based customer support platform, knowledge base tool, and an embeddable search/contact widget for customer service professionals. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/helpScout/). - - -## Basic Operations - -* Conversation - * Create a new conversation - * Delete a conversation - * Get a conversation - * Get all conversations -* Customer - * Create a new customer - * Get a customer - * Get all customers - * Get customer property definitions - * Update a customer -* Mailbox - * Get data of a mailbox - * Get all mailboxes -* Thread - * Create a new chat thread - * Get all chat threads - -## Example Usage - -This workflow allows you to get all mailboxes from Help Scout. You can also find the [workflow](https://n8n.io/workflows/567) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Help Scout]() - -The final workflow should look like the following image. - -![A workflow with the Help Scout node](/_images/integrations/builtin/app-nodes/helpscout/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Help Scout node - -1. First of all, you'll have to enter credentials for the Help Scout node. You can find out how to do that [here](/integrations/builtin/credentials/helpScout/). -2. Select the 'Mailbox' option from the *Resource* dropdown list. -3. Select the 'Get All' option from the *Operation* dropdown list. -4. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.highLevel.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.highLevel.md deleted file mode 100644 index 58624a42d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.highLevel.md +++ /dev/null @@ -1,34 +0,0 @@ -# HighLevel - -[HighLevel](https://www.gohighlevel.com/){:target=_blank .external-link} is an all-in-one sales and marketing platform. - -## Related resources - -### Credentials - -You can find authentication information for this node [here](/integrations/builtin/credentials/highLevel/). - -### HighLevel documentation and support - -HighLevel has [API documentation and support forums](https://help.gohighlevel.com/support/solutions/articles/48001060529-highlevel-api){:target=_blank .external-link}. - -## Operations - -* Contact - * Create or Update - * Delete - * Get - * Get All - * Lookup - * Update -* Opportunity - * Create - * Delete - * Get - * Get All - * Update -* Task - * Create - * Get - * Get All - * Update diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.homeAssistant.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.homeAssistant.md deleted file mode 100644 index 76edfbb1c..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.homeAssistant.md +++ /dev/null @@ -1,53 +0,0 @@ -# Home Assistant - -[Home Assistant](https://www.home-assistant.io/) is a free and open-source software for home automation that is designed to be the central control system for smart home devices with focus on local control and privacy. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/homeAssistant/). - - -## Basic operations - -* Camera Proxy - * Get the camera screenshot -* Config - * Get the configuration - * Check the configuration -* Event - * Create an event - * Get all events -* Log - * Get a log for a specific entity - * Get all logs -* Service - * Call a service within a specific domain - * Get all services -* State - * Create a new record, or update the current one if it already exists (upsert) - * Get a state for a specific entity - * Get all states -* Template - * Create a template - -## Example - -This workflow allows you to retrieve your current Home Assistant configuration details. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Home Assistant]() - -The final workflow should look like the following image. - -![A workflow with the Home Assistant node](/_images/integrations/builtin/app-nodes/homeassistant/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Home Assistant node - -1. First select your credentials for the Home Assistant node. You can find out how to create credentials [here](/integrations/builtin/credentials/homeAssistant/). -2. From the **Resource** dropdown select **Config**. -3. From the **Operation** dropdown select **Get**. -4. Click on **Execute Node** to run the workflow. - -![The Home Assistant node](/_images/integrations/builtin/app-nodes/homeassistant/home_assistant_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.hubspot.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.hubspot.md deleted file mode 100644 index 75a27aab6..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.hubspot.md +++ /dev/null @@ -1,78 +0,0 @@ -# HubSpot - -[HubSpot](https://www.hubspot.com/) provides tools for social media marketing, content management, web analytics, landing pages, customer support, and search engine optimization. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/hubspot/). - - -## Basic Operations - -* Contact - * Create/Update a contact - * Delete a contact - * Get a contact - * Get all contacts - * Get recently created/updated contacts - * Search contacts -* Contact List - * Add contact to a list - * Remove a contact from a list -* Company - * Create a company - * Delete a company - * Get a company - * Get all companies - * Get recently created companies - * Get recently modified companies - * Search companies by domain - * Update a company -* Deal - * Create a deal - * Delete a deal - * Get a deal - * Get all deals - * Get recently created deals - * Get recently modified deals - * Search deals - * Update a deal -* Engagement - * Create an engagement - * Delete an engagement - * Get an engagement - * Get all engagements -* Form - * Get all fields from a form - * Submit data to a form -* Ticket - * Create a ticket - * Delete a ticket - * Get a ticket - * Get all tickets - * Update a ticket - -## Example Usage - -This workflow allows you to retrieve a contact from HubSpot. You can also find the [workflow](https://n8n.io/workflows/466) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [HubSpot]() - -The final workflow should look like the following image. - -![A workflow with the HubSpot node](/_images/integrations/builtin/app-nodes/hubspot/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. HubSpot node - -1. First of all, you'll have to enter credentials for the HubSpot node. You can find out how to do that [here](/integrations/builtin/credentials/hubspot/). -2. Select the 'Contact' option under the *Resource* field. -3. Select the 'Get' option under the *Operation* field. -4. Enter the contact ID under the *Contact ID* field. -3. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.humanticAi.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.humanticAi.md deleted file mode 100644 index 2be483ae6..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.humanticAi.md +++ /dev/null @@ -1,85 +0,0 @@ -# Humantic AI - -[Humantic AI](https://humantic.ai/) provides AI-driven behavior and personality assessment of a candidate. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/humanticAi/). - - -## Basic Operations - -* Profile - * Create a profile - * Retrieve a profile - * Update a profile - -## Example Usage - -This workflow allows you to create, update, and get a profile using the Humantic AI node. You can also find the [workflow](https://n8n.io/workflows/784) 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/) -- [Humantic AI]() - -The final workflow should look like the following image. - -![A workflow with the Humantic AI node](/_images/integrations/builtin/app-nodes/humanticai/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Humantic AI node (create: profile) - -This node will create a new profile for a candidate in Humantic AI. We will create a new profile using the LinkedIn URL of a candidate. - -1. First of all, you'll have to enter credentials for the Humantic AI node. You can find out how to do that [here](/integrations/builtin/credentials/humanticAi/). -2. Enter the LinkedIn URL of the candidate in the ***User ID*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new profile using the LinkedIn URL of the candidate. - -![Using the Humantic AI node to create a new profile](/_images/integrations/builtin/app-nodes/humanticai/humanticai_node.png) - -### 3. HTTP Request node (GET) - -This node will fetch the resume of the candidate from a URL that we specify. We will pass on this resume to the next node in the workflow. - -1. Enter the URL of the candidate's resume in the ***URL*** field. -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 node fetches the resume of the candidate from the URL we specified. - -![Using the HTTP Request node to fetch a resume](/_images/integrations/builtin/app-nodes/humanticai/httprequest_node.png) - -### 4. Humantic AI1 node (update: profile) - -This node will update the information of the candidate that we created using the Humantic AI node. We will add the candidate's resume that we fetched in the previous node. - - -1. Select the credentials that you entered in the previous Humantic AI node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***User ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Humantic AI > Output Data > JSON > results > userid. You can also add the following expression: `{{$node["Humantic AI"].json["results"]["userid"]}}`. -5. Toggle ***Send Resume*** to `true`. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node updates the information of the candidate that we created using the Humantic AI node. Here, the node has added the resume of the candidate. - -![Using the Humantic AI node to add resume to the candidate's profile](/_images/integrations/builtin/app-nodes/humanticai/humanticai1_node.png) - -### 5. Humantic AI2 node (get: profile) - -This node will return the `Hiring` persona for the candidate that we created using the Humantic AI node. - -1. Select the credentials that you entered in the previous node. -2. Click on the gears icon next to the ***User ID*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Nodes > Humantic AI > Output Data > JSON > results > userid. You can also add the following expression: `{{$node["Humantic AI"].json["results"]["userid"]}}`. -4. Click on the ***Add Option*** button. -5. Select 'Hiring' from the ***Persona*** dropdown list. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the `Hiring` persona for the candidate that we created using the Humantic AI node (column headers are not visible in the screenshot since we've scrolled down to show the data). - -![Using the Humantic AI node to get the information of the candidate](/_images/integrations/builtin/app-nodes/humanticai/humanticai2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.hunter.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.hunter.md deleted file mode 100644 index d77307736..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.hunter.md +++ /dev/null @@ -1,35 +0,0 @@ -# Hunter - -[Hunter](https://hunter.io/) is a company that produces a platform that helps find and verify professional email addresses. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/hunter/). - - -## Basic Operations - -* Get every email address found on the internet using a given domain name, with sources -* Generate or retrieve the most likely email address from a domain name, a first name and a last name -* Verify the deliverability of an email address - - -## Example Usage - -This workflow allows you to verify the deliverability of an email address using Hunter. You can also find the [workflow](https://n8n.io/workflows/519) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Hunter]() - -The final workflow should look like the following image. - -![A workflow with the Hunter node](/_images/integrations/builtin/app-nodes/hunter/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Hunter node - -1. First of all, you'll have to enter credentials for the Hunter node. You can find out how to do that [here](/integrations/builtin/credentials/hunter/). -2. Select 'Email Verifier' from the *Operation* dropdown list. -3. Enter the email in the *Email* field. -4. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.intercom.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.intercom.md deleted file mode 100644 index ccc5568fc..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.intercom.md +++ /dev/null @@ -1,49 +0,0 @@ -# Intercom - -[Intercom](https://www.intercom.com/) is a company that produces a messaging platform which allows businesses to communicate with prospective and existing customers within their app, on their website, through social media, or via email. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/intercom/). - - -## Basic Operations - -* Company - * Create a new company - * Get data of a company - * Get data of all companies - * Update a company - * List company's users -* Lead - * Create a new lead - * Delete a lead - * Get data of a lead - * Get data of all leads - * Update new lead -* User - * Create a new user - * Delete a user - * Get data of a user - * Get data of all users - * Update a user - -## Example Usage - -This workflow allows you to create a new user in Intercom. You can also find the [workflow](https://n8n.io/workflows/464) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Intercom]() - -The final workflow should look like the following image. - -![A workflow with the Intercom node](/_images/integrations/builtin/app-nodes/intercom/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Intercom node - -1. First of all, you'll have to enter credentials for the Intercom node. You can find out how to do that [here](/integrations/builtin/credentials/intercom/). -2. Select 'Email' from the dropdown list for the *Identifier Type* field. -3. Enter the email in the *Value* field. -4. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.invoiceNinja.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.invoiceNinja.md deleted file mode 100644 index ac6bba150..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.invoiceNinja.md +++ /dev/null @@ -1,63 +0,0 @@ -# Invoice Ninja - -[Invoice Ninja](https://www.invoiceninja.com/) is a free open-source online invoicing app for freelancers & businesses. It offers invoicing, payments, expense tracking, & time-tasks. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/invoiceNinja/). - - -## Basic Operations - -* Client - * Create a new client - * Delete a client - * Get data of a client - * Get data of all clients -* Expense - * Create a new expense - * Delete an expense - * Get data of an expense - * Get data of all expenses -* Invoice - * Create a new invoice - * Delete a invoice - * Email an invoice - * Get data of a invoice - * Get data of all invoices -* Payment - * Create a new payment - * Delete a payment - * Get data of a payment - * Get data of all payments -* Quote - * Create a new quote - * Delete a quote - * Email an quote - * Get data of a quote - * Get data of all quotes -* Task - * Create a new task - * Delete a task - * Get data of a task - * Get data of all tasks - -## Example Usage - -This workflow allows you to get multiple clients' data from Invoice Ninja. You can also find the [workflow](https://n8n.io/workflows/534) on this website. This example usage workflow uses the following two nodes. - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Invoice Ninja]() - -The final workflow should look like the following image. - -![A workflow with the Invoice Ninja node](/_images/integrations/builtin/app-nodes/invoiceninja/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Invoice Ninja node - -1. First of all, you'll have to enter credentials for the Invoice Ninja node. You can find out how to do that [here](/integrations/builtin/credentials/invoiceNinja/). -2. Select the 'Get All' option from the *Operation* dropdown list. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.iterable.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.iterable.md deleted file mode 100644 index d494e002e..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.iterable.md +++ /dev/null @@ -1,83 +0,0 @@ -# Iterable - -[Iterable](https://iterable.com/) is a cross-channel platform that allows marketers to create, optimize, and measure every interaction throughout the customer journey. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/iterable/). - - -## Basic Operations - -* Event - * Record the actions a user perform -* User - * Create/Update a user - * Delete a user - * Get a user -* User List - * 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 deleted file mode 100644 index bc02ca357..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.jenkins.md +++ /dev/null @@ -1,46 +0,0 @@ -# Jenkins - -[Jenkins](https://www.jenkins.io/) is an open source automation server that provides hundreds of plugins to support building, deploying and automating any project. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/jenkins/). - - -## Basic Operations - -* Build - * List Builds -* Instance - * Cancel quiet down state - * Put Jenkins in quiet mode, no builds can be started, Jenkins is ready for shutdown - * Restart Jenkins immediately on environments where it is possible - * Restart Jenkins once no jobs are running on environments where it is possible - * Shutdown once no jobs are running - * Shutdown Jenkins immediately -* Job - * Copy a specific job - * Create a new job - * 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* is not 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.jira.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.jira.md deleted file mode 100644 index 1886fef03..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.jira.md +++ /dev/null @@ -1,76 +0,0 @@ -# Jira - -[Jira](https://www.atlassian.com/software/jira) is a proprietary issue tracking product developed by Atlassian that allows bug tracking and agile project management. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/jira/). - - -## Basic Operations - -* Issue - * Get issue changelog - * Create a new issue - * Delete an issue - * Get an issue - * Get all issues - * Create an email notification for an issue and add it to the mail queue - * Return either all transitions or a transition that can be performed by the user on an issue, based on the issue's status - * Update an issue -* Issue Attachment - * Add attachment to issue - * Get an attachment - * Get all attachments - * Remove an attachment -* Issue Comment - * Add comment to issue - * Get a comment - * Get all comments - * Remove a comment - * Update a comment -* User - * Create a new user. - * Delete a user. - * Retrieve a user. - -## Example Usage - -This workflow allows you to create a new issue in Jira. You can also find the [workflow](https://n8n.io/workflows/459) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Jira]() - -The final workflow should look like the following image. - -![A workflow with the Jira node](/_images/integrations/builtin/app-nodes/jira/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Jira node - -1. First of all, you'll have to enter credentials for the Jira node. You can find out how to do that [here](/integrations/builtin/credentials/jira/). -2. Select your project from the dropdown list for the *Project* field. -3. Select an issue type from the dropdown list for the *Issue Type* field. -4. Enter the summary of the issue in the *Summary* field. -5. Click on *Execute Node* to run the workflow. - -## FAQs - -### How to fetch issues for a specific project? - -The 'Get All' operation returns all the issues from Jira. To fetch issues for a particular project, you need to use JQL (Jira Query Language). - -For example, if you want to receive all the issues of a project named `n8n`, follow the steps mentioned below. -- Select 'Get All' from the ***Operation*** dropdown list. -- Toggle ***Return All*** to true. -- Click on ***Add Option*** and select 'JQL'. -- Enter `project=n8n` in the ***JQL*** field. - -This query will fetch all the issues in the project named `n8n`. Enter the name of your project instead of `n8n` to fetch all the issues for your project. - -You can refer to the [official documentation](https://www.atlassian.com/software/jira/guides/expand-jira/jql) about JQL to learn more about it. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.kafka.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.kafka.md deleted file mode 100644 index fc5137702..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.kafka.md +++ /dev/null @@ -1,93 +0,0 @@ -# Kafka - -[Kafka](https://kafka.apache.org/) is an open-source distributed event streaming platform that one can use for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/kafka/). - - -## Basic Operations - -- Send message - -## Example Usage - -This workflow allows you to send updates about the position of the ISS every minute to a topic in Kafka using the Kafka node. You can also find the [workflow](https://n8n.io/workflows/750) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Kafka]() - -The final workflow should look like the following image. - -![A workflow with the Kafka node](/_images/integrations/builtin/app-nodes/kafka/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow every minute. - -1. Click on ***Add Cron Time***. -2. Select 'Every Minute' from the ***Mode*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every minute. - -![Using the Cron node to trigger the workflow every minute](/_images/integrations/builtin/app-nodes/kafka/cron_node.png) - -### 2. HTTP Request node (GET) - -This node will make a GET request to the API `https://api.wheretheiss.at/v1/satellites/25544/positions` to fetch the position of the ISS. This information gets passed on to the next node in the workflow. - -1. Enter `https://api.wheretheiss.at/v1/satellites/25544/positions` in the ***URL*** field. -2. Click on the ***Add Parameter*** button in the ***Query Parameters*** section. -3. Enter `timestamps` in the ***Name*** field. -4. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -5. Enter the following expression: `{{Date.now()}}`. This expression will return the current timestamp. -6. 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 the information about the location of the ISS. - -![Using the HTTP Request node to get the information about the location of the ISS](/_images/integrations/builtin/app-nodes/kafka/httprequest_node.png) - -### 3. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `Name` in the ***Name*** 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 > HTTP Request > Output Data > JSON > 0 > name. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["name"]}}`. -5. Click on ***Add Value*** and select 'String' from the dropdown list. -6. Enter `Latitude` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > 0 > latitude. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["latitude"]}}`. -9. Click on ***Add Value*** and select 'String' from the dropdown list. -10. Enter `Longitude` in the ***Name*** field. -11. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > 0 > longitude. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["longitude"]}}`. -13. Click on ***Add Value*** and select 'String' from the dropdown list. -14. Enter `Timestamp` in the ***Name*** field. -15. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -16. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > 0 > timpestamp. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["timestamp"]}}`. -17. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -18. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uses the data from the previous node and returns the data that we set for the workflow. - -![Using the Set node to set the data](/_images/integrations/builtin/app-nodes/kafka/set_node.png) - -### 4. Kafka node - -This node will send the data from the previous node to the `iss-position` topic in Kafka. If you have created a topic with a different name in Kafka, you can use that topic name instead. - -1. First of all, you'll have to enter credentials for the Kafka node. You can find out how to do that [here](/integrations/builtin/credentials/kafka/). -2. Enter the name of the topic in the ***Topic*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends the data from the previous node to the `iss-position` topic in Kafka. - -![Using the Kafka node to send the data to a topic](/_images/integrations/builtin/app-nodes/kafka/kafka_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.keap.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.keap.md deleted file mode 100644 index 4daad3673..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.keap.md +++ /dev/null @@ -1,67 +0,0 @@ -# Keap - -[Keap](https://keap.com/) is an e-mail marketing and sales platform for small businesses, including products to manage and optimize the customer lifecycle, customer relationship management, marketing automation, lead capture, and e-commerce. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/keap/). - - -## Basic Operations - -* Company - * Create a company - * Retrieve all companies -* Contact - * Create/update a contact - * Delete an contact - * Retrieve an contact - * Retrieve all contacts -* Contact Note - * Create a note - * Delete a note - * Get a notes - * Retrieve all notes - * Update a note -* Contact Tag - * Add a list of tags to a contact - * Delete a contact's tag - * Retrieve all contact's tags -* Ecommerce Order - * Create an ecommerce order - * Get an ecommerce order - * Delete an ecommerce order - * Retrieve all ecommerce orders -* Ecommerce Product - * Create an ecommerce product - * Delete an ecommerce product - * Get an ecommerce product - * Retrieve all ecommerce product -* Email - * Create a record of an email sent to a contact - * Retrieve all sent emails - * Send Email -* File - * Delete a file - * Retrieve all files - * Upload a file - -## Example Usage - -This workflow allows you to get all contacts from Keap. You can also find the [workflow](https://n8n.io/workflows/553) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Keap]() - -The final workflow should look like the following image. - -![A workflow with the Keap node](/_images/integrations/builtin/app-nodes/keap/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Keap node - -1. First of all, you'll have to enter credentials for the Keap node. You can find out how to do that [here](/integrations/builtin/credentials/keap/). -2. Select the 'Contact' option from the *Resource* dropdown list. -3. Select the 'Get All' option from the *Operation* dropdown list. -4. 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 deleted file mode 100644 index 051b49a80..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.kitemaker.md +++ /dev/null @@ -1,81 +0,0 @@ -# Kitemaker - -[Kitemaker](https://www.kitemaker.co/) is a collaboration tool built for designers, engineers, and product managers in remote software development teams. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/kitemaker/). - - -## Basic Operations - -* Organization - * Retrieve data on the logged-in user's organization. -* Space - * Retrieve data on all the spaces in the logged-in user's organization. -* User - * Retrieve data on all the users in the logged-in user's organization. -* Work Item - * Create - * Get - * 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.koBoToolbox.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.koBoToolbox.md deleted file mode 100644 index 1cf257a6b..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.koBoToolbox.md +++ /dev/null @@ -1,164 +0,0 @@ -# KoBo Toolbox - -[KoBo toolbox](https://www.kobotoolbox.org/) is a field survey and data collection tool that makes it easy to design interactive forms to be completed offline from mobile devices. It is available both as a free cloud solution or as a self-hosted version. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/kobotoolbox/). - -## Operations - -* Form - * Get - * GetAll -* Hook - * Get - * GetAll - * Logs - * Retry All - * Retry One -* Submission - * Delete - * Get - * Get All - * Get Validation Status - * Update Validation Status - -## Options - -### Query Options - -The Query Submission operation supports query options: - -* In the main section of the **Parameters** panel: - * **Start** controls the index offset to start the query from (to use the API pagination logic). - * **Limit** sets the maximum number of records to return. Note that the API always has a limit of 30,000 returned records, whatver value you provide. -* In the **Query Options** section, you can activate the following parameters: - * **Query** lets you specify filter predicates in MongoDB's JSON query format. For example: `{"status": "success", "_submission_time": {"$lt": "2021-11-01T01:02:03"}}` queries for all submissions with the value `success` for the field `status`, and submitted before November 1st, 2021, 01:02:03. - * **Fields** lets you specifiy the list of fields you want to fetch, to make the response lighter. - * **Sort** lets you provide a list of sorting criteria in MongoDB JSON format. For example, `{"status": 1, "_submission_time": -1}` specifies a sort order by ascending status, and then descending submission time. - -More details about these options can be found in the [Formhub API docs](https://github.com/SEL-Columbia/formhub/wiki/Formhub-Access-Points-(API)#api-parameters) - -### Submission options - -All operations that return form submission data offer options to tweak the response. These include: - -- Download options lets you download any attachment linked to each particular form submissions, such as pictures and videos. It also lets you select the naming pattern, and the file size to download (if available - typically for images). -- Formatting options perform some reformatting as described in [About reformatting](#about-reformatting). - -#### About reformatting - -The default JSON format for KoBoToolbox submission data is sometimes hard to deal with, because it is not schema-aware, and all fields are therefore returned as strings. - -This node provides a lightweight opinionated reformatting logic, enabled with the **Reformat?** parameter, available on all operations that return form submissions: the submission query, get, and the attachment download operations. - -When enabled, the reformatting: - -- Reorganizes the JSON into a multi-level hierarchy following the form's groups. By default, question grouping hierarchy is materialized by a `/` character in the field names, for example `Group1/Question1`. With reformatting enabled, n8n reorganizes these into `Group1.Question1`, as nested JSON objects. -- Renames fields to trim `_` (not supported by many downstream systems). -- Parses all geospatial fields (Point, Line, and Area question types) into their standard GeoJSON equivalent. -- Splits all fields matching any of the the **Multiselect Mask** wildcard masks into an array. Since the multi-select fields appear as space-separated strings, they can't be guessed algorithmically, so you must provide a field naming mask. Format the masks as a comma-separated list. Lists support the `*` wildcard. -- Converts all fields matching any of the **Number Mask** wildcard masks into a JSON float. - -Here's a detailed example in JSON: - -```json -{ - "_id": 471987, - "formhub/uuid": "189436bb09a54957bfcc798e338b54d6", - "start": "2021-12-05T16:13:38.527+02:00", - "end": "2021-12-05T16:15:33.407+02:00", - "Field_Details/Field_Name": "Test Fields", - "Field_Details/Field_Location": "-1.932914 30.078211 1421 165", - "Field_Details/Field_Shape": "-1.932914 30.078211 1421 165;-1.933011 30.078085 0 0;-1.933257 30.078004 0 0;-1.933338 30.078197 0 0;-1.933107 30.078299 0 0;-1.932914 30.078211 1421 165", - "Field_Details/Crops_Grown": "maize beans avocado", - "Field_Details/Field_Size_sqm": "2300", - "__version__": "veGcULpqP6JNFKRJbbMvMs", - "meta/instanceID": "uuid:2356cbbe-c1fd-414d-85c8-84f33e92618a", - "_xform_id_string": "ajXVJpBkTD5tB4Nu9QXpgm", - "_uuid": "2356cbbe-c1fd-414d-85c8-84f33e92618a", - "_attachments": [], - "_status": "submitted_via_web", - "_geolocation": [ - -1.932914, - 30.078211 - ], - "_submission_time": "2021-12-05T14:15:44", - "_tags": [], - "_notes": [], - "_validation_status": {}, - "_submitted_by": null -} -``` - -With reformatting enabled, and the appropriate masks for multi-select and number formatting (for example, `Crops_*` and `*_sqm` respecitvely), n8n parses it into: - -```json -{ - "id": 471987, - "formhub": { - "uuid": "189436bb09a54957bfcc798e338b54d6" - }, - "start": "2021-12-05T16:13:38.527+02:00", - "end": "2021-12-05T16:15:33.407+02:00", - "Field_Details": { - "Field_Name": "Test Fields", - "Field_Location": { - "lat": -1.932914, - "lon": 30.078211 - }, - "Field_Shape": { - "type": "polygon", - "coordinates": [ - { - "lat": -1.932914, - "lon": 30.078211 - }, - { - "lat": -1.933011, - "lon": 30.078085 - }, - { - "lat": -1.933257, - "lon": 30.078004 - }, - { - "lat": -1.933338, - "lon": 30.078197 - }, - { - "lat": -1.933107, - "lon": 30.078299 - }, - { - "lat": -1.932914, - "lon": 30.078211 - } - ] - }, - "Crops_Grown": [ - "maize", - "beans", - "avocado" - ], - "Field_Size_sqm": 2300 - }, - "version": "veGcULpqP6JNFKRJbbMvMs", - "meta": { - "instanceID": "uuid:2356cbbe-c1fd-414d-85c8-84f33e92618a" - }, - "xform_id_string": "ajXVJpBkTD5tB4Nu9QXpgm", - "uuid": "2356cbbe-c1fd-414d-85c8-84f33e92618a", - "attachments": [], - "status": "submitted_via_web", - "geolocation": { - "lat": -1.932914, - "lon": 30.078211 - }, - "submission_time": "2021-12-05T14:15:44", - "tags": [], - "notes": [], - "validation_status": {}, - "submitted_by": null -} -``` \ No newline at end of file diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.lemlist.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.lemlist.md deleted file mode 100644 index 52390e7b7..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.lemlist.md +++ /dev/null @@ -1,89 +0,0 @@ -# Lemlist - -[Lemlist](https://Lemlist.com) is an email outreach platform that allows you to automatically generate personalized images and videos and send personalized cold emails. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/lemlist/). - - -## Basic Operations - -* Activity - * Get All -* Campaign - * Get All -* Lead - * Create - * Delete - * Get - * Unsubscribe -* Team - * Get -* Unsubscribes - * Add - * 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.line.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.line.md deleted file mode 100644 index d6da13d3b..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.line.md +++ /dev/null @@ -1,66 +0,0 @@ -# Line - -[Line](https://line.me/en/) is a mobile messenger app that allows you to make free voice calls and send messages. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/line/). - - -## Basic Operations - -* Notification - * Sends notifications to users or groups - -## Example Usage - -This workflow allows you to send daily weather updates via a notification using the Line node. You can also find the [workflow](https://n8n.io/workflows/773) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/) -- [Line]() - -The final workflow should look like the following image. - -![A workflow with the Line node](/_images/integrations/builtin/app-nodes/line/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow daily at 9 AM. - -1. Click on ***Add Cron Time***. -2. Set hours to 9 in the ***Hour*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every day at 9 AM. - -![Using the Cron node to trigger the workflow daily at 9 am](/_images/integrations/builtin/app-nodes/line/cron_node.png) - -### 2. OpenWeatherMap node (Current Weather) - -This node will return data about the current weather in Berlin. To get the weather updates for your city, you can enter the name of your city instead. - -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. Enter `berlin` in the ***City*** field. -3. 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/line/openweathermap_node.png) - -### 3. Line node (send: notification) - -This node will send a notification with the weather update. - -1. First of all, you'll have to enter credentials for the Line node. You can find out how to do that [here](/integrations/builtin/credentials/line/). -2. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. - -3. Enter the following message in the ***Expression*** field: `Hey! The temperature outside is {{$node["OpenWeatherMap"].json["main"]["temp"]}}°C.`. -4. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends a notification with the weather update. - -![Using the Line node to send weather updates via a notification](/_images/integrations/builtin/app-nodes/line/line_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.linear.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.linear.md deleted file mode 100644 index 3ea942c7a..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.linear.md +++ /dev/null @@ -1,15 +0,0 @@ -# Linear - -[Linear](https://linear.app/) is a SaaS issue tracking tool. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/linear/). - -## Operations - -* Issue - * Create - * Delete - * Get - * Get All - * Update \ No newline at end of file diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.lingvaNex.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.lingvaNex.md deleted file mode 100644 index d308ae974..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.lingvaNex.md +++ /dev/null @@ -1,56 +0,0 @@ -# LingvaNex - -[LingvaNex](https://lingvanex.com) is a service that translates text, web pages, text on images, documents between English and over 112 other languages. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/lingvaNex/). - - -## Basic Operations - -- 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.linkedIn.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.linkedIn.md deleted file mode 100644 index 3eaa52f8b..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.linkedIn.md +++ /dev/null @@ -1,54 +0,0 @@ -# LinkedIn - -[LinkedIn](https://www.linkedin.com/) is an employment-oriented online service. It is mainly used for professional networking, including employers posting jobs and job seekers posting their CVs. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/linkedIn/). - - -## Basic Operations - -* Post - * Create a new post - -!!! note "Keep in mind" - If posting as an Organization enter only the organization number in the URN field. For example, `03262013` not `urn:li:company:03262013`. - - -## Example Usage - -This workflow allows you to get an image from a URL and post it on LinkedIn. You can also find the [workflow](https://n8n.io/workflows/681) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [LinkedIn]() - -The final workflow should look like the following image. - -![A workflow with the LinkedIn node](/_images/integrations/builtin/app-nodes/linkedin/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. HTTP Request node - -1. Enter the URL of the image you want to download in the ***URL*** field. -2. Select ***File*** from the ***Response Format*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -![Downloading an image with the HTTP Request node](/_images/integrations/builtin/app-nodes/linkedin/httprequest_node.png) - -### 3. LinkedIn node - -1. First of all, you'll have to enter credentials for the LinkedIn node. You can find out how to do that [here](/integrations/builtin/credentials/linkedIn/). -2. Select 'Person' from the ***Post As*** dropdown list. -3. Select the person you want to post as from the ***Person*** dropdown list. -4. Enter a message in the ***Text*** field. -5. Select 'Image' from the ***Media Category*** dropdown list. -6. Click on ***Execute Node*** to run the node. - -![Posting with the LinkedIn node](/_images/integrations/builtin/app-nodes/linkedin/linkedin_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 deleted file mode 100644 index f8108c045..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.magento2.md +++ /dev/null @@ -1,29 +0,0 @@ -# Magento 2 - -[Magento](https://www.magento.com/) is an e-commerce platform enabling retailers and brands to build engaging online shopping experiences. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/magento2/). - - -## Basic Operations - -* Customer - * Create a new customer - * Delete a customer - * Get a customer - * Get all customers - * Update a customer -* Invoice - * Create an invoice -* Order - * Cancel an order - * Get an order - * Get all orders - * Ship an order -* Product - * Create a product - * Delete a product - * Get a product - * Get all producs - * Update a product diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailcheck.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailcheck.md deleted file mode 100644 index a9c8da2cd..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailcheck.md +++ /dev/null @@ -1,96 +0,0 @@ -# Mailcheck - -[Mailcheck](https://www.mailcheck.co/) is an application that allows you to clean your subscription list from bounces and enrich data with customers. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mailcheck/). - - -## Basic Operations - -* Email - * Check - -## Example Usage - -This workflow allows you to validate emails stored in Airtable using the Mailcheck node. You can also find the [workflow](https://n8n.io/workflows/1055) 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/) -- [Mailcheck]() -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) - -The final workflow should look like the following image. - -![A workflow with the Mailcheck node](/_images/integrations/builtin/app-nodes/mailcheck/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Airtable node (List) - -Create a table like [this](https://airtable.com/shrDUFXWoHCuJjYjT) in your Airtable base. The Airtable node will list all the records from a table. - -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 ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns all the records from the table. - -![Using the Airtable node to list data from an Airtable table](/_images/integrations/builtin/app-nodes/mailcheck/airtable_node.png) - -### 2. Mailcheck node (check: email) - -This node will check the emails that got returned by the previous node. - -1. First of all, you'll have to enter credentials for the Mailcheck node. You can find out how to do that [here](/integrations/builtin/credentials/mailcheck/). - -2. Click on the gears icon next to the ***Email*** field and click on ***Add Expression***. -3. 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"]}}`. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node checks the email that got returned by the previous node. - -![Using the Mailcheck node to check email](/_images/integrations/builtin/app-nodes/mailcheck/mailcheck_node.png) - -### 3. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. - -1. Click on the ***Add Value*** button and select 'Boolean' from the dropdown list. -2. Enter `Valid` in the ***Name*** field. -3. Click on the gears icon next to the ***Value*** field. -4. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > mxExists. You can also add the following expression: `{{$json["mxExists"]}}`. -5. Click on the ***Add Value*** button and select 'String' from the dropdown list. -6. Enter `ID` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field. -8. Select the following in the ***Variable Selector*** section: Nodes > Airtable > Output Data > JSON > id. You can also add the following expression: `{{$node["Airtable"].json["id"]}}`. -9. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sets the value for `Valid` and `ID`. - -![Using the Set node to set data to be updated by the Airtable node](/_images/integrations/builtin/app-nodes/mailcheck/set_node.png) - -### 4. Airtable (Update) - -This node will update the Valid field in the table. - -1. Select the credentials that you entered in the previous Airtable node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Base ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Airtable > Parameters > application. You can also add the following expression: `{{$node["Airtable"].parameter["application"]}}`. -5. Click on the gears icon next to the ***Table*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Airtable > Parameters > table. You can also add the following expression: `{{$node["Airtable"].parameter["table"]}}`. -7. Click on the gears icon next to the ***Id*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > ID. You can also add the following expression: `{{$json["ID"]}}`. -9. Toggle ***Update All Fields*** to `false`. This option will update only the fields that we specify. -10. Click on the ***Add Field*** button. -11. Enter `Valid` in the ***Name*** field. -12. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node updates the Valid field in the table. - -![Using the Airtable node to update data of a record](/_images/integrations/builtin/app-nodes/mailcheck/airtable1_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailchimp.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailchimp.md deleted file mode 100644 index 6b88c99b7..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailchimp.md +++ /dev/null @@ -1,51 +0,0 @@ -# Mailchimp - -[Mailchimp](https://mailchimp.com/) is an integrated marketing platform that allows business owners to automate their email campaigns and track user engagement. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mailchimp/). - - -## Basic Operations - -* Campaign - * Delete a campaign - * Get a campaign - * Get all the campaigns - * Replicate a campaign - * Creates a Resend to Non-Openers version of this campaign - * Send a campaign -* List Group - * Get all groups -* Member - * Create a new member on list - * Delete a member on list - * Get a member on list - * Get all members on list - * Update a new member on list -* Member Tag - * Add tags from a list member - * Remove tags from a list member - -## Example Usage - -This workflow allows you to add a new member to a list in Mailchimp. You can also find the [workflow](https://n8n.io/workflows/413) on this website. This example usage workflow uses the following two nodes. - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Mailchimp]() - -The final workflow should look like the following image. - -![A workflow with the Mailchimp node](/_images/integrations/builtin/app-nodes/mailchimp/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Mailchimp node - -1. First of all, you'll have to enter credentials for the Mailchimp node. You can find out how to do that [here](/integrations/builtin/credentials/mailchimp/). -4. Select the Mailchimp list from the *List* dropdown list. -5. Enter the email address in the *Email* field. -6. Select the status from the *Status* dropdown list. -8. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailerLite.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailerLite.md deleted file mode 100644 index f5512bf62..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailerLite.md +++ /dev/null @@ -1,80 +0,0 @@ -# MailerLite - -[MailerLite](https://www.mailerlite.com/) is an email marketing solution that provides you with a user-friendly content editor, simplified subscriber management, and campaign reports with the most important statistics. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mailerLite/). - - -## Basic Operations - -* Subscriber - * Create a new subscriber - * Get an subscriber - * 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.mailgun.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailgun.md deleted file mode 100644 index a2c32e45b..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailgun.md +++ /dev/null @@ -1,35 +0,0 @@ -# Mailgun - -[Mailgun](https://www.mailgun.com/) is a developer-friendly email sending platform that provides API-based email services that are easy to use. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mailgun/). - - -## Basic Operations - -- Send an email - -## Example Usage - -This workflow allows you to send an email using Mailgun. You can also find the [workflow](https://n8n.io/workflows/522) on this website. This example usage workflow uses the following two nodes. - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Mailgun]() - -The final workflow should look like the following image. - -![A workflow with the Mailgun node](/_images/integrations/builtin/app-nodes/mailgun/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Mailgun node - -1. First of all, you'll have to enter credentials for the Mailgun node. You can find out how to do that [here](/integrations/builtin/credentials/mailgun/). -2. Enter the email address from which you want to send the email in the *From Email* field. -3. Enter the recipient email in the *To Email* field. -4. Enter the subject for the email in the *Subject* field. -5. Enter the content of the email in the *Text* field. -6. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailjet.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailjet.md deleted file mode 100644 index cbd1178cc..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mailjet.md +++ /dev/null @@ -1,39 +0,0 @@ -# Mailjet - -[Mailjet](https://www.mailjet.com/) is a cloud-based email sending and tracking system. The platform allows professionals to send both marketing emails and transactional emails. It includes tools for designing emails, sending massive volumes and tracking these messages. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mailjet/). - - -## Basic Operations - -* Email - * Send a email - * Send a email template -* SMS - * Send a sms - -## Example Usage - -This workflow allows you to send an email using Mailjet. You can also find the [workflow](https://n8n.io/workflows/520) on this website. This example usage workflow uses the following two nodes. - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Mailjet]() - -The final workflow should look like the following image. - -![A workflow with the Mailjet node](/_images/integrations/builtin/app-nodes/mailjet/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Mailjet node - -1. First of all, you'll have to enter credentials for the Mailjet node. You can find out how to do that [here](/integrations/builtin/credentials/mailjet/). -2. Enter the email address from which you want to send the email in the *From Email* field. -3. Enter the recipient email address in the *To Email* field. -4. Enter the subject for the email in the *Subject* field. -5. Enter the content of the email in the *Text* field. -6. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mandrill.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mandrill.md deleted file mode 100644 index b2d53872e..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mandrill.md +++ /dev/null @@ -1,40 +0,0 @@ -# Mandrill - -[Mandrill](https://mandrillapp.com/) is a transactional email service developed by MailChimp. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mandrill/). - - -## Basic Operations - -* Message - * Send message based on template. - * Send message based on HTML. - -## Example Usage - -This workflow allows you to send an email using a template via Mandrill. You can also find the [workflow](https://n8n.io/workflows/571) on this website. This example usage workflow uses the following two nodes. - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Mandrill]() - -The final workflow should look like the following image. - -![A workflow with the Mandrill node](/_images/integrations/builtin/app-nodes/mandrill/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Mandrill node - -1. First of all, you'll have to enter credentials for the Mandrill node. You can find out how to do that [here](/integrations/builtin/credentials/mandrill/). -2. Select the template you would like to use from the *Template* dropdown list. -3. Enter the email address from which you want to send the email in the *From Email* field. -4. Enter the recipient email address in the *To Email* field. -5. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.marketstack.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.marketstack.md deleted file mode 100644 index a29de29a8..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.marketstack.md +++ /dev/null @@ -1,43 +0,0 @@ -# Marketstack - -[Marketstack](https://marketstack.com/) is a REST API that provides stock market data in JSON format. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/marketstack/). - - -## Basic operations - -* End-of-Day Data - * Get All -* Exchange - * Get -* Ticker - * Get - -## Example usage - -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]() - -The final workflow should look like the following image. - -![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 - -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. -5. Click the **Add Filter** button and select **Timeframe Start Date > A Week Ago**. -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) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.matrix.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.matrix.md deleted file mode 100644 index 28cb91505..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.matrix.md +++ /dev/null @@ -1,155 +0,0 @@ -# Matrix - -[Matrix](https://matrix.org) is an open standard for interoperable, decentralized, real-time communication over IP. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/matrix/). - - -## Basic Operations - -* Account - * Get current user's account information -* Event - * Get single event by ID -* Media - * Send media to a chat room -* Message - * Send a message to a room - * Gets all messages from a room -* Room - * New chat room with defined settings - * Invite a user to a room - * Join a new room - * Kick a user from a room - * Leave a room -* Room Member - * Get all members - -## Example Usage - -This workflow allows you to create a room, invite members from a different room, and send a message to the room that we created using the Matrix node. You can also find the [workflow](https://n8n.io/workflows/724) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Matrix]() -- [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 Matrix node](/_images/integrations/builtin/app-nodes/matrix/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Matrix node (create: room) - -This node will create a new room called `n8n` on the Matrix server. - -1. First of all, you'll have to enter credentials for the Matrix node. You can find out how to do that [here](/integrations/builtin/credentials/matrix/). - -2. Select 'Room' from the ***Resource*** dropdown list. -3. Enter `n8n` in the ***Room Name*** field. You can also enter a different name for the room. -4. Enter an alias for the room in the ***Room Alias*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a room `n8n` with an alias `#discussion-n8n:matrix.org`. - -![Using the Matrix node to create a room](/_images/integrations/builtin/app-nodes/matrix/matrix_node.png) - -### 3. Matrix1 node (me: account) - -This node will get your account information from the Matrix server. We are doing this because Matrix will send an invite to all members of the room, including you. Since you are already a member of the room, you will get an error. We will use the data from this node later on to make sure that you don't send an invite to yourself. - - -1. Select the credentials that you entered in the previous node. -2. Select 'Account' from the ***Resource*** dropdown list. -3. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns your user ID. - -![Using the Matrix node to get your account information](/_images/integrations/builtin/app-nodes/matrix/matrix1_node.png) - -### 3. Matrix2 node (getAll: roomMember) - -This node will return the information of all the members in a room. - - -1. Select the credentials that you entered in the previous node. -2. Select 'Room Member' from the ***Resource*** dropdown list. -3. Select a room from the ***Room ID*** dropdown list. We will invite the members of this room later on in the workflow. -4. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns the information of all the members in the room that we specified. The output of this node will be passed on to the next nodes in the workflow. - -![Using the Matrix node to get the information of the members in a room](/_images/integrations/builtin/app-nodes/matrix/matrix2_node.png) - -### 4. IF node - -This node will compare your user ID with the user ID of other members. If the user IDs are not equal, the output will be true. - - -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 > Matrix1 > Output Data > JSON > user_id. You can also add the following expression: `{{$node["Matrix1"].json["user_id"]}}`. -4. Select 'Not Equal' from the ***Operation*** dropdown list. -5. Click on the gears icon next to the ***Value 2*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Matrix2 > Output Data > JSON > user_id. You can also add the following expression: `{{$node["Matrix2"].json["user_id"]}}`. -7. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns the information of all the members of the room except your own. - -![Using the IF node to compare your user id with the user id of the members in a room](/_images/integrations/builtin/app-nodes/matrix/if_node.png) - -### 4. Matrix3 node (invite: room) - -This node will send an invitation to the members returned by the previous node to join the room that we created using the Matrix node. - - -1. Connect the node to the 'true' output of the IF node -2. Select the credentials that you entered in the previous node. -3. Select 'Room' from the ***Resource*** dropdown list. -4. Select 'Invite' from the ***Operation*** dropdown list. -5. Click on the gears icon next to the ***Room ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Matrix > Output Data > JSON > room_id. You can also add the following expression: `{{$node["Matrix"].json["room_id"]}}`. -7. Click on the gears icon next to the ***User ID*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > IF > Output Data > JSON > user_id. You can also add the following expression: `{{$node["IF"].json["user_id"]}}`. -9. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends an invite to join the `n8n` room to the members of the other room. - -![Using the Matrix node to send an invite to join the room](/_images/integrations/builtin/app-nodes/matrix/matrix3_node.png) - -### 5. Matrix4 node (create: message) - -This node will send a message to the new room that we created using the Matrix node. - - -1. Select the credentials that you entered in the previous node. -2. Click on the gears icon next to the ***Room ID*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Nodes > Matrix > Output Data > JSON > room_id. You can also add the following expression: `{{$node["Matrix"].json["room_id"]}}`. -4. Enter a message in the ***Text*** field. -5. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends a message to the room that we created with the Matrix node. - -![Using the Matrix node to send a message to the room we created](/_images/integrations/builtin/app-nodes/matrix/matrix4_node.png) - -### 6. 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/matrix/noop_node.png) - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mattermost.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mattermost.md deleted file mode 100644 index 2a364d928..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mattermost.md +++ /dev/null @@ -1,112 +0,0 @@ -# Mattermost - -[Mattermost](https://mattermost.org/) is an open-source, self-hostable online chat service with file sharing, search, and integrations. It is designed as an internal chat for organisations and companies. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mattermost/). - - -## Basic Operations - -* Channel - * Add a user to a channel - * Create a new channel - * Soft delete a channel - * Get a page of members for a channel - * Restores a soft deleted channel - * Search for a channel - * Get statistics for a channel -* Message - * Soft delete a post, by marking the post as deleted in the database - * Post a message into a channel - * Post an ephemeral message into a channel -* Reaction - * Add a reaction to a post. - * Remove a reaction from a post - * Get all the reactions to one or more posts -* User - * Create a new user - * Deactivates the user and revokes all its sessions by archiving its user object. - * Retrieve all users - * Get a user by email - * Get a user by ID - * Invite user to team - -## Example Usage - -This workflow allows you to create a channel, add a member, and post a message to the channel on Mattermost. You can also find the [workflow](https://n8n.io/workflows/832) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Mattermost]() - -The final workflow should look like the following image. - -![A workflow with the Mattermost node](/_images/integrations/builtin/app-nodes/mattermost/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Mattermost node (create: channel) - -This node will create a new channel named `docs` in Mattermost. If you want to create a channel with a different name, enter that name instead. - -1. First of all, you'll have to enter credentials for the Mattermost node. You can find out how to do that [here](/integrations/builtin/credentials/mattermost/). -2. Select 'Channel' from the ***Resource*** dropdown list. -3. Select a team from the ***Team ID*** dropdown list. -4. Enter `Docs` in the ***Display Name*** field. -5. Enter `docs` in the ***Name*** field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new channel named `docs` in Mattermost. - -![Using the Mattermost node to create a channel](/_images/integrations/builtin/app-nodes/mattermost/mattermost_node.png) - -### 3. Mattermost1 node (addUser: channel) - -This node will add a member to 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 'Add User' 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 > Mattermost > Output Data > JSON > id. You can also add the following expression: `{{$node["Mattermost"].json["id"]}}`. -6. Select a user from the ***User ID*** dropdown list. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node adds a user to the channel that we created in the previous node. - -![Using the Mattermost node to add a user to a channel](/_images/integrations/builtin/app-nodes/mattermost/mattermost1_node.png) - -### 4. Mattermost2 node (post: message) - -This node will post a message to the channel that we created using the Mattermost node. - -1. Select the credentials that you entered in the previous node. -2. Click on the gears icon next to the ***Channel ID*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Nodes > Mattermost > Output Data > JSON > id. You can also add the following expression: `{{$node["Mattermost"].json["id"]}}`. -4. Enter a message in the ***Message*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node posts a message to the channel that we created in the Mattermost node. - -![Using the Mattermost node to post a message to a channel](/_images/integrations/builtin/app-nodes/mattermost/mattermost2_node.png) - -## FAQs - -### How do I resolve the error for the ***Channel ID*** field? - -If you're not the System Administrator, you might get an error `there was a problem loading the parameter options from server: "Mattermost error response: You do not have the appropriate permissions."` next to the ***Channel ID*** field. - -If the system administrator has granted you the `post:channel` permissions, you will be able to execute the node successfully even with the error. - -### How do I find the Channel ID? - -To find the Channel ID in Mattermost, follow the steps mentioned below. - -1. Select the channel from the left sidebar. -2. Click on the channel name on the top and select 'View Info' from the dropdown list. -3. Use the displayed ***ID*** in n8n. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mautic.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mautic.md deleted file mode 100644 index 89feca33d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mautic.md +++ /dev/null @@ -1,61 +0,0 @@ -# Mautic - -[Mautic](https://www.mautic.org/) is an open-source marketing automation software that helps online businesses automate their repetitive marketing tasks such as lead generation, contact scoring, contact segmentation, and marketing campaigns. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mautic/). - - -## Basic Operations - -* Campaign Contact - * Add contact to a campaign - * Remove contact from a campaign -* Company - * Create a new company - * Delete a company - * Get data of a company - * Get data of all companies - * Update a company -* Company Contact - * Add contact to a company - * Remove a contact from a company -* Contact - * Create a new contact - * Delete a contact - * Edit contact's points - * Add/remove contacts from/to the do not contact list - * Get data of a contact - * Get data of all contacts - * Send email to contact - * Update a contact -* Contact Segment - * Add contact to a segment - * Remove contact from a segment -* Segment Email - * Send - -## Example Usage - -This workflow allows you to get all contacts from Mautic. You can also find the [workflow](https://n8n.io/workflows/549) on the website. This example usage workflow uses the following two nodes. - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Mautic]() - -The final workflow should look like the following image. - -![A workflow with the Mautic node](/_images/integrations/builtin/app-nodes/mautic/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Mautic node - -1. First of all, you'll have to enter credentials for the Mautic node. You can find out how to do that [here](/integrations/builtin/credentials/mautic/). -2. Select 'Get All' from the *Operation* dropdown list. -3. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.medium.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.medium.md deleted file mode 100644 index 14bd45955..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.medium.md +++ /dev/null @@ -1,44 +0,0 @@ -# Medium - -[Medium](https://www.medium.com/) is an online publishing platform and home to a diverse array of stories, ideas, and perspectives. It empowers writers to share their work and ideas with the readers. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/medium/). - - -## Basic Operations - -* Post - * Create a post -* Publication - * 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.messageBird.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.messageBird.md deleted file mode 100644 index b9351268c..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.messageBird.md +++ /dev/null @@ -1,36 +0,0 @@ -# MessageBird - -[MessageBird](https://www.messagebird.com/) is a cloud communications platform that connects enterprises to their global customers. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/messageBird/). - - -## Basic Operations - -* SMS - * Send text messages (SMS) -* Balance - * Get the balance - -## Example Usage - -This workflow allows you to send an SMS with MessageBird. You can also find the [workflow](https://n8n.io/workflows/455) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [MessageBird]() - -The final workflow should look like the following image. - -![A workflow with the MessageBird node](/_images/integrations/builtin/app-nodes/messagebird/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. MessageBird node - -1. First of all, you'll have to enter credentials for the MessageBird node. You can find out how to do that [here](/integrations/builtin/credentials/messageBird/). -2. Enter the phone number from which you'll be sending the message in the *From* field. -3. Enter the phone number to which you'll be sending the message in the *To* field. -4. Enter you message in the *Message* field. -5. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.metabase.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.metabase.md deleted file mode 100644 index cf42a9d3d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.metabase.md +++ /dev/null @@ -1,23 +0,0 @@ -# Metabase - -[Metabase](https://www.metabase.com/){:target=_blank .external-link} is a business data analysis tool. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/metabase/). - -## Resources and operations - -* Alert - * Get - * Get All -* Database - * Add - * Get All - * Get Fields -* Metric - * Get - * Get All -* Question - * Get - * Get All - * Result Data diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftDynamicsCrm.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftDynamicsCrm.md deleted file mode 100644 index d362a25e9..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftDynamicsCrm.md +++ /dev/null @@ -1,16 +0,0 @@ -# Microsoft Dynamics CRM - -[Microsoft Dynamics CRM](https://dynamics.microsoft.com/en-us/) is a is a customer relationship management application developed by Microsoft. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/microsoft/). - - -## Basic Operations - -* Account - * Create - * Delete - * Get - * Get All - * Update diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftExcel.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftExcel.md deleted file mode 100644 index 55e2b1ae0..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftExcel.md +++ /dev/null @@ -1,41 +0,0 @@ -# Microsoft Excel - -[Microsoft Excel](https://office.live.com/start/excel.aspx) is a spreadsheet developed by Microsoft. It features calculation, graphing tools, pivot tables, and a macro programming language called Visual Basic for Applications. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/microsoft/). - - -## Basic Operations - -* Table - * Adds rows to the end of the table - * Retrieve a list of tablecolumns - * Retrieve a list of tablerows - * Looks for a specific column value and then returns the matching row -* Workbook - * Adds a new worksheet to the workbook. - * Get data of all workbooks -* Worksheet - * Get all worksheets - * Get worksheet content - -## Example Usage - -This workflow allows you to get information about all workbooks from Microsoft Excel. You can also find the [workflow](https://n8n.io/workflows/566) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Microsoft Excel]() - -The final workflow should look like the following image. - -![A workflow with the Microsoft Excel node](/_images/integrations/builtin/app-nodes/microsoftexcel/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Microsoft Excel node - -1. First of all, you'll have to enter credentials for the Microsoft Excel node. You can find out how to do that [here](/integrations/builtin/credentials/microsoft/). -2. Select the 'Get All' option from the *Operation* dropdown list. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftGraphSecurity.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftGraphSecurity.md deleted file mode 100644 index 869ec2364..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftGraphSecurity.md +++ /dev/null @@ -1,17 +0,0 @@ -# Microsoft Graph Security - -The [Microsoft Graph Security API](https://docs.microsoft.com/en-us/graph/security-concept-overview) allows connecting to Microsoft security products, services, and partners to streamline security operations and improve threat protection, detection, and response capabilities. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/microsoft/). - - -## Basic Operations - -* Secure Score - * Get - * Get All -* Secure Score Control Profile - * Get - * Get All - * Update diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftOneDrive.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftOneDrive.md deleted file mode 100644 index ea6dec4c5..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftOneDrive.md +++ /dev/null @@ -1,48 +0,0 @@ -# Microsoft OneDrive - -[Microsoft OneDrive](https://onedrive.live.com/) is a file hosting service and synchronization service operated by Microsoft. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/microsoft/). - - -## Basic Operations - -* File - * Copy a file - * Delete a file - * Download a file - * Get a file - * Rename a file - * Search a file - * Share a file - * Upload a file up to 4MB in size -* Folder - * Create a folder - * Delete a folder - * Get Children (get items inside a folder) - * Rename a folder - * Search a folder - * Share a folder - -## Example Usage - -This workflow allows you to create a folder in Microsoft OneDrive. You can also find the [workflow](https://n8n.io/workflows/565) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Microsoft OneDrive]() - -The final workflow should look like the following image. - -![A workflow with the Microsoft OneDrive node](/_images/integrations/builtin/app-nodes/microsoftonedrive/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Microsoft OneDrive node - -1. First of all, you'll have to enter credentials for the Microsoft OneDrive node. You can find out how to do that [here](/integrations/builtin/credentials/microsoft/). -2. Select the 'Folder' option from the *Resource* dropdown list. -3. Select the 'Create' option from the *Operation* dropdown list. -4. Enter the folder name in the *Name* field. -5. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftOutlook.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftOutlook.md deleted file mode 100644 index 572ed11a9..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftOutlook.md +++ /dev/null @@ -1,119 +0,0 @@ -# Microsoft Outlook - -[Microsoft Outlook](https://outlook.live.com/) is a personal information manager software system from Microsoft. Microsoft Outlook is an email client that includes calendaring, task managing, contact managing, note-taking, journal logging, and web browsing. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/microsoft/). - - -## Basic Operations - -* Draft - * Create a new email draft - * Delete a draft - * Get a single draft - * Send an existing draft message - * Update a draft -* Folder - * Create a new mail folder in the root folder of the user's mailbox - * Delete a folder - * Get a single folder details - * Get all folders under the root folder of the signed-in user - * Lists all child folders under the folder -* Folder Message - * Get all the messages in a folder -* Message - * Delete a message - * Get a single message - * Get all messages in the signed-in user's mailbox - * Get MIME content of a message - * Move a message - * Create reply to a message - * Send a message - * Update a message -* Message Attachment - * Add an attachment to a message - * Download attachment content - * Get an attachment from a message - * Get all the message's attachments - -## Example Usage - -This workflow allows you to create, add an attachment, and send a draft using the Microsoft Outlook node. You can also find the [workflow](https://n8n.io/workflows/867) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Microsoft Outlook]() -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) - -The final workflow should look like the following image. - -![A workflow with the Microsoft Outlook node](/_images/integrations/builtin/app-nodes/microsoftoutlook/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Microsoft Outlook node (create: draft) - -This node will create a draft message that we will send using the Microsoft Outlook node later in the workflow. - -1. First of all, you'll have to enter credentials for the Microsoft Outlook node. You can find out how to do that [here](/integrations/builtin/credentials/microsoft/). -2. Select 'Draft' from the ***Resource*** dropdown list. -3. Enter the subject in the ***Subject*** field. -4. Enter the following content in the ***Body Content*** field. -```html -

Hello from n8n!

-

We are sending this email using the Microsoft Outlook node in n8n

-

Best,

-

Sender

-``` -5. Click on ***Add Field*** and select 'Body Content Type' from the dropdown list. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new draft with the subject `Hello from n8n!` and HTML body content. - -![Using the Microsoft Outlook node to create a draft](/_images/integrations/builtin/app-nodes/microsoftoutlook/microsoftoutlook_node.png) - -### 3. HTTP Request node (GET) - -This node will fetch the logo of n8n from a URL. We will attach this file to our draft message that we created earlier. If you want to attach a different file, enter the URL of that file instead. - -1. Enter `https://n8n.io/n8n-logo.png` in the ***URL*** field. -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 node returns the n8n logo. We will attach this file to the draft message that we created using the previous node. - -![Using the HTTP Request to get a file](/_images/integrations/builtin/app-nodes/microsoftoutlook/httprequest_node.png) - -### 4. Microsoft Outlook1 node (add: messageAttachment) - -This node will attach the file that we received from the previous node to the drat message we created using the Microsoft Outlook node. - -1. Select the credentials that you entered in the previous Microsoft Outlook node. -2. Select 'Message Attachment' from the ***Resource*** dropdown list. -3. Click on the gears icon next to the ***Message ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Microsoft Outlook > Output Data > JSON > id. You can also add the following expression: `{{$node["Microsoft Outlook"].json["id"]}}`. -5. Click on the ***Add Field*** button. -6. Enter `n8n.png` in the ***File Name*** field. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node attaches the file to the draft message that we created using the Microsoft Outlook node. - -![Using the Microsoft Outlook node to add an attachment to a draft message](/_images/integrations/builtin/app-nodes/microsoftoutlook/microsoftoutlook1_node.png) - -### 5. Microsoft Outlook2 node (send: draft) - -This node will send the draft message that we created using the Microsoft Outlook node to a recipient. - -1. Select the credentials that you entered in the previous node. -2. Select 'Draft' from the ***Resource*** dropdown list. -3. Select 'Send' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Message ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > Microsoft Outlook > Output Data > JSON > id. You can also add the following expression: `{{$node["Microsoft Outlook"].json["id"]}}`. -6. Click on the ***Add Field*** button. -7. Enter the recipient's email address in the ***Recipients*** field. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends the draft message that we created using the Microsoft Outlook node to a recipient. - -![Using the Microsoft Outlook node to send a draft](/_images/integrations/builtin/app-nodes/microsoftoutlook/microsoftoutlook2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftSql.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftSql.md deleted file mode 100644 index a3a12c790..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftSql.md +++ /dev/null @@ -1,36 +0,0 @@ -# Microsoft SQL - -[Microsoft SQL](https://www.microsoft.com/en-us/sql-server) is a relational database management system. As a database server, it is a software product with the primary function of storing and retrieving data as requested by other software applications—which may run either on the same computer or on another computer across a network. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/microsoftSql/). - - -## Basic Operations - -* Execute an SQL query -* Insert rows in database -* Update rows in database -* Delete rows in database - - -## Example Usage - -This workflow allows you to execute an SQL query in Microsoft SQL. You can also find the [workflow](https://n8n.io/workflows/479) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Microsoft SQL]() - -The final workflow should look like the following image. - -![A workflow with the Microsoft SQL node](/_images/integrations/builtin/app-nodes/microsoftsql/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Microsoft SQL node - -1. First of all, you'll have to enter credentials for the Microsoft SQL node. You can find out how to do that [here](/integrations/builtin/credentials/microsoftSql/). -2. Select 'Execute Query' from the *Operation* dropdown list. -3. Enter your SQL query in the *Query* field. -4. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftTeams.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftTeams.md deleted file mode 100644 index b6cab9a28..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftTeams.md +++ /dev/null @@ -1,80 +0,0 @@ -# Microsoft Teams - -[Microsoft Teams](https://teams.microsoft.com/) is a business-oriented communication and collaboration platform that combines workplace chat, video meetings, file storage , and application integration. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/microsoft/). - - -## Basic Operations - -* Channel - * Create a channel - * Delete a channel - * Get a channel - * Get all channels - * Update a channel -* Channel Message (Beta) - * Create a message - * Get all messages -* Task - * Create a task - * Delete a task - * Get a task - * 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 deleted file mode 100644 index 6b6bfac3e..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.microsoftToDo.md +++ /dev/null @@ -1,95 +0,0 @@ -# Microsoft To Do - -[Microsoft To Do](https://todo.microsoft.com) is a cloud-based task management application. It allows users to manage their tasks from a smartphone, tablet, and computer. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/microsoft/). - - -## Basic Operations - -* Linked Resource - * Create - * Delete - * Get - * Get All - * Update -* List - * Create - * Delete - * Get - * Get All - * Update -* Task - * Create - * Delete - * Get - * 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 deleted file mode 100644 index 36de0733e..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mindee.md +++ /dev/null @@ -1,62 +0,0 @@ -# Mindee - -[Mindee](https://mindee.com) develops API-based products for instantly extracting information from any kind of image and transforming it into usable data. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mindee/). - - -## Basic Operations - -**Invoice** -- Predict - - -**Receipt** -- 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.misp.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.misp.md deleted file mode 100644 index 2a6421fbf..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.misp.md +++ /dev/null @@ -1,61 +0,0 @@ -# MISP - -[MISP](https://www.misp-project.org/) is an open source threat intelligence platform. The project develops utilities and documentation for more effective threat intelligence. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/misp/). - - -## Basic Operations - -* Attribute - * Create - * Delete - * Get - * Get All - * Update -* Event - * Create - * Delete - * Get - * Get All - * Publish - * Unpublish - * Update -* Event Tag - * Add - * Remove -* Feed - * Create - * Disable - * Enable - * Get - * Get All - * Update -* Galaxy - * Delete - * Get - * Get All -* Noticelist - * Get - * Get All -* Organisation - * Create - * Delete - * Get - * Get All - * Update -* Tag - * Create - * Delete - * Get All - * Update -* User - * Create - * Delete - * Get - * Get All - * Update -* Warninglist - * Get - * Get All diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mocean.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mocean.md deleted file mode 100644 index fb625b6da..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mocean.md +++ /dev/null @@ -1,40 +0,0 @@ -# Mocean - -[Mocean](https://www.moceanapi.com/) makes sending and receiving SMS easy. It also has voice API which allows you to make outbound and inbound calls. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mocean/). - - -## Basic Operations - -* SMS - * Send SMS/Voice message -* Voice - * Send SMS/Voice message - - -## Example Usage - -This workflow allows you to send an SMS using the Mocean node. You can also find the [workflow](https://n8n.io/workflows/667) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Mocean]() - -The final workflow should look like the following image. - -![A workflow with the Mocean node](/_images/integrations/builtin/app-nodes/mocean/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. Mocean node - -1. First of all, you'll have to enter credentials for the Mocean node. You can find out how to do that [here](/integrations/builtin/credentials/mocean/). -2. Enter the sender ID in the ***From*** field. -3. Enter the receivers' number in the ***To*** field. -4. Enter the message in the ***Message*** field. -5. Click on ***Execute Node*** to run the node. - -![Using the Mocean node to send an SMS](/_images/integrations/builtin/app-nodes/mocean/mocean_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mondayCom.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mondayCom.md deleted file mode 100644 index 9c953ffee..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mondayCom.md +++ /dev/null @@ -1,53 +0,0 @@ -# monday.com - -[monday.com](https://monday.com/) is a work operating system that enables organizations to manage tasks, projects, and team work. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mondayCom/). - - -## Basic Operations - -* Board - * Archive a board - * Create a new board - * Get a board - * Get all boards -* Board Column - * Create a new column - * Get all columns -* Board Group - * Delete a group in a board - * Create a group in a board - * Get list of groups in a board -* Board Item - * Add an update to an item. - * Change a column value for a board item - * Change multiple column values for a board item - * Create an item in a board's group - * Delete an item - * Get an item - * Get all items - * Get items by column value - * Move item to group - -## Example Usage - -This workflow allows you to get a board from monday.com. You can also find the [workflow](https://n8n.io/workflows/556) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [monday.com]() - -The final workflow should look like the following image. - -![A workflow with the monday.com node](/_images/integrations/builtin/app-nodes/mondaycom/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. monday.com node - -1. First of all, you'll have to enter credentials for the monday.com node. You can find out how to do that [here](/integrations/builtin/credentials/mondayCom/). -2. Select the 'Get' option from the *Operation* dropdown list. -3. Select the board you want to get from the *Board ID* dropdown list. -4. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mongoDb.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mongoDb.md deleted file mode 100644 index 6e31be84f..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mongoDb.md +++ /dev/null @@ -1,51 +0,0 @@ -# MongoDB - -[MongoDB](https://www.mongodb.com/) is a cross-platform document-oriented database program developed by MongoDB Inc. It is classified as a NoSQL database program. MongoDB uses JSON-like documents with optional schemas. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mongoDb/). - - -## Operations - -* Aggregate documents -* Delete documents -* Find documents -* Find and replace documents -* Find and update documents -* Insert documents -* Update documents - - -## Example Usage - -This workflow allows you to insert a document into a MongoDB collection. You can also find the [workflow](https://n8n.io/workflows/503) on the website. This example usage workflow would use the following three nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [MongoDB]() - -The final workflow should look like the following image. - -![A workflow with the MongoDB node](/_images/integrations/builtin/app-nodes/mongodb/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Set node - -1. Click on the *Add Value* button and select 'String' from the dropdown list. -2. Enter `my_key`in the *Name* field. -3. Enter `my_value` in the *Value* field. - -### 3. MongoDB node - -1. First of all, you'll have to enter credentials for the MongoDB node. You can find out how to do that [here](/integrations/builtin/credentials/mongoDb/). -2. Select 'Insert' from the *Operation* dropdown list. -3. Enter the name of your MongoDB collection in the *Collection* field. -4. Enter `my_key` in the *Fields* field. -5. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.monicaCrm.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.monicaCrm.md deleted file mode 100644 index 4cacb4085..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.monicaCrm.md +++ /dev/null @@ -1,100 +0,0 @@ -# Monica CRM - -[Monica CRM](https://www.monicahq.com/) is an open-source web application to organize and record your interactions with your loved ones. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/monicaCrm/). - - -## Basic operations - -* Activity - * Create an activity - * Delete an activity - * Retrieve an activity - * Retrieve all activities - * Update an activity -* Call - * Create a call - * Delete a call - * Retrieve a call - * Retrieve all calls - * Update a call -* Contact - * Create a contact - * Delete a contact - * Retrieve a contact - * Retrieve all contacts - * Update a contact -* Contact Field - * Create a contact field - * Delete a contact field - * Retrieve a contact field - * Update a contact field -* Contact Tag - * Add - * Remove -* Conversation - * Create a conversation - * Delete a conversation - * Retrieve a conversation - * Update a conversation -* Conversation Message - * Add a message to a conversation - * Update a message in a conversation -* Journal Entry - * Create a journal entry - * Delete a journal entry - * Retrieve a journal entry - * Retrieve all journal entries - * Update a journal entry -* Note - * Create a note - * Delete a note - * Retrieve a note - * Retrieve all notes - * Update a note -* Reminder - * Create a reminder - * Delete a reminder - * Retrieve a reminder - * Retrieve all reminders - * Update a reminder -* Tag - * Create a tag - * Delete a tag - * Retrieve a tag - * Retrieve all tags - * Update a tag -* Task - * Create a task - * Delete a task - * Retrieve a task - * Retrieve all tasks - * Update a task - - -## Example usage - -This workflow allows you to create a new contact in Monica CRM. This example usage workflow would use the following three nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Monica CRM]() - -The final workflow should look like the following image. - -![A workflow with the Monica CRM node](/_images/integrations/builtin/app-nodes/monicacrm/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Monica CRM node - -1. First enter your credentials for the Monica CRM node. You can find out how to do that [here](/integrations/builtin/credentials/monicaCrm/). -2. Select *Contact* from the *Resource* dropdown list. -3. Select *Create* from the *Operation* dropdown list. -3. Enter the *First Name* of your new contact. -4. Enter the *Gender* of your new contact using the dropdown list. -5. Click on *Execute Node* to run the workflow. - -![The Monica CRM node](/_images/integrations/builtin/app-nodes/monicacrm/monicacrm_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mqtt.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mqtt.md deleted file mode 100644 index 83b1a3e65..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mqtt.md +++ /dev/null @@ -1,89 +0,0 @@ -# MQTT - -[MQTT](https://mqtt.org) is an open OASIS and ISO standard lightweight, publish-subscribe network protocol that transports messages between devices. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mqtt/). - - -## Example Usage - -This workflow allows you to send position updates of the ISS every minute to a topic in MQTT using the MQTT node. You can also find the [workflow](https://n8n.io/workflows/1069) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [MQTT]() - -The final workflow should look like the following image. - -![A workflow with the MQTT node](/_images/integrations/builtin/app-nodes/mqtt/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow every minute. - -1. Click on ***Add Cron Time***. -2. Select 'Every Minute' from the ***Mode*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every minute. - -![Using the Cron node to trigger the workflow every minute](/_images/integrations/builtin/app-nodes/mqtt/cron_node.png) - -### 2. HTTP Request node (GET) - -This node will make a GET request to the API `https://api.wheretheiss.at/v1/satellites/25544/positions` to fetch the position of the ISS. This information gets passed on to the next node in the workflow. - -1. Enter `https://api.wheretheiss.at/v1/satellites/25544/positions` in the ***URL*** field. -2. Click on the ***Add Parameter*** button in the ***Query Parameters*** section. -3. Enter `timestamps` in the ***Name*** field. -4. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -5. Enter the following expression: `{{Date.now()}}`. This expression will return the current timestamp. -6. 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 the information about the location of the ISS. - -![Using the HTTP Request node to get the information about the location of the ISS](/_images/integrations/builtin/app-nodes/mqtt/httprequest_node.png) - -### 3. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `Name` in the ***Name*** 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: Current Node > Input Data > JSON > 0 > name. You can also add the following expression: `{{$json["0"]["name"]}}`. -5. Click on ***Add Value*** and select 'String' from the dropdown list. -6. Enter `Latitude` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > 0 > latitude. You can also add the following expression: `{{$json["0"]["latitude"]}}`. -9. Click on ***Add Value*** and select 'String' from the dropdown list. -10. Enter `Longitude` in the ***Name*** field. -11. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > 0 > longitude. You can also add the following expression: `{{$json["0"]["longitude"]}}`. -13. Click on ***Add Value*** and select 'String' from the dropdown list. -14. Enter `Timestamp` in the ***Name*** field. -15. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -16. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > 0 > timpestamp. You can also add the following expression: `{{$json["0"]["timestamp"]}}`. -17. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -18. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uses the data from the previous node and returns the data that we set for the workflow. - -![Using the Set node to set the data](/_images/integrations/builtin/app-nodes/mqtt/set_node.png) - -### 4. MQTT node - -This node will send the data from the previous node to the `iss-position` topic in MQTT. If you have created a topic with a different name in MQTT, you can use that topic name instead. - -1. First of all, you'll have to enter credentials for the MQTT node. You can find out how to do that [here](/integrations/builtin/credentials/mqtt/). -2. Enter the name of the topic in the ***Topic*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends the data from the previous node to the `iss-position` topic in MQTT. - -![Using the MQTT node to send the data to a topic](/_images/integrations/builtin/app-nodes/mqtt/mqtt_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.msg91.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.msg91.md deleted file mode 100644 index 9424edcba..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.msg91.md +++ /dev/null @@ -1,42 +0,0 @@ -# MSG91 - -[MSG91](https://msg91.com/) is an enterprise SMS Solution providing Bulk SMS, Transactional SMS API, Regional SMS, OTP Verification APIs, Promotional SMS via powerful, and a robust SMS Gateway. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/msg91/). - - -## Basic Operations - -* SMS - * Send SMS - -## Example Usage - -This workflow allows you to send an SMS using MSG91. You can also find the [workflow](https://n8n.io/workflows/511) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [MSG91]() - -The final workflow should look like the following image. - -![A workflow with the MSG91 node](/_images/integrations/builtin/app-nodes/msg91/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. MSG91 node - -1. First of all, you'll have to enter credentials for the MSG91 node. You can find out how to do that [here](/integrations/builtin/credentials/msg91/). -2. Enter the sender ID in the *Sender ID* field. You can find instructions on how to obtain the sender ID in the FAQs below. -3. Enter the phone number to which you'll be sending the message in the *To* field. -4. Enter you message in the *Message* field. -5. Click on *Execute Node* to run the workflow. - - -## FAQs - -### How do I find my Sender ID? - -1. Log in to your MSG91 dasboard 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.mySql.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.mySql.md deleted file mode 100644 index 1c9efdc7b..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.mySql.md +++ /dev/null @@ -1,58 +0,0 @@ -# MySQL - -[MySQL](https://www.mysql.com/) is an open-source relational database management system. MySQL has stand-alone clients that allow users to interact directly with a MySQL database using SQL, but more often MySQL is used with other programs to implement applications that need relational database capability. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mySql/). - - -## Basic Operations - -* Execute an SQL query. -* Insert rows in database. -* Update rows in database - -## Example Usage - -This workflow allows you to create a table and insert data in it on a MySQL database. You can also find the [workflow](https://n8n.io/workflows/598) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [MySQL]() - -The final workflow should look like the following image. - -![A workflow with the MySQL node](/_images/integrations/builtin/app-nodes/mysql/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. MySQL node (Execute Query) - -1. First of all, you'll have to enter credentials for the MySQL node. You can find out how to do that [here](/integrations/builtin/credentials/mySql/). -2. Select 'Execute Query' from the ***Operation*** dropdown list. -3. Enter the following SQL query in the ***Query*** field: `CREATE TABLE test (id INT, name VARCHAR(255), PRIMARY KEY (id));`. -4. Click on ***Execute Node*** to run the node. - -![Using the MySQL node to create a table](/_images/integrations/builtin/app-nodes/mysql/mysql_node.png) - -### 3. Set node - -1. Set the ***Keep Only Set*** toggle to true. -2. Click on the ***Add Value*** button and select 'Number' from the dropdown list. -3. Enter `id` in the ***Name*** field. -4. Click on the ***Add Value*** button and select 'String' from the dropdown list. -5. Enter `name` in the ***Name*** field. -6. Enter the value for the name in the ***Value*** field. -7. Click on ***Execute Node*** to run the node. - -![Using the Set node to set data to be inserted by the MySQL node](/_images/integrations/builtin/app-nodes/mysql/set_node.png) - -### 4. MySQL1 node (Insert) - -1. Select the credentials that you entered in the previous MySQL node. -2. Enter `test` in the ***Table*** field. -3. Enter `id, name` in the ***Columns*** field. -4. Click on ***Execute Node*** to run the node. - -![Using the MySQL node to insert data into a table](/_images/integrations/builtin/app-nodes/mysql/mysql1_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.n8nTrainingCustomerDatastore.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.n8nTrainingCustomerDatastore.md deleted file mode 100644 index 78d8ff063..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.n8nTrainingCustomerDatastore.md +++ /dev/null @@ -1,3 +0,0 @@ -# Customer Datastore (n8n Training) - -This node is used exclusively for the n8n new user onboarding tutorial. It provides dummy data for testing purposes and has no further functionality. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.n8nTrainingCustomerMessenger.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.n8nTrainingCustomerMessenger.md deleted file mode 100644 index bde41c2a1..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.n8nTrainingCustomerMessenger.md +++ /dev/null @@ -1,3 +0,0 @@ -# Customer Messenger (n8n Training) - -This node is used exclusively for the n8n new user onboarding tutorial. It provides no further functionality. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.nasa.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.nasa.md deleted file mode 100644 index dbf6d7199..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.nasa.md +++ /dev/null @@ -1,99 +0,0 @@ -# NASA - -[NASA](https://nasa.gov/) is an independent agency of the U.S. federal government responsible for the civilian space program, as well as aeronautics and space research. The NASA API makes NASA data, including imagery, accessible to application developers. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/nasa/). - - -## Basic Operations - -* Astronomy Picture of the Day - * Get the Astronomy Picture of the Day -* Asteroid Neo-Feed - * Retrieve a list of asteroids based on their closest approach date to Earth -* Asteroid Neo-Lookup - * Look up an asteroid based on its NASA SPK-ID -* Asteroid Neo-Browse - * Browse the overall asteroid dataset -* DONKI Coronal Mass Ejection - * Retrieve DONKI coronal mass ejection data -* DONKI Interplanetary Shock - * Retrieve DONKI interplanetary shock data -* DONKI Solar Flare - * Retrieve DONKI solar flare data -* DONKI Solar Energetic Particle - * Retrieve DONKI solar energetic particle data -* DONKI Magnetopause Crossing - * Retrieve data on DONKI magnetopause crossings -* DONKI Radiation Belt Enhancement - * Retrieve DONKI radiation belt enhancement data -* DONKI High Speed Stream - * Retrieve DONKI high speed stream data -* DONKI WSA+EnlilSimulation - * Retrieve DONKI WSA+EnlilSimulation data -* DONKI Notifications - * Retrieve DONKI notifications data -* Earth Imagery - * Retrieve Earth imagery -* Earth Assets - * Retrieve Earth assets - -## Example Usage - -This workflow allows you to send the Astronomy Picture of the day daily to a Telegram channel. You can also find the [workflow](https://n8n.io/workflows/828) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [NASA]() -- [Telegram](/integrations/builtin/app-nodes/n8n-nodes-base.telegram/) - -The final workflow should look like the following image. - -![A workflow with the NASA node](/_images/integrations/builtin/app-nodes/nasa/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow daily at 8 PM. - -1. Click on ***Add Cron Time***. -2. Set hours to 20 in the ***Hour*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every day at 8 PM. - -![Using the Cron node to trigger the workflow daily at 8 pm](/_images/integrations/builtin/app-nodes/nasa/cron_node.png) - -### 2. NASA node (get:astronomyPictureOfTheDay) - -This node will return the Astronomy Picture of the Day. - -1. First of all, you'll have to enter credentials for the NASA node. You can find out how to do that [here](/integrations/builtin/credentials/nasa/). -2. Toggle ***Download Image*** to `false`. By setting this option to false the node will not return binary data. -2. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns data for the Astronomy Picture of the Day. This data will be used by the next node in the workflow. - -![Using the NASA node to get the Astronomy Picture of the Day](/_images/integrations/builtin/app-nodes/nasa/nasa_node.png) - -### 3. Telegram node (sendPhoto: message) - -This node will send the picture that we receive from the previous node to a channel. - -1. First of all, you'll have to enter credentials for the Telegram node. You can find out how to do that [here](/integrations/builtin/credentials/telegram/). -2. Select 'Send Photo' from the ***Operation*** dropdown list. -3. Enter a chat ID in the ***Chat ID*** field. -4. Click on the gears icon next to the ***Photo*** field and click on ***Add Expression***. - -5. Select the following in the ***Variable Selector*** section: Nodes > NASA > Output Data > JSON > url. You can also add the following expression: `{{$node["NASA"].json["url"]}}`. -6. Click on ***Add Field*** and select 'Caption' from the dropdown list. -7. Click on the gears icon next to the ***Caption*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > NASA > Output Data > JSON > title. You can also add the following expression: `{{$node["NASA"].json["title"]}}`. -9. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends the image with a caption to the channel that we specifiy. - -![Using the Telegram node to send the Astronomy Picture of the Day](/_images/integrations/builtin/app-nodes/nasa/telegram_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.netlify.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.netlify.md deleted file mode 100644 index 9948b4967..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.netlify.md +++ /dev/null @@ -1,19 +0,0 @@ -# Netlify - -[Netlify](https://netlify.com/) offers hosting and serverless backend services for web applications and static websites. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/netlify/). - - -## Basic Operations - -* Deploy - * Cancel a deployment - * Create a new deployment - * Get a deployment - * Get all deployments -* Site - * Delete a site - * Get a site - * Returns all sites diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.nextCloud.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.nextCloud.md deleted file mode 100644 index 21ce3e898..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.nextCloud.md +++ /dev/null @@ -1,81 +0,0 @@ -# Nextcloud - -[Nextcloud](https://nextcloud.com/) is a free and open-source suite of client-server software for creating and using file hosting services. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/nextCloud/). - - -## Basic Operations - -* File - * Copy a file - * Delete a file - * Download a file - * Move a file - * Share a file - * Upload a file -* Folder - * Copy a folder - * Create a folder - * Delete a folder - * Return the contents of a given folder - * Move a folder - * Share a folder -* User - * Invite a user to a NextCloud organization - * Delete a user. - * Retrieve information about a single user. - * Retrieve a list of users. - * Edit attributes related to a user. - -## Example Usage - -This workflow allows you to create a folder in Nextcloud, upload a file into that folder, and list the contents of the folder. You can also find the [workflow](https://n8n.io/workflows/620) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Nextcloud]() -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) - -The final workflow should look like the following image. - -![A workflow with the Nextcloud node](/_images/integrations/builtin/app-nodes/nextcloud/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Nextcloud node (create: folder) - -1. First of all, you'll have to enter credentials for the Nextcloud node. You can find out how to do that [here](/integrations/builtin/credentials/nextCloud/). -2. Select the 'Folder' option from the ***Resource*** dropdown list. -3. Enter a folder name in the ***Folder*** field. -4. Click on ***Execute Node*** to run the node. - -![Create a folder in Nextcloud using the Nextcloud node](/_images/integrations/builtin/app-nodes/nextcloud/nextcloud_node.png) - -### 3. HTTP Request node (GET) - -1. Enter `https://n8n.io/n8n-logo.png` in the ***URL*** field. -2. Select 'File' from the ***Response Format*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -![Get a file to upload in Nextcloud using the HTTP Request node](/_images/integrations/builtin/app-nodes/nextcloud/httprequest_node.png) - -### 4. Nextcloud1 node (upload: file) - -1. Select the credentials that you entered in the Nextcloud node. -2. Enter the path of the Nextcloud folder you created in the previous steps along with a file name in the ***File Path*** field. -3. Set the ***Binary Data*** toggle to true. -4. Click on ***Execute Node*** to run the node. - -![Upload a file in Nextcloud using the Nextcloud node](/_images/integrations/builtin/app-nodes/nextcloud/nextcloud1_node.png) - -### 5. Nextcloud2 node (list: folder) - -1. Select the credentials that you entered in the Nextcloud node. -2. Select 'Folder' from the ***Resource*** dropdown list. -3. Select 'List' from the ***Operation*** dropdown list. -4. Enter the name of the Nextcloud folder you created in the previous steps in the ***Folder Path*** field. -5. Click on ***Execute Node*** to run the node. - -![List the contents of a Nextcloud folder using the Nextcloud node](/_images/integrations/builtin/app-nodes/nextcloud/nextcloud2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.nocoDb.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.nocoDb.md deleted file mode 100644 index 29b04c06a..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.nocoDb.md +++ /dev/null @@ -1,44 +0,0 @@ -# NocoDB - -[NocoDB](https://www.nocodb.com/) is an open source Airtable alternative. It works by connecting to any relational database and transforming them into a spreadsheet interface. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/nocoDb/). - - -## Basic operations - -* Row - * Create a row - * Delete a row - * Retrieve all rows - * Retrieve a row - * Update a row - -## Example usage - -This workflow allows you to get all rows in your table. -This example workflow use the following two nodes. - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [NocoDB]() - -The final workflow should look like the following image. - -![A workflow with the NocoDB node](/_images/integrations/builtin/app-nodes/nocodb/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. NocoDB node - -1. First enter your credentials for the NocoDB node. You can find out how to do that [here](/integrations/builtin/credentials/nocoDb/). -2. Select NocoDB version your project using. -3. The **Row Resource** is selected by default. -4. Select **Get All** from the **Operation** dropdown. -5. Enter the NocoDB **Project Name**. (Project ID for older versions) -6. Enter the name of the targeted **Table**. -7. Click on **Execute Node** to run the workflow. - -![The NocoDB node](/_images/integrations/builtin/app-nodes/nocodb/nocodb_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.notion.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.notion.md deleted file mode 100644 index 776da5d6d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.notion.md +++ /dev/null @@ -1,92 +0,0 @@ -# Notion - -[Notion](https://notion.so) is an all-in-one workspace for your notes, tasks, wikis, and databases. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/notion/). - - -## Basic Operations - -**Block** -- Append a block -- Get all children block - - -**Database** -- Get a database -- Get all database -- Query a database - - -**Database Record** -- Create a record in a database -- Update a record in a database - - -**Page** -- Create a page -- Get a page -- Text search for pages - - -**User** -- Get a user -- Get all users - - -## Example Usage - -This workflow allows you to add a new user to your Notion database when an invite gets created via Calendly. You can also find the [workflow](https://n8n.io/workflows/1088) on n8n.io. This example usage workflow uses the following nodes. - -- [Calendly Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.calendlytrigger/) -- [Notion]() - -The final workflow should look like the following image. - -![A workflow with the Notion node](/_images/integrations/builtin/app-nodes/notion/workflow.png) - -### 1. Calendly Trigger node - -The Calendly node will trigger the workflow when an invite gets created. - -1. First of all, you'll have to enter credentials for the Notion node. You can find out how to do that [here](/integrations/builtin/credentials/calendly/). -2. Select 'invitee.created' from the ***Events*** dropdown list. -3. Save your workflow so that the webhook gets registered. -4. Click on ***Execute Node*** to run the node. - -**Note:** Since you'll be using the test webhook while building the workflow, the node only stays active for 120 seconds. After you click on the ***Execute Node*** button, create an invite via Calendly. - -In the screenshot below, you will notice that the Calendly Trigger node triggers the workflow when an invite is created. - -![Using the Calendly Trigger node to trigger the workflow](/_images/integrations/builtin/app-nodes/notion/calendlytrigger_node.png) - - -### 2. Notion node (create: databaseRecord) - -This node will create a new record using the information received from the previous node. - -1. First of all, you'll have to enter credentials for the Notion node. You can find out how to do that [here](/integrations/builtin/credentials/notion/). - -2. Select 'Database Record' from the ***Resource*** dropdown list. -3. Select the database from the ***Database ID*** dropdown list. -4. Click on the ***Add Property*** button. -5. Select 'Name' from the ***Key*** dropdown list. -6. Click on the gears icon next to the ***Title*** field and click on ***Add Expression***. -7. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > payload > invitee > name. You can also add the following expression: `{{$json["payload"]["invitee"]["name"]}}`. -8. Click on the ***Add Property*** button. -9. Select 'Email' from the ***Key*** dropdown list. -10. Click on the gears icon next to the ***Email*** field and click on ***Add Expression***. -11. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > payload > invitee > email. You can also add the following expression: `{{$json["payload"]["invitee"]["email"]}}`. -11. Click on the ***Add Property*** button. -12. Select 'Status' from the ***Key*** dropdown list. -13. Select 'Scheduled' from the ***Option*** dropdown list. -14. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new record from the information that gets received from the previous node. - -![Using the Notion node to add a new record in Notion](/_images/integrations/builtin/app-nodes/notion/notion_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Calendly Trigger node. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.odoo.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.odoo.md deleted file mode 100644 index 08bb11f81..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.odoo.md +++ /dev/null @@ -1,36 +0,0 @@ -# Odoo - -[Odoo](https://www.odoo.com/) is a suite of open-source business apps covering functionality such as: CRM, eCommerce, accounting, inventory, point of sale, project management. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/odoo/). - - -## Operations - -* Contact - * Create a new contact - * Delete a contact - * Get a contact - * Get all contacts - * Update a contact -* Custom Resource - * Create a new item - * Delete an item - * Get an item - * Get all items - * Update an item -* Note - * Create a new note - * Delete a note - * Get a note - * Get all notes - * Update a note -* Opportunity - * Create a new opportunity - * Delete an opportunity - * Get an opportunity - * Get all opportunities - * Update an opportunity - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.oneSimpleApi.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.oneSimpleApi.md deleted file mode 100644 index 37fd3ba57..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.oneSimpleApi.md +++ /dev/null @@ -1,24 +0,0 @@ -# One Simple API - -[One Simple API](https://onesimpleapi.com/) is an API toolbox offering PDF generation, Currency Exchange, QR codes, Screenshots, and more. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/oneSimpleApi/). - - -## Basic Operations - -* Information - * Convert a value between currencies - * Retrieve image metadata from a URL -* Social Profile - * Get details about an Instagram profile - * Get details about a Spotify Artist -* Utility - * Expand a shortened url - * Generate a QR Code - * Validate an email address -* Website - * Generate a PDF from a webpage - * Get SEO information from website - * Create a screenshot from a webpage diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.onfleet.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.onfleet.md deleted file mode 100644 index 41e74bdaf..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.onfleet.md +++ /dev/null @@ -1,56 +0,0 @@ -# Onfleet - -[Onfleet](https://onfleet.com/) is a logistics platform offering a last-mile delivery solution. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/onfleet/). - - -## Operations - -* Admin - * Create a new Onfleet admin - * Delete an Onfleet admin - * Get all Onfleet admins - * Update an Onfleet admin -* Container - * Add task at index (or append) - * Get container information - * Fully replace a container's tasks -* Destination - * Create a new destination - * Get a specific destination -* Hub - * Create a new Onfleet hub - * Get all Onfleet hubs - * Update an Onfleet hub -* Organization - * Retrieve your own organization's details - * Retrieve the details of an organization with which you are connected -* Recipient - * Create a new Onfleet recipient - * Get a specific Onfleet recipient - * Update an Onfleet recipient -* Task - * Create a new Onfleet task - * Clone an Onfleet task - * Force-complete a started Onfleet task - * Delete an Onfleet task - * Get all Onfleet tasks - * Get a specific Onfleet task - * Update an Onfleet task -* Team - * Automatically dispatch tasks assigned to a team to on-duty drivers - * Create a new Onfleet team - * Delete an Onfleet team - * Get a specific Onfleet team - * Get all Onfleet teams - * Get estimated times for upcoming tasks for a team, returns a selected driver - * Update an Onfleet team -* Worker - * Create a new Onfleet worker - * Delete an Onfleet worker - * Get a specific Onfleet worker - * Get all Onfleet workers - * Get a specific Onfleet worker schedule - * Update an Onfleet worker diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.openThesaurus.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.openThesaurus.md deleted file mode 100644 index f0dfbf88e..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.openThesaurus.md +++ /dev/null @@ -1,36 +0,0 @@ -# OpenThesaurus - -[OpenThesaurus](https://www.openthesaurus.de/) is a free German dictionary for synonyms. - -!!! note "Credentials" - The OpenThesaurus node does not require authentication. - - -## Basic Operations - -* Get synonyms for a German word in German - -## Example Usage - -This workflow allows you to get synonyms of a German word in German. You can also find the [workflow](https://n8n.io/workflows/806) on the website. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [OpenThesaurus]() - -The final workflow should look like the following image. - -![A workflow with the OpenThesaurus node](/_images/integrations/builtin/app-nodes/openthesaurus/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. OpenThesaurus node - -This node will return synonyms of the word `Hallo` in German. If you want to get synonyms of another German word, use that word instead. - -1. Enter `Hallo` in the ***Text*** field. -2. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that the node returns the synonyms of the word `Hallo`. - -![Using the OpenThesaurus node to get the synonyms of the word Hallo](/_images/integrations/builtin/app-nodes/openthesaurus/openthesaurus_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap.md deleted file mode 100644 index 90e746b79..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap.md +++ /dev/null @@ -1,37 +0,0 @@ -# OpenWeatherMap - -[OpenWeatherMap](https://openweathermap.org/) is an online service that provides weather data. It provides current weather data, forecasts, and historical data. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/openWeatherMap/). - - -## Basic Operations - -* Returns the current weather data -* Returns the weather data for the next 5 days - -## Example Usage - -This workflow allows you to get the current weather data for a city. You can also find the [workflow](https://n8n.io/workflows/460) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [OpenWeatherMap]() - -The final workflow should look like the following image. - -![A workflow with the OpenWeatherMap node](/_images/integrations/builtin/app-nodes/openweathermap/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. OpenWeatherMap node - -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. Enter the name of the city in the *City* field. -3. Click on *Execute Node* to run the workflow. - - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.orbit.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.orbit.md deleted file mode 100644 index 6f27b4a0f..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.orbit.md +++ /dev/null @@ -1,117 +0,0 @@ -# Orbit - -[Orbit](https://orbit.love) is a platform for managing and growing communities. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/orbit/). - - -## Basic Operations - -* Activity - * Create an activity for a member - * Get all activities -* Member - * Delete a member - * Get a member - * Get all members in a workspace - * Lookup a member by identity - * Update a member - * Create/Update a member -* Note - * Create a note - * Get all notes for a member - * Update a note -* Post - * Create a post - * 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.oura.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.oura.md deleted file mode 100644 index 3f7f01147..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.oura.md +++ /dev/null @@ -1,95 +0,0 @@ -# Oura - -[Oura](https://www.ouraring.com/) is a wellness ring and app that helps you keep track of your activities and sleep. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/oura/). - - -## Basic Operations - -* Profile - * Get the user's personal information. -* Summary - * Get the user's activity summary. - * Get the user's readiness summary. - * Get the user's sleep summary - -## Example Usage - -This workflow allows you to get activity summary from Oura and store the output in Airtable. You can also find the [workflow](https://n8n.io/workflows/882) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [Oura]() -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Airtable](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/) - -The final workflow should look like the following image. - -![A workflow with the Oura node](/_images/integrations/builtin/app-nodes/oura/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow every Sunday at 9 AM. - -1. Click on ***Add Cron Time***. -2. Select 'Every Week' from the ***Mode*** dropdown list. -3. Enter `9` in the ***Hour*** field. -4. Select 'Sunday' from the ***Weekday*** dropdown list. -5. Click on ***Execute Node*** to run the node. - -![Using the Cron node to trigger the workflow once a week](/_images/integrations/builtin/app-nodes/oura/cron_node.png) - -### 2. Oura node (getActivity: summary) - -This node will return the activity summary of a week. - -1. First of all, you'll have to enter credentials for the Oura node. You can find out how to do that [here](/integrations/builtin/credentials/oura/). -2. Select 'Get Activity Summary' from the ***Operation*** dropdown list. -3. Toggle ***Return All*** to `true`. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the activity summary. - -![Using the Oura node to get the activity summary](/_images/integrations/builtin/app-nodes/oura/oura_node.png) - -### 3. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. - - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `Day` in the ***Name*** 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: Current Node > Input Data > JSON > summary_date. You can also add the following expression: `{{$json["summary_date"]}}`. -5. Click on ***Add Value*** and select 'String' from the dropdown list. -6. Enter `Steps` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > steps. You can also add the following expression: `{{$json["steps"]}}`. -9. Click on ***Add Value*** and select 'String' from the dropdown list. -10. Enter `Activity Score` in the ***Name*** field. -11. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > score. You can also add the following expression: `{{$json["score"]}}`. -13. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -14. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uses the data from the previous node and returns the data that we set for the workflow. - -![Using the Set node to set the data](/_images/integrations/builtin/app-nodes/oura/set_node.png) - -## 4. Airtable node (Append) - -This node will append the data that we set in the previous node to a table. Create a table like [this](https://airtable.com/shrUqFItKPlSpgrht) 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 'Append' 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 ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node appends the data that we had set in the previous node. - -![Using the Airtable node to insert data into an Airtable table](/_images/integrations/builtin/app-nodes/oura/airtable_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.paddle.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.paddle.md deleted file mode 100644 index e98a1857a..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.paddle.md +++ /dev/null @@ -1,50 +0,0 @@ -# Paddle - -[Paddle](https://www.paddle.com/) is an all-in-one SaaS Commerce platform for software and SaaS companies to run and grow their business. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/paddle/). - - -## Basic Operations - -* Coupon - * Create a coupon. - * Get all coupons. - * Update a coupon. -* Payment - * Get all payment. - * Reschedule payment. -* Plan - * Get a plan. - * Get all plans. -* Product - * Get all products. -* User - * 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 deleted file mode 100644 index 6563b1dcd..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.pagerDuty.md +++ /dev/null @@ -1,84 +0,0 @@ -# PagerDuty - -[PagerDuty](https://www.pagerduty.com/) is a cloud computing company that produces a SaaS incident response platform for IT departments. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/pagerDuty/). - - -## Basic Operations - -* Incident - * Create an incident - * Get an incident - * Get all incidents - * Update an incident -* Incident Note - * Create an incident note - * Get all incident's notes -* Log Entry - * Get a log entry - * Get all log entries -* User - * 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 deleted file mode 100644 index e5380ae56..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.payPal.md +++ /dev/null @@ -1,36 +0,0 @@ -# PayPal - -[PayPal](https://paypal.com) is a digital payment service that supports online funds transfers and that customers can use when shopping online. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/payPal/). - - -## Basic Operations - -* Payout - * Create a batch payout - * Show batch payout details -* Payout Item - * Cancels an unclaimed payout item - * Show payout item details - -## Example Usage - -This workflow shows you how to create a PayPal batch payout. You can also find the [workflow](https://n8n.io/workflows/438) on this website. This example usage workflow uses the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [PayPal]() - -The final workflow should look like the following image. - -![A workflow with the PayPal node](/_images/integrations/builtin/app-nodes/paypal/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. PayPal node - -1. First of all, you'll have to enter credentials for the PayPal node. You can find out how to do that [here](/integrations/builtin/credentials/payPal/). -2. Enter an ID in the *Sender Batch ID* field. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.peekalink.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.peekalink.md deleted file mode 100644 index b68fe19a6..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.peekalink.md +++ /dev/null @@ -1,83 +0,0 @@ -# Peekalink - -[Peekalink](https://peekalink.io) is an API that allows developers to preview links on the web. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/peekalink/). - - -## Basic Operations - -* 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.phantombuster.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.phantombuster.md deleted file mode 100644 index 23b5dddf9..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.phantombuster.md +++ /dev/null @@ -1,83 +0,0 @@ -# Phantombuster - -[Phantombuster](https://www.phantombuster.com/) is a scraping platform that allows chain actions and data extraction on the web to generate business leads, marketing audiences, and overall growth. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/phantombuster/). - - -## Basic Operations - -* Agent - * Delete an agent by ID. - * Get an agent by ID. - * Get all agents of the current user's organization. - * Get the output of the most recent container of an agent. - * Add an agent to the launch queue. - -## Example Usage - -This workflow allows you to store the output of a phantom in Airtable. You can also find the [workflow](https://n8n.io/workflows/882) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Phantombuster]() -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Airtable](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/) - -The final workflow should look like the following image. - -![A workflow with the Phantombuster node](/_images/integrations/builtin/app-nodes/phantombuster/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Phantombuster node (getOutput: agent) - -Create and launch the [LinkedIn Profile Scraper](https://phantombuster.com/automations/linkedin/3112/linkedin-profile-scraper) in your Phantombuster account. This node will return the output of this phantom. - -1. First of all, you'll have to enter credentials for the Phantombuster node. You can find out how to do that [here](/integrations/builtin/credentials/phantombuster/). -2. Select 'Get Output' from the ***Operation*** dropdown list. -3. Select a phantom from the ***Agent*** dropdown list. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the output from the LinkedIn Profile Scraper phantom. - -![Using the Phantombuster node to get the output of a phantom](/_images/integrations/builtin/app-nodes/phantombuster/phantombuster_node.png) - -### 3. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. - - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `Name` in the ***Name*** 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 > Phantombuster > Output Data > JSON > general > fullName. You can also add the following expression: `{{$node["Phantombuster"].json["general"]["fullName"]}}`. -5. Click on ***Add Value*** and select 'String' from the dropdown list. -6. Enter `Email` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > Phantombuster > Output Data > JSON > details > mail. You can also add the following expression: `{{$node["Phantombuster"].json["details"]["mail"]}}`. -9. Click on ***Add Value*** and select 'String' from the dropdown list. -10. Enter `Company` in the ***Name*** field. -11. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Nodes > Phantombuster > Output Data > JSON > jobs> [Item: 0] > companyName. You can also add the following expression: `{{$node["Phantombuster"].json["jobs"][0]["companyName"]}}`. -13. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -14. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uses the data from the previous node and returns the data that we set for the workflow. - -![Using the Set node to set the data](/_images/integrations/builtin/app-nodes/phantombuster/set_node.png) - -## 4. Airtable node (Append) - -This node will append the data that we set in the previous node to a table. Create a table like [this](https://airtable.com/shr6hP774ijrXFput) 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 'Append' 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 ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node appends the data that we had set in the previous node. - -![Using the Airtable node to insert data into an Airtable table](/_images/integrations/builtin/app-nodes/phantombuster/airtable_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 deleted file mode 100644 index a17d68c34..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.philipsHue.md +++ /dev/null @@ -1,38 +0,0 @@ -# Philips Hue - -[Philips Hue](https://www.philips-hue.com/) is a line of smart color-changing LED lamps and bulbs that can be controlled wirelessly. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/philipsHue/). - - -## Basic Operations - -* Light - * Delete a light - * Retrieve a light - * Retrieve all lights - * 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.pipedrive.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.pipedrive.md deleted file mode 100644 index c5135f009..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.pipedrive.md +++ /dev/null @@ -1,84 +0,0 @@ -# Pipedrive - -[Pipedrive](https://www.pipedrive.com/) is a cloud-based sales software company that aims to improve the productivity of businesses through the use of their software. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/pipedrive/). - - -## Basic Operations - -* Activity - * Create an activity - * Delete an activity - * Get data of an activity - * Get data of all activities - * Update an activity -* Deal - * Create a deal - * Delete a deal - * Duplicate a deal - * Get data of a deal - * Get data of all deals - * Search a deal - * Update a deal -* Deal Activity - * Get all activities of a deal -* Deal Product - * Add a product to a deal - * Get all products in a deal - * Remove a product from a deal - * Update a product in a deal -* File - * Create a file - * Delete a file - * Download a file - * Get data of a file -* Lead - * Create a lead - * Delete a lead - * Get data of a lead - * Get data of all leads - * Update a lead -* Note - * Create a note - * Delete a note - * Get data of a note - * Get data of all notes - * Update a note -* Organization - * Create an organization - * Delete an organization - * Get data of an organization - * Get data of all organizations - * Update an organization - * Search organizations -* Person - * Create a person - * Delete a person - * Get data of a person - * Get data of all persons - * Search all persons - * Update a person -* Product - * Get data of all products - -## Example Usage - -This workflow allows you to create an deal in Pipedrive. You can also find the [workflow](https://n8n.io/workflows/489) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Pipedrive]() - -The final workflow should look like the following image. - -![A workflow with the Pipedrive node](/_images/integrations/builtin/app-nodes/pipedrive/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Pipedrive node - -1. First of all, you'll have to enter credentials for the Pipedrive node. You can find out how to do that [here](/integrations/builtin/credentials/pipedrive/). -2. Enter the title of the deal in the *Title* field. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.plivo.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.plivo.md deleted file mode 100644 index b68614861..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.plivo.md +++ /dev/null @@ -1,72 +0,0 @@ -# Plivo - -[Plivo](https://www.plivo.com/) is a cloud communications platform as a service company that allows you to add SMS, MMS, and Voice calling functionality within your apps programmatically. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/plivo/). - - -## Basic Operations - -* Call - * Make a voice call -* MMS - * Send an MMS message (US/Canada only) -* SMS - * Send an SMS message. - -## Example Usage - -This workflow allows you to send daily weather updates via an SMS message using the Plivo node. You can also find the [workflow](https://n8n.io/workflows/1005) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/) -- [Plivo]() - -The final workflow should look like the following image. - -![A workflow with the Plivo node](/_images/integrations/builtin/app-nodes/plivo/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow daily at 9 AM. - -1. Click on ***Add Cron Time***. -2. Set hours to 9 in the ***Hour*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every day at 9 AM. - -![Using the Cron node to trigger the workflow daily at 9 am](/_images/integrations/builtin/app-nodes/plivo/cron_node.png) - -### 2. OpenWeatherMap node (Current Weather) - -This node will return data about the current weather in Berlin. To get the weather updates for your city, you can enter the name of your city instead. - -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. Enter `berlin` in the ***City*** field. -3. 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/plivo/openweathermap_node.png) - -### 3. Plivo node (send: sms) - -This node will send an SMS with the weather update, which was sent by the previous node. - -1. First of all, you'll have to enter credentials for the Plivo node. You can find out how to do that [here](/integrations/builtin/credentials/plivo/). -2. Enter a Plivo phone number in the ***From*** field. -3. Enter the receiver's phone number in the ***To*** field. -4. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. - -5. Enter the following message in the ***Expression*** field: `Hey! The temperature outside is {{$node["OpenWeatherMap"].json["main"]["temp"]}}°C.`. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends an SMS to the phone number that we specified with the weather update. - -![Using the Plivo node to send weather updates via SMS](/_images/integrations/builtin/app-nodes/plivo/plivo_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Cron 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 deleted file mode 100644 index c9d00b505..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.postHog.md +++ /dev/null @@ -1,64 +0,0 @@ -# PostHog - -[PostHog](https://posthog.com) is an open-source product analytics platform. It provides tools to improve your product, such as session recording, heatmaps, and feature flags. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/postHog/). - - -## Basic Operations - -* Alias - * Create an alias -* Event - * Create an event -* Identity - * Create -* Track - * 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.postbin.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.postbin.md deleted file mode 100644 index db7819697..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.postbin.md +++ /dev/null @@ -1,20 +0,0 @@ -# Postbin - -[Postbin](https://www.toptal.com/developers/postbin/){:target=_blank .external-link} is a service that collects all requests to a URL, which you can use to test your API Clients or your WebHooks. - - -## Send requests - -To send requests to a Postbin bin: - -1. Go to [Postbin](https://www.toptal.com/developers/postbin/){:target=_blank .external-link} and follow the steps to generate a new bin. Postbin gives you a unique URL, including a bin ID. -2. In the Postbin node, select the **Request** resource. -3. Choose the type of **Operation** you want to perform. -4. Enter your bin ID in **Bin ID**. - -## Create and manage bins - -You can create and manage Postbin bins using the Postbin node. - -1. In **Resource**, select **Bin**. -2. Choose an **Operation**. You can create, delete, or get a bin. \ No newline at end of file diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.postgres.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.postgres.md deleted file mode 100644 index 155f6e3ae..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.postgres.md +++ /dev/null @@ -1,104 +0,0 @@ -# Postgres - -[PostgreSQL](https://www.postgresql.org/), also known as Postgres, is a free and open-source relational database management system emphasizing extensibility and SQL compliance. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/postgres/). - - -## Basic Operations - -* Execute an SQL query -* Insert rows in database -* Update rows in database - - -## Example Usage - -This workflow allows you to run an SQL query on a Postgres instance. You can also find the [workflow](https://n8n.io/workflows/599) on n8n.io. This example usage workflow would use the following nodes. - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Postgres]() - -The final workflow should look like the following image. - -![A workflow with the Postgres node](/_images/integrations/builtin/app-nodes/postgres/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Postgres node (Execute Query) - -1. Enter credentials for the Postgres node. You can find out how to do that [here](/integrations/builtin/credentials/postgres/). -2. Select **Execute Query** from the **Operation** dropdown list. -3. Enter the following SQL query in the **Query** field: `CREATE TABLE test (id INT, name VARCHAR(255), PRIMARY KEY (id));`. -4. Click on the **Node** tab and toggle **Always Output Data** to true. -5. Click on **Execute Node** to run the node. - -![Using the Postgres node to create a table](/_images/integrations/builtin/app-nodes/postgres/postgres_node.png) - -### 3. Set node - -1. Click on the **Add Value** button and select **Number** from the dropdown list. -2. Enter `id` in the **Name** field. -3. Click on the **Add Value** button and select **String** from the dropdown list. -4. Enter `name` in the **Name** field. -5. Enter the value for the name in the **Value** field. -6. Click on **Execute Node** to run the node. - -![Using the Set node to set data to be inserted by the Postgres node](/_images/integrations/builtin/app-nodes/postgres/set_node.png) - -### 4. Postgres1 node (Insert) - -1. Select the credentials that you entered in the previous Postgres node. -2. Enter `test` in the **Table** field. -3. Enter `id, name` in the **Columns** field. -4. Click on **Execute Node** to run the node. - -![Using the Postgres node to insert data into a table](/_images/integrations/builtin/app-nodes/postgres/postgres1_node.png) - - - -## Specify the data type of a column - -To specify the data type of a column, append the column name with `:type`, where `type` is the data type of that column. For example, if you want to specify the type `int` for the column *id* and type `text` for the column *name*, you can use the following snippet in the **Columns** field: `id:init,name:text`. - -## Use query parameters - -When creating a query to run on a Postgres database, you can use the **Query Parameters** field in the **Additional Fields** section to load data into the query. n8n sanitizes data in query parameters, which prevents SQL injection. - -For example, you want to find a person by their email address. Given the following input data: - -```json -{ - { - "email": "alex@example.com", - "name": "Alex", - "age": 21 - }, - { - "email": "jamie@example.com", - "name": "Jamie", - "age": 33 - } -} -``` - -You can write a query like: - -```sql -SELECT * FROM users WHERE email = $1; -``` - -Then in **Query Parameters**, map the value to `email` by dragging and dropping the **email** column head from the **INPUT** view into **Query Parameters**: - -![Screenshot of the query parameters and input data fields](/_images/integrations/builtin/app-nodes/postgres/use-query-parameters.png) - - - - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.profitWell.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.profitWell.md deleted file mode 100644 index 1d4758a6c..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.profitWell.md +++ /dev/null @@ -1,77 +0,0 @@ -# ProfitWell - -[ProfitWell](https://www.profitwell.com/) provides real-time subscription financial metrics. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/profitWell/). - - -## Basic Operations - -* Company - * Get your companys ProfitWell account settings -* Metric - * Retrieve financial metric broken down by day for either the current month or the last - -## Example Usage - -This workflow allows you to send financial metrics monthly to a Mattermost channel. You can also find the [workflow](https://n8n.io/workflows/798) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [ProfitWell]() -- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/) - -The final workflow should look like the following image. - -![A workflow with the ProfitWell node](/_images/integrations/builtin/app-nodes/profitwell/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow on the first day of every month at 9 AM. - -1. Click on ***Add Cron Time***. -2. Select 'Every Month' from the ***Mode*** dropdown list. -3. Set hours to 9 in the ***Hour*** field. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow on the first day of every month at 9 AM. - -![Using the Cron node to trigger the workflow every month](/_images/integrations/builtin/app-nodes/profitwell/cron_node.png) - -### 2. ProfitWell node (get: metric) - -This node will return monthly financial metrics. - -1. First of all, you'll have to enter credentials for the ProfitWell node. You can find out how to do that [here](/integrations/builtin/credentials/profitWell/). -2. Select 'Monthly' from the ***Type*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns montly financial metrics. - -![Using the ProfitWell node to get monthly financial metrics](/_images/integrations/builtin/app-nodes/profitwell/profitwell_node.png) - -### 3. Mattermost node (post: message) - -This node will send a message with the metrics that we get from the previous node in the 'Monthly Metrics' channel in Mattermost. If you have a different channel, use that instead. - -1. First of all, you'll have to enter credentials for the Mattermost node. You can find out how to do that [here](/integrations/builtin/credentials/mattermost/). - -2. Select a channel from the ***Channel ID*** dropdown list. -3. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. -4. Enter the following message in the ***Expression*** field: -``` -Active Customers: {{$node["ProfitWell"].json["active_customers"]}} -Trailing Customers: {{$node["ProfitWell"].json["active_trialing_customers"]}} -New Customers: {{$node["ProfitWell"].json["new_customers"]}} -Growth Rate: {{$node["ProfitWell"].json["growth_rate"]}} -Recurring Revenue: {{$node["ProfitWell"].json["recurring_revenue"]}} -``` -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends a message with the metrics that we get from the previous node. - -![Using the Mattermost node to send a message with the metrics ](/_images/integrations/builtin/app-nodes/profitwell/mattermost_node.png) - - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.pushbullet.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.pushbullet.md deleted file mode 100644 index 760afdb06..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.pushbullet.md +++ /dev/null @@ -1,66 +0,0 @@ -# Pushbullet - -[Pushbullet](https://www.pushbullet.com/) connects your devices and allows you to see your phone's notifications on your computer, transfer links, and files between devices. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/pushbullet/). - - -## Basic Operations - -* Push - * Create a push - * Delete a push - * Get all pushes - * Update a push - -## Example Usage - -This workflow allows you to send daily weather updates via a push notification using the Pushbullet node. You can also find the [workflow](https://n8n.io/workflows/740) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/) -- [Pushbullet]() - -The final workflow should look like the following image. - -![A workflow with the Pushbullet node](/_images/integrations/builtin/app-nodes/pushbullet/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow daily at 9 AM. - -1. Click on ***Add Cron Time***. -2. Set hours to 9 in the ***Hour*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every day at 9 AM. - -![Using the Cron node to trigger the workflow daily at 9 am](/_images/integrations/builtin/app-nodes/pushbullet/cron_node.png) - -### 2. OpenWeatherMap node (Current Weather) - -This node will return data about the current weather in Berlin. To get the weather updates for your city, you can enter the name of your city instead. - -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. Enter `berlin` in the ***City*** field. -3. 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/pushbullet/openweathermap_node.png) - -### 3. Pushbullet node (create: push) - -This node will send a push notification with the weather update to the default device. If you want to send it to a specific device, select 'Device ID' from the ***Target*** dropdown list and enter the device ID in the ***Value*** field. - -1. First of all, you'll have to enter credentials for the Pushbullet node. You can find out how to do that [here](/integrations/builtin/credentials/pushbullet/). -2. Enter `Today's Weather Update` in the ***Title*** field. -3. Click on the gears icon next to the ***Body*** field and click on ***Add Expression***. - -4. Enter the following message in the ***Expression*** field: `Hey! The temperature outside is {{$node["OpenWeatherMap"].json["main"]["temp"]}}°C.`. -5. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends a push notification to the default device with the weather update. - -![Using the Pushbullet node to send weather updates via a push notification](/_images/integrations/builtin/app-nodes/pushbullet/pushbullet_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.pushcut.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.pushcut.md deleted file mode 100644 index da43ba84c..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.pushcut.md +++ /dev/null @@ -1,70 +0,0 @@ -# Pushcut - -[Pushcut](https://pushcut.io) is an app for iOS that lets you create smart notifications to kick off shortcuts, URLs, and online automation. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/pushcut/). - - -## Basic Operations - -* Notification - * Send a notification - -## Example Usage - -This workflow allows you to send daily weather updates via a push notification using the Pushcut node. You can also find the [workflow](https://n8n.io/workflows/843) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/) -- [Pushcut]() - -The final workflow should look like the following image. - -![A workflow with the Pushcut node](/_images/integrations/builtin/app-nodes/pushcut/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow daily at 9 AM. - -1. Click on ***Add Cron Time***. -2. Set hours to 9 in the ***Hour*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every day at 9 AM. - -![Using the Cron node to trigger the workflow daily at 9 am](/_images/integrations/builtin/app-nodes/pushcut/cron_node.png) - -### 2. OpenWeatherMap node (Current Weather) - -This node will return data about the current weather in Berlin. To get the weather updates for your city, you can enter the name of your city instead. - -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. Enter `berlin` in the ***City*** field. -3. 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/pushcut/openweathermap_node.png) - -### 3. Pushcut node (send: notification) - -This node will send a push notification with the weather update, which was sent by the previous node. - -1. First of all, you'll have to enter credentials for the Pushcut node. You can find out how to do that [here](/integrations/builtin/credentials/pushcut/). -2. Select a notification from the ***Notification Name*** dropdown list. -3. Click on ***Add Field*** and select 'Title' from the dropdown list. -4. Enter `Today's Weather Update` in the ***Title*** field. -5. Click on ***Add Field*** and select 'Text' from the dropdown list. -6. Click on the gears icon next to the ***Text*** field and click on ***Add Expression***. - -7. Enter the following message in the ***Expression*** field: `Hey! The temperature outside is {{$node["OpenWeatherMap"].json["main"]["temp"]}}°C.`. -8. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends a push notification to your device with the weather update. - -![Using the Pushcut node to send weather updates via a push notification](/_images/integrations/builtin/app-nodes/pushcut/pushcut_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.pushover.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.pushover.md deleted file mode 100644 index 3b254cf06..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.pushover.md +++ /dev/null @@ -1,66 +0,0 @@ -# Pushover - -[Pushover](https://www.pushover.net/) is a simple push notification service that integrates easily into web apps, network monitors, shell scripts, servers, and anything else that needs to send alerts to your Android, iPhone, iPad, and Desktop. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/pushover/). - - -## Basic Operations - -* Message - * Push - -## Example Usage - -This workflow allows you to send daily weather updates via a push notification using the Pushover node. You can also find the [workflow](https://n8n.io/workflows/740) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/) -- [Pushover]() - -The final workflow should look like the following image. - -![A workflow with the Pushover node](/_images/integrations/builtin/app-nodes/pushover/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow daily at 9 AM. - -1. Click on ***Add Cron Time***. -2. Set hours to 9 in the ***Hour*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every day at 9 AM. - -![Using the Cron node to trigger the workflow daily at 9 am](/_images/integrations/builtin/app-nodes/pushover/cron_node.png) - -### 2. OpenWeatherMap node (Current Weather) - -This node will return data about the current weather in Berlin. To get the weather updates for your city, you can enter the name of your city instead. - -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. Enter `berlin` in the ***City*** field. -3. 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/pushover/openweathermap_node.png) - -### 3. Pushover node (push: message) - -This node will send a push notification with the weather update, which was sent by the previous node. - -1. First of all, you'll have to enter credentials for the Pushover node. You can find out how to do that [here](/integrations/builtin/credentials/pushover/). -2. Enter a user key in the ***User Key*** field. You can obtain your user key from the [Pushover Dashboard](https://www.pushover.net/). -3. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. - -5. Enter the following message in the ***Expression*** field: `Hey! The temperature outside is {{$node["OpenWeatherMap"].json["main"]["temp"]}}°C.`. -6. Select 'Normal Priority' from the ***Priority*** dropdown list. This will trigger sound, vibration, and display an alert according to the user's device settings. -7. Click on ***Add Field*** and select 'Title' from the dropdown list. -8. Enter `Today's Weather` in the ***Title*** field. -9. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends a push notification to a device with the weather update. - -![Using the Pushover node to send weather updates via a push notification](/_images/integrations/builtin/app-nodes/pushover/pushover_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.questDb.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.questDb.md deleted file mode 100644 index c3d20ba88..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.questDb.md +++ /dev/null @@ -1,69 +0,0 @@ -# QuestDB - -[QuestDB](https://questdb.io/) is an open-source NewSQL relational database designed to process time-series data, faster. QuestDB's stack is engineered from scratch, zero-GC Java and dependency-free. It supports a a Java API, SQL via HTTP and the PostgreSQL wire protocol. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/questDb/). - - -## Basic Operations - -* Executes a SQL query. -* Insert rows in database. - -## Example Usage - -This workflow allows you to create a table and insert data into it in QuestDB. You can also find the [workflow](https://n8n.io/workflows/592) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [QuestDB]() - -The final workflow should look like the following image. - -![A workflow with the QuestDB node](/_images/integrations/builtin/app-nodes/questdb/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. QuestDB node (Execute Query) - -1. First of all, you'll have to enter credentials for the QuestDB node. You can find out how to do that [here](/integrations/builtin/credentials/questDb/). -2. Select 'Execute Query' from the ***Operation*** dropdown list. -3. Enter the following SQL query in the ***Query*** field: `CREATE TABLE test (id INT, name STRING);`. -4. Click on the ***Node*** tab and toggle ***Always Output Data*** to true. -5. Click on ***Execute Node*** to run the node. - -![Using the QuestDB node to create a table](/_images/integrations/builtin/app-nodes/questdb/questdb_node.png) - - -### 3. Set node - -1. Click on the ***Add Value*** button and select 'Number' from the dropdown list. -2. Enter `id` in the ***Name*** field. -3. Click on the ***Add Value*** button and select 'String' from the dropdown list. -4. Enter `name` in the ***Name*** field. -5. Enter the value for the name in the ***Value*** field. -6. Click on ***Execute Node*** to run the node. - -![Using the Set node to set data to be inserted by the QuestDB node](/_images/integrations/builtin/app-nodes/questdb/set_node.png) - - -### 4. QuestDB1 node (Insert) - -1. Select the credentials that you entered in the previous QuestDB node. -2. Enter `test` in the ***Table*** field. -3. Enter `id, name` in the ***Columns*** field. -4. Click on ***Execute Node*** to run the node. - -![Using the QuestDB node to insert data into a table](/_images/integrations/builtin/app-nodes/questdb/questdb1_node.png) - -## FAQs - -### How to specify the data type of a column? -To specify the data type of a column, append the column name with `:type`, where `type` is the data type of that column. For example, if you want to specify the type `int` for the column *id* and type `text` for the column *name*, you can use the following snippet in the ***Columns*** field: `id:init,name:text`. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.quickbase.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.quickbase.md deleted file mode 100644 index 31bb048e4..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.quickbase.md +++ /dev/null @@ -1,123 +0,0 @@ -# Quick Base - -[Quick Base](https://www.quickbase.com/) is a low-code application development platform. It allows you to connect data, integrate your systems in real-time, and orchestrate automated workflows using simple business logic. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/quickbase/). - - -## Basic Operations - -* Field - * Get all fields -* File - * Delete a file - * Download a file -* Record - * Create a record - * Delete a record - * Get all records - * Update a record - * Upsert a record -* Report - * Get a report - * Run a report - -## Example Usage - -This workflow allows you to create, update, and get all records in Quick Base. You can also find the [workflow](https://n8n.io/workflows/805) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Quick Base]() - -The final workflow should look like the following image. - -![A workflow with the Quick Base node](/_images/integrations/builtin/app-nodes/quickbase/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Set node - -We will use the Set node to set the name and age for a new record. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `name` in the ***Name*** field. -3. Enter `n8n` in the ***Value*** field. -4. Click on ***Add Value*** and select 'Number' from the dropdown list. -5. Enter `age` in the ***Name*** field. -6. Set the value to `8`. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that node sets the value for name and age. - -![Using the Set node to set the data](/_images/integrations/builtin/app-nodes/quickbase/set_node.png) - -### 3. Quick Base node (create: record) - -This node will create a new record in a table. - -#### Creating a Quick Base table -1. Create a new table with the fields `name` and `age`. -2. Copy the string of characters located between `db/` and `?a=td` in your Quick Base URL. This string is the Table ID that we will use in the Quick Base node. - -#### Configure the Quick Base node -1. First of all, you'll have to enter credentials for the Quick Base node. You can find out how to do that [here](/integrations/builtin/credentials/quickbase/). -2. Paste the Table ID you copied in the previous step, in the ***Table ID*** field. -3. Enter `name,age` in the ***Columns*** field. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new record in Quick Base using the information from the previous node. - -![Using the Quick Base node to create an entry](/_images/integrations/builtin/app-nodes/quickbase/quickbase_node.png) - -### 4. Set1 node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. We will set the value of `age` and `Record ID#` in this node. - -1. Click on ***Add Value*** and select 'Number' from the dropdown list. -2. Enter `age` in the ***Name*** field. -3. Set the value to `10`. -4. Click on ***Add Value*** and select 'Number' from the dropdown list. -5. Enter `Record ID#` in the ***Name*** field. -6. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -7. Select the following in the ***Variable Selector*** section: Nodes > Quick Base > Output Data > JSON > Record ID#. You can also add the following expression: `{{$node["Quick Base"].json["Record ID#"]}}`. -8. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -9. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sets the value of `age` and `Record ID#`. This value is passed to the next node in the workflow. - -![Using the Set node to set the values for age and Record ID#](/_images/integrations/builtin/app-nodes/quickbase/set1_node.png) - -### 5. Quick Base1 node (update: record) - -This node will update the age field with the new value that we set 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 ***Table ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Quick Base > Parameters > tableId. You can also add the following expression: `{{$node["Quick Base"].parameter["tableId"]}}`. -5. Enter `age` in the ***Columns*** field. If you want to update a different column, enter that column name instead. -6. Enter `Record ID#` in the ***Update Key*** field. -7. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node updates the age field with the new value that we set in the previous node. - -![Using the Quick Base node to update an entry](/_images/integrations/builtin/app-nodes/quickbase/quickbase1_node.png) - -### 6. Quick Base2 node (getAll: record) - -This node returns all the records from Quick Base. - -1. Select the credentials that you entered in the previous node. -2. Select 'Get All' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Table ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Quick Base > Parameters > tableId. You can also add the following expression: `{{$node["Quick Base"].parameter["tableId"]}}`. -5. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns all the records from Quick Base. - -![Using the Quick Base node to get all the records](/_images/integrations/builtin/app-nodes/quickbase/quickbase2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.quickbooks.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.quickbooks.md deleted file mode 100644 index d68e99ca2..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.quickbooks.md +++ /dev/null @@ -1,133 +0,0 @@ -# QuickBooks - -[QuickBooks](https://quickbooks.intuit.com) is an accounting software package developed by Intuit. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/quickbooks/). - - -## Basic Operations - -* Bill - * Create - * Delete - * Get - * Get All - * Update -* Customer - * Create - * Get - * Get All - * Update -* Employee - * Create - * Get - * Get All - * Update -* Estimate - * Create - * Delete - * Get - * Get All - * Send - * Update -* Invoice - * Create - * Delete - * Get - * Get All - * Send - * Update - * Void -* Item - * Get - * Get All -* Payment - * Create - * Delete - * Get - * Get All - * Send - * Update - * Void -* Purchase - * Get - * Get All -* Transaction - * Get Report -* Vendor - * Create - * Get - * Get All - * Update - -## Example Usage - -This workflow allows you to create a customer and an invoice, and send the invoice to the customer. You can also find the [workflow](https://n8n.io/workflows/949) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [QuickBooks]() - -The final workflow should look like the following image. - -![A workflow with the QuickBooks node](/_images/integrations/builtin/app-nodes/quickbooks/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. QuickBooks node (create:customer) - -This node will create a new customer in QuickBooks. - -1. First of all, you'll have to enter credentials for the QuickBooks node. You can find out how to do that [here](/integrations/builtin/credentials/quickbooks/). -2. Select 'Create' from the ***Operation*** dropdown list. -3. Enter a display name in the ***Display Name*** field. -4. Click on the ***Add Field*** button and select 'Primary Email Address'. -5. Enter the email address of the customer in the ***Primary Email Address*** field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new customer. - -![Using the QuickBooks node to create a new customer](/_images/integrations/builtin/app-nodes/quickbooks/quickbooks_node.png) - -### 3. QuickBooks1 node (create:invoice) - -This node will create an invoice for the customer that we created in the previous node. - - -1. Select the credentials that you entered in the previous node. -2. Select 'Invoice' from the ***Resource*** dropdown list. -3. Select 'Create' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***For Customer*** 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 the ***Add Item*** button. -7. Select 'Item' from the ***Add Line Item Property*** dropdown list. -8. Select an item from the ***Item*** dropdown list. -9. Select 'Amount' from the ***Add Line Item Property*** dropdown list. -10. Enter an amount in the ***Amount*** field. -11. Select 'Detail Type' from the ***Add Line Item Property*** dropdown list. -12. Select a type from the ***Detail Type*** dropdown list. -13. Select 'Description' from the ***Add Line Item Property*** dropdown list. -14. Enter a description in the ***Description*** field. -15. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates an invoice for the customer that we created in the previous node. - -![Using the QuickBooks node to create a new invoice](/_images/integrations/builtin/app-nodes/quickbooks/quickbooks1_node.png) - -### 4. QuickBooks2 node (send:invoice) - -This node will send the invoice that we created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Invoice' from the ***Resource*** dropdown list. -3. Select 'Send' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Invoice 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. Enter the email address of the customer in the ***Email*** field. -7. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends the invoice to the customer. - -![Using the QuickBooks node to send an invoice to a customer](/_images/integrations/builtin/app-nodes/quickbooks/quickbooks2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.rabbitmq.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.rabbitmq.md deleted file mode 100644 index feffd90b2..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.rabbitmq.md +++ /dev/null @@ -1,89 +0,0 @@ -# RabbitMQ - -[RabbitMQ](https://www.rabbitmq.com) is an open-source message broker that accepts and forwards messages. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/rabbitmq/). - - -## Example Usage - -This workflow allows you to send updates about the position of the ISS every minute to a queue using the RabbitMQ node. You can also find the [workflow](https://n8n.io/workflows/844) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [RabbitMQ]() - -The final workflow should look like the following image. - -![A workflow with the RabbitMQ node](/_images/integrations/builtin/app-nodes/rabbitmq/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow every minute. - -1. Click on ***Add Cron Time***. -2. Select 'Every Minute' from the ***Mode*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every minute. - -![Using the Cron node to trigger the workflow every minute](/_images/integrations/builtin/app-nodes/rabbitmq/cron_node.png) - -### 2. HTTP Request node (GET) - -This node will make a GET request to the API `https://api.wheretheiss.at/v1/satellites/25544/positions` to fetch the position of the ISS. This information gets passed on to the next node in the workflow. - -1. Enter `https://api.wheretheiss.at/v1/satellites/25544/positions` in the ***URL*** field. -2. Click on the ***Add Parameter*** button in the ***Query Parameters*** section. -3. Enter `timestamps` in the ***Name*** field. -4. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -5. Enter the following expression: `{{Date.now()}}`. This expression will return the current timestamp. -6. 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 the information about the location of the ISS. - -![Using the HTTP Request node to get the information about the location of the ISS](/_images/integrations/builtin/app-nodes/rabbitmq/httprequest_node.png) - -### 3. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `Name` in the ***Name*** 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 > HTTP Request > Output Data > JSON > 0 > name. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["name"]}}`. -5. Click on ***Add Value*** and select 'String' from the dropdown list. -6. Enter `Latitude` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > 0 > latitude. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["latitude"]}}`. -9. Click on ***Add Value*** and select 'String' from the dropdown list. -10. Enter `Longitude` in the ***Name*** field. -11. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > 0 > longitude. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["longitude"]}}`. -13. Click on ***Add Value*** and select 'String' from the dropdown list. -14. Enter `Timestamp` in the ***Name*** field. -15. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -16. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > 0 > timpestamp. You can also add the following expression: `{{$node["HTTP Request"].json["0"]["timestamp"]}}`. -17. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -18. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uses the data from the previous node and returns the data that we set for the workflow. - -![Using the Set node to set the data](/_images/integrations/builtin/app-nodes/rabbitmq/set_node.png) - -### 4. RabbitMQ node - -This node will send the data from the previous node to the `iss-position` queue in RabbitMQ. If you have created a queue with a different name in RabbitMQ, you can use that queue instead. - -1. First of all, you'll have to enter credentials for the RabbitMQ node. You can find out how to do that [here](/integrations/builtin/credentials/rabbitmq/). -2. Enter the name of the queue or topic in the ***Queue / Topic*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends the data from the previous node to the `iss-position` queue in RabbitMQ. - -![Using the RabbitMQ node to send the data to a queue](/_images/integrations/builtin/app-nodes/rabbitmq/rabbitmq_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.raindrop.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.raindrop.md deleted file mode 100644 index 229d35137..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.raindrop.md +++ /dev/null @@ -1,106 +0,0 @@ -# Raindrop - -[Raindrop](https://raindrop.io) is a bookmarking tool that allows you to organize your bookmarks. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/raindrop/). - - -## Basic Operations - -* Bookmark - * Create - * Delete - * Get - * Get All - * Update -* Collection - * Create - * Delete - * Get - * Get All - * Update -* Tag - * Delete - * Get All -* 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 deleted file mode 100644 index 0afd817be..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.reddit.md +++ /dev/null @@ -1,87 +0,0 @@ -# Reddit - -[Reddit](https://www.reddit.com) is a social news aggregation, web content rating, and discussion website. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/reddit/). - - -## Basic Operations - -* Post - * Submit a post to a subreddit - * Delete a post from a subreddit - * Get a post from a subreddit - * Get all posts from a subreddit - * Search posts in a subreddit or in all of Reddit. -* Post Comment - * Create a top-level comment in a post - * Retrieve all comments in a post - * Remove a comment from a post - * Write a reply to a comment in a post -* Profile - * Get -* Subreddit - * Retrieve background information about a subreddit. - * Retrieve information about subreddits from all of Reddit. -* 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 deleted file mode 100644 index 3a0bfb07e..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.redis.md +++ /dev/null @@ -1,43 +0,0 @@ -# Redis - -[Redis](https://redis.io/) is an open-source, in-memory data structure store, used as a database, cache and message broker. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/redis/). - - -## Basic Operations - -* Delete a key from Redis. -* Get the value of a key from Redis. -* Returns generic information about the Redis instance. -* Atomically increments a key by 1. Creates the key if it does not exist. -* Returns all the keys matching a pattern. -* Set the value of a key in redis. -* Publish message to redis channel. - - -## Example Usage - -This workflow allows you to get the value of a key in Redis. You can also find the [workflow](https://n8n.io/workflows/557) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Redis]() - -The final workflow should look like the following image. - -![A workflow with the Redis node](/_images/integrations/builtin/app-nodes/redis/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Redis node - -1. First of all, you'll have to enter credentials for the Redis node. You can find out how to do that [here](/integrations/builtin/credentials/redis/). -2. Select the 'Get' option from the *Operation* dropdown list. -3. Enter the key for which you want to retrieve the value in the *Key* field. -4. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.rocketchat.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.rocketchat.md deleted file mode 100644 index e8ce44818..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.rocketchat.md +++ /dev/null @@ -1,38 +0,0 @@ -# Rocket.Chat - -[Rocket.Chat](https://rocket.chat/) is a free and open source team chat collaboration platform that allows users to communicate securely in real-time across devices. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/rocketchat/). - - -## Basic Operations - -* 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.rundeck.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.rundeck.md deleted file mode 100644 index 12494069c..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.rundeck.md +++ /dev/null @@ -1,46 +0,0 @@ -# Rundeck - -[Rundeck](https://www.rundeck.com/) is an open-source runbook automation for incident management, business continuity, and self-service operations. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/rundeck/). - - -## Basic Operations - -**Job** -- Execute a job -- Get metadata of a job - - -## Example Usage - -This workflow allows you to execute a job on Rundeck. You can also find the [workflow](https://n8n.io/workflows/539) on this website. This example usage workflow uses the following two nodes. - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Rundeck]() - -The final workflow should look like the following image. - -![A workflow with the Rundeck node](/_images/integrations/builtin/app-nodes/rundeck/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Rundeck node - -1. First of all, you'll have to enter credentials for the Rundeck node. You can find out how to do that [here](/integrations/builtin/credentials/rundeck/). -2. Enter your Rundeck job ID in the *Job Id* field. You can find instructions on how to obtain the job ID in the FAQs below. -3. Click on *Execute Node* to run the workflow. - -## FAQs - -### How do I find the Job ID? - -1. Access your Rundeck dashboard. -2. Open the project that contains the job you want to use with n8n. -3. In the sidebar, click on 'JOBS'. -4. Under 'All Jobs', click on the name of the job you want to use with n8n. -5. In the top left corner, under the name of the job, copy the string that is displayed in smaller font below the job name. This is your job ID. -6. Paste this job ID in the `Job Id` field in n8n. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.s3.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.s3.md deleted file mode 100644 index c1c85b660..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.s3.md +++ /dev/null @@ -1,83 +0,0 @@ -# S3 - -S3 is an object storage service that allows you to block public access to all of your objects at the bucket or the account level with S3 Block Public Access. S3 maintains compliance programs, such as PCI-DSS, HIPAA/HITECH, FedRAMP, EU Data Protection Directive, and FISMA, to help you meet regulatory requirements. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/s3/). - - -## Basic Operations - -* Bucket - * Create a bucket - * Delete a bucket - * Get all buckets - * Search within a bucket -* File - * Copy a file - * Delete a file - * Download a file - * Get all files - * Upload a file -* Folder - * Create a folder - * Delete a folder - * Get all folders - -**Note:** To attach a file for upload, you will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to pass the file as a data property. - -## Example Usage - -This workflow allows you to upload a file to an S3 compatible server and get a list of all the files in a bucket using the S3 node. You can also find the [workflow](https://n8n.io/workflows/674) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [S3]() - -The final workflow should look like the following image. - -![A workflow with the S3 node](/_images/integrations/builtin/app-nodes/s3/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. HTTP Request node (GET) - -1. Enter the URL of the file in the ***URL*** field. -2. Select 'File' from the ***Response Format*** field. -3. Click on ***Execute Node*** to run the node. - -![Using the HTTP Request node to get a file](/_images/integrations/builtin/app-nodes/s3/httprequest_node.png) - - -### 3. S3 node (upload: file) - -1. First of all, you'll have to enter credentials for the S3 node. You can find out how to do that [here](/integrations/builtin/credentials/s3/). -2. Select 'Upload' from the ***Operation*** dropdown list. -3. Enter the bucket name in the ***Bucket Name*** field. -4. Click on the gears icon next to the ***File Name*** field and click on ***Add Expression***. - -5. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > Binary > data > fileName. You can also add the following expression: `{{$node["HTTP Request"].binary.data.fileName}}` -6. Click on ***Execute Node*** to run the node. - - -![Using the S3 node to upload a file to a bucket](/_images/integrations/builtin/app-nodes/s3/s3_node.png) - -### 4. S node (getAll: file) - -1. Select the credentials that you entered in the previous node. -2. Select 'Get All' from the ***Operation*** dropdown list. -3. Enter the bucket name in the ***Bucket Name*** field. -4. Toggle ***Return All*** to true. -5. Click on ***Execute Node*** to run the node. - -![Using the S3 node to get a list of all the files in a bucket](/_images/integrations/builtin/app-nodes/s3/s_node.png) - -## FAQs - -### Setting file permissions in Wasabi - -When uploading files to [Wasabi](https://wasabi.com/), permissions for the files must be set using the **ACL** dropdown and not the toggles. - -![File permissions when using the S3 node with Wasabi](/_images/integrations/builtin/app-nodes/s3/acl_dropdown.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.salesforce.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.salesforce.md deleted file mode 100644 index 369ae4f2c..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.salesforce.md +++ /dev/null @@ -1,146 +0,0 @@ -# Salesforce - -[Salesforce](https://www.salesforce.com/) is a cloud-based software company. It provides customer relationship management service and also sells a complementary suite of enterprise applications focused on customer service, marketing automation, analytics, and application development. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/salesforce/). - - -## Basic Operations - -* Account - * Add note to an account - * Create an account - * Create a new account, or update the current one if it already exists (upsert) - * Get an account - * Get all accounts - * Returns an overview of account's metadata. - * Delete an account - * Update an account -* Attachment - * Create a attachment - * Delete a attachment - * Get a attachment - * Get all attachments - * Returns an overview of attachment's metadata. - * Update a attachment -* Case - * Add a comment to a case - * Create a case - * Get a case - * Get all cases - * Returns an overview of case's metadata - * Delete a case - * Update a case -* Contact - * Add lead to a campaign - * Add note to a contact - * Create a contact - * Create a new contact, or update the current one if it already exists (upsert) - * Delete a contact - * Get a contact - * Returns an overview of contact's metadata - * Get all contacts - * Update a contact -* Custom Object - * Create a custom object record - * Create a new record, or update the current one if it already exists (upsert) - * Get a custom object record - * Get all custom object records - * Delete a custom object record - * Update a custom object record -* Document - * Upload a document -* Flow - * Get all flows - * Invoke a flow -* Lead - * Add lead to a campaign - * Add note to a lead - * Create a lead - * Create a new lead, or update the current one if it already exists (upsert) - * Delete a lead - * Get a lead - * Get all leads - * Returns an overview of Lead's metadata - * Update a lead -* Opportunity - * Add note to an opportunity - * Create an opportunity - * Create a new opportunity, or update the current one if it already exists (upsert) - * Delete an opportunity - * Get an opportunity - * Get all opportunities - * Returns an overview of opportunity's metadata - * Update an opportunity -* Search - * Execute a SOQL query that returns all the results in a single response -* Task - * Create a task - * Delete a task - * Get a task - * Get all tasks - * Returns an overview of task's metadata - * Update a task -* User - * Get a user - * Get all users - -## Working with Salesforce custom fields - -To add custom fields to your request: - -1. Select **Additional Fields** > **Add Field**. -2. In the dropdown, select **Custom Fields**. - -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.salesmate.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.salesmate.md deleted file mode 100644 index 2ec1e65e9..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.salesmate.md +++ /dev/null @@ -1,50 +0,0 @@ -# Salesmate - -[Salesmate](https://www.salesmate.io/) is a cloud-based CRM solution that caters to small and midsize businesses across various industries. Key features include contact management, sales pipeline management, email marketing and internal chat and phone integration. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/salesmate/). - - -## Basic Operations - -* Activity - * Create an activity - * Delete an activity - * Get an activity - * Get all companies - * Update an activity -* Company - * Create a company - * Delete a company - * Get a company - * Get all companies - * Update a company -* Deal - * Create a deal - * Delete a deal - * Get a deal - * Get all deals - * Update a deal - -## Example Usage - -This workflow allows you to create a company in Salesmate. You can also find the [workflow](https://n8n.io/workflows/500) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Salesmate]() - -The final workflow should look like the following image. - -![A workflow with the Salesmate node](/_images/integrations/builtin/app-nodes/salesmate/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Salesmate node - -1. First of all, you'll have to enter credentials for the Salesmate node. You can find out how to do that [here](/integrations/builtin/credentials/salesmate/). -2. Select the 'Company' option from the *Resource* dropdown list. -3. Enter the name of the company in the *Name* field. -4. Select the owner from the *Owner* dropdown list. -5. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.seaTable.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.seaTable.md deleted file mode 100644 index 00f838f61..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.seaTable.md +++ /dev/null @@ -1,16 +0,0 @@ -# SeaTable - -[SeaTable](https://seatable.co) is a collaborative database application with a spreadsheet interface. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/seaTable/). - - -## Basic operations - -* Row - * Create - * Delete - * Get - * Get All - * Update diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.securityScorecard.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.securityScorecard.md deleted file mode 100644 index aaef9f408..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.securityScorecard.md +++ /dev/null @@ -1,94 +0,0 @@ -# SecurityScorecard - -[SecurityScorecard](https://securityscorecard.com) enables organizations to prove and maintain compliance with leading regulations and standards mandates that include PCI, NIST, SOX, GDPR, and many others. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/securityScorecard/). - - -## Basic Operations - -* Company - * Get company factor scores and issue counts - * Get company's historical factor scores - * Get company's historical scores - * Get company information and summary of their scorecard - * Get company's score improvement plan -* Industry - * Get Factor Scores - * Get Historical Factor Scores - * Get Score -* Invite - * Create an invite for a company/user -* Portfolio - * Create a portfolio - * Delete a portfolio - * Get all portfolios - * Update a portfolio -* Portfolio Company - * Add a company to portfolio - * Get all companies in a portfolio - * Remove a company from portfolio -* Report - * Download a generated report - * 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.segment.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.segment.md deleted file mode 100644 index 770c1412d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.segment.md +++ /dev/null @@ -1,39 +0,0 @@ -# Segment - -[Segment](https://segment.com/) is a customer data platform (CDP) that helps you collect, clean, and control your customer data. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/segment/). - - -## Basic Operations - -* Group - * Add a user to a group -* Identify - * Create an identity -* Track - * Record the actions your users perform. Every action triggers an event, which can also have associated properties. - * Record page views on your website, along with optional extra information about the page being viewed. - -## Example Usage - -This workflow allows you to track an event in Segment. You can also find the [workflow](https://n8n.io/workflows/495) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Segment]() - -The final workflow should look like the following image. - -![A workflow with the Segment node](/_images/integrations/builtin/app-nodes/segment/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Segment node - -1. First of all, you'll have to enter credentials for the Segment node. You can find out how to do that [here](/integrations/builtin/credentials/segment/). -2. Select the 'Track' option from the *Resource* dropdown list. -3. Enter the ID of the user in the *User ID* field. -4. Enter the name of event in the *Event* field. -5. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.sendGrid.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.sendGrid.md deleted file mode 100644 index 182212b27..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.sendGrid.md +++ /dev/null @@ -1,88 +0,0 @@ -# SendGrid - -[SendGrid](https://SendGrid.co) provides a cloud-based service that assists businesses with email delivery. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/sendgrid/). - - -## Basic Operations - -* Contact - * Create/update a contact - * Delete a contact - * Get a contact by ID - * Get all contacts -* List - * Create a list - * Delete a list - * Get a list - * Get all lists - * Update a list -* Mail - * Send an email. - -## Example Usage - -This workflow allows you to create, update and get a contact using the SendGrid node. You can also find the [workflow](https://n8n.io/workflows/901) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [SendGrid]() - -The final workflow should look like the following image. - -![A workflow with the SendGrid node](/_images/integrations/builtin/app-nodes/sendgrid/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. SendGrid node (upsert:contact) - -This node will create a contact in SendGrid. - -1. First of all, you'll have to enter credentials for the SendGrid node. You can find out how to do that [here](/integrations/builtin/credentials/sendgrid/). -2. Select 'Contact' from the ***Resource*** dropdown list. -3. Select 'Create/Update' from the ***Operation*** dropdown list. -4. Enter an email address in the ***Email*** field. -5. Click on the ***Add Field*** button and select 'First Name'. -6. Enter the name of the contact in the ***First Name*** field. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates contact with their first name. - -![Using the SendGrid node to create a new contact](/_images/integrations/builtin/app-nodes/sendgrid/sendgrid_node.png) - -### 3. SendGrid1 node (upsert:contact) - -This node will update the contact that we created in the previous node. - - -1. Select the credentials that you entered in the previous node. -2. Select 'Contact' from the ***Resource*** dropdown list. -3. Select 'Create/Update' 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 > SendGrid > Parameters > email. You can also add the following expression: `{{$node["SendGrid"].parameter["email"]}}`. -6. Click on the ***Add Field*** button and select 'Last Name'. -7. Enter the last name of the contact in the ***Last Name*** field. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node updates the contact that we created in the previous node. - -![Using the SendGrid node to update a contact](/_images/integrations/builtin/app-nodes/sendgrid/sendgrid1_node.png) - -### 4. SendGrid2 node (get:contact) - -This node will return the information of the contact that we created using the SendGrid node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Contact' from the ***Resource*** dropdown list. -3. Select 'Get' from the ***Operation*** dropdown list. -4. Select 'Email' from the ***By*** dropdown list. -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 > SendGrid > Parameters > email. You can also add the following expression: `{{$node["SendGrid"].parameter["email"]}}`. -7. 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 SendGrid node. - -![Using the SendGrid node to get information of a contact](/_images/integrations/builtin/app-nodes/sendgrid/sendgrid2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.sendInBlue.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.sendInBlue.md deleted file mode 100644 index ef31b6ffc..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.sendInBlue.md +++ /dev/null @@ -1,28 +0,0 @@ -# Sendinblue - -Sendinblue is a digital marketing platform to help users grow their business. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/sendInBlue/). - -## Operations - -* Contact - * Create - * Create or Update - * Delete - * Get - * Get All - * Update -* Contact Attribute - * Create - * Delete - * Get All - * Update -* Email - * Send - * Send Template -* Sender - * Create - * Delete - * Get All \ No newline at end of file diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.sendy.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.sendy.md deleted file mode 100644 index e9adfb3a8..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.sendy.md +++ /dev/null @@ -1,70 +0,0 @@ -# Sendy - -[Sendy](https://sendy.co) is a self-hosted email newsletter application that lets you send trackable emails via AWS SES. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/sendy/). - - -## Basic Operations - -* Campaign - * Create a campaign -* Subscriber - * Add a subscriber to a list - * Count subscribers - * Delete a subscriber from a list - * 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.sentryIo.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.sentryIo.md deleted file mode 100644 index 925811d74..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.sentryIo.md +++ /dev/null @@ -1,82 +0,0 @@ -# Sentry.io - -[Sentry.io](https://sentry.io) is a service that helps you monitor and fix crashes in realtime. Sentry's platform helps every developer diagnose, fix, and optimize the performance of their code. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/sentryIo/). - - -## Basic Operations - -* Event - * Get event by ID - * Get all events -* Issue - * Delete an issue - * Get issue by ID - * Get all issues - * Update an issue -* Project - * Create a new project - * Delete a project - * Get project by ID - * Get all projects - * Update a project -* Release - * Create a release - * Delete a release - * Get release by version identifier - * Get all releases - * Update a release -* Organization - * Create an organization - * Get organization by slug - * Get all organizations - * Update an organization -* Team - * Create a new team - * Delete a team - * Get team by slug - * Get all teams - * Update a team - -## Example Usage - -This workflow allows you to create a release and get all releases using the Sentry.io node. You can also find the [workflow](https://n8n.io/workflows/643) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Sentry.io]() - -The final workflow should look like the following image. - -![A workflow with the Sentry.io node](/_images/integrations/builtin/app-nodes/sentryio/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Sentry.io node (create: release) - -1. First of all, you'll have to enter credentials for the Sentry.io node. You can find out how to do that [here](/integrations/builtin/credentials/sentryIo/). -2. Select 'Release' from the ***Resource*** dropdown list. -3. Select 'Create' from the ***Operation*** dropdown list. -4. Select the organization from the ***Organization Slug*** dropdown list. -5. Enter the version in the ***Version*** field. -6. Enter the URL that points to the release in the ***URL*** field. -7. Select the project from ***Projects*** dropdown list. -8. Click on ***Execute Node*** to run the node. - -![Using the Sentry.io node to create a release](/_images/integrations/builtin/app-nodes/sentryio/sentry.io_node.png) - - - -### 2. Sentry.io node (getAll: release) - -1. Select the credentials that you entered in the previous Sentry.io node. -2. Select 'Release' from the ***Resource*** dropdown list. -3. Select 'Get All' from the ***Operation*** dropdown list. -4. Select the organization from the ***Organization Slug*** dropdown list. -5. Toggle ***Return All*** to true. -6. Click on ***Execute Node*** to run the node. - - -![Using the Sentry.io node to get all releases](/_images/integrations/builtin/app-nodes/sentryio/sentry.io1_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.serviceNow.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.serviceNow.md deleted file mode 100644 index 27b868297..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.serviceNow.md +++ /dev/null @@ -1,66 +0,0 @@ -# ServiceNow - -[ServiceNow](https://www.servicenow.com/) is a cloud computing platform to help companies manage digital workflows for their operations. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/serviceNow/). - - -## Basic operations - -* Business Service - * Get All -* Configuration Items - * Get All -* Department - * Get All -* Dictionary - * Get All -* Incident - * Create - * Delete - * Get - * Get All - * Update -* Table Record - * Create - * Delete - * Get - * Get All - * Update -* User - * Create - * Delete - * Get - * Get All - * Update -* User Group - * Get All -* User Role - * Get All - -## Example usage - -This workflow allows you to get the 50 most recent incidents and view only the desired fields. This example usage workflow uses the following nodes: - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [ServiceNow]() - -The final workflow should look like the following image. - -![A workflow with the ServiceNow node](/_images/integrations/builtin/app-nodes/servicenow/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. ServiceNow node - -1. First enter credentials, you can find out how to do that [here](/integrations/builtin/credentials/serviceNow/). -2. Select **Incident** from the ***Resource*** dropdown. -3. Select **Get All** from the ***Operation*** dropdown. -4. Click ***Add Option*** and select **Fields**. -5. Use the dropdown to select the fields you want to view, here we used `Close code`, `Severity`, `Sys ID`, and `Resolve time`. -6. Click on ***Execute Node*** to run the workflow. - -![The ServiceNow node](/_images/integrations/builtin/app-nodes/servicenow/servicenow_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.shopify.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.shopify.md deleted file mode 100644 index 9b7fcd5a7..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.shopify.md +++ /dev/null @@ -1,43 +0,0 @@ -# Shopify - -[Shopify](https://www.shopify.com/) is an e-commerce platform that allows users to set up an online store and sell their products. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/shopify/). - - -## Basic Operations - -* Order - * Create an order - * Delete an order - * Get an order - * Get all orders - * Update an order -* Product - * Create a product - * Delete a product - * Get a product - * Get all products - * Update a product - -## Example Usage - -This workflow allows you to get all orders from Shopify. You can also find the [workflow](https://n8n.io/workflows/548) on the website. This example usage workflow uses the following two nodes. - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Shopify]() - -The final workflow should look like the following image. - -![A workflow with the Shopify node](/_images/integrations/builtin/app-nodes/shopify/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Shopify node - -1. First of all, you'll have to enter credentials for the Shopify node. You can find out how to do that [here](/integrations/builtin/credentials/shopify/). -2. Select 'Get All' from the *Operation* dropdown list. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.signl4.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.signl4.md deleted file mode 100644 index 06aed15b5..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.signl4.md +++ /dev/null @@ -1,35 +0,0 @@ -# SIGNL4 - -[SIGNL4](https://www.signl4.com/) is a plug-and-play cloud solution produced by Derdack. It automatically notifies teams on their mobile devices in case of critical events. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/signl4/). - - -## Basic Operations - -* Alert - * Send an alert - * Resolve an alert - -## Example Usage - -This workflow allows you to send an alert on SIGNL4. You can also find the [workflow](https://n8n.io/workflows/441) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [SIGNL4]() - -The final workflow should look like the following image. - -![A workflow with the SIGNL4 node](/_images/integrations/builtin/app-nodes/signl4/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. SIGNL4 node - -1. First of all, you'll have to enter credentials for the SIGNL4 node. You can find out how to do that [here](/integrations/builtin/credentials/signl4/). -2. Enter a message in the *Message* field. -3. Click on the *Add Field* button and select 'Title'. -4. Enter a title in the *Title* field. -5. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.slack.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.slack.md deleted file mode 100644 index 8bb25daea..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.slack.md +++ /dev/null @@ -1,182 +0,0 @@ -# Slack - -[Slack](https://slack.com) is a business communication platform offering many IRC-style features, including persistent chat rooms (channels), private groups, and direct messaging. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/slack/). - - -## Basic Operations - -* Channel - * Archives a conversation. - * Closes a direct message or multi-person direct message. - * Initiates a public or private channel-based conversation - * Get information about a channel. - * Get all channels in a Slack team. - * Get a conversation's history of messages and events. - * Invite a user to a channel - * Joins an existing conversation. - * Removes a user from a channel. - * Leaves a conversation. - * List members of a conversation. - * Opens or resumes a direct message or multi-person direct message. - * Renames a conversation. - * Get a thread of messages posted to a channel - * Sets the purpose for a conversation. - * Sets the topic for a conversation. - * Unarchives a conversation. -* File - * Get a file info - * Get & filters team files. - * Create or upload an existing file. -* Message - * Deletes a message - * Get Permanent Link of a message - * Post a message into a channel - * Post an ephemeral message to a user in channel - * Updates a message -* Reaction - * Adds a reaction to a message - * Get the reactions of a message - * Remove a reaction of a message -* Star - * Add a star to an item. - * Delete a star from an item. - * Get all stars of autenticated user. -* User - * Get information about a user - * Get a list of users - * Get online status of a user -* User Group - * Create a user group - * Disable a user group - * Enable a user group - * Get all user groups - * Update a user group -* User Profile - * Get your user's profile - * Update user's profile - -## Example Usage - -This workflow allows you to create a channel, invite users to the channel, post a message, and upload a file to the channel. You can also find the [workflow](https://n8n.io/workflows/811) on n8n.io This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Slack]() -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) - -The final workflow should look like the following image. - -![A workflow with the Slack node](/_images/integrations/builtin/app-nodes/slack/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Slack node (create: channel) - -This node will create a new channel in your Slack workspace. This operation requires the `channel:manage` scope. Add this scope under the ***Bot Token Scopes*** section on Slack. You can refer to the [FAQs](#how-to-add-oauth-scopes-to-a-slack-app) to learn how to add scopes. - -1. Select 'Access Token' from the ***Authentication*** dropdown list. -2. You'll have to enter credentials for the Slack node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/slack/). -3. Select 'Channel' from the ***Resource*** dropdown list. -4. Enter a channel name in the ***Channel*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that node creates a new channel in Slack. - -![Using the Slack node to create a channel](/_images/integrations/builtin/app-nodes/slack/slack_node.png) - -### 3. Slack1 node (invite: channel) - -This node will invite a member to the channel that we created in the previous node. This operation requires the `channel:read` scope. Add this scope under the ***Bot Token Scopes*** section on Slack. - -1. Select 'Access Token' from the ***Authentication*** dropdown list. -2. Select the credentials that you entered in the previous node. -3. Select 'Channel' from the ***Resource*** dropdown list. -4. Select 'Invite' from the ***Operation*** dropdown list. -5. Click on the gears icon next to the ***Channel*** field click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Slack > Output Data > JSON > id. You can also add the following expression: `{{$node["Slack"].json["id"]}}`. -7. Select the users from the ***User IDs*** dropdown list. The users you select in this field will be added to the channel. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that node invites the user to the channel we created using the previous node. - -![Using the Slack node to invite a user to a channel](/_images/integrations/builtin/app-nodes/slack/slack1_node.png) - -### 4. Slack2 node (post: message) - -This node will post a message in the channel with an attachment. - -1. Select 'Access Token' from the ***Authentication*** dropdown list. -2. Select the credentials that you entered in the previous node. -3. Click on the gears icon next to the ***Channel*** field click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Slack > Output Data > JSON > id. You can also add the following expression: `{{$node["Slack"].json["id"]}}`. -5. Enter a message in the ***Text*** field. -6. Toggle ***As User*** to `true`. This option allows you to post a message as a bot. -7. Click on the ***Add attachment*** button. -8. Select 'Image URL' from the ***Add attachment item*** dropdown list. -9. Enter the URL of an image in the ***Image URL*** field. -10. Select 'Title' from the ***Add attachment item*** dropdown list. -11. Enter a title in the ***Title*** field. -12. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that node sends a message with an attachment to the channel that we created in the previous node. - -![Using the Slack node to send a message with an attachment to a channel](/_images/integrations/builtin/app-nodes/slack/slack2_node.png) - -### 5. HTTP Request node (GET) - -This node will fetch a file from a URL. You can also use the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node to read a file from the path you specify. - -1. Enter the URL of a file in the ***URL*** field. -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 fetches the file from the URL. This file gets passed on as binary data to the next node in the workflow. - -![Using the HTTP Request node to fetch a file from a URL](/_images/integrations/builtin/app-nodes/slack/httprequest_node.png) - -### 6. Slack3 node (upload: file) - -This node will upload the file that we got from the previous node to a channel we specify. - -1. Select 'Access Token' from the ***Authentication*** dropdown list. -2. Select the credentials that you entered in the previous Slack node. -3. Select 'File' from ***Resource*** dropdown list. -4. Select 'Upload' from the ***Operation*** dropdown list. -5. Toggle ***Binary Data*** to true. -6. Click on ***Add options*** and select 'Channels'. -7. Select the channel from the ***Channels*** dropdown list. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uploads the file to the channel that we created earlier. - -![Using the Slack node to upload a file to a channel](/_images/integrations/builtin/app-nodes/slack/slack3_node.png) - -## FAQs - -### How to create a private channel? - -To create a private channel, follow the steps mentioned below. -1. Select 'Channel' from the ***Resource*** dropdown list. -2. Select 'Create' from the ***Operation*** dropdown list. -3. Click on the ***Add Field*** button. -4. Toggle ***Is Private*** to `true`. - -### How to add OAuth Scopes to a Slack app? - -Your app needs appropriate scopes and permissions to perform actions. For example, if you want to create a new channel, your app requires the `channel:manage` scope. To add scopes and permissions, follow the steps mentioned below. -1. Navigate to the [Slack App dashboard](https://api.slack.com/apps) page and select your app. -2. Click on 'OAuth & Permissions' under the ***Feature*** section on the left sidebar. -3. Scroll down to the ***Scopes*** section. -4. If you're building a bot, click on ***Add an OAuth Scope*** under the ***Bot Token Scopes***. -5. Select the permissions you want to give to your bot from the dropdown list. -6. If you want the app to access user data and act on behalf of users that authorize them, add scopes under the ***User Token Scopes***. -7. When you add new scopes, Slack will ask you to reinstall the app. Click on 'reinstall your app' on the top of the page and reinstall the app. - -You can refer to the official documentation on [Scopes and permissions](https://api.slack.com/scopes) to learn more. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.sms77.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.sms77.md deleted file mode 100644 index 23352fbd6..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.sms77.md +++ /dev/null @@ -1,36 +0,0 @@ -# sms77 - -[sms77](https://www.sms77.io/) is a full service messaging provider that helps improve communication with a powerful API and comprehensive products like Voice, SMS, and Text2Speech. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/sms77/). - - -## Basic Operations - -* SMS - * Send SMS -* Voice Call - * Converts text to voice and calls a given number - -## Example Usage - -This workflow allows you to send an SMS to a specified phone number from any phone number. You can also find the [workflow](https://n8n.io/workflows/469) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [sms77]() - -The final workflow should look like the following image. - -![A workflow with the sms77 node](/_images/integrations/builtin/app-nodes/sms77/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. sms77 node - -1. First of all, you'll have to enter credentials for the sms77 node. You can find out how to do that [here](/integrations/builtin/credentials/sms77/). -2. Enter the phone number from which you'll be sending the message in the *From* field. -3. Enter the phone number to which you'll be sending the message in the *To* field. -4. Enter you message in the *Message* field. -5. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.snowflake.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.snowflake.md deleted file mode 100644 index 78d1abaed..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.snowflake.md +++ /dev/null @@ -1,105 +0,0 @@ -# Snowflake - -[Snowflake](https://snowflake.com) is a cloud data platform that provides a data warehouse-as-a-service designed for the cloud. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/snowflake/). - - -## Basic Operations - -* Execute an SQL query. -* Insert rows in database. -* Update rows in database. - -## Example Usage - -This workflow allows you to create a table, insert, and update data in a table in Snowflake. You can also find the [workflow](https://n8n.io/workflows/824) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Snowflake]() - -The final workflow should look like the following image. - -![A workflow with the Snowflake node](/_images/integrations/builtin/app-nodes/snowflake/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. Snowflake node (Execute Query) - -This node will create a table named `docs` with `id` and `name` columns. - -1. First of all, you'll have to enter credentials for the Snowflake node. You can find out how to do that [here](/integrations/builtin/credentials/snowflake/). -2. Select 'Execute Query' from the ***Operation*** dropdown list. -3. Enter the following SQL query in the ***Query*** field: `CREATE TABLE docs (id INT, name STRING);`. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a table named `docs` in Snowflake. - -![Using the Snowflake node to create a table](/_images/integrations/builtin/app-nodes/snowflake/snowflake_node.png) - - -### 3. Set node - -We will use the Set node to set the values for the id and name columns for a new record. - -1. Click on the ***Add Value*** button and select 'Number' from the dropdown list. -2. Enter `id` in the ***Name*** field. -3. Enter an id in the ***Value*** field. -3. Click on the ***Add Value*** button and select 'String' from the dropdown list. -4. Enter `name` in the ***Name*** field. -5. Enter the value for the name in the ***Value*** field. -6. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sets the value for `id` and `name`. - -![Using the Set node to set data to be inserted by the Snowflake node](/_images/integrations/builtin/app-nodes/snowflake/set_node.png) - -### 4. Snowflake1 node (Insert) - -This node will insert the data that we set in the previous node into the `docs` table in Snowflake. - -1. Select the credentials that you entered in the previous Snowflake node. -2. Enter `docs` in the ***Table*** field. -3. Enter `id, name` in the ***Columns*** field. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node inserts the data in the table that we created using the Snowflake node. - -![Using the Snowflake node to insert data into a table](/_images/integrations/builtin/app-nodes/snowflake/snowflake1_node.png) - -### 5. Set1 node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. We will set the value of `name` in this node. - -1. Click on the ***Add Value*** button and select 'Number' from the dropdown list. -2. Enter `id` in the ***Name*** field. -3. Enter `1` in the ***Value*** field. -4. Click on the ***Add Value*** button and select 'String' from the dropdown list. -5. Enter `name` in the ***Name*** field. -6. Enter `nodemation` in the ***Value*** field. -7. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sets the value of `name`. This value is passed to the next node in the workflow. - -![Using the Set node to set data to be updated by the Snowflake node](/_images/integrations/builtin/app-nodes/snowflake/set1_node.png) - -### 6. Snowflake2 node (Update) - -This node will update the value of the `name` column for the id `1`. - -1. Select the credentials that you entered in the previous Snowflake node. -2. Select 'Update' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Table*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Snowflake1 > Parameters > table. You can also add the following expression: `{{$node["Snowflake1"].parameter["table"]}}`. -4. Enter `name` in the ***Columns*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node updates the value of the name field for the record with id `1`. - -![Using the Snowflake node to update data](/_images/integrations/builtin/app-nodes/snowflake/snowflake2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.splunk.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.splunk.md deleted file mode 100644 index 4f1aa6e3d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.splunk.md +++ /dev/null @@ -1,29 +0,0 @@ -# Splunk - -[Splunk](https://www.splunk.com/) produces software for searching, monitoring, and analyzing machine-generated data via a Web-style interface. It indexes and correlates information in a container that makes it searchable, and makes it possible to generate alerts, reports and visualizations. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/splunk/). - - -## Basic Operations - -* Fired Alert - * Retrieve a fired alerts report -* Search Configuration - * Delete a search configuration - * Retrieve a search configuration - * Retrieve all search configurations -* Search Job - * Create a search job - * Delete a search job - * Retrieve a search job - * Retrieve all search jobs -* Search Result - * Retrieve all search results for a search job -* User - * Create an user - * Delete an user - * Retrieve an user - * Retrieve all users - * Update an user diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.spontit.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.spontit.md deleted file mode 100644 index 551c5d2b3..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.spontit.md +++ /dev/null @@ -1,67 +0,0 @@ -# Spontit - -[Spontit](https://www.spontit.com/) enables you to send push notifications without your app or website. You can create different channels and send push notifications to specific followers. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/spontit/). - - -## Basic Operations - -* Push - * Create a push notification - -## Example Usage - -This workflow allows you to send daily weather updates via a push notification using the Spontit node. You can also find the [workflow](https://n8n.io/workflows/796) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/) -- [Spontit]() - -The final workflow should look like the following image. - -![A workflow with the Spontit node](/_images/integrations/builtin/app-nodes/spontit/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow daily at 9 AM. - -1. Click on ***Add Cron Time***. -2. Set hours to 9 in the ***Hour*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every day at 9 AM. - -![Using the Cron node to trigger the workflow daily at 9 am](/_images/integrations/builtin/app-nodes/spontit/cron_node.png) - -### 2. OpenWeatherMap node (Current Weather) - -This node will return data about the current weather in Berlin. To get the weather updates for your city, you can enter the name of your city instead. - -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. Enter `berlin` in the ***City*** field. -3. 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/spontit/openweathermap_node.png) - -### 3. Spontit node (create: push) - -This node will send a push notification with the weather update. - -1. First of all, you'll have to enter credentials for the Spontit node. You can find out how to do that [here](/integrations/builtin/credentials/spontit/). -2. Click on ***Add Field*** and select 'Title' from the dropdown list. -3. Enter `Today's Weather Update` in the ***Title*** field. -4. Click on the gears icon next to the ***Content*** field and click on ***Add Expression***. - -5. Enter the following message in the ***Expression*** field: `Hey! The temperature outside is {{$node["OpenWeatherMap"].json["main"]["temp"]}}°C.`. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends a push notification with the weather update. - -![Using the Spontit node to send weather updates via a push notification](/_images/integrations/builtin/app-nodes/spontit/spontit_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.spotify.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.spotify.md deleted file mode 100644 index 7ad270299..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.spotify.md +++ /dev/null @@ -1,69 +0,0 @@ -# Spotify - -[Spotify](https://www.spotify.com/) is a music streaming service containing millions of music tracks and podcasts. Spotify allows users to create and manage their own playlists, explore new music through recommendation services, and listen to songs on demand. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/spotify/). - - -## Basic Operations - -* Album - * Get an album by URI or ID. - * Get a list of new album releases. - * Get an album's tracks by URI or ID. - * Search albums by keyword. -* Artist - * Get an artist by URI or ID. - * Get an artist's albums by URI or ID. - * Get an artist's related artists by URI or ID. - * Get an artist's top tracks by URI or ID. - * Search artists by keyword. -* Library - * Get the user's liked tracks. -* My Data - * Get your followed artists. -* Player - * Add a song to your queue. - * Get your currently playing track. - * Skip to your next track. - * Pause your music. - * Skip to your previous song. - * Get your recently played tracks. - * Resume playback on the current active device. - * Set volume on the current active device. - * Start playing a playlist, artist, or album. -* Playlist - * Add tracks from a playlist by track and playlist URI or ID. - * Create a new playlist. - * Get a playlist by URI or ID. - * Get a playlist's tracks by URI or ID. - * Get a user's playlists. - * Remove tracks from a playlist by track and playlist URI or ID. - * Search playlists by keyword. -* Track - * Get a track by its URI or ID. - * Get audio features for a track by URI or ID. - * Search tracks by keyword - -## Example Usage - -This workflow allows you to add a song to your queue in Spotify. You can also find the [workflow](https://n8n.io/workflows/440) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Spotify]() - -The final workflow should look like the following image. - -![A workflow with the Spotify node](/_images/integrations/builtin/app-nodes/spotify/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Spotify node - -1. First of all, you'll have to enter credentials for the Spotify node. You can find out how to do that [here](/integrations/builtin/credentials/spotify/). -2. Enter the song's URI (or ID) to the *Track ID* field. The following GIF shows you how to find the Track ID on Spotify's UI. -3. Click on *Execute Node* to run the workflow. - -![Spotify URI](/_images/integrations/builtin/app-nodes/spotify/spotifyuri.gif) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.stackby.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.stackby.md deleted file mode 100644 index e56bd6c50..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.stackby.md +++ /dev/null @@ -1,77 +0,0 @@ -# Stackby - -[Stackby](https://stackby.com/) is a real-time database and team collaboration platform. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/stackby/). - - -## Basic Operations - -- Append -- Delete -- List -- Read - -## Example Usage - -This workflow allows you to insert and retrieve data from a table in Stackby. You can also find the [workflow](https://n8n.io/workflows/934) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Stackby]() - -The final workflow should look like the following image. - -![A workflow with the Stackby node](/_images/integrations/builtin/app-nodes/stackby/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Set node - -We will use the Set node to set the values for the name and id fields for a new record. - -1. Click on the ***Add Value*** button and select 'Number' from the dropdown list. -2. Enter `ID` in the ***Name*** field. -3. Enter an id in the ***Value*** field. -4. Click on the ***Add Value*** button and select 'String' from the dropdown list. -5. Enter `Name` in the ***Name*** field. -6. Enter a name in the ***Value*** field. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sets the value for `ID` and `Name`. - -![Using the Set node to set data](/_images/integrations/builtin/app-nodes/stackby/set_node.png) - -### 3. Stackby node (Append) - -This node will append the data that we set in the previous node to a table. Create a table like [this](https://stackby.com/embed/shr161295766228627eec5) in your Stackby stack. - -Copy the string of characters located after `/stack/` in your Stackby URL. This is your Stack ID. For example, if the URL is `https://stackby.com/stack/stabdcat4234324/`, the Stack ID will be `stabdcat4234324`. - -1. First of all, you'll have to enter credentials for the Stackby node. You can find out how to do that [here](/integrations/builtin/credentials/stackby/). -2. Paste the Stack ID in the ***Stack ID*** field. -3. Enter the name of your table in the ***Table*** field. -4. Enter `ID, Name` in the ***Columns*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node appends the data that we had set in the previous node. - -![Using the Stackby node to insert data into a Stackby table](/_images/integrations/builtin/app-nodes/stackby/stackby_node.png) - -### 4. Stackby1 node (List) - -This node will list all the records from a table. - -1. Select the credentials that you entered in the previous node. -2. Select 'List' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Stack ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Stackby > Parameters > stackId. You can also add the following expression: `{{$node["Stackby"].parameter["stackId"]}}`. -5. Click on the gears icon next to the ***Table*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Stackby > Parameters > table. You can also add the following expression: `{{$node["Stackby"].parameter["table"]}}`. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns all the entries that are stored in the table. - -![Using the Stackby node to read data from a Stackby table](/_images/integrations/builtin/app-nodes/stackby/stackby1_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 deleted file mode 100644 index 0b6432193..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.storyblok.md +++ /dev/null @@ -1,74 +0,0 @@ -# Storyblok - -[Storyblok](https://www.storyblok.com/) is a headless content management system with a visual editor. It provides developers with all the flexibility they need to build reliable and fast websites, while giving content creators with no coding skills the ability to edit content independently of the developer. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/storyblok/). - - -## Basic Operations - -### Content API -**Story** -- Get a story -- Get all stories - - -### Management API -**Story** -- Delete a story -- Get a story -- Get all stories -- Publish a story -- 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.strapi.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.strapi.md deleted file mode 100644 index 133097745..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.strapi.md +++ /dev/null @@ -1,120 +0,0 @@ -# Strapi - -[Strapi](https://www.strapi.io/) is an open-source Headless CMS that gives developers the freedom to choose their tools and frameworks while also allowing editors to easily manage and distribute their content. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/strapi/). - - -!!! warning "Strapi Version 4" - The Strapi node node was built for Strapi version 3. Some of its operations will not work with Strapi version 4. - - -## Basic Operations - -* Entry - * Create an entry - * Delete an entry - * Get an entry - * Get all entries - * Update an entry - - -## Example Usage - -This workflow allows you to create, update, and get an entry in Strapi. You can also find the [workflow](https://n8n.io/workflows/779) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Strapi]() - -The final workflow should look like the following image. - -![A workflow with the Strapi node](/_images/integrations/builtin/app-nodes/strapi/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Set node - -We will use the Set node to set the title, content, and description for an entry of the content type `Post`. If you have a different content type in Strapi, set the values accordingly. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `Title` in the ***Name*** field. -3. Enter `Automate Strapi with n8n` in the ***Value*** field. -4. Click on ***Add Value*** and select 'String' from the dropdown list. -5. Enter `Content` in the ***Name*** field. -6. Enter `Strapi is a headless CMS. We will use Strapi and n8n to automate our content creation workflows.` in the ***Value*** field. -7. Click on ***Add Value*** and select 'String' from the dropdown list. -8. Enter `Description` in the ***Name*** field. -9. Enter `Learn how to automate Strapi with n8n.` in the ***Value*** field. -10. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that node sets the value for title, content, and description. - -![Using the Set node to set the data](/_images/integrations/builtin/app-nodes/strapi/set_node.png) - -### 2. Strapi node (create: entry) - -This node will create an entry for the content type `posts`. If you have a different content type, use that content type instead. - -1. First of all, you'll have to enter credentials for the Strapi node. You can find out how to do that [here](/integrations/builtin/credentials/strapi/). -2. Select 'Create' from the ***Operation*** dropdown list. -3. Enter `posts` in the ***Content Type*** field. -4. Enter `Title, Content, Description` in the ***Columns*** field. If you want to add data for other columns, enter those column names. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new entry in Strapi using the information from the previous node. - -![Using the Strapi node to create an entry](/_images/integrations/builtin/app-nodes/strapi/strapi_node.png) - -### 3. Set1 node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. We will set the value of `id` and `slug` in this node. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `id` in the ***Name*** 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 > Strapi > Output Data > JSON > id. You can also add the following expression: `{{$node["Strapi"].json["id"]}}`. -5. Click on ***Add Value*** and select 'String' from the dropdown list. -6. Enter `slug` in the ***Name*** field. -7. Enter `automate-strapi-with-n8n` in the ***Value*** field. -8. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -9. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sets the values of `id` and `slug`. These values are passed to the next node in the workflow. - -![Using the Set node to set the values for id and slug](/_images/integrations/builtin/app-nodes/strapi/set1_node.png) - -### 4. Strapi1 node (update: entry) - -This node will update the slug for the entry that we created using the Strapi 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 ***Content Type*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Strapi > Parameters > contentType. You can also add the following expression: `{{$node["Strapi"].parameter["contentType"]}}`. -5. Enter `id` in the ***Update Key*** field. -6. Enter `slug` in the ***Columns*** field. If you want to update a different column, enter that column name instead. -7. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node adds a slug to the entry that we created using the Strapi node. - -![Using the Strapi node to update an entry](/_images/integrations/builtin/app-nodes/strapi/strapi1_node.png) - -### 5. Strapi2 node (get: entry) - -This node returns information about the entry that we created using the Strapi node. - -1. Select the credentials that you entered in the previous node. -2. Click on the gears icon next to the ***Content Type*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Nodes > Strapi > Parameters > contentType. You can also add the following expression: `{{$node["Strapi"].parameter["contentType"]}}`. -4. Click on the gears icon next to the ***Entry ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > Strapi > Output Data > JSON > id. You can also add the following expression: `{{$node["Strapi1"].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 entry that we specified. - -![Using the Strapi node to get information of an entry](/_images/integrations/builtin/app-nodes/strapi/strapi2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.strava.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.strava.md deleted file mode 100644 index 284a75277..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.strava.md +++ /dev/null @@ -1,90 +0,0 @@ -# Strava - -[Strava](https://www.strava.com/) is an internet service for tracking human exercise which incorporates social network features. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/strava/). - - -## Basic Operations - -* Activity - * Create a new activity - * Get an activity - * Get all activities - * Get all activity comments - * Get all activity kudos - * Get all activity laps - * Get all activity zones - * Update an activity - -## Example Usage - -This workflow allows you to create, update, and get an activity in Strava. You can also find the [workflow](https://n8n.io/workflows/744) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Strava]() - -The final workflow should look like the following image. - -![A workflow with the Strava node](/_images/integrations/builtin/app-nodes/strava/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Strava node (create: activity) - -This node will create an activity with the name `Morning Run` in Strava. To create an activity with a different name, you can enter the name of your activity instead. - -1. First of all, you'll have to enter credentials for the Strava node. You can find out how to do that [here](/integrations/builtin/credentials/strava/). -2. Enter `Morning Run` in the ***Name*** field. -3. Enter `Run` in the ***Type*** field. -4. Select the date and time in the ***Start Date*** field. -5. Set ***Elapsed Time (Seconds)*** to `3600`. -6. Click on the ***Add Field*** button and select 'Distance' from the dropdown list. -7. Set ***Distance*** to `1000`. Strava measures distance in meters. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates an activity with the name `Morning Run` and type `Run`. - -![Using the Strava node to create an activity](/_images/integrations/builtin/app-nodes/strava/strava_node.png) - - - -### 3. Strava1 node (update: activity) - -This node will update the activity 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 ***Activity ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Strava > Output Data > JSON > id. You can also add the following expression: `{{$node["Strava"].json["id"]}}`. -5. Click on the ***Add Field*** button and select 'Description' from the dropdown list. -6. Enter the description of the activity in the ***Description*** field. -7. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node adds a description to the activity that we created using the Strava node. - -![Using the Strava node to update an activity](/_images/integrations/builtin/app-nodes/strava/strava1_node.png) - - - -### 4. Strava2 node (get: activity) - -This node returns the information of the activity that we created using the Strava 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 ***Activity ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Strava > Output Data > JSON > id. You can also add the following expression: `{{$node["Strava"].json["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 activity that we specified in this node. - -![Using the Strava node to get an issue](/_images/integrations/builtin/app-nodes/strava/strava2_node.png) - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.stripe.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.stripe.md deleted file mode 100644 index 9e1b2afdb..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.stripe.md +++ /dev/null @@ -1,88 +0,0 @@ -# Stripe - -[Stripe](https://stripe.com/) offers payment processing software and application programming interfaces for e-commerce websites and mobile applications. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/stripe/). - - -## Basic operations - -* Balance - * Get a balance -* Charge - * Create a charge - * Get a charge - * Get all charges - * Update a charge -* Coupon - * Create a coupon - * Get all coupons -* Customer - * Create a customer - * Delete a customer - * Get a customer - * Get all customers - * Update a customer -* Customer Card - * Add a customer card - * Get a customer card - * Remove a customer card -* Source - * Create a source - * Delete a source - * Get a source -* Token - * Create a token - -## Example - -This workflow allows you to create a new customer, create a card token, and associate this token as that customer's card. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Stripe]() - -The final workflow should look like the following image. - -![A workflow with the Stripe node](/_images/integrations/builtin/app-nodes/stripe/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Stripe node - -1. First enter your Stripe API credentials. You can learn how to create that [here](/integrations/builtin/credentials/stripe/). -2. Fill in the remaining parameters as follows: - * **Resource**: Select the entity you want to work with, **Customer** in this example. - * **Operation**: Select the action to perform, **Create** in this example. - * **Name**: Enter the customer name. - * **Additional Fields**: Provide any further details, available options are: Address, Description, Email, Metadata, and Shipping. - * **Type**: The type of token to create, **Card Token** by default. - -![The Stripe node](/_images/integrations/builtin/app-nodes/stripe/stripe_node.png) - -### 3. Stripe1 node - -1. First enter your Stripe API credentials as with the first node. -2. Fill in the remaining parameters as follows: - * **Resource**: Select the entity you want to work with, **Token** in this example. - * **Operation**: Select the action to perform, **Create** in this example. - * **Type**: The type of token to create, **Card Token** by default. - * **Card Number**: Enter the customer credit card number. - * **CVC**: Enter the security code for this card. - * **Expiration Month**: Enter the expiration month for this card. - * **Expiration Year**: Enter the expiration year for this card. - -![The Stripe1 node](/_images/integrations/builtin/app-nodes/stripe/stripe1_node.png) - -### 4. Stripe2 node - -1. First enter your Stripe API credentials as with the previous node. -2. Fill in the remaining parameters as follows: - * **Resource**: Select the entity you want to work with, **Customer Card** in this example. - * **Operation**: Select the action to perform, **Add** in this example. - * **Customer ID**: Enter the customer ID generated by the first node. - * **Card Token**: Enter the token generated by the second node. - * **Type**: The type of token to create, **Card Token** by default. - -![The Stripe2 node](/_images/integrations/builtin/app-nodes/stripe/stripe2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.supabase.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.supabase.md deleted file mode 100644 index 04d6fb453..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.supabase.md +++ /dev/null @@ -1,16 +0,0 @@ -# Supabase - -[Supabase](https://supabase.com/) is an open source Firebase alternative. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/supabase/). - - -## Basic Operations - -* Row - * Create a new row - * Delete a row - * Get a row - * Get all rows - * Update a row diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.syncroMsp.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.syncroMsp.md deleted file mode 100644 index e205dcc32..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.syncroMsp.md +++ /dev/null @@ -1,34 +0,0 @@ -# SyncroMSP - -[SyncroMSP](https://syncromsp.com/) is a cloud-based remote monitoring and management platform (RMM). - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/syncroMsp/). - - -## Basic Operations - -* Contact - * Create new contact - * Delete contact - * Retrieve contact - * Retrieve all contacts - * Update contact -* Customer - * Create new customer - * Delete customer - * Retrieve customer - * Retrieve all customers - * Update customer -* RMM - * Create new RMM Alert - * Delete RMM Alert - * Retrieve RMM Alert - * Retrieve all RMM Alerts - * Mute RMM Alert -* Ticket - * Create new ticket - * Delete ticket - * Retrieve ticket - * Retrieve all tickets - * Update ticket diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.taiga.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.taiga.md deleted file mode 100644 index 73744414a..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.taiga.md +++ /dev/null @@ -1,72 +0,0 @@ -# Taiga - -[Taiga](https://www.taiga.io/) is a free and open-source project management platform for startups, agile developers, and designers. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/taiga/). - - -## Basic Operations - -**Issue** -- Create an issue -- Delete an issue -- Get an issue -- Get all issues -- Update an issue - - - -## 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.tapfiliate.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.tapfiliate.md deleted file mode 100644 index c6c44a531..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.tapfiliate.md +++ /dev/null @@ -1,89 +0,0 @@ -# Tapfiliate - -[Tapfiliate](https://tapfiliate.com) allows you to create, track, and grow your affiliate marketing programs. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/tapfiliate/). - - -## Basic Operations - -* Affiliate - * Create an affiliate - * Delete an affiliate - * Get an affiliate by ID - * Get all affiliates -* Affiliate Metadata - * Add metadata to affiliate - * Remove metadata from affiliate - * Update affiliate's metadata -* Program Affiliate - * Add affiliate to program - * Approve an affiliate for a program - * Disapprove an affiliate - * Get an affiliate in a program - * Get all affiliates in program - -## Example Usage - -This workflow allows you to create an affiliate, add metadata, and add the affiliate to a program. You can also find the [workflow](https://n8n.io/workflows/936) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Tapfiliate]() - -The final workflow should look like the following image. - -![A workflow with the Tapfiliate node](/_images/integrations/builtin/app-nodes/tapfiliate/workflow.png) - -### 1. Start node - -The Start node exists by default when you create a new workflow. - -### 2. Tapfiliate node (create:affiliate) - -This node will create an affiliate in Tapfiliate. - -1. First of all, you'll have to enter credentials for the Tapfiliate node. You can find out how to do that [here](/integrations/builtin/credentials/tapfiliate/). -2. Enter an email address in the ***Email*** field. -3. Enter the first name of the affiliate in the ***First Name*** field. -4. Enter the last name of the affiliate in the ***Last Name*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates an affiliate in Tapfiliate. - -![Using the Tapfiliate node to create a new affiliate](/_images/integrations/builtin/app-nodes/tapfiliate/tapfiliate_node.png) - -### 3. Tapfiliate1 node (add:affiliateMetadata) - -This node will add metadata to the affiliate that we created with the previous node. - - -1. Select the credentials that you entered in the previous node. -2. Select 'Affiliate Metadata' from the ***Resource*** dropdown list. -3. Select 'Add' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Affiliate 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 the ***Add Metadata*** button. -7. Enter `tag` in the ***Key*** field. -8. Enter `n8n` in the ***Value*** field. -9. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node adds the metadata to the affiliate that we created with the previous node. - -![Using the Tapfiliate node to add metadata](/_images/integrations/builtin/app-nodes/tapfiliate/tapfiliate1_node.png) - -### 4. Tapfiliate2 node (get:contact) - -This node will add the affiliate that we created with the Tapfiliate node to an affiliate program. - -1. Select the credentials that you entered in the previous node. -2. Select 'Program Affiliate' from the ***Resource*** dropdown list. -3. Select 'Add' from the ***Operation*** dropdown list. -4. Select a program from the ***Program ID*** dropdown list. -5. Click on the gears icon next to the ***Affiliate ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Tapfiliate > Output Data > JSON > id. You can also add the following expression: `{{$node["Tapfiliate"].json["id"]}}`. -7. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node adds the affiliate to a program. - -![Using the Tapfiliate node to add an affiliate to a program](/_images/integrations/builtin/app-nodes/tapfiliate/tapfiliate2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.telegram.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.telegram.md deleted file mode 100644 index 2e22d1cab..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.telegram.md +++ /dev/null @@ -1,122 +0,0 @@ -# Telegram - -[Telegram](https://telegram.org) is a cloud-based instant messaging and voice-over-IP service. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/telegram/). - - -## Basic Operations - -* Chat - * Get up to date information about a chat. - * Leave a group, supergroup or channel. - * Get the member of a chat. - * Set the description of a chat. - * Set the title of a chat. -* Callback - * Send answer to callback query sent from inline keyboard. - * Send answer to callback query sent from inline bot. -* File - * Get a file. -* Message - * Delete a chat message - * Edit a text message - * Pin a chat message - * Send an animated file - * Send a audio file - * Send a chat action - * Send a document - * Send a location - * Send group of photos or videos to album - * Send a text message - * Send a photo - * Send a sticker - * Send a video - * Unpin a chat message - -## Example Usage - -This workflow allows you to send a cocktail recipe to a specified chat ID every day via a Telegram bot. You can also find the [workflow](https://n8n.io/workflows/781) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [Telegram]() - -The final workflow should look like the following image. - -![A workflow with the Telegram node](/_images/integrations/builtin/app-nodes/telegram/workflow.png) -### 1. Cron node - -The Cron node will trigger the workflow daily at 8 PM. - -1. Click on ***Add Cron Time***. -2. Set hours to `20` in the ***Hour*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every day at 8 PM. - -![Using the Cron node to trigger the workflow daily at 8 PM](/_images/integrations/builtin/app-nodes/telegram/cron_node.png) - -### 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/telegram/httprequest_node.png) - -### 3. Telegram node (sendPhoto: message) - -This node will send a message on Telegram with an image and the recipe of the cocktail that we got from the previous node. - -1. First of all, you'll have to enter credentials for the Telegram node. You can find out how to do that [here](/integrations/builtin/credentials/telegram/). - -2. Select 'Send Photo' from the ***Operation*** dropdown list. -3. Enter the target chat ID in the ***Chat ID*** field. Refer to the [FAQs](#how-do-i-get-a-chat-id) to learn how to get the chat ID. -4. Click on the gears icon next to the ***Photo*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > drinks > [item: 0] > strDrinkThumb. You can also add the following expression: `{{$node["HTTP Request"].json["drinks"][0]["strDrinkThumb"]}}`. -6. Click on ***Add Field*** and select 'Caption' from the dropdown list. -7. Click on the gears icon next to the ***Caption*** field and click on ***Add Expression***. -8. 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"]}}`. -9. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends a message on Telegram with an image and the recipe of the cocktail. - -![Using the Telegram node to send a message with an image and instruction of a cocktail](/_images/integrations/builtin/app-nodes/telegram/telegram_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. - - -## FAQs - -### How can I send more than 30 messages per second? - -The Telegram API has a [limitation](https://core.telegram.org/bots/faq#broadcasting-to-users) of sending only 30 messages per second. Follow the steps mentioned below to send more than 30 messages: -1. Split In Batches node: Use the [Split in Batches](/integrations/builtin/core-nodes/n8n-nodes-base.splitInBatches/) node to get at most 30 chat IDs from your database. -2. Telegram node: Connect the Telegram node with the Split In Batches node. Use the ***Expression Editor*** to select the Chat IDs from the Split in Batches node. -3. Function node: Connect the [Function](/integrations/builtin/core-nodes/n8n-nodes-base.function/) node with the Telegram node. Use the Function node to wait for a few seconds before fetching the next batch of chat IDs. Connect this node with the Split In Batches node. - -You can also use this [workflow](https://n8n.io/workflows/772). - -### How do I add a bot to a Telegram channel? - -1. In the Telegram app, access the target channel and tap on the channel name. -2. Make sure that the channel name is labeled as "public channel". -3. Tap on ***Administrators*** and then on ***Add Admin***. -4. Search for the username of the bot and select it. -5. Tap on the checkmark on the top-right corner to add the bot to the channel. - -### How do I get the Chat ID? - -There are two ways to get the Chat ID in Telegram. - -- Using the [Telegram Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.telegramtrigger/) node: On successful execution, the Telegram Trigger node returns a Chat ID. You can use the Telegram Trigger node in your workflow to get a Chat ID. -- Using the `@RawDataBot`: The `@RawDataBot` returns the raw data of the chat with a Chat ID. Invite the `@RawDataBot` to your channel/group, and upon joining, it will output a Chat ID along with other information. Be sure to remove the `@RawDataBot` from your group/channel afterwards. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.theHive.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.theHive.md deleted file mode 100644 index 14a113d0d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.theHive.md +++ /dev/null @@ -1,123 +0,0 @@ -# TheHive - -[TheHive](https://thehive-project.org/) is a scalable open-source and free security incident response platform. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/theHive/). - - -## Basic Operations - -**Alert** -- Count alerts -- Create an alert -- Execute a responder on a specified alert -- Get an alert -- Get all alerts -- Mark an alert as read -- Mark an alert as unread -- Merge an alert into an existing case -- Promote an alert into a case -- Update an alert - - -**Case** -- Count cases -- Create a case -- Execute a responder on a specified case -- Get all cases -- Get a single case -- Update a case - - -**Log** -- Create a task log -- Execute a responder on a selected log -- Get all task logs -- Get a single log - - -**Observable** -- Count observables -- Create an observable -- Execute an analyzer -- Execute a responder on selected observable -- Get all observables of a specific case -- Get a single observable -- Search observables -- Update an observable - - -**Task** -- Count tasks -- Create a task -- Execute a responder on a specified task -- Get a single task -- Search tasks -- Update a task - - -## Example Usage - -This workflow allows you to create, update, and get a case in TheHive. You can also find the [workflow](https://n8n.io/workflows/808) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [TheHive]() - -The final workflow should look like the following image. - -![A workflow with the TheHive node](/_images/integrations/builtin/app-nodes/thehive/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. TheHive node (create: case) - -This node will create a new case in TheHive with the title `n8n` and set its severity to `low`. You can create a case with a different title and severity. - -1. First of all, you'll have to enter credentials for the TheHive node. You can find out how to do that [here](/integrations/builtin/credentials/theHive/). -2. Select 'Case' from the ***Resource*** dropdown list. -3. Select 'Create' from the ***Operation*** dropdown list. -4. Enter a title in the ***Title*** field. -5. Enter a description in the ***Description*** field. -6. Select 'Low' from the ***Severity*** dropdown list. -7. Set the start date in the ***Start Date*** field. -8. Enter a case owner in the ***Owner*** field. -9. Enter tags in the ***Tags*** field. You can enter multiple tags separate by a comma. -10. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new case with the title `n8n` and `low` severity . - -![Using TheHive node to create a new case](/_images/integrations/builtin/app-nodes/thehive/thehive_node.png) - -### 3. TheHive node (update: case) - -This node will update the case that we created in the previous node. We will update the severity of the case. - -1. Select the credentials that you entered in the previous node. -2. Select 'Case' from the ***Resource*** dropdown list. -3. Select 'Update' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Case ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > TheHive > Output Data > JSON > id. You can also add the following expression: `{{$node["TheHive"].json["id"]}}`. -6. Click on ***Add Field*** and select 'Severity' from the dropdown list. -7. Select 'High' from the ***Severity*** dropdown list. -8. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node updates the severity of the case that we created in the previous node. - -![Using TheHive node to update the severity of a case](/_images/integrations/builtin/app-nodes/thehive/thehive1_node.png) - -### 4. TheHive node (get: case) - -This node will return the information of the case that we created in the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'Case' from the ***Resource*** dropdown list. -3. Select 'Get' from the ***Operation*** dropdown list. -4. Click on the gears icon next to the ***Case ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > TheHive > Output Data > JSON > id. You can also add the following expression: `{{$node["TheHive"].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 case that we created earlier. - -![Using TheHive node to return the information a case](/_images/integrations/builtin/app-nodes/thehive/thehive2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.timescaleDb.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.timescaleDb.md deleted file mode 100644 index fb9fa0d51..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.timescaleDb.md +++ /dev/null @@ -1,100 +0,0 @@ -# TimescaleDB - -[TimescaleDB](https://www.timescale.com/) is an open-source time-series SQL database optimized for fast ingest and complex queries. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/timescaleDb/). - - -## Basic Operations - -* Execute an SQL query -* Insert rows in database -* Update rows in database - -## Example Usage - -This workflow allows you to receive updates of the position of the ISS every minute and insert it to a table using the TimscaleDB node. You can also find the [workflow](https://n8n.io/workflows/917) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [TimescaleDB]() - -The final workflow should look like the following image. - -![A workflow with the TimescaleDB node](/_images/integrations/builtin/app-nodes/timescaledb/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow every minute. - -1. Click on ***Add Cron Time***. -2. Select 'Every Minute' from the ***Mode*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every minute. - -![Using the Cron node to trigger the workflow every minute](/_images/integrations/builtin/app-nodes/timescaledb/cron_node.png) - -### 2. HTTP Request node (GET) - -This node will make a GET request to the API `https://api.wheretheiss.at/v1/satellites/25544/positions` to fetch the position of the ISS. This information gets passed on to the next node in the workflow. - -1. Enter `https://api.wheretheiss.at/v1/satellites/25544/positions` in the ***URL*** field. -2. Click on the ***Add Parameter*** button in the ***Query Parameters*** section. -3. Enter `timestamps` in the ***Name*** field. -4. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -5. Enter the following expression: `{{Date.now()}}`. This expression will return the current timestamp. -6. 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 the information about the location of the ISS. - -![Using the HTTP Request node to get the information about the location of the ISS](/_images/integrations/builtin/app-nodes/timescaledb/httprequest_node.png) - -### 3. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `latitude` in the ***Name*** 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: Current Node > Input Data > JSON > 0 > latitude. You can also add the following expression: `{{$json["0"]["latitude"]}}`. -5. Click on ***Add Value*** and select 'String' from the dropdown list. -6. Enter `longitude` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > 0 > longitude. You can also add the following expression: `{{$json["0"]["longitude"]}}`. -9. Click on ***Add Value*** and select 'String' from the dropdown list. -10. Enter `timestamp` in the ***Name*** field. -11. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > 0 > timpestamp. You can also add the following expression: `{{$json["0"]["timestamp"]}}`. -13. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -14. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uses the data from the previous node and returns the data that we set for the workflow. - -![Using the Set node to set the data](/_images/integrations/builtin/app-nodes/timescaledb/set_node.png) - -### 4. TimescaleDB node (Insert) - -We will insert the data from the previous node to a table named `iss`. To create the table, use the following SQL command. -``` -CREATE TABLE iss(latitude NUMERIC, longitude NUMERIC, timestamp NUMERIC); -``` - -1. First of all, you'll have to enter credentials for the TimescaleDB node. You can find out how to do that [here](/integrations/builtin/credentials/timescaleDb/). -2. Enter `iss` in the ***Table*** field. -3. Enter `latitude, longitude, timestamp` in the ***Columns*** field. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node inserts the data from the previous node to the `iss` table in TimescaleDB. - -![Using the TimescaleDB node to insert the data to a table](/_images/integrations/builtin/app-nodes/timescaledb/timescaledb_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the Cron 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 as specified by the settings in the Cron node. - - -## FAQs - -### How to specify the data type of a column? -To specify the data type of a column, append the column name with `:type`, where `type` is the data type of that column. For example, if you want to specify the type `int` for the column *id* and type `text` for the column *name*, you can use the following snippet in the ***Columns*** field: `id:init,name:text`. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.todoist.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.todoist.md deleted file mode 100644 index 1ee2717dc..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.todoist.md +++ /dev/null @@ -1,43 +0,0 @@ -# Todoist - -[Todoist](https://todoist.com/) is a task management software that can be used for small teams, individuals and professionals to manage anything from a shopping list to major projects at work. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/todoist/). - - -## Basic Operations - -* Task - * Create a new task - * Close a task - * Delete a task - * Get a task - * Get all tasks - * Reopen a task - * Update a task - -## Example Usage - -This workflow allows you to create a new task in Todoist. You can also find the [workflow](https://n8n.io/workflows/481) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Todoist]() - -The final workflow should look like the following image. - -![A workflow with the Todoist node](/_images/integrations/builtin/app-nodes/todoist/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Todoist node - -1. First of all, you'll have to enter credentials for the Todoist node. You can find out how to do that [here](/integrations/builtin/credentials/todoist/). -2. Select your project from the *Project* dropdown list. -3. Enter the content for the task in the *Content* field. -4. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.travisCi.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.travisCi.md deleted file mode 100644 index 57c596a12..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.travisCi.md +++ /dev/null @@ -1,41 +0,0 @@ -# Travis CI - -[Travis CI](https://travis-ci.com) is a hosted continuous integration service used to build and test software projects hosted at GitHub and Bitbucket. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/travisCi/). - - -## Basic Operations - -* Build - * Cancel a build - * Get a build - * Get all builds - * 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.trello.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.trello.md deleted file mode 100644 index 2f4489651..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.trello.md +++ /dev/null @@ -1,97 +0,0 @@ -# Trello - -[Trello](https://trello.com/) is a web-based Kanban-style list-making application which is a subsidiary of Atlassian. Users can create their task boards with different columns and move the tasks between them. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/trello/). - - -## Basic Operations - -* Attachment - * Create a new attachment for a card - * Delete an attachment - * Get the data of an attachment - * Returns all attachments for the card -* Board - * Create a new board - * Delete a board - * Get the data of a board - * Update a board -* Board Member - * Add - * Get All - * Invite - * Remove -* Card - * Create a new card - * Delete a card - * Get the data of a card - * Update a card -* Card Comment - * Create a comment on a card - * Delete a comment from a card - * Update a comment on a card -* Checklist - * Create a checklist item - * Create a new checklist - * Delete a checklist - * Delete a checklist item - * Get the data of a checklist - * Returns all checklists for the card - * Get a specific checklist on a card - * Get the completed checklist items on a card - * Update an item in a checklist on a card -* Label - * Add a label to a card. - * Create a new label - * Delete a label - * Get the data of a label - * Returns all labels for the board - * Remove a label from a card. - * Update a label. -* List - * Archive/Unarchive a list - * Create a new list - * Get the data of a list - * Get all the lists - * Get all the cards in a list - * Update a list - -## Example Usage - -This workflow allows you to create a new card in Trello. You can also find the [workflow](https://n8n.io/workflows/461) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Trello]() - -The final workflow should look like the following image. - -![A workflow with the Trello node](/_images/integrations/builtin/app-nodes/trello/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Trello node - -1. First of all, you'll have to enter credentials for the Trello node. You can find out how to do that [here](/integrations/builtin/credentials/trello/). -2. Enter the ID of the list in which you want to create a new card in the *List ID* field. You can find instructions on how to obtain the ID of the list in the FAQs below. -3. Enter the name of the card in the *Name* field. -4. Enter the description of the card in the *Description* field. -5. Click on *Execute Node* to run the workflow. - - -## FAQs - -### How do I find the List ID? - -1. Open the Trello board that contains the list. -2. If the list doesn't have any cards, add a card to the list. -3. Open the card, add '.json' at the end of the URL, and press enter. -4. In the JSON file, you will see a field called `idList`. -5. Copy `idList`and paste it in the *List ID* field in n8n. - - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.twake.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.twake.md deleted file mode 100644 index bac2a5a7f..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.twake.md +++ /dev/null @@ -1,37 +0,0 @@ -# Twake - -[Twake](https://twake.app/) is an open-source collaborative workspace. It can be self-hosted and easily integrated into your teams. Twake offers features for collaboration like team chat, team calendar, video call, todo list, and storage space. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/twake/). - - -## Basic Operations - -* Message - * Send a message - - -## Example Usage - -This workflow allows you to send a message to a channel on Twake. You can also find the [workflow](https://n8n.io/workflows/595) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Twake]() - -The final workflow should look like the following image. - -![A workflow with the Twake node](/_images/integrations/builtin/app-nodes/twake/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. Twake node - -1. First of all, you'll have to enter credentials for the Twake node. You can find out how to do that [here](/integrations/builtin/credentials/twake/). -2. Select the channel from the ***Channel ID*** dropdown list. -3. Enter the content of the message in the ***Content*** field. -4. Click on ***Execute Node*** to run the node. - -![Using the Twake node to send a message](/_images/integrations/builtin/app-nodes/twake/twake_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.twilio.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.twilio.md deleted file mode 100644 index f6ebfc8da..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.twilio.md +++ /dev/null @@ -1,40 +0,0 @@ -# Twilio - -[Twilio](https://www.twilio.com/) is a cloud communications platform as a service company. Twilio allows software developers to programmatically make and receive phone calls, send and receive text messages, and perform other communication functions using its web service APIs. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/twilio/). - - -## Basic Operations - -* SMS - * Send SMS/MMS/WhatsApp message - -## Example Usage - -This workflow allows you to send an SMS or a Whatsapp message to a specified phone number from your Twilio number. You can also find the [workflow](https://n8n.io/workflows/401) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Twilio]() - -The final workflow should look like the following image. - -![A workflow with the Twilio node](/_images/integrations/builtin/app-nodes/twilio/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Twilio node - -1. First of all, you'll have to enter credentials for the Twilio node. You can find out how to do that [here](/integrations/builtin/credentials/twilio/). -2. Enter the phone number from which you'll be sending the message in the *From* field. -3. Enter the phone number to which you'll be sending the message in the *To* field. -4. In case you want to send a Whatsapp message, toggle the *To Whatsapp* button. -5. Enter you message in the *Message* field. -6. Click on *Execute Node* to run the workflow. - - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.twist.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.twist.md deleted file mode 100644 index 9544dea4a..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.twist.md +++ /dev/null @@ -1,121 +0,0 @@ -# Twist - -[Twist](https://twist.com) is a communication app that helps teams balance focused work with collaborative conversations. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/twist/). - - -## Basic Operations - -* Channel - * Archive a channel - * Initiates a public or private channel-based conversation - * Delete a channel - * Get information about a channel - * Get all channels - * Unarchive a channel - * Update a channel -* Comment - * Create a new comment to a thread - * Delete a comment - * Get information about a comment - * Get all comments - * Update a comment -* Message Conversation - * Create a message in a conversation - * Delete a message in a conversation - * Get a message in a conversation - * Get all messages in a conversation - * Update a message in a conversation -* Thread - * Create a new thread in a channel - * Delete a thread - * Get information about a thread - * 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 - -### Where can I get the User ID? - -To get the User ID for a user follow the steps mentioned below -1. Click on the ***Team*** tab. -2. Click on a user's avatar. -3. Copy the string of characters located after `/u/` in your Twist URL. This string is the User ID. For example, if the URL is `https://twist.com/a/4qw45/people/u/475370` the User ID will be `475370`. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.twitter.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.twitter.md deleted file mode 100644 index 394a0b0f5..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.twitter.md +++ /dev/null @@ -1,38 +0,0 @@ -# Twitter - -[Twitter](https://twitter.com/) is a microblogging and social networking service on which users post and interact with messages known as "tweets". - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/twitter/). - - -## Basic Operations - -* Direct Message - * Create a direct message -* Tweet - * Create or reply a tweet - * Delete a tweet - * Search tweets - * Like a tweet - * Retweet a tweet - -## Example Usage - -This workflow allows you to tweet on Twitter. You can also find the [workflow](https://n8n.io/workflows/445) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Twitter]() - -The final workflow should look like the following image. - -![A workflow with the Twitter node](/_images/integrations/builtin/app-nodes/twitter/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Twitter node - -1. First of all, you'll have to enter credentials for the Twitter node. You can find out how to do that [here](/integrations/builtin/credentials/twitter/). -2. Type the message you want to tweet in the *Text* field. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.unleashedSoftware.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.unleashedSoftware.md deleted file mode 100644 index 08b429c40..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.unleashedSoftware.md +++ /dev/null @@ -1,39 +0,0 @@ -# Unleashed Software - -[Unleashed Software](https://www.unleashedsoftware.com) is a cloud app that gives product businesses the freedom to better make, manage and move products by enabling them to achieve complete clarity and control over suppliers, production, warehouses, and sales. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/unleashedSoftware/). - - -## Basic Operations - -* Sales Order - * Get all sales orders -* Stock On Hand - * Get a stock on hand - * Get all stocks on hand - -## Example Usage - -This workflow allows you to get a list of all the orders from Unleashed Software based on the order status. You can also find the [workflow](https://n8n.io/workflows/641) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Unleashed Software]() - -The final workflow should look like the following image. - -![A workflow with the Unleashed Software node](/_images/integrations/builtin/app-nodes/unleashedsoftware/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Unleashed Software node - -1. First of all, you'll have to enter credentials for the Unleashed Software node. You can find out how to do that [here](/integrations/builtin/credentials/unleashedSoftware/). -2. Toggle ***Return All*** to true. -3. Click on the ***Add Filter*** button and select 'Order Status' from the dropdown list. -4. Select 'Completed' from the ***Order Status*** dropdown list. -5. Click on ***Execute Node*** to run the node. - -![Using the Unleashed Software node to get the list of completed sales order](/_images/integrations/builtin/app-nodes/unleashedsoftware/unleashedsoftware_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.uplead.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.uplead.md deleted file mode 100644 index 7be6ffb75..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.uplead.md +++ /dev/null @@ -1,34 +0,0 @@ -# UpLead - -[UpLead](https://www.uplead.com/) helps increase sales by quickly finding, connecting, and engaging with qualified prospects. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/uplead/). - - -## Basic Operations - -* Company - * Enrich -* Person - * Enrich - -## Example Usage - -This workflow allows you to get information about a company with UpLead. You can also find the [workflow](https://n8n.io/workflows/504) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [UpLead]() - -The final workflow should look like the following image. - -![A workflow with the UpLead node](/_images/integrations/builtin/app-nodes/uplead/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. UpLead node - -1. First of all, you'll have to enter credentials for the UpLead node. You can find out how to do that [here](/integrations/builtin/credentials/uplead/). -2. Enter the name of the company in the *Company* field. For example, I entered `Apple`. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.uproc.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.uproc.md deleted file mode 100644 index 9bc2eb0fb..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.uproc.md +++ /dev/null @@ -1,544 +0,0 @@ -# uProc - -[uProc](https://uproc.io/) is a data platform that allows to clean, verify, and enrich any data field. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/uProc/). - - -## Basic Operations - -**Audio** - -- Get advanced human audio file by provided text and language -- Get an audio file by provided text and language - - -**Communication** - -- Discover if a domain has a social network presence -- Discover if an email is valid, hard bounce, soft bounce, spam-trap, free, temporary, and recipient exists -- Discover if the email recipient exists, returning email status -- Check if an email domain has an SMTP server to receive emails -- Discover if the email has a social network presence -- Check if an email has a valid format -- Check if an email domain belongs to a disposable email service -- Check if email belongs to free service provider like Gmail, Hotmail -- Check if email is catchall -- Discover if an email exists in the Robinson list (only Spain) -- Check if email belongs to a system or role-based account -- Check if an email is a spam trap -- Discover if an IMEI number has a valid format -- Check if a LinkedIn profile is a first-degree contact -- Discover if mobile phone number exists in network operator, with worldwide coverage -- Discover if a mobile phone number has a valid format with worldwide coverage -- Discover if a mobile phone number has a valid format (only Spain) -- Discover if a mobile phone number has a valid prefix, with worldwide coverage -- Discover if a Spanish mobile phone number has a valid prefix -- Discover if a mobile number is switched on to call it later, with worldwide coverage -- Discover if a mobile number can receive SMS with worldwide coverage -- Discover if a phone (landline or mobile) exists in a Robinson list (only Spain) -- Discover if a landline or mobile number has a valid prefix -- Discover if a landline phone number is valid, with Spain coverage -- Allows discovering if landline number has a good international format, depending on the country -- Discover if a landline phone number prefix exists, with worldwide coverage -- Clean a phone removing non allowed characters -- Allows getting country code of a mobile phone number with international format -- Allows getting a domain from an email -- Discover an email by company website or domain and prospect's first-name and last-name -- Check if an email is personal or generic -- Get emails list found on the internet by domain or URI -- Get an emails list found on the internet by non-free email -- Get emails list found inside the website by domain or URI -- Get three first web references of an email published on the internet -- Allows you to fix the email domain of those misspelled emails -- Fix the international prefix of a phone based on the ISO code of a country -- Get GDPR compliant emails list by domain for your Email Marketing campaigns in Europe -- Discover if mobile exist via real-time HLR query -- Get personal email by social network profile -- Get portability data about a landline or mobile number, only for Spain -- Extract results from a LinkedIn search (employees in a company) -- Get members in a LinkedIn group -- Get 'Search LinkedIn Contacts' URL -- Extract the last 80 connections from your LinkedIn profile -- Extract the last 80 invitations sent from your LinkedIn -- Get users who comment on a post on LinkedIn -- Get users who like a post on LinkedIn -- Extract a LinkedIn profile -- Extract results from a LinkedIn search (profiles) -- Extract fastly last profiles that have published content on LinkedIn by specific keywords -- Discover if mobile exist via real-time HLR query, as well as portability and roaming data -- Get existence, portability, and roaming of a mobile phone via MNP query -- Discover if mobile or landline prefix exists in Spain -- Allows normalizing email address, removing non allowed characters -- Allows normalizing a mobile phone, removing non-allowed characters -- Parse phone number in multiple fields and verify format and prefix validity -- Allows getting country prefix number by country code -- Discover an email by company website or domain and prospect's first-name and last-name -- This tool parses a social URI address and extracts any available indicators -- Search all social networks by domain, parses all found URLs, and returns social networks KPIs -- Discover if a domain or a website has social activity and returns all social network profiles found -- Discover if an email has social activity, and get all social network profiles found -- Discover if a mobile phone has social activity, and get all social network profiles found -- Get web references for an email published on the internet -- Send a custom message invitation to a non connected LinkedIn profile -- Send a custom email to a recipient -- Send a custom SMS to a recipient with worldwide coverage -- Send a custom invitation message if a profile is connected or a custom message otherwise -- Visits a profile to show interest and get profile views in return from contact, increasing your LinkedIn network -- Send a custom private message to a connected LinkedIn profile -- Get an email by contact's LinkedIn profile URI -- Discover an email by company's name and prospect's full name -- Discover an email by company's website or domain and prospect's full name -- Get email by firstname, lastname, and company -- Get parsed and validated phone - - -**Company** - -- Discover if a CIF card number is valid -- Check if a company is a debtor by TaxID -- Check if the ISIN number is valid -- Check if the SS number is valid, only for Spain -- Identify and classify a prospecting role in detecting the right area and seniority to filter later -- Get a company's contact, social, and technology data by domain -- Get a company's contact, social, and technology data by email -- Get a company's data by CIF -- Get a company's data by DUNS -- Get a company's data by domain -- Get a company's data by email -- Get a company's data by IP address -- Get a company's data by name -- Get a company's data by phone number -- Get a company's data by social networks URI (LinkedIn, Twitter) -- Get a company's name by company domain -- Get professional data of a decision-maker by company name/domain and area -- Discover more suitable decision-maker using search engines (Bing) by company name and area -- Get professional emails of decision-makers by company domain and area -- Discover up to ten decision-makers using search engines (Bing) by company name and area -- Get a company's domain by company name -- Get employees by company name or domain, area, seniority, and country -- Get a company's Facebook profile by name without manually searching on Google or Facebook -- Get geocoded company data by IP address -- Get a company's LinkedIn profile by name without manually searching on Google or LinkedIn -- Allows normalizing a CIF number, removing non-allowed characters -- Get a company's phone by company domain -- Get a company's sales data by a company's DUNS number -- Get a company's sales data by a company's domain name -- Get a company's sales data by a company's name -- Get a company's sales data by a company's tax ID (CIF) -- Get a company's Twitter profile by name without manually searching on Google or Twitter -- Get decision maker by search engine -- Get decision makers by search engine -- Get Facebook URI by company's domain -- Get GitHub URI by company's domain -- Get Instagram URI by company's domain -- Get LinkedIn URI by company's domain -- Get Pinterest URI by company's domain -- Get Twitter URI by company's domain -- Get YouTube URI by company's domain - - -**Finance** - -- Check if crypto wallet is valid -- Discover if a BIC number has a valid format -- Discover if an account number has a valid format -- Check if credit card number checksum is valid -- Discover if an IBAN account number has a valid format -- Discover if an ISO currency code is valid -- Check if a TIN exists in Europe -- Convert amount between supported currencies and an exchange date -- Get credit card type -- Get multiple ISO currency codes by a country name -- Get all ISO currency by an IP address -- Get multiple ISO currency codes by a country ISO code -- Get ISO currency code by IP address -- Get ISO currency code by a currency ISO code -- Get ISO currency code by an ISO country code -- Get ISO currency code by a country name -- Get related European TIN in Europe -- Get IBAN by account number of the country -- Get to search data bank information by IBAN account number -- Get country VAT by address -- Get country VAT by coordinates -- Get Swift code lookup -- Get VAT by IP address -- Get VAT value by country ISO code -- Get VAT by phone number, with worldwide coverage -- Get VAT by zipcode - - -**Geographical** - -- Check if a country's ISO code exists -- Discover if the distance between two coordinates is equal to another -- Discover if the distance(in kilometers) between two coordinates is greater than the given input -- Discover if the distance(in kilometers) between two coordinates is greater or equal to the given input -- Discover if the distance(in kilometers) between two coordinates is lower than the given input -- Check if an address exists by a partial address search -- Check if a house number exists by a partial address search -- Check if coordinates have a valid format -- Discover if a zipcode number prefix exists (only for Spain) -- Discover if a zipcode number has a valid format (only for Spain) -- Get cartesian coordinates(X, Y, Z/WGS84) by Latitude and Longitude -- Get location by parameters -- Get multiple cities by phone prefix (only for Spain) -- Get multiple cities by partial initial text (only for Spain) -- Get multiple cities by zip code prefix (only for Spain) -- Get a city from IP -- City search by partial name (only for Spain) -- Discover the city name by a local phone number (only for Spain) -- Discover the city name by the zip code (only for Spain) -- Discover the community name from a zipcode (only for Spain) -- Discover latitude and longitude coordinates of an IP address -- Discover latitude and longitude coordinates of a postal address -- Get multiple country names by currency ISO code -- Get multiple countries by ISO code -- Get multiple country names by initial name -- Get country name by currency ISO code -- Get country name by IP address -- Get country name by its ISO code -- Get country by a prefix -- Get country name by phone number, with worldwide coverage -- Get Aplha2 code by a country prefix or a name -- Get decimal coordinates (degrees, minutes, and seconds) by latitude and longitude -- Returns straight-line distance(in kilometers) between two addresses -- Returns straight-line distance(in kilometers) between two GPS coordinates (latitude and longitude) -- Returns straight-line distance(in kilometers) between two IP addresses -- Returns straight-line distance(in kilometers) between two landline phones, using city and province of every phone -- Returns straight-line distance(in kilometers) between two zip codes, using city and province of every zip code -- Get an exact address by a partial address search -- Discover geographical, company, timezone, and reputation data by IPv4 address -- Discover the city name, zip code, province, country, latitude, and longitude from an IPv4 or IPv6 address and geocodes it -- Parse postal address into separated fields, getting an improved resolution -- Discover locale data (currency, language) by IPv4 or IPv6 address -- Discover the city name, zip code, province, or country by latitude and longitude -- Discover the city name, zip code, province, country, latitude, and longitude from an IPv4 or IPv6 address -- Discover the city and the province from a landline phone number (only Spain) -- Discover location data by name -- Discover the city and the province from a zipcode number (only Spain) -- Get the most relevant locations by name -- Get the most relevant locations by name, category, location, and radius -- Get multiple personal names by a prefix -- Discover network data by IPv4 or IPv6 address -- Allow normalizing an address by removing non allowed characters -- Allow normalizing a city by removing non allowed characters -- Allow normalizing a country by removing non allowed characters -- Allow normalizing a province by removing non allowed characters -- Allow normalizing a zipcode by removing non allowed characters -- Get normalized country -- Parse postal address into separated fields, getting a basic resolution -- Discover the province name from an IP address -- Get the first province by a name prefix (only for Spain) -- Discover the province name from a landline phone number (only for Spain) -- Discover the province name from a zipcode number (only for Spain) -- Get a province list by a name prefix (only for Spain) -- Get a province list by a phone prefix (only for Spain) -- Get a province list by a zipcode prefix (only for Spain) -- Discover reputation by IPv4 or IPv6 address -- Returns driving routing time, distance, fuel consumption, and cost between two addresses -- Returns driving routing time, distance, fuel consumption, and cost between two GPS coordinates -- Returns driving routing time, distance, fuel consumption, and cost between two IP addresses -- Returns driving routing time, distance, fuel consumption, and cost between two landline phones, using city and province of every phone (only for Spain) -- Returns driving routing time, distance, fuel consumption, and cost between two zip codes, using city and province of every zip code -- Discover date-time data by IPv4 or IPv6 address -- Get USNG coordinates by latitude and longitude -- Get UTM coordinates by latitude and longitude -- Discover the zip code if you have an IP address -- Get the first zipcode by prefix, only for Spain -- Get multiple zip codes by prefix, with worldwide coverage -- Get time data by coordinates -- Get time data by postal address - - -**Image** - -- Get QR code decoded content by an image URL -- It allows discovering all geographical and technical EXIF metadata present in a photographic JPEG image -- Get an encoded barcode by number and a required standard -- Get QR code encoded by a text -- Generate a new image by URL and text -- Discover logo (favicon) used in a domain -- Generate a screenshot by URL provided using Chrome browser -- Get OCR text from image - - -**Internet** - -- Check if a domain exists -- Check if a domain has a DNS record -- Check if a domain has the given IP address assigned -- Check if a domain has an MX record -- Check if a domain has a valid SSL certificate -- Check if a domain has a valid format -- Check if a domain accepts all emails, existing or not -- Check if a domain is a free service domain provider -- Check if a domain is temporary or not -- Discover if a computer is switched on -- Discover if service in a port is available -- Check if an URL contains a string or regular expression -- Check if an URL exists -- Check that an URL has a valid format -- Get full SSL certificate data by a domain (or website) and monitor your certificate status -- Get feed entries by domain -- Get last feed entry by domain -- Get text data from web, pdf or image allowing to filter some elements by regular expressions or field names -- Decode URL to recover original -- Get valid, existing, and default URL when accessing a domain using a web browser -- Get long version of shortened URL -- Discover device features by a user agent -- Get the network name of and IP address -- Get the domain record by its type -- Encode URL to avoid problems -- Copy file from one URL to another URL -- Fix an IP address to the right format -- Get the IPv4 address linked with a domain -- Convert a number to an IP address -- Get ISP known name of email domain name -- Convert an IP address to numeric notation -- Scan a host and returns the most commonly open ports -- Obtains a list with multiple results from a website -- Obtains the content of a website -- Decode URL into multiple fields -- Generate a PDF file by URL (provided using Chrome browser) -- Get the root domain of any web address, removing non needed characters -- Generates shareable URIs to use on social networks and email using a content URI and a text -- Get data from the existing table in an HTML page or a PDF file -- Discover client and server technologies used in a domain -- Discover client and server technologies used in web pages -- Analyze URL's health status about SSL, broken links, conflictive HTTP links with SSL, and more -- Get website visits and rank of any domain -- Get a domain's Whois data by fields -- Get Whois data fields by IP address provided - - -**Personal** - -- Check if age is between two numbers -- Check if date returns an age between 20 and 29 -- Check if date returns an age between 40 and 49 -- Check if age is greater than another -- Check if birth date returns an age greater than 64 -- Check if birth date belongs to an adult (18 years for Spain) -- Check if age is lower than another -- Check if age is lower or equal than another -- Check if ages are equal -- Discover if a date is between two dates -- Discover if a date is greater -- Discover if a date is greater or equal -- Discover if a date belongs to a leap year -- Discover if a date is lower -- Discover if a date is lower or equal -- Discover if a date has a valid format -- Discover if a gender value is valid -- Discover if an NIE card number is valid -- Discover if a NIF card number is valid -- Check if a personal name exists in the INE data source (only for Spain) -- Check if a name contains accepted characters -- Discover if a NIF exists in the Robison list (only for Spain) -- Check if surname contains accepted characters -- Check if a personal surname appears in INE data source (only for Spain) -- Discover if a DNI card number is valid -- Discover the age of a birt date -- Discover the age range of a person by birth date -- Get the difference between two dates -- Discover the gender of a person by the email -- Discover the gender of a person or company by the name -- Get LinkedIn employee profile URI by business email -- Get LinkedIn employee profile URI by first name, last name, and company -- Discover the letter of a DNI card number -- Get first personal name matching by prefix and gender from INE data source (only for Spain) -- Get LinkedIn URI by email -- Get LinkedIn URI by phone -- Allow normalizing a DNI number by removing non allowed characters -- Allow normalizing an NIE number by removing non allowed characters -- Normalize name by removing non allowed characters -- Normalize surname -- Get parsed date-time -- Normalize full name, fixing abbreviations, sorting if necessary, and returning first name, last name, and gender -- Get prospect's contact data and the company's location and social data by email -- Get contact, location, and social data by email and company name and location -- Get personal and social data by social profile -- Get personal data by email -- Get personal data by first name, last name, company, and location -- Get personal data by mobile -- Get personal data by social network profile -- Generate random fake data -- Get first personal surname matching by prefix from INE data source (only for Spain) -- Get personal surname matching by prefix from INE data source (only for Spain) -- Get Twitter profile by first name, last name, and company -- Get Xing profile by first name, last name, and company -- Add a contact email to a person list - - -**Product** - -- Check if an ASIN code exists on the Amazon Marketplace -- Check if an ASIN code has a valid format -- Check if an EAN code exists on Amazon Marketplace -- Check if an EAN barcode has a valid format -- Check if an EAN barcode of 13 digits has a valid format -- Check if an EAN barcode of 14 digits has a valid format -- Check if an EAN barcode of 18 digits has a valid format -- Check if an EAN barcode of 8 digits has a valid format -- Check if a GTIN barcode has a valid format -- Check if a GTIN barcode of 13 digits has a valid format -- Check if a GTIN barcode of 14 digits has a valid format -- Check if a GTIN barcode of 8 digits has a valid format -- Check if VIN Number is valid -- Allows checking if an ISBN book exists -- Allows checking if an ISBN10/13 code has a valid format -- Allows checking if an ISBN10 code has a valid format -- Allows checking if an ISBN13 code has a valid format -- Check if a UPC exists -- Check if a UPC has a valid format -- Get ASIN by EAN -- Get a book by author's surname -- Get all publications by category -- Get book data by an editor's name -- Get book or publication data by 10 or 13 digits ISBN code -- Get book data by title -- Get books by author's surname -- Get all books by category -- Get all books by editor -- Get all books by title -- Get EAN code by ASIN code -- Get product data on a UPC on Amazon Marketplace -- Get ISBN10 code by ISBN13 code -- Get ISBN13 code by ISBN10 code -- Get data By VIN number - - - -**Security** - -- Check if a Luhn number is valid -- Check if a password is strong -- Check if a UUID number is valid -- Get blacklists for a domain -- Get blacklists for an IP address - - -**Text** - -- Check if a string only contains alphabets -- Check if a string is alphanumeric -- Check if a string is boolean -- Check if the largest item in a list matches the provided item -- Check if IPv4 or IPv6 address has a valid format -- Check if IPv4 address has a valid format -- Check if IPv6 address has a valid format -- Check if the length of a list is between two quantities -- Checks if the length of a list equals a specified quantity -- Checks if the length of a list is greater than or equal to a certain amount -- Check if the length of a list is lower than a certain amount -- Check if the list contains a specific item -- Check if the list ends with a specific element -- Check if a list is sorted in ascending order -- Check if the list starts with a specific element -- Checks if the smallest element in a list matches the provided element -- Check if a string contains only numbers -- Check if a string contains a character -- Check if a string ends with a character -- Check if a string has no content -- Check if a string contains random characters -- Check if a string contains a value that matches with a regular expression -- Check if the length of a string is between two numbers -- Check if the length of a string is equal to a number -- Check if the length of a string is greater than a number -- Check if the length of a string is greater or equal to a number -- Check if the length of a string is lower than a number -- Check if the length of a string is lower or equal to a number -- Check if a string starts with a character -- Check if a string contains only lowercase characters -- Check if a string contains only uppercase characters -- Check if a list consists of unique elements -- Check if the supplied values form a valid list of elements -- Check if the number of words in a sentence is between two determined quantities -- Check if the number of words in a sentence equals a certain amount -- Check if the number of words in a sentence is greater than a certain amount -- Check if the number of words in a sentence is greater than -- Check if the word count is lower -- Check if the number of words present in a sentence is less than or equal to a quantity -- Convert a string to Base64 encoded value -- Discover banned English words in an email body or subject -- Get field names by analyzing the field value provided -- Get HTML code from Markdown -- Get Markdown text from HTML -- Get text without HTML -- Get spin string -- Format a string using a format pattern -- Generate random string using a regular expression as a pattern -- Return the largest item in a list -- Return the smallest item in a list -- Convert to lowercase -- Convert a string to MD5 encoded value -- Merge two strings -- Normalize a string depending on the field name -- Analyze string and return all emails, phones, zip codes, and links -- Convert a string to an SHA encoded value -- Analyze an English text with emojis and detect sentiment -- Returns an ascending sorted list -- Split a value into two parts and join them using a separator from the original string -- Split a value into two parts using a separator from the original string -- Get the length of a string -- Lookup string between multiple values by fuzzy logic and regex patterns -- Clean abuse words from a string -- Replace the first value found in a string with another -- Replace all values found in a string with another -- Translate a text into any language -- Return a single list with no repeating elements -- Convert all letters to uppercase -- Count total words in a text - - -## Example Usage - -This workflow allows you to take a screenshot of a website and send it to a Telegram channel. You can also find the [workflow](https://n8n.io/workflows/858) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [uProc]() -- [Telegram](/integrations/builtin/app-nodes/n8n-nodes-base.telegram/) - -The final workflow should look like the following image. - -![A workflow with the uProc node](/_images/integrations/builtin/app-nodes/uproc/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. uProc node (getUrlScreenshot) - - -This node will return the screenshot of the n8n website. If you want to get the screenshot of a different website, enter the domain of that website instead. - -1. First of all, you'll have to enter credentials for the uProc node. You can find out how to do that [here](/integrations/builtin/credentials/uProc/). -2. Select 'Image' from the ***Resource*** dropdown list. -3. Select 'Get Screenshot by URL' from the ***Operation*** dropdown list. -4. Enter `https://n8n.io` in the ***URL*** field. -5. Select '1024' from the ***Width*** dropdown list. -6. Select 'Yes' from the ***Fullpage*** dropdown list. -7. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns a URL of the screenshot of the website. - -![Using the uProc node to get a screenshot of a website](/_images/integrations/builtin/app-nodes/uproc/uproc_node.png) - -### 3. Telegram node (sendPhoto: message) - -This node will send the screenshot that we received from the previous node. - -1. First of all, you'll have to enter credentials for the Telegram node. You can find out how to do that [here](/integrations/builtin/credentials/telegram/). -2. Select 'Send Photo' from the ***Operation*** dropdown list. -3. Enter a chat ID in the ***Chat ID*** field. Refer to the [FAQs](/integrations/builtin/app-nodes/n8n-nodes-base.telegram/#how-do-i-get-the-chat-id) of the Telegram node to learn how to get the chat ID. -4. Click on the gears icon next to the ***Photo*** field and click on ***Add Expression***. - -5. Select the following in the ***Variable Selector*** section: Nodes > uProc > Output Data > JSON > message > result. You can also add the following expression: `{{$node["uProc"].json["message"]["result"]}}`. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends the screenshot image to the channel that we specify. - -![Using the Telegram node to send the image of the screenshot](/_images/integrations/builtin/app-nodes/uproc/telegram_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.uptimeRobot.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.uptimeRobot.md deleted file mode 100644 index 329fd11c5..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.uptimeRobot.md +++ /dev/null @@ -1,100 +0,0 @@ -# UptimeRobot - -[UptimeRobot](https://uptimerobot.com/) is an uptime monitoring service. It monitors your website every 5 mins. You can set an HTTP/S, ping, port, keyword, or heartbeat monitor and get notifications to your email, phone, Telegram, Slack, Twitter, etc. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/uptimeRobot/). - - -## Basic Operations - -* Account - * Get account details -* Alert Contact - * Create an alert contact - * Delete an alert contact - * Get an alert contact - * Get all alert contacts - * Update an alert contact -* Maintenance Window - * Create a maintenance window - * Delete a maintenance window - * Get a maintenance window - * Get all a maintenance windows - * Update a maintenance window -* Monitor - * Create a monitor - * Delete a monitor - * Get a monitor - * Get all monitors - * Reset a monitor - * Update a monitor -* Public Status Page - * Create a public status page - * Delete a public status page - * 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.urlScanIo.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.urlScanIo.md deleted file mode 100644 index 787e26e42..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.urlScanIo.md +++ /dev/null @@ -1,14 +0,0 @@ -# urlscan.io - -[urlscan.io](https://urlscan.io/) is a free service to scan and analyse websites. When a URL is submitted to urlscan.io, an automated process will browse to the URL like a regular user and record the activity that this page navigation creates. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/urlScanIo/). - - -## Basic Operations - -* Scan - * Get - * Get All - * Perform diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.venafiTlsProtectCloud.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.venafiTlsProtectCloud.md deleted file mode 100644 index 5da667502..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.venafiTlsProtectCloud.md +++ /dev/null @@ -1,32 +0,0 @@ -# Venafi TLS Protect Cloud - -[Venafi](https://www.venafi.com/){:target=_blank .external-link} is a cybersecurity company providing services for machine identity management. They offer solutions to manage and protect identities for a wide range of machine types, delivering global visibility, lifecycle automation, and actionable intelligence. - -The n8n Venafi TLS Protect Cloud node allows you to integrate with the [cloud-based Venafi TLS Protect](https://vaas.venafi.com/){:target=_blank} service. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/venafiTlsProtectCloud/). - -## Operations - -* Certificate - * Delete - * Download - * Get - * Get Many - * Renew -* Certificate Request - * Create - * Get - * Get Many - -## Related resources - -Refer to [Venafi's REST API documentation](https://docs.venafi.cloud/api/vaas-rest-api/){:target=_blank .external-link} for more information on this service. - -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/) and [trigger node](/integrations/builtin/trigger-nodes/n8n-nodes-base.venafitlsprotectdatacentertrigger/) 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 deleted file mode 100644 index c8671047d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectdatacenter.md +++ /dev/null @@ -1,27 +0,0 @@ -# Venafi TLS Protect Datacenter - -[Venafi](https://www.venafi.com/){:target=_blank .external-link} is a cybersecurity company providing services for machine identity management. They offer solutions to manage and protect identities for a wide range of machine types, delivering global visibility, lifecycle automation, and actionable intelligence. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/venafiTlsProtectDatacenter/). - -## Operations - -* Certificate - * Create - * Delete - * Download - * Get - * Get Many - * Renew -* Policy - * Get - -## Related resources - -View [example workflows and related content](https://n8n.io/integrations/venafi-tls-protect-datacenter/){:target=_blank .external-link} on n8n's website. - -n8n also provides: - -* A [trigger node](/integrations/builtin/trigger-nodes/n8n-nodes-base.venafitlsprotectdatacentertrigger/) for Venafi TLS Protect Datacenter. -* 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. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.vero.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.vero.md deleted file mode 100644 index 3422f1474..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.vero.md +++ /dev/null @@ -1,41 +0,0 @@ -# Vero - -[Vero](https://www.getvero.com/) is a messaging platform that helps manage real-time data to create a better customer experience. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/vero/). - - -## Basic Operations - -* User - * Create or update a user profile - * Change a users identifier - * Unsubscribe a user. - * Resubscribe a user. - * Delete a user. - * Adds a tag to a users profile. - * Removes a tag from a users profile. -* Event - * 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.vonage.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.vonage.md deleted file mode 100644 index ff8cff90d..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.vonage.md +++ /dev/null @@ -1,68 +0,0 @@ -# Vonage - -[Vonage](https://vonage.com/) provides unified communications, contact centers, and programmable communications APIs. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/vonage/). - - -## Basic Operations - -* SMS - * Send - -## Example Usage - -This workflow allows you to send daily weather updates via an SMS message using the Vonage node. You can also find the [workflow](https://n8n.io/workflows/723) on n8n.io. This example usage workflow uses the following nodes. -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/) -- [Vonage]() - -The final workflow should look like the following image. - -![A workflow with the Vonage node](/_images/integrations/builtin/app-nodes/vonage/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow daily at 9 AM. - -1. Click on ***Add Cron Time***. -2. Set hours to 9 in the ***Hour*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every day at 9 AM. - -![Using the Cron node to trigger the workflow daily at 9 am](/_images/integrations/builtin/app-nodes/vonage/cron_node.png) - -### 2. OpenWeatherMap node (Current Weather) - -This node will return data about the current weather in Berlin. To get the weather updates for your city, you can enter the name of your city instead. - -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. Enter `berlin` in the ***City*** field. -3. 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/vonage/openweathermap_node.png) - -### 3. Vonage node (send: sms) - -This node will send an SMS with the weather update, which was sent by the previous node. - -1. First of all, you'll have to enter credentials for the Vonage node. You can find out how to do that [here](/integrations/builtin/credentials/vonage/). -2. Enter a Vonage phone number or the brand name in the ***From*** field. -3. Enter the receiver's phone number in the ***To*** field. -4. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. - -5. Enter the following message in the ***Expression*** field: `Hey! The temperature outside is {{$node["OpenWeatherMap"].json["main"]["temp"]}}°C.`. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends an SMS to the phone number that we specified with the weather update, which was sent by the previous node. - -![Using the Vonage node to send weather updates via SMS](/_images/integrations/builtin/app-nodes/vonage/vonage_node.png) - - - - diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.webflow.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.webflow.md deleted file mode 100644 index d5def6d77..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.webflow.md +++ /dev/null @@ -1,110 +0,0 @@ -# Webflow - -[Webflow](https://webflow.com) is an application that allows you to build responsive websites with browser-based visual editing software. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/webflow/). - - -## Basic Operations - -* Item - * Create - * Delete - * Get - * 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.wekan.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.wekan.md deleted file mode 100644 index 42cad928b..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.wekan.md +++ /dev/null @@ -1,156 +0,0 @@ -# Wekan - -[Wekan](https://wekan.github.io/) is an open-source kanban board that allows a card-based task and to-do management. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/wekan/). - - -## Basic Operations - -* Board - * Create a new board - * Delete a board - * Get the data of a board - * Get all user boards -* Card - * Create a new card - * Delete a card - * Get a card - * Get all cards - * Update a card -* Card Comment - * Create a comment on a card - * Delete a comment from a card - * Get a card comment - * Get all card comments -* Checklist - * Create a new checklist - * Delete a checklist - * Get the data of a checklist - * Returns all checklists for the card -* Checklist Item - * Delete a checklist item - * Get a checklist item - * Update a checklist item -* List - * Create a new list - * Delete a list - * Get the data of a list - * Get all board lists - -## Example Usage - -This workflow allows you to create a board and two lists called `To Do` and `Done` using the Wekan node. It also allows you to create a card and update the list ID of the card, enabling you to move it from the `To Do` list to the `Done` list. You can also find the [workflow](https://n8n.io/workflows/728) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Wekan]() - -The final workflow should look like the following image. - -![A workflow with the Wekan node](/_images/integrations/builtin/app-nodes/wekan/workflow.png) - - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. Wekan node (create: board) - -This node will create a board called `Documentation` in Wekan. To create a board with a different name, you can enter the name of your board instead. - -1. First of all, you'll have to enter credentials for the Wekan node. You can find out how to do that [here](/integrations/builtin/credentials/wekan/). - -2. Select 'Board' from the ***Resource*** dropdown list. -3. Enter `Documentation` in the ***Title*** field. -4. Select the owner of the board from the ***Owner*** dropdown list. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new board with the title `Documentation`. - - -![Using the Wekan node to create a board](/_images/integrations/builtin/app-nodes/wekan/wekan_node.png) - - -### 3. Wekan1 node (create: list) - -This node will create a list with the title `To Do` in the `Documentation` board, which was created using the previous node. - -1. Select the credentials that you entered in the previous node. -2. Select 'List' from the ***Resource*** dropdown list. -3. Click on the gears icon next to the ***Board ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Wekan > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan"].json["_id"]}}`. -5. Enter `To Do` in the ***Title*** field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new list called `To Do` in the `Documentation` board. - - -![Using the Wekan node to create a list with the title To Do](/_images/integrations/builtin/app-nodes/wekan/wekan1_node.png) - - -### 4. Wekan2 node (create: list) - -This node will create a list with the title `Done` in the `Documentation` board, which was created using the Wekan node. - -1. Select the credentials that you entered in the previous node. -2. Select 'List' from the ***Resource*** dropdown list. -3. Click on the gears icon next to the ***Board ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Wekan > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan"].json["_id"]}}`. -5. Enter `Done` in the ***Title*** field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new list called `Done` in the `Documentation` board. - - -![Using the Wekan node to create a list with the title Done](/_images/integrations/builtin/app-nodes/wekan/wekan2_node.png) - - -### 5. Wekan3 node (create: card) - -This node will create a card in the `Documentation` board under the list titled `To Do`, which was created using the Wekan1 node. - -1. Select the credentials that you entered in the previous node. -2. Click on the gears icon next to the ***Board ID*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Nodes > Wekan > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan"].json["_id"]}}`. -4. Click on the gears icon next to the ***List ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > Wekan1 > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan1"].json["_id"]}}`. -6. Enter `Document Wekan node` in the ***Title*** field. -7. Select 'Default' from the ***Swimlane ID*** dropdown list. -8. Select an author from the ***Author ID*** dropdown list. -9. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new card with the title `Document Wekan node` in the `To Do` list of the `Documentation` board. - - -![Using the Wekan node to create a card in the To Do list](/_images/integrations/builtin/app-nodes/wekan/wekan3_node.png) - - -### 6. Wekan4 node (update: card) - -This node will update the list ID of the card created by the previous node and move it from the `To Do` list to the `Done` list. - -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 ***Board ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Wekan > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan"].json["_id"]}}`. -5. Click on the gears icon next to the ***List ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Wekan1 > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan1"].json["_id"]}}`. -7. Click on the gears icon next to the ***Card ID*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > Wekan3 > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan3"].json["_id"]}}`. -9. Click on the ***Add Field*** button and select 'List ID'. -10. Click on the gears icon next to the ***List ID*** field and click on ***Add Expression***. -11. Select the following in the ***Variable Selector*** section: Nodes > Wekan2 > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan2"].json["_id"]}}`. -12. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node updates the list id of the card that we created in the previous node and moves it from the `To Do` list to the `Done` list. - - -![Using the Wekan node to update the card](/_images/integrations/builtin/app-nodes/wekan/wekan4_node.png) - - -## FAQs - -### How to load all the parameters for the node? - -To load all the parameters, for example, Author ID, you need to give admin permissions to the user. Refer to the [Wekan documentation](https://github.com/wekan/wekan/wiki/Features#members-click-member-initials-or-avatar--permissions-adminnormalcomment-only) to learn how to change permissions. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.whatsapp.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.whatsapp.md deleted file mode 100644 index db0a9df32..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.whatsapp.md +++ /dev/null @@ -1,22 +0,0 @@ -# WhatsApp Business Platform - -[WhatsApp Business Platform](https://developers.facebook.com/docs/whatsapp/){:target=_blank .external-link} gives medium to large businesses the ability to connect with customers at scale. You can start conversations with customers in minutes, send customer care notifications or purchase updates, offer your customers a level of personalized service and provide support in the channel that your customers prefer to be reached on. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/whatsapp/). - -## Operations - -* Message - * Send - * Send Template -* Media - * Upload - * Download - * Delete - -## Related resources - -Refer to [WhatsApp Business Platform's Cloud API documentation](https://developers.facebook.com/docs/whatsapp/cloud-api){:target=_blank} for details about the operations. - -View [example workflows and related content](https://n8n.io/integrations/whatsapp-business-cloud/){:target=_blank .external-link} on n8n's website. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.wise.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.wise.md deleted file mode 100644 index 41071d11e..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.wise.md +++ /dev/null @@ -1,111 +0,0 @@ -# Wise - -[Wise](https://wise.com) allows you to transfer money abroad with low-cost money transfers, receive money with international account details, and track transactions on your phone. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/wise/). - - -## Basic Operations - -* Account - * Retrieve balances for all account currencies of this user. - * Retrieve currencies in the borderless account of this user. - * Retrieve the statement for the borderless account of this user. -* Exchange Rate - * Get -* Profile - * Get - * Get All -* Recipient - * Get All -* Quote - * Create - * Get -* Transfer - * Create - * Delete - * Execute - * 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.wooCommerce.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.wooCommerce.md deleted file mode 100644 index e2d20bc8f..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.wooCommerce.md +++ /dev/null @@ -1,88 +0,0 @@ -# WooCommerce - -[WooCommerce](https://woocommerce.com/) is a customizable, open-source e-commerce plugin for WordPress. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/wooCommerce/). - - -## Basic Operations - -* Customer - * Create a customer - * Delete a customer - * Retrieve a customer - * Retrieve all customers - * Update a customer -* Order - * Create a order - * Delete a order - * Get a order - * Get all orders - * Update an order -* Product - * Create a product - * Delete a product - * Get a product - * Get all products - * Update a product - -## Example Usage - -This workflow allows you to create, update, and get a product from WooCommerce. You can also find the [workflow](https://n8n.io/workflows/847) on n8n.io. This example usage workflow uses the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [WooCommerce]() - -The final workflow should look like the following image. - -![A workflow with the WooCommerce node](/_images/integrations/builtin/app-nodes/woocommerce/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. WooCommerce node (create: product) - -This node will create a new product in WooCommerce. - -1. First of all, you'll have to enter credentials for the WooCommerce node. You can find out how to do that [here](/integrations/builtin/credentials/wooCommerce/). -2. Enter the product name in the ***Name*** field. -3. Click on ***Add Field*** and select 'Description'. -4. Enter a description in the ***Description*** field. -5. Click on ***Add Field*** and select 'Regular Price'. -6. Enter the price in the ***Regular Price*** field. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new product. - -![Using the WooCommerce node to create a new product](/_images/integrations/builtin/app-nodes/woocommerce/woocommerce_node.png) - -### 3. WooCommerce1 node (update: product) - -This node will update the product that we created in the previous node. We will update the quantity of the product. - -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 ***Product ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > WooCommerce > Output Data > JSON > id. You can also add the following expression: `{{$node["WooCommerce"].json["id"]}}`. -5. Click on ***Add Field*** and select 'Stock Quantity'. -6. Set the quantity in the ***Stock Quantity*** field. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node updates the quantity of the product that we created in the previous node. - -![Using the WooCommerce node to update the quantity of a product](/_images/integrations/builtin/app-nodes/woocommerce/woocommerce1_node.png) - -### 4. WooCommerce2 node (get: product) - -This node will get the information about the product that we created using the WooCommerce 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 ***Product ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > WooCommerce > Output Data > JSON > id. You can also add the following expression: `{{$node["WooCommerce"].json["id"]}}`. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the information about the product that we created using the WooCommerce node. - -![Using the WooCommerce node to get the information of a product](/_images/integrations/builtin/app-nodes/woocommerce/woocommerce2_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 deleted file mode 100644 index 862af0536..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.wordpress.md +++ /dev/null @@ -1,56 +0,0 @@ -# WordPress - -[WordPress](https://wordpress.org/) is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/wordpress/). - - -## Basic Operations - -* Post - * Create a post - * Get a post - * Get all posts - * Update a post -* User - * Create a user - * Get a user - * 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.xero.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.xero.md deleted file mode 100644 index b2ab2c39f..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.xero.md +++ /dev/null @@ -1,41 +0,0 @@ -# Xero - -Xero offers an online cloud-based SaaS accounting software platform for small and medium-sized businesses. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/xero/). - - -## Basic Operations - -* Contact - * Create a contact - * Get a contact - * Get all contacts - * Update a contact -* Invoice - * Create a invoice - * Get a invoice - * Get all invoices - * Update a invoice - -## Example Usage - -This workflow allows you to get upto 100 invoices from Xero. You can also find the [workflow](https://n8n.io/workflows/543) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Xero]() - -The final workflow should look like the following image. - -![A workflow with the Xero node](/_images/integrations/builtin/app-nodes/xero/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Xero node - -1. First of all, you'll have to enter credentials for the Xero node. You can find out how to do that [here](/integrations/builtin/credentials/xero/). -2. Select 'Get All' from the *Operation* dropdown list. -3. Select the organization for which you want to get the invoices from the *Organization ID* dropdown list. -4. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.youTube.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.youTube.md deleted file mode 100644 index c005700fd..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.youTube.md +++ /dev/null @@ -1,103 +0,0 @@ -# YouTube - -[YouTube](https://www.youtube.com) is an online video-sharing platform. YouTube allows users to upload, view, rate, share, add to playlists, report, comment on videos, and subscribe to other users. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Basic Operations - -* Channel - * Retrieve a channel - * Retrieve all channels - * Update a channel - * Upload a channel banner -* Playlist - * Create a playlist - * Delete a playlist - * Get a playlist - * Retrieve all playlists - * Update a playlist -* Playlist Item - * Add an item to a playlist - * Delete a item from a playlist - * Get a playlist's item - * Retrieve all playlist items -* Video - * Delete a video - * Get a video - * Retrieve all videos - * Rate a video - * Update a video - * Upload a video -* Video Category - * Retrieve all video categories - -## Example Usage - -This workflow allows you to upload a video, create a playlist, and add the video to the playlist in YouTube. You can also find the [workflow](https://n8n.io/workflows/638) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) -- [YouTube]() - -The final workflow should look like the following image. - -![A workflow with the Gmail node](/_images/integrations/builtin/app-nodes/youtube/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Read Binary File node - -1. Enter the path to the video file you want to upload in the ***File Path*** field. -2. Click on ***Execute Node*** to run the node. - -![Using the Read Binary File node to get the video](/_images/integrations/builtin/app-nodes/youtube/readbinaryfile_node.png) - - - -### 3. YouTube node (upload: video) - -1. First of all, you'll have to enter credentials for the YouTube node. You can find out how to do that [here](/integrations/builtin/credentials/google/). -2. Select 'Video' from the ***Resource*** dropdown list. -3. Select 'Upload' from the ***Operation*** dropdown list. -4. Enter the title of the video in the ***Title*** field. -5. Select the region code from ***Region Code*** dropdown list. -6. Select the video category from the ***Category ID*** dropdown list. -7. Click on ***Execute Node*** to run the node. - - -![Using the YouTube node to upload a video](/_images/integrations/builtin/app-nodes/youtube/youtube_node.png) - - - -### 4. YouTube1 node (create: playlist) - -1. Select the credentials that you entered in the previous YouTube node. -2. Select 'Playlist' from the ***Resource*** dropdown list. -3. Select 'Create' from the ***Operation*** dropdown list. -4. Enter the title of the playlist in the ***Title*** field. -5. Click on ***Execute Node*** to run the node. - - -![Using the YouTube node to create a playlist](/_images/integrations/builtin/app-nodes/youtube/youtube1_node.png) - - - -### 5. YouTube2 node (add: playlistItem) - -1. Select the credentials that you entered in the previous YouTube node. -2. Select 'Playlist Item' from the ***Resource*** dropdown list. -3. Select the playlist from the ***Playlist ID*** dropdown list. -4. Click on the gears icon next to the ***Video ID*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > YouTube > Output Data > JSON > id. You can also add the following expression: `{{$node["YouTube"].json["id"]}}`. -6. Click on ***Execute Node*** to run the node. - - -![Using the YouTube node to add the video to the playlist](/_images/integrations/builtin/app-nodes/youtube/youtube2_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 deleted file mode 100644 index 2b32a0201..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.yourls.md +++ /dev/null @@ -1,56 +0,0 @@ -# Yourls - -[Yourls](http://yourls.org/) is a free and open-source software that allows you to run your URL shortening service. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/yourls/). - - -## Basic Operations - -* URL - * Expand a URL - * 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/docs/integrations/builtin/app-nodes/n8n-nodes-base.zammad.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.zammad.md deleted file mode 100644 index ba08b27fe..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.zammad.md +++ /dev/null @@ -1,34 +0,0 @@ -# Zammad - -[Zammad](https://zammad.com/) is a free helpdesk and issue tracking system. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/zammad/). - - -## Basic Operations - -* Group - * Create a group - * Delete a group - * Retrieve a group - * Get all groups - * Update a group -* Organization - * Create an organization - * Delete an organization - * Retrieve an organization - * Retrieve all organizations - * Update an organization -* Ticket - * Create a ticket - * Delete a ticket - * Retrieve a ticket - * Retrieve all tickets -* User - * Create a user - * Delete a user - * Retrieve a user - * Retrieve all users - * Retrieve currently logged-in user - * Update a user diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.zendesk.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.zendesk.md deleted file mode 100644 index a2998891a..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.zendesk.md +++ /dev/null @@ -1,57 +0,0 @@ -# Zendesk - -[Zendesk](https://www.zendesk.com/) is a support ticketing system, designed to help track, prioritize, and solve customer support interactions. More than just a help desk, Zendesk Support helps nurture customer relationships with personalized, responsive support across any channel. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/zendesk/). - - -## Basic Operations - -* Ticket - * Create a ticket - * Delete a ticket - * Get a ticket - * Get all tickets - * Recover a suspended ticket - * Update a ticket -* Ticket Field - * Get a ticket field - * Get all system and custom ticket fields -* User - * Create a user - * Delete a user - * Get a user - * Get all users - * Get a user's organizations - * Get data related to the user - * Search users - * Update a user -* Organization - * Create an organization - * Delete an organization - * Count organizations - * Get an organization - * Get all organizations - * Get data related to the organization - * Update a organization - -## Example Usage - -This workflow allows you to create a ticket in Zendesk. You can also find the [workflow](https://n8n.io/workflows/496) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Zendesk]() - -The final workflow should look like the following image. - -![A workflow with the Zendesk node](/_images/integrations/builtin/app-nodes/zendesk/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Zendesk node - -1. First of all, you'll have to enter credentials for the Zendesk node. You can find out how to do that [here](/integrations/builtin/credentials/zendesk/). -2. Enter the description of the ticket in the *Description* field. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.zohoCrm.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.zohoCrm.md deleted file mode 100644 index ae525c917..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.zohoCrm.md +++ /dev/null @@ -1,101 +0,0 @@ -# Zoho CRM - -[Zoho CRM](https://www.zoho.com/crm/) is an online Sales CRM software that manages sales, marketing and support. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/zoho/). - - -## Basic Operations - -* Account - * Create an account - * Create a new record, or update the current one if it already exists (upsert) - * Delete an account - * Get an account - * Get all accounts - * Update an account -* Contact - * Create a contact - * Create a new record, or update the current one if it already exists (upsert) - * Delete a contact - * Get a contact - * Get all contacts - * Update a contact -* Deal - * Create a deal - * Create a new record, or update the current one if it already exists (upsert) - * Delete a contact - * Get a contact - * Get all contacts - * Update a contact -* Invoice - * Create an invoice - * Create a new record, or update the current one if it already exists (upsert) - * Delete an invoice - * Get an invoice - * Get all invoices - * Update an invoice -* Lead - * Create a lead - * Create a new record, or update the current one if it already exists (upsert) - * Delete a lead - * Get a lead - * Get all leads - * Get lead fields - * Update a lead -* Product - * Create a product - * Create a new record, or update the current one if it already exists (upsert) - * Delete a product - * Get a product - * Get all products - * Update a product -* Purchase Order - * Create a purchase order - * Create a new record, or update the current one if it already exists (upsert) - * Delete a purchase order - * Get a purchase order - * Get all purchase orders - * Update a purchase order -* Quote - * Create a quote - * Create a new record, or update the current one if it already exists (upsert) - * Delete a quote - * Get a quote - * Get all quotes - * Update a quote -* Sales Order - * Create a sales order - * Create a new record, or update the current one if it already exists (upsert) - * Delete a sales order - * Get a sales order - * Get all sales orders - * Update a sales order -* Vendor - * Create a vendor - * Create a new record, or update the current one if it already exists (upsert) - * Delete a vendor - * Get a vendor - * Get all vendors - * Update a vendor - -## Example Usage - -This workflow allows you to get the data of all leads from Zoho CRM. You can also find the [workflow](https://n8n.io/workflows/552) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Zoho CRM]() - -The final workflow should look like the following image. - -![A workflow with the Zoho CRM node](/_images/integrations/builtin/app-nodes/zohocrm/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Zoho CRM node - -1. First of all, you'll have to enter credentials for the Zoho CRM node. You can find out how to do that [here](/integrations/builtin/credentials/zoho/). -2. Select the 'Get All' option from the *Operation* dropdown list. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.zoom.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.zoom.md deleted file mode 100644 index 99b952ee7..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.zoom.md +++ /dev/null @@ -1,36 +0,0 @@ -# Zoom - -[Zoom](https://zoom.us/) is a communications technology company that provides videotelephony and online chat services through a cloud-based peer-to-peer software platform and is used for teleconferencing, telecommuting, distance education, and social relations. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/zoom/). - - -## Basic Operations - -* Meeting - * Create a meeting - * Delete a meeting - * Retrieve a meeting - * Retrieve all meetings - * Update a meeting - -## Example Usage - -This workflow allows you to create a meeting in Zoom. You can also find the [workflow](https://n8n.io/workflows/453) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Zoom]() - -The final workflow should look like the following image. - -![A workflow with the Zoom node](/_images/integrations/builtin/app-nodes/zoom/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Zoom node - -1. First of all, you'll have to enter credentials for the Zoom node. You can find out how to do that [here](/integrations/builtin/credentials/zoom/). -2. Enter the topic of the meeting in the *Topic* field. -3. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.zulip.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.zulip.md deleted file mode 100644 index 112461dc5..000000000 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.zulip.md +++ /dev/null @@ -1,50 +0,0 @@ -# Zulip - -[Zulip](https://zulipchat.com/) is an open source chat and collaborative software. In Zulip, communication occurs in streams (which are like channels in IRC). - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/zulip/). - - -## Basic Operations - -* Message - * Delete a message - * Get a message - * Send a private message - * Send a message to stream - * Update a message - * Upload a file -* Stream - * Create a stream. - * Delete a stream. - * Get all streams. - * Get subscribed streams. - * Update a stream. -* User - * Create a user. - * Deactivate a user. - * Get a user. - * Get all users. - * Update a user. - -## Example Usage - -This workflow allows you to send a private message on Zulip. You can also find the [workflow](https://n8n.io/workflows/498) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Zulip]() - -The final workflow should look like the following image. - -![A workflow with the Zulip node](/_images/integrations/builtin/app-nodes/zulip/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Zulip node - -1. First of all, you'll have to enter credentials for the Zulip node. You can find out how to do that [here](/integrations/builtin/credentials/zulip/). -2. Select the user you want to send a private message to from the *To* dropdown list. -3. Type the message you want to post in the *Content* field. -4. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/core-nodes/index.md b/docs/integrations/builtin/core-nodes/index.md deleted file mode 100644 index 4be788574..000000000 --- a/docs/integrations/builtin/core-nodes/index.md +++ /dev/null @@ -1,6 +0,0 @@ -# Core nodes library - -This section provides information about n8n's core nodes. - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.activationTrigger.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.activationTrigger.md deleted file mode 100644 index d95ab7e1f..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.activationTrigger.md +++ /dev/null @@ -1,57 +0,0 @@ -# Activation Trigger - -The Activation Trigger node gets triggered when an event gets fired by n8n or a workflow. - -!!! warning - The Activation Trigger node has been deprecated. It has been replaced by two new nodes - the [n8n Trigger](/integrations/builtin/core-nodes/n8n-nodes-base.n8nTrigger/) and the [Workflow Trigger](/integrations/builtin/core-nodes/n8n-nodes-base.workflowTrigger/) node. For more details, check out the entry in the [breaking changes](https://github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md#01170) page. - - -!!! note "Keep in mind" - If you want to use the Activation Trigger node for a workflow, add the node to the workflow. You don't have to create a separate workflow. - - -The Activation Trigger node gets triggered for the workflow that it gets added to. The Activation Trigger node can be used to trigger a workflow to notify the state of the workflow. - -## Node Reference - -- Events - - ***Activation:*** Run when the workflow gets activated - - ***Start:*** Run when n8n starts or restarts - - ***Update:*** Run when the workflow gets saved while it is active - -## Example Usage - -This workflow allows you to receive a message on Mattermost when a workflow is updated. You can also find the [workflow](https://n8n.io/workflows/1033) on n8n.io. This example usage workflow uses the following nodes. -- [Activation Trigger]() -- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/) - -The final workflow should look like the following image. - -![A workflow with the Webhook node](/_images/integrations/builtin/core-nodes/activationtrigger/workflow.png) - -### 1. Activation Trigger node - -Open the workflow where you want to add the activation workflow. Add the Activation Trigger node to the workflow. - -The Activation Trigger node will trigger the workflow when the workflow gets updated. - -1. Select 'Update' from the ***Events*** dropdown list. - -In the screenshot below, you will notice that the node triggers the workflow when the workflow gets updated. - -![Using the Activation Trigger node to trigger the workflow](/_images/integrations/builtin/core-nodes/activationtrigger/activationtrigger_node.png) - -### 2. Mattermost node (post: message) - -This node will send a message in the `workflow` channel on Mattermost. - -1. First of all, you'll have to enter credentials for the Mattermost node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/mattermost/). -2. Select a channel from the ***Channel ID*** dropdown list. -3. Click on the gears icon next to the ***Message*** field click on ***Add Expression***. - -4. Enter the following message in the ***Expression*** field: `The workflow {{$workflow.name}}, was updated.`. `$workflow.name` returns the name of the workflow. -5. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that the node sends a message to Mattermost. - -![Using the Mattermost node to send a message to a channel](/_images/integrations/builtin/core-nodes/activationtrigger/mattermost_node.png) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.code.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.code.md deleted file mode 100644 index 213177221..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.code.md +++ /dev/null @@ -1,41 +0,0 @@ -# Code - -The Code node allows you to write custom JavaScript and run it as a step in your workflow. - -!!! note "Function and Function Item nodes" - The Code node replaces the Function and Function Item nodes from version 0.198.0 onwards. If you're using an older version of n8n, you can still view the [Function node documentation](https://github.com/n8n-io/n8n-docs/blob/67935ad2528e2e30d7984ea917e4af2910a096ec/docs/integrations/builtin/core-nodes/n8n-nodes-base.function.md){:target=_blank .external-link} and [Function Item node documentation](https://github.com/n8n-io/n8n-docs/blob/67935ad2528e2e30d7984ea917e4af2910a096ec/docs/integrations/builtin/core-nodes/n8n-nodes-base.functionItem.md){:target=_blank .external-link}. - -## Choose a mode - -There are two modes: - -* **Run Once for All Items**: this is the default. When your workflow runs, the code in the code node executes once, regardless of how many input items there are. -* **Run Once for Each Item**: choose this if you want your code to run for every input item. - -## Supported JavaScript features - -The Code node supports: - -* Promises. Instead of returning the items directly, you can return a promise which resolves accordingly. -* Writing to your browser console using `console.log`. This is useful for debugging and troubleshooting your workflows. - -## Data structure and item linking - -When working with the Code node, you need to understand the following concepts: - -* [Data structure](/data/data-structure/): understand the data you receive in the Code node, and requirements for outputting data from the node. -* [Item linking](/data/data-mapping/data-item-linking/): learn how data items work. You need to handle item linking when the number of input and output items doesn't match. - -## Built-in methods and variables - -n8n includes built-in methods and variables. These provide support for: - -* Accessing specific item data -* Accessing data about workflows, executions, and your n8n environment -* Convenience variables to help with data and time - -Refer to [methods and variables](/code-examples/methods-variables-reference/) for more information. - -## External libraries - -If you self-host n8n, you can import and use built-in and external npm modules in the Code node. To learn how to enable external modules, refer the [Configuration](/hosting/configuration/#use-built-in-and-external-modules-in-the-code-node) guide. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.comparedatasets.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.comparedatasets.md deleted file mode 100644 index 230b568ce..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.comparedatasets.md +++ /dev/null @@ -1,23 +0,0 @@ -# Compare Datasets - -The Compare Datasets node helps you compare data from two input streams. - -## Usage - -1. Decide which fields to compare. In **Input 1 Field**, enter the name of the field you want to use from input stream 1. In **Input 2 Field**, enter the name of the field you want to use from input stream 2. -2. **Optional**: you can compare by multiple fields. Select **Add Fields to Match** to set up more comparisons. -3. Choose how to handle differences between the datasets. In **When There Are Differences**, select one of the following: - * **Use Input 1 Version** - * **Use Input 2 Version** - * **Use a Mix of Versions** - * **Include Both Versions** - - -## Understand the output - -There are four output options: - -* **In 1 only Branch**: data that occurs only in the first input. -* **Same Branch**: data that is the same in both inputs. -* **Different Branch**: data that is different between inputs. -* **In 2 only Branch**: data that occurs only in the second output. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.compression.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.compression.md deleted file mode 100644 index 25ba710d2..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.compression.md +++ /dev/null @@ -1,89 +0,0 @@ -# Compression - -The Compression node is useful to compress and decompress files. You can either use the `gzip` or `zip` file format. - - -## Node Reference - -- Operations - - Compress - - Decompress -- Options - - ***Binary Property*** field: This field allows you to specify the name of the binary property - - ***Output Prefix*** field: This field allows you to specify a prefix for the name of the file that gets generated. This field gets displayed for the 'Decompress' operation and the 'gzip' output format for the 'Compress' operation - - ***Output Format*** field: This field allows you to select an output format. This field is displayed when 'Compress' gets selected from the ***Operation*** dropdown list. The following are the available formats: - - gzip - - zip - - ***File Name*** field: This field allows you to specify a file name. This field is displayed when 'zip' gets selected from the ***Output Format*** dropdown list. - - ***Binary Property Output*** field: This field allows you to specify a name for the file that gets generated. This field is displayed when 'zip' gets selected from the ***Output Format*** dropdown list. - -## Example Usage - -This workflow allows you to compress binary files to zip format and upload them to Dropbox. You can also find the [workflow](https://n8n.io/workflows/908) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [Dropbox](/integrations/builtin/app-nodes/n8n-nodes-base.dropbox/) - - -The final workflow should look like the following image. - -![A workflow with the Edit Image node](/_images/integrations/builtin/core-nodes/compression/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. HTTP Request node (GET) - -This example workflow uses the HTTP Request node to fetch an image from a URL. You can also use the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node to read a file from the path you specify. - -1. Enter the URL of the image in the ***URL*** field. For example, `https://docs.n8n.io/assets/img/final-workflow.f380b957.png`. -2. Select 'File' from the ***Response Format*** dropdown list. -3. Enter `workflow_image` in the ***Binary Property*** field. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the HTTP Request node fetches the image from the URL. This image gets passed on as binary data to the next node in the workflow. - -![Using the HTTP Request node to fetch an image from a URL](/_images/integrations/builtin/core-nodes/compression/httprequest_node.png) - -### 3. HTTP Request1 node (GET) - -This node fetches an image from a URL. You can also use the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node to read a file from the path you specify. - -1. Enter the URL of the image in the ***URL*** field. For example, `https://n8n.io/n8n-logo.png`. -2. Select 'File' from the ***Response Format*** dropdown list. -3. Enter `logo` in the ***Binary Property*** field. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the HTTP Request node fetches the image from the URL. This image gets passed on as binary data to the next node in the workflow. - -![Using the HTTP Request node to fetch an image from a URL](/_images/integrations/builtin/core-nodes/compression/httprequest1_node.png) - - -### 4. Compression node (compress) - -This node compresses the binary file that we received from the HTTP Request nodes in a zip file. If you want to compress them in `gzip` format, select that option instead. - -1. Select 'Compress' from the ***Operation*** dropdown list. -2. Enter `logo,workflow_image` in the ***Binary Property*** field. -3. Select 'zip' from the ***Output Format*** dropdown list. -4. Enter `images.zip` in the ***File Name*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node compresses the files and generates `images.zip`. - -![Using the Compression node to compress files](/_images/integrations/builtin/core-nodes/compression/compression_node.png) - -### 5. Dropbox node (upload: file) - -This node will upload the compressed file to your Dropbox account. - -1. First of all, you'll have to enter credentials for the Dropbox node. You can find out how to do that [here](/integrations/builtin/credentials/dropbox/). -2. Enter `/images.zip` in the ***File Path*** field. -3. Toggle ***Binary Data*** to `true`. This option allows us to upload binary data from the previous node. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uploads the compressed file that we generated in the previous node. - -![Using the Dropbox node to upload a file](/_images/integrations/builtin/core-nodes/compression/dropbox_node.png) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.crypto.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.crypto.md deleted file mode 100644 index 76d87dd7c..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.crypto.md +++ /dev/null @@ -1,43 +0,0 @@ -# Crypto - -The Crypto node is used to encrypt data in workflows. - -## Node Reference - -You can configure further options for each action by selecting the type of encryption and encoding to be used, in the *Type* and *Encoding* fields respectively. - -- Action - - Hash a text in a specified format - - Hmac a text in a specified format - - Sign a string using a private key -- Type - - MD5 - - SHA256 - - SHA3-256 - - SHA384 - - SHA3-384 - - SHA512 - - SHA3-512 -- Encoding - - BASE64 - - HEX - -## Example Usage - -This workflow allows you to encrypt data using the Crypto node. You can also find the [workflow](https://n8n.io/workflows/574) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Crypto]() - - -The final workflow should look like the following image. - -![A workflow with the Crypto node](/_images/integrations/builtin/core-nodes/crypto/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Crypto node - -1. Enter the data that you want to encrypt in the *Value* field. -2. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.dateTime.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.dateTime.md deleted file mode 100644 index 2c6673971..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.dateTime.md +++ /dev/null @@ -1,81 +0,0 @@ -# Date & Time - -The Date & Time node is used to manipulate date and time data and convert it to different formats. - -!!! note "Keep in mind" - Make sure that the timezone is set correctly for the n8n instance (or the workflow). - - -## Node Reference - -- Action - - Convert a date to a different format - -You can specify the format that the date has to be converted to from the *To Format* dropdown list. - -- To Format - - MM/DD/YYYY - - YYYY/MM/DD - - MMMM DD YYYY - - MM-DD-YYYY - - YYYY-MM-DD - - Unix Timestamp - - Unix Ms Timestamp - -You can also specify a custom format by setting the *Custom Format* toggle to 'On'. - -- Options - - *From Format* field: Allows you to specify the format of the input values. Refer to the [FAQs](#what-values-can-i-use-in-the-from-format-field) to learn about the possible vaules. - - *From Timezone* field: Allows you to specify the timezone of the input values, for input timezones that are different from n8n's system clock. - - *To Timezone* field: Allows you to specify the timezone that the input values have to be converted to. - - -## Example Usage - -This workflow allows you to convert a date from one format to another using the Date & Time node. You can also find the [workflow](https://n8n.io/workflows/575) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Date & Time]() - - -The final workflow should look like the following image. - -![A workflow with the Date & Time node](/_images/integrations/builtin/core-nodes/datetime/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Date & Time node - -1. Enter the date that you want to convert in the *Value* field. -2. Click on the *Add Option* dropdown. -3. Click on the *From Format* option, and enter the format of the input date. -4. Select the format you want to convert it to from the *To Format* dropdown list. -5. Click on *Execute Node* to run the workflow. - -## FAQs - -### What values can I use in the From Format field? - -You can use the following values in the ***From Format*** field: - -| Input | Example | Description | -|-------|---------|-------------| -|X | 1616108400 | Unix timestamp | -|x | 1616108400000 | Unix ms timestamp | -| DD-MM-YYYY | 19-03-2021 | Date, month, and year separated by `-` | -| DD/MM/YYYY | 19/03/2021 | Date, month, and year separated by `/` | -| DD.MM.YYYY | 19.03.2021 | Date, month, and year separated by `.` | -| DD.MM.YYYY HH\:mm\:ss | 19.03.2021 08:00:00 | Date, month, year, hours, minutes, and seconds| -| MM/DD/YYYY | 03/19/2021 | Month, date, and year separated by `/` | -| MM-DD-YYYY | 03-19-2021 | Month, date, and year separated by `-` | -| MM.DD.YYYY | 03.19.2021 | Month, date, and year separated by `.` | -| MM/DD/YYYY HH\:mm\:ss | 03/19/2021 08:00:00 | Month, date, year, hours, minutes, and seconds | -| YYYY/MM/DD | 2021/03/19 | Year, month, and date separated by `/` | -| YYYY-MM-DD | 2021-03-19 | Year, month, and date separated by `-` | -| YYYY.MM.DD | 2021.03.19 | Year, month, and date separated by `.` | -| YYYY/MM/DD HH\:mm\:ss | 2021/03/19 08:00:00 | Year, month, date, hours, minutes, and seconds | -| MMMM DD YYYY | March 03 2021 | Month, date, and year | -| MMMM DD YYYY HH\:mm\:ss | March 03 2021 08:00:00 | Month, date, year, hours, minutes, and seconds | -| DD MMMM YYYY | 03 March 2021 | Date, month, and year | -| DD MMMM YYYY HH\:mm\:ss | 03 March 2021 08:00:00 | Date, month, year, hours, minutes, and seconds | diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.editImage.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.editImage.md deleted file mode 100644 index 1a0d22f16..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.editImage.md +++ /dev/null @@ -1,72 +0,0 @@ -# Edit Image - -The Edit Image node is used to manipulate and edit images. - -!!! note "Keep in mind" - 1. If you are not running n8n on Docker, you'll need to install [GraphicsMagick](http://www.graphicsmagick.org/README.html). -2. You will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to pass the image file as a data property to the Edit Image node. - - -## Node Reference - -- Operations - - Add a blur to the image to reduce sharpness - - Add a border to the image - - Create a new image - - Crop the image - - Composite an image on top of another image - - Draw on an image - - Get information about the image - - Rotate the image - - Change the size of the image - - Shear image along the X or Y axis - - Add text to the image - -You can also specify a file format using the *Format* field in the *Add Option* dropdown list. - -- Options - - ***File Name*** field: Allows you to specify the filename of the output file. - - ***Format*** field: Allows you to specify the image format of the output file: - - BMP - - GIF - - JPEG - - PNG - - TIFF - - -## Example Usage - -This workflow allows you to add text to an image downloaded from the internet using the Edit Image node. You can also find the [workflow](https://n8n.io/workflows/591) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [Edit Image]() - - -The final workflow should look like the following image. - -![A workflow with the Edit Image node](/_images/integrations/builtin/core-nodes/editimage/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. HTTP Request node - -1. Enter `https://docs.n8n.io/assets/img/final-workflow.f380b957.png` in the ***URL*** field. -2. Select 'File' from the ***Response Format*** dropdown list. -3. Click on *Execute Node* to run the node. - -![Using the HTTP Request node to get an image](/_images/integrations/builtin/core-nodes/editimage/httprequest_node.png) - - -### 3. Edit Image node - -1. Select 'Text' from the ***Operation*** dropdown list. -2. Enter `This is n8n`in the ***Text*** field. -3. Enter 100 in the ***Font Size*** field. -4. Enter 300 in the ***Position X*** field. -5. Enter 500 in the ***Position Y*** field. -6. Click on *Execute Node* to run the node. - -![Using the Edit Image node to add text to an image](/_images/integrations/builtin/core-nodes/editimage/editimage_node.png) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.emailimap.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.emailimap.md deleted file mode 100644 index f829f1c20..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.emailimap.md +++ /dev/null @@ -1,17 +0,0 @@ -# Email Trigger (IMAP) - -The IMAP Email node allows you to receive emails using an IMAP email server. This node is a trigger node. - -!!! note "Credential" - You can find authentication information for this node [here](/integrations/builtin/credentials/imap/). - - -## Basic Operations - -- Receive an email - -## Node Reference - -- **Mailbox Name** field: The mailbox from which you want to receive emails. -- **Action** field: Used to specify whether an email should be marked as read when n8n receives it. -- **Download Attachment** field: Used to specify whether you want to download any attachments received with the emails. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.errorTrigger.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.errorTrigger.md deleted file mode 100644 index 375f73327..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.errorTrigger.md +++ /dev/null @@ -1,57 +0,0 @@ -# Error Trigger - -The Error Trigger node triggers a workflow when another workflow has an error. Once a workflow fails, this node gets details about the failed workflow and the errors. This triggers the error workflow. - -!!! note "Keep in mind" - 1. If a workflow is using the Error Trigger node, you don't have to activate the workflow. -2. If you want to receive error messages for a workflow, make sure that you select the 'Error Workflow' in the ***Workflow Settings*** for the workflow. -3. If a workflow is using the Error Trigger node, by default, the workflow will use itself as the Error Workflow. -4. The Error Trigger node is designed to get triggered ONLY when the workflows execute automatically which means you will not be able to test this while running the workflows manually. - - -## Example Usage - -This workflow allows you to send an SMS when a workflow fails. You can also find the [workflow](https://n8n.io/workflows/665) on n8n.io. This example usage workflow would use the following nodes. -- [Twilio](/integrations/builtin/app-nodes/n8n-nodes-base.twilio/) - -The final workflow should look like the following image. - -![A workflow with the Error Trigger node](/_images/integrations/builtin/core-nodes/errortrigger/workflow.png) - -### 1. Error Trigger node - -This node will execute when an error occurs. - -### 2. Twilio node (send: sms) - -1. First of all, you'll have to enter credentials for the Twilio node. You can find out how to do that [here](/integrations/builtin/credentials/twilio/). -2. Enter the Twilio phone number in the ***From*** field. -3. Enter the receiver's phone number in the ***To*** field. -4. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. - -5. Enter `Your workflow with ID: {{$node["Error Trigger"].json["workflow"]["id"]}} and name: {{$node["Error Trigger"].json["workflow"]["name"]}} failed to execute.` in the ***Expression*** field. -6. The node will execute when the Error Trigger node is triggered. - - - -## FAQs - -### How to set an error workflow for an n8n workflow? - -Let's say we want to get a notification every time **Workflow A** fails. Create a new workflow, **Workflow B**. Add an Error Trigger node and set **Workflow B** as the error workflow for **Workflow A** by following these steps. -- Open **Workflow A**. -- Click on ***Workflows*** in the left menu and select 'Settings' from the dropdown list. -- Select **Workflow B** from the ***Error Workflow*** dropdown list. -- Click on the ***Save*** button. - -### Can we send a custom error message? - -The Error Trigger node sends the actual error message thrown by the workflow. You can use this information as shown in the [Example Usage](#example-usage) section as well as send a custom error message like in the Twilio node. However, you cannot send a custom error message to the Error Trigger node. - -### How do we call the Error Workflow manually? - -There is currently no functionality to call an Error Workflow manually. - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.executeCommand.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.executeCommand.md deleted file mode 100644 index bc3b51692..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.executeCommand.md +++ /dev/null @@ -1,146 +0,0 @@ -# Execute Command - -The Execute Command node runs shell commands on the host machine that runs n8n. - -!!! note "Which shell runs the command?" - This node executes the command in the default shell of the host machine. For example, cmd on Windows and zsh on macOS. - - If you run n8n with Docker, your command will run in the n8n container and not the Docker host. - -!!! note "Not available on Cloud" - This node isn't available on n8n Cloud. - - -## Node Reference - -The Execute Command node has two properties: - -1. **Execute Once** toggle: This is a boolean field that specifies whether you want the node to execute only once, or once for every item it receives an input. -2. **Command** field: This is a text field that specifies the command tto execute on the host machine. - - -## Example Usage - -This workflow allows you to execute a command that returns the percentage of the hard disk that is full using the Execute Command node. The workflow triggers twice a day, and if the memory usage exceeds 80%, it sends an SMS using the Twilio node. You can also find the [workflow](https://n8n.io/workflows/716) on n8n.io. This example usage workflow would use the following nodes. - -- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/) -- [Execute Command]() -- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/) -- [Twilio](/integrations/builtin/app-nodes/n8n-nodes-base.twilio/) -- [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 Execute Command node](/_images/integrations/builtin/core-nodes/executecommand/workflow.png) - -### 1. Cron node - -The Cron node will trigger the workflow twice a day, at 9 AM and 4 PM. - -1. Click on **Add Cron Time**. -2. Select 'Every Day' from the **Mode** dropdown list. -3. Enter `9` in the **Hour** field. -4. Click on **Add Cron Time**. -5. Select 'Every Day' from the **Mode** dropdown list. -6. Enter `16` in the **Hour** field. -7. Click on **Execute Node** to run the node. - -![Using the Cron node to trigger the workflow twice a day](/_images/integrations/builtin/core-nodes/executecommand/cron_node.png) - - -### 2. Execute Command node - -The Execute Command node executes the command and return the percentage of hard disk space used on the host machine. - -1. Enter `df -k / | tail -1 | awk '{print $5}'` in the **Command** field. -2. Click on **Execute Node** to run the node. - - -In the screenshot below, note that the node executes the command and returns the percentage of the hard disk that is full. - -![Using the Execute Command node to get the percentage of hard disk used on the host machine](/_images/integrations/builtin/core-nodes/executecommand/executecommand_node.png) - - -### 3. IF node - -This node will compare the percentage of the hard disk space used we got from the Execute Command node. If the usage of the memory exceeds 80%, it will return true otherwise false. - -1. Click on **Add Condition** and select 'Number' from the dropdown list. -2. Click on the gears icon next to the **Value 1** field and click on **Add Expression**. -3. Enter `{{parseInt($node["Execute Command"].json["stdout"])}}` in the **Expression** field. The output from the Execute Command node is a string. The `parseInt()` method converts the string into an integer. -4. Select 'Larger' from the **Operation** dropdown list. -5. Set **Value 2** to 80. -5. Click on **Execute Node** to run the node. - - -In the screenshot below, you will notice that the node returns an output when the percentage of hard disk space used exceeds 80%. - -![Using the IF node to check if the percentage of hard disk space used is greater than eighty percent](/_images/integrations/builtin/core-nodes/executecommand/if_node.png) - -### 4. Twilio node (send: sms) - -This node sends an SMS to the specified phone number when the usage of hard disk space exceeds 80%. - -1. Create a Twilio node connected to the 'true' output of the IF node. -2. You'll have to enter credentials for the Twilio node. You can find out how to do that [here](/integrations/builtin/credentials/twilio/). -3. Enter the Twilio phone number in the **From** field. -4. Enter the receiver's phone number in the **To** field. -5. Click on the gears icon next to the **Message** field and click on **Add Expression**. - -6. Enter `Your hard disk space is filling up fast! Your hard disk is {{$node["Execute Command"].json["stdout"]}} full.` in the **Expression** field. -7. Click on **Execute Node** to run the node. - - -In the screenshot below, note that the node sends an SMS with the percentage of the hard disk space used that you got from the Execute Command node. - -![Using the Twilio node to send an SMS](/_images/integrations/builtin/core-nodes/executecommand/twilio_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/core-nodes/executecommand/noop_node.png) - -## FAQs - -### How to run multiple commands in the Execute Command node? - -You can combine multiple commands using `&&`. For example, you can combine the change directory (cd) command with the list (ls) command using `&&`. - -```bash -cd bin && ls -``` - -To run multiple commands, you can also write the commands on separate lines. For example, you can write the list (ls) command on a new line after the change directory (cd) command. - -```bash -cd bin -ls -``` - -### How to run the curl command in the Execute Command node? - -You can also use the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to make a cURL request. - -If you want to run the curl command in the Execute Command node, you will have to build a Docker image based on the existing n8n image. The default n8n Docker image uses Alpine Linux. You will have to install the curl package. - -1. Create a file named Dockerfile. -2. Add the below code snippet to the Dockerfile. - ```shell - FROM n8nio/n8n - RUN apk --update add curl - ``` -3. In the same folder, execute the command below command to build the Docker image. - ```shell - docker build -t n8n-curl - ``` -4. Replace the Docker image you used before. For example, replace `n8nio/n8n` with `n8n-curl`. -5. Run the newly created Docker image, and you will now be able to execute ssh via the Execute Command-Node. - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.executeWorkflow.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.executeWorkflow.md deleted file mode 100644 index f61dd3e68..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.executeWorkflow.md +++ /dev/null @@ -1,29 +0,0 @@ -# Execute Workflow - -Use the Execute Workflow node to run a different workflow on the host machine that runs n8n. - -## Node reference - -The Execute Workflow node has two properties: - -- **Source**: This field specifies from where to get the workflow's information. - - Database - - Local File - - Parameter - - URL -- **Workflow**: This field contains information about the workflow, such as the workflow ID, URL, or a file. - - -## FAQs - -### How to find the workflow ID - -1. Open the workflow for which you want to get the workflow ID. -2. Copy the number after `workflow/` in your URL and paste that in the **Workflow ID** field. - - -### How does data get passed from one workflow to another? - -Let's say that there's a Execute Workflow node in **Workflow A**. The Execute Workflow node calls another workflow, **Workflow B**. -- The Execute Workflow node passes the data to the Start node of **Workflow B**. -- The last node of **Workflow B** sends the data back to the Execute Workflow node in **Workflow A**. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.executeworkflowtrigger.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.executeworkflowtrigger.md deleted file mode 100644 index ae02f7b65..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.executeworkflowtrigger.md +++ /dev/null @@ -1,10 +0,0 @@ -# Execute Workflow Trigger - -Use this node to start a workflow in response to another workflow. It should be the first node in the workflow. - -n8n allows you to call workflows from other workflows. This is useful if you want to: - -* Reuse a workflow: for example, you could have multiple workflows pulling and processing data from different sources, then have all those workflows call a single workflow that generates a report. -* Break large workflows into smaller components. - -This node runs in response to a call from the [Execute Workflow](/integrations/builtin/core-nodes/n8n-nodes-base.executeWorkflow/) node. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.ftp.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.ftp.md deleted file mode 100644 index 73d1902e6..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.ftp.md +++ /dev/null @@ -1,64 +0,0 @@ -# FTP - -The FTP node is useful to access and upload files to an FTP server. - -!!! note "Credential" - You can find authentication information for this node [here](/integrations/builtin/credentials/ftp/). - - -## Basic Operations - -- Delete a file -- Download a file -- List contents of a folder -- Rename/move content from old path to new path -- Upload a file - -**Note:** To attach a file for upload, you will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to pass the file as a data property. - -## Node Reference - -- ***Protocol:*** A dropdown list to choose between the FTP or SFTP protocol. -- ***Path:*** A field used to specify the remote path that you would like to connect to. -- ***Recursive:*** A toggle that can be used to include all subdirectories and files. - -## Example Usage - -This workflow allows you to upload a file to an FTP server and get a list of all files using the FTP node. You can also find the [workflow](https://n8n.io/workflows/663) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [FTP]() - -The final workflow should look like the following image. - -![A workflow with the FTP node](/_images/integrations/builtin/core-nodes/ftp/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. HTTP Request node - -1. Enter the URL of the file you want to download in the ***URL*** field. -2. Select ***File*** from the ***Response Format*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -![Downloading a file with the HTTP Request node](/_images/integrations/builtin/core-nodes/ftp/httprequest_node.png) - -### 3. FTP node (ftp: upload) - -1. First of all, you'll have to enter credentials for the FTP node. You can find out how to do that [here](/integrations/builtin/credentials/ftp/). -2. Select ***Upload*** from the ***Operation*** dropdown list. -3. Enter the path where you would like to upload the file in the ***Path*** field. -4. Click on ***Execute Node*** to run the node. - -![Uploading a file with the FTP node](/_images/integrations/builtin/core-nodes/ftp/ftp_node.png) - -### 4. FTP1 node (ftp: list) - -1. Select the credentials that you entered in the previous node. -2. Select ***List*** from the ***Operation*** dropdown list. -3. Enter the path to the folder where you uploaded the file in the previous step in the ***Path*** field. -4. Click on ***Execute Node*** to run the node. - -![Getting a list of files with the FTP node](/_images/integrations/builtin/core-nodes/ftp/ftp1_node.png) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.git.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.git.md deleted file mode 100644 index 1ed7f9a16..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.git.md +++ /dev/null @@ -1,93 +0,0 @@ -# Git - -[Git](https://git-scm.com/) is a free and open-source distributed version control system designed to handle everything from small to large projects with speed and efficiency. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/git/). - - - -## Basic Operations - -* Add a file or folder to commit -* Add configuration property -* Clone a repository -* Commit files or folders to git -* Fetch from remote repository -* Return current configuration -* Return git commit history -* Pull from remote repository -* Push to remote repository -* Push Tags to remote repository -* Return status of current repository -* Create a new tag -* Set the user - -## Example Usage - -This workflow allows you to add, commit, and push changes to a git repository. You can also find the [workflow](https://n8n.io/workflows/1115) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Git]() - -The final workflow should look like the following image. - -![A workflow with the Git node](/_images/integrations/builtin/core-nodes/git/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Git node (Add) - -This node will add the `README.md` file to the staging area. If you want to add a different file, enter the path of that file instead. - -1. Select 'Add' from the ***Operation*** dropdown list. -2. Enter the repository path in the ***Repository Path*** field. -3. Enter the file path in the ***Paths to Add*** field. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node adds the `README.md` file to the staging area. - -![Using the Git node to add a file to the staging area](/_images/integrations/builtin/core-nodes/git/git_node.png) - -### 3. Git1 node (Commit) - -This node will commit all the changes that were added to the staging area by the previous node. - -1. Select 'Commit' from the ***Operation*** dropdown list. -2. Click on the gears icon next to the ***Repository Path*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Nodes > Git > Parameters > repositoryPath. You can also add the following expression: `{{$node["Git"].parameter["repositoryPath"]}}`. -4. Enter a commit message in the ***Message*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new commit. - -![Using the Git node to commit changes](/_images/integrations/builtin/core-nodes/git/git1_node.png) - -### 4. Git2 node (Log) - -This node will return the commit logs of your repository. - -1. Click on the gears icon next to the ***Repository Path*** field and click on ***Add Expression***. -2. Select the following in the ***Variable Selector*** section: Nodes > Git > Parameters > repositoryPath. You can also add the following expression: `{{$node["Git"].parameter["repositoryPath"]}}`. -3. Toggle ***Return All*** to `true`. This option will return all the logs. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates a new commit. - -![Using the Git node to log the commits](/_images/integrations/builtin/core-nodes/git/git2_node.png) - -### 5. Git3 node (Push) - -This node will push the changes to a cloud repository. - -1. Select 'Push' from the ***Operation*** dropdown list. -2. Click on the gears icon next to the ***Repository Path*** field and click on ***Add Expression***. -3. Select the following in the ***Variable Selector*** section: Nodes > Git > Parameters > repositoryPath. You can also add the following expression: `{{$node["Git"].parameter["repositoryPath"]}}`. -4. Click on ***Execute Node*** to run the node. - -**Note:** If you're not using SSH, you will have to create credentials to authenticate yourself. You also need to set an upstream branch to push the changes. This is required only once. You can set up an upstream branch by executing the command `git push -u origin master` from a terminal. - -In the screenshot below, you will notice that the node pushes the local changes to a cloud repository. - -![Using the Git node to push the changes](/_images/integrations/builtin/core-nodes/git/git3_node.png) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.graphql.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.graphql.md deleted file mode 100644 index 28ee45b81..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.graphql.md +++ /dev/null @@ -1,74 +0,0 @@ -# GraphQL - -[GraphQL](https://graphql.org/) is an open-source data query and manipulation language for APIs, and a runtime for fulfilling queries with existing data. - - -## Basic Operations - -- Query a GraphQL endpoint - -## Example Usage - -This workflow allows you to get information about the five most recent SpaceX launches from [spacex.land](https://spacex.land/). You can also find the [workflow](https://n8n.io/workflows/558) on the website. This example usage workflow uses the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [GraphQL]() - -The final workflow should look like the following image. - -![A workflow with the GraphQL node](/_images/integrations/builtin/core-nodes/graphql/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. GraphQL node - -1. Enter `https://api.spacex.land/graphql/` in the *Endpoint* field. -2. Select the 'JSON' option from the *Request Format* dropdown list. -3. Enter the GraphQL query shown below in the *Query* field. -4. Click on *Execute Node* to run the workflow. - -#### GraphQL query -```json -{ - launchesPast(limit: 5) { - mission_name - launch_date_local - launch_site { - site_name_long - } - links { - article_link - video_link - } - rocket { - rocket_name - first_stage { - cores { - flight - core { - reuse_count - status - } - } - } - second_stage { - payloads { - payload_type - payload_mass_kg - payload_mass_lbs - } - } - } - ships { - name - home_port - image - } - } -} -``` - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.htmlExtract.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.htmlExtract.md deleted file mode 100644 index 60883beb7..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.htmlExtract.md +++ /dev/null @@ -1,82 +0,0 @@ -# HTML Extract - -The HTML Extract node is useful to extract the HTML content of a webpage. - -## Node Reference - -- **Source Data:** This field specifies if HTML should be read from binary or JSON data. In this dropdown list, there are two options. - - Binary - - JSON -- ***JSON Property:*** The name of the JSON property in which the HTML (from which to extract the data) can be found. This field is displayed when 'JSON' is selected in the ***Source Data*** field. -- ***Binary Property:*** The name of the binary property in which the HTML (from which to extract the data) can be found. This field is displayed when 'Binary' is selected in the ***Source Data*** field. -The property can either contain a string or an array of strings. -- ***Extraction Values:*** - - ***Key:*** The key under which the extracted value should be saved. - - ***CSS Selector:*** The CSS selector to use. - - ***Return Value:*** The kind of data that should be returned. In this dropdown list there are four options. - - ***Attribute:*** Get an attribute value like 'class' from an element. - - ***Attribute:*** The name of the attribute to return the value of. - - ***HTML:*** Get the HTML that the element contains. - - ***Text:*** Get only the text content of the element. - - ***Value:*** Get the value of an input, select, or textarea. - - ***Return Array:*** Returns the values as an array so that if multiple ones are found, they also get returned separately. If not set, all values will be returned as a single string. -- ***Options:*** - - ***Trim Values:*** Removes all spaces and newlines from the beginning and end of the values. - - -## Example Usage - -This workflow allows you to extract titles and URLs of all the articles from the [Hackernoon](https://hackernoon.com/) homepage using the HTML Extract node. You can also find the [workflow](https://n8n.io/workflows/434) 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/) -- [HTML Extract]() - -The final workflow should look like the following image. - -![A workflow with the HTML Extract node](/_images/integrations/builtin/core-nodes/htmlextract/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. HTTP Request node (GET) - -1. Enter `https://hackernoon.com` in the ***URL*** field. -2. Select 'String' from the ***Response Format*** dropdown list. -2. Click on ***Execute Node*** to run the node. - -![Get the articles from Hackernoon using the HTTP Request node](/_images/integrations/builtin/core-nodes/htmlextract/httprequest_node.png) - - -### 3. HTML Extract node (json: data) - -1. Click on the ***Add Value*** button. -2. Enter `item` in the ***Key*** field. -3. Enter `h2` in the ***CSS Selector*** field. -4. Select 'HTML' from the ***Return Value*** dropdown list. -5. Toggle ***Return Array*** to true. -6. Click on ***Execute Node*** to run the node. - -![Extract title of the articles using the HTML Extract node](/_images/integrations/builtin/core-nodes/htmlextract/htmlextract_node.png) - - -### 4. HTML Extract1 node (json: item) - -1. Enter `item` in the ***JSON Property*** field. -2. Click on the ***Add Value*** button. -3. Enter `title` in the ***Key*** field. -4. Enter `a` in the ***CSS Selector*** field. -5. Click on the ***Add Value*** button. -6. Enter `url` in the ***Key*** field. -7. Enter `a` in the ***CSS Selector*** field. -8. Select 'Attribute' from the ***Return Value*** dropdown list. -9. Enter `href` in the ***Attribute*** field. -10. Click on ***Execute Node*** to run the node. - -![Extract title and link of the articles using the HTML Extract node](/_images/integrations/builtin/core-nodes/htmlextract/htmlextract1_node.png) - - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest.md deleted file mode 100644 index ab6112e40..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest.md +++ /dev/null @@ -1,127 +0,0 @@ -# HTTP Request - -The HTTP Request node is one of the most versatile nodes in n8n. It allows you to make HTTP requests to query data from any app or service with a REST API. - -When using this node, you're creating a REST API call. You need some understanding of basic API terminology and concepts. - -## Node fields - -### Method - -Select the method to be used for the request: - -- DELETE -- GET -- HEAD -- OPTIONS -- PATCH -- POST -- PUT - -### URL - -Enter the endpoint you want to use. - -### Authentication - -There are two options for authentication. n8n recommends using the **Predefined credential type** option when it's available. It offers an easier way to set up and manage credentials, compared to configuring generic credentials. - -#### Predefined credentials - -Select **Predefined Credential Type**. This allows you to perform custom operations, without additional authentication setup. For example, n8n has an Asana node, and supports using your Asana credentials in the HTTP Request node. Refer to [Custom API operations](/integrations/custom-operations/) for more information. - -#### Generic credentials - -Select **Generic Credential Type** to set up authentication using one of the following methods: - -- Basic Auth -- Digest Auth -- Header Auth -- OAuth1 -- OAuth2 -- None - -Refer to [HTTP request credentials](/integrations/builtin/credentials/httpRequest/) for more information setting up each credential type. - -### Parameters, headers, and body - -You can choose to send additional information with your request. The data you need to send depends on the API you're interacting with, and the type of request you're making. Refer to your service's API documentation for detailed guidance. - -* **Send Query Parameters**: include query parameters. Query parameters are usually used as filters or searches on your query. -* **Send Headers**: include request headers. Headers contain metadata about your request. -* **Send Body**: send additional information in the body of your request. - - -### Options - -Select **Add Option** to view and select these options. - -- **Batching**: control how to batch large responses. -- **Ignore SSL Issues**: download the response even if SSL validation isn't possible. -- **Redirects**: choose whether to follow redirects. Disabled by default. -- **Response**: provide settings about the expected API response. -- **Proxy**: use this if you need to specify an HTTP proxy. -- **Timeout**: set a timeout for the request. - - -## Basic example - -This example uses [Reqres](https://reqres.in/){:target=_blank .external-link}, a service for testing APIs with fake data. It provides a basic usage example. - -### Setup - -Create a new workflow and add the HTTP Request node. - -Enter `https://reqres.in/api/users` in the **URL** field. All the examples call this endpoint. - -### Get a list of users - -Ensure the **Method** is set to **GET**. - -Select **Execute node**. n8n calls the `users` endpoint of the Reqres API, and outputs the response. - -### Add a user - -1. Select **POST** in the **Method** dropdown list. -2. Enable **Send Body**. -3. Enter `name` in the **Name** field. -4. Enter `Neo` in the **Value** field. -5. Select **Add Parameter** -6. Enter `job` in the **Name** field. -7. Enter `Programmer` in the **Value** field. -8. Select **Execute node** to run the workflow. n8n calls the `users` endpoint of the Reqres API, and outputs the response. - -## More examples - -### Fetch a binary file from a URL - -1. Enter the URL of the file in the **URL** field. For example, you can enter `https://docs.n8n.io/_images/n8n-docs-icon.svg` to fetch the n8n logo. -2. Select **Add Option > Response**. -3. Set **Response Format** to **File**. -4. Select **Execute node** to run the node. - -### Send a binary file to an API endpoint - -1. Connect the HTTP Request node with a node that has previously fetched the binary file. For example, this could be an HTTP Request node, [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node, [Google Drive](/integrations/builtin/app-nodes/n8n-nodes-base.googleDrive/) node, and so on. -2. Select **POST** in the **Method** dropdown. Check the API documentation of your API to make sure that you have selected the correct HTTP request method. -3. Enter the URL you want to send the binary file to in the **URL** field. -4. Enable **Send Body**. -5. In **Body Content Type**, select **n8n Binary Data**. -6. In **Input Data Field Name**, enter the name of the field containing the binary data. -9. Select **Execute node** to run the node. - -Refer to this [workflow template](https://n8n.io/workflows/1338-update-twitter-banner-using-http-request/){:target=_blank .external link} for a full example. - -### Get the HTTP status code after an execution - -1. Select **Add Option** > **Response**. -2. Enable **Include Response Headers and Status**. - -When you execute the node, n8n includes the headers, status code, and status message in the output. - -### Send XML data - -1. Enable **Send Body**. -2. In **Body Content Type**, select **Raw**. -3. In **Content Type**, enter `application/xml`. -4. Enter the XML data in the **Body** field. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.iCal.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.iCal.md deleted file mode 100644 index 0de1fb04d..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.iCal.md +++ /dev/null @@ -1,51 +0,0 @@ -# iCalendar - -The iCalendar node allows you to create event files that can be shared as an attachment. - -## Basic Operations - -- Create Event File - -## Example Usage - -This workflow allows you to create an event file and send it as an attachment via email. You can also find the [workflow](https://n8n.io/workflows/1083) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Send Email](/integrations/builtin/core-nodes/n8n-nodes-base.sendEmail/) - -The final workflow should look like the following image. - -![A workflow with the Gmail node](/_images/integrations/builtin/core-nodes/icalendar/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. iCalendar node (createEventFile) - -This node will create an event file. We use this file as an attachment in the next node. - -1. Enter the event title in the ***Event Title*** field. -2. Select the event start date and time in the ***Start*** field. -3. Select the event end date and time in the ***End*** field. -4. Select 'Get All' from the ***Operation*** dropdown list. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node creates the event file. - -![Using the iCalendar node to create an event file](/_images/integrations/builtin/core-nodes/icalendar/icalendar_node.png) - -### 3. Send Email node - -This node will send the event file as an attachment. - -1. First of all, you'll have to enter credentials for the Send Email node. You can find out how to do that [here](/integrations/builtin/credentials/sendEmail/). -2. Enter the sender's email address in the ***From Email*** field. -3. Enter the receiver's email address in the ***To Email*** field. -4. Enter a subject in the ***Subject*** field. -5. Enter the email content in the ***Text*** field. -6. Enter `data` in the ***Attachments*** field. If you used a different name for the Binary Property, use that name instead. We add the name of the Binary Property and not the file name in the ***Attachments*** field. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends an email with the event file as an attachment. - -![Using the Send Email node to send an email with an attachemnt](/_images/integrations/builtin/core-nodes/icalendar/sendemail_node.png) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.if.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.if.md deleted file mode 100644 index 04858af8e..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.if.md +++ /dev/null @@ -1,122 +0,0 @@ -# IF - -The IF node is used to split a workflow conditionally based on comparison operations. - -## Node Reference - -You can add comparison conditions using the **Add Condition** dropdown. Conditions can be created based on the data type, the available comparison operations vary for each data type. - -**Boolean** - -- Equal -- Not Equal - - -**Number** - -- Smaller -- Smaller Equal -- Equal -- Not Equal -- Larger -- Larger Equal -- Is Empty - - -**String** - -- Contains -- Equal -- Not Contains -- Not Equal -- Regex -- Is Empty - - -You can choose to split a workflow when any of the specified conditions are met, or only when all the specified conditions are met using the options in the **Combine** dropdown list. - -## Branch execution with If and Merge nodes - ---8<-- "_snippets/integrations/builtin/core-nodes/merge/if-merge-branch-execution.md" - -## Example Usage - -This workflow executes two different *Set* nodes based on the output given by an *IF* node. You can also find the [workflow](https://n8n.io/workflows/581) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Function](/integrations/builtin/core-nodes/n8n-nodes-base.function/) -- [IF]() -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) - - -The final workflow should look like the following image. - -![A workflow with the IF node](/_images/integrations/builtin/core-nodes/if/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. Function node - -1. Enter the following code in the **Function** field. -``` -return [ - { - json: { - id: 0, - } - }, - { - json: { - id: 1, - } - } -]; -``` -2. Click on **Execute Node** to run the workflow. - -![Using the Function node to send data to the IF node](/_images/integrations/builtin/core-nodes/if/function_node.png) - - -### 3. IF node - - -1. Click on the **Add Condition** button and select 'Number' from the dropdown list. -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 > Function > Output Data > JSON > ID. You can also add the following expression: `{{$node["Function"].json["id"]}}`. -4. From the **Operation** dropdown list, select 'Equal'. -5. Click on **Execute Node** to run the workflow. - - -![Using the IF node to conditionally execute based on the input](/_images/integrations/builtin/core-nodes/if/if_node.png) - - -### 4. Set node (for 'true' condition) - -1. Create a Set node connected to the 'true' output of the IF node. -2. Click on the **Add Value** button and select 'String' from the dropdown list. -3. Enter `name` in the **Name** field. -4. Enter `n8n` in the **Value** field. -5. Click on **Execute Node** to run the workflow. - -**Note:** Notice that only the ID with the value 0 made its way to this Set node. - -![Using the Set node to set a value when the condition is true](/_images/integrations/builtin/core-nodes/if/set_node.png) - - -### 5. Set1 node (for 'false' condition) - -1. Create a *Set* node connected to the 'false' output of the IF node. -2. Click on the **Add Value** button and select 'String' from the dropdown list. -3. Enter `name` in the **Name** field. -4. Enter `nodemation` in the **Value** field. -5. Click on **Execute Node** to run the workflow. - -**Note:** Notice that only the ID with the value 1 made its way to this *Set* node. - -![Using the Set node to set a value when the condition is false](/_images/integrations/builtin/core-nodes/if/set1_node.png) - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.interval.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.interval.md deleted file mode 100644 index cbfe7d0d0..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.interval.md +++ /dev/null @@ -1,20 +0,0 @@ -# Interval - -The Interval node is used to trigger the workflow to run in regular intervals of time. This node is a Trigger node. - -!!! note "Keep in mind" - If a workflow is using the Interval node as a trigger, make sure that you save and activate the workflow. - - -The Interval node has two fields: -1. *Interval* field: This is a numerical field where you can specify the interval after which the workflow should get triggered again. -2. *Unit* field: This is a dropdown list which allows you to select a unit for the value that was provided for the *Interval* field. This field offers the following options for its dropdown list: - - Seconds - - Minutes - - Hours - -![A workflow with the Interval node](/_images/integrations/builtin/core-nodes/interval/workflow.png) - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.itemLists.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.itemLists.md deleted file mode 100644 index 12014b306..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.itemLists.md +++ /dev/null @@ -1,91 +0,0 @@ -# Item Lists - -The Item Lists node simplifies working with returned data that contain lists (arrays), enabling you to easily modify the structure for further processing without the need to use [Function](/integrations/builtin/core-nodes/n8n-nodes-base.function/) nodes and write custom JavaScript. - -## Operations - -The Item Lists node enables you to perform the following operations: - -* *Split Out Items*: Create separate items from a list of data within an item. -* *Aggregate Items*: Merge multiple items into a single new item. -* *Remove Duplicates*: Remove extraneous items. -* *Sort*: Change the ordering of items. -* *Limit*: Remove items beyond a defined maximum number. - -!!! note "" - Usually, you shouldn't use expressions for fields that expect a `key` value (for example, **Field to Split Out**). Expressions usually return values, not keys. - - -### Split Out Items - -This operation is useful if your data contains a list of items, for example a list of customers, and you want to split them so that you have an item for each customer. - -![Split Out Items output](/_images/integrations/builtin/core-nodes/itemlists/split_out.png) - -When using the *Split Out Items* operation, configure the following parameters and options: - -* *Field to Split Out*: The field containing the list you want to separate out into individual items (e.g. `Name` in the example here). **Must be plaintext and not an expression.** -* *Include*: Select if any other fields from the input data should be kept with each new individual item. You can select: - * *No Other Fields* - * *All Other Fields* - * *Selected Other Fields*: When selected, a *Fields to Include* field is displayed. Enter a comma separated list of desired fields. -* *Disable Dot Notation*: When disabled, child fields (in the format `parent.child`) cannot be referenced. -* *Destination Field Name*: Optionally set the field name under which to put the new split contents. - -### Aggregate Items - -The Aggregate Items operations is useful when you want to take many separate items, or just particular portions of them, and group them together into individual items. For example, the image below shows customer names and email addresses being grouped into individual items from a series of individual customer records that contained many other details. - -![Aggregate Items output](/_images/integrations/builtin/core-nodes/itemlists/aggregate.png) - -When using the *Aggregate Items* operation, configure the following parameters and options: - -* *Field To Aggregate*: The name of the field in the input data to be aggregated together. -* *Rename Field*: Enable this toggle to enter a field name for the aggregated output data. When aggregating multiple fields you must provide new output field names, **multiple fields cannot be left undefined**. -* *Output Field Name*: Displayed only when *Rename Field* is enabled. The field name for the aggregated output data. -* *Disable Dot Notation*: When disabled, child fields (in the format `parent.child`) cannot be referenced. -* *Preserve Aggregated Lists*: If enabled, fields to aggregate that are lists will output a list of lists (rather than being merged into a single list). - -### Remove Duplicates - -There are many situations where you can end up with duplicate data, a user creating multiple accounts, a customer submitting the same order multiple time, etc. When working with large datasets it becomes more difficult to easily spot and remove these items. - -The Remove Duplicates operation allows you to identify those items that are identical across all fields or only a desired subset of fields. - -![Remove Duplicate Items output](/_images/integrations/builtin/core-nodes/itemlists/duplicates.png) - -When using the *Remove Duplicates* operation, configure the following parameters and options: - -* *Compare*: Provide which fields of the input data should be compared to check if they are the same. The following options are available: - * *All Fields*: Compares all fields of the input data. - * *All Fields Except*: Enter which input data fields should be excluded from the comparison. Multiple values can be provided separated by commas. - * *Selected Fields*: Enter which input data fields should be included in the comparison. Multiple values can be provided separated by commas. -* *Disable Dot Notation*: When disabled, child fields (in the format `parent.child`) cannot be referenced. - -### Sort - -The Sort operation allows you to organize lists of in a desired ordering, or generate a random selection if desired (i.e. assign tasks to users randomly). - -!!! note "Keep in mind" - The Sort operation uses the default JavaScript operation where the elements to be sorted are converted into strings and their values compared. See [here](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort) to learn more. - - -![Sort Items output](/_images/integrations/builtin/core-nodes/itemlists/sort.png) - -When using the *Sort* operation, configure the following parameters and options: - -* *Type*: Use the dropdown to select how you want to input the sorting. The following options are available: - * *Simple*: When you selected, you can use the **Add Field To Sort By* button to input the desired fields, and select whether *Ascending* or *Descending* order is desired. - * *Random*: Select to create a random order in the list. - * *Code*: When selected, displays a code input field where you can enter custom JavaScript code to perform the sort operation. - -### Limit - -If you want to keep and process only a specific number of items from your incoming data, the Limit operation allows you to select the desired number of items to keep and whether they should be taken from the beginning or end of the data (e.g. take the 5 highest priority tickets, the oldest order, etc.). - -![Limit Items output](/_images/integrations/builtin/core-nodes/itemlists/limit.png) - -When using the *Limit* operation, configure the following parameters and options: - -* *Max Items*: Enter the maximum number of items that should be kept. If the input data contains more than this value, items will be removed. -* *Keep*: When items must be removed, select if the input items at the beginning or end are kept. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.localFileTrigger.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.localFileTrigger.md deleted file mode 100644 index 54ffd0081..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.localFileTrigger.md +++ /dev/null @@ -1,17 +0,0 @@ -# Local File Trigger - -The [Local File Trigger]() node starts a workflow when changes on the file system are detected. These changes involve a file or folder geting added, changed or deleted. - -## Node Reference - -- ***Trigger On:*** - - ***Changes to a Specifc File:*** Triggers when the specified file is changed - - ***Changes Involving a Specific Folder:*** Triggers when the a change in the selected folder occurs -- ***Additional Fields:*** - - ***File to Watch:*** The path to the file to watch. This field is shown when 'Trigger On' is set to 'Changes to a Specifc File'. - - ***Folder to Watch:*** The path of the folder to watch. This field is shown when 'Trigger On' is set to 'Changes Involving a Specific Folder'. - - ***Watch for:*** The type of change to watch for. This field is shown when 'Trigger On' is set to 'Changes Involving a Specific Folder'. - - ***Options:*** - - ***Include Linked Files/Folders:*** Also watch for changes to linked files or folders. - - ***Ignore:*** Files or paths to ignore. The whole path is tested, not just the filename. Supports the [Anymatch](https://github.com/micromatch/anymatch) syntax. - - ***Max Folder Depth:*** How deep into the folder structure to watch for changes. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.manualworkflowtrigger.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.manualworkflowtrigger.md deleted file mode 100644 index 6c4c78b87..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.manualworkflowtrigger.md +++ /dev/null @@ -1,5 +0,0 @@ -# Manual Trigger - -Use this node if you want to start a workflow by selecting **Execute Workflow**, and don't want any option for the workflow to run automatically. - -Workflows always need a trigger (start point). In most cases, a trigger node starts the workflow in response to an external event. However, you still need a trigger node even when starting the workflow manually. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.markdown.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.markdown.md deleted file mode 100644 index eb2b968ed..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.markdown.md +++ /dev/null @@ -1,70 +0,0 @@ -# Markdown - -The Markdown node converts between Markdown and HTML formats. - -## Options - -You can configure the node's output using **Options**. Click **Add Option** to view and select your options. - -!!! note "Test out the options" - Some of the options depend on each other, or can interact. We recommend testing out options to check the effects are what you want. - -### Markdown to HTML - -| Option | Description | Default | -| ------ | ----------- | ------- | -| **Add Blank To Links** | Whether to open links a new window (enabled) or not (disabled). | Disabled | -| **Automatic Linking To URLs** | Whether to automatically link to URLs (enabled) or not (disabled). If enabled, n8n converts any string that it identifies as a URL to a link. | Disabled | -| **Backslash Escapes HTML Tags** | Whether to allow backslash escaping of HTML tags (enabled) or not (disabled). When enabled, n8n escapes any `<` or `>` prefaced with `\`. For example, `\` renders as `<div>`. | Disabled | -| **Complete HTML Document** | Whether to output a complete HTML document (enabled) or an HTML fragment (disabled). A complete HTML document includes the `` declaration, `` and `` tags, and the `` element. | Disabled | -| **Customized Header ID** | Whether to support custom heading IDs (enabled) or not (disabled). When enabled, you can add custom heading IDs using `{header ID here}` after the heading text. | Disabled | -| **Emoji Support** | Whether to support emojis (enabled) or not (disabled). | Disabled. | -| **Encode Emails** | Whether to transform ASCII character emails into their equivalent decimal entities (enabled) or not (disabled). | Enabled | -| **Exclude Trailing Punctuation From URLs** | Whether to exclude trailing punctuation from auto-linked URLs (enabled) or not (disabled). For use with **Automatic Linking To URLs**. | Disabled | -| **GitHub Code Blocks** | Whether to enable GitHub Flavored Markdown code blocks (enabled) or not (disabled). | Enabled | -| **GitHub Compatible Header IDs** | Whether to generate GitHub Flavored Markdown heading IDs (enabled) or not (disabled). GitHub Flavored Markdown generates heading IDs with `-` in place of spaces and removes non-alphanumeric characters. | Disabled | -| **GitHub Mention Link** | Change the link used with **GitHub Mentions**. | Disabled | -| **GitHub Mentions** | Whether to support tagging GitHub users with `@` (enabled) or not (disabled). When enabled, n8n replaces `@name` with `https://github.com/name`. | Disabled | -| **GitHub Task Lists** | Whether to support GitHub Flavored Markdown task lists (enabled) or not (disabled). | Disabled | -| **Header Level Start** | Number. Set the start level for headers. For example, changing this field to `2` causes n8n to treat `#` as `

`, `##` as `

`, and so on. | 1 | -| **Mandatory Space Before Header** | Whether to make a space between `#` and heading text required (enabled) or not (disabled). When enabled, n8n renders a heading written as `##Some header text` literally (it does not turn it into a heading element) | Disabled | -| **Middle Word Asterisks** | Whether n8n should treat asterisks in words as Markdown (disabled) or render them as literal asterisks (enabled). | Disabled | -| **Middle Word Underscores** | Whether n8n should treat underscores in words as Markdown (disabled) or render them as literal underscores (enabled). | Disabled | -| **No Header ID** | Disable automatic generation of header IDs (enabled). | Disabled | -| **Parse Image Dimensions** | Support setting maximum image dimensions in Markdown syntaxt (enabled). | Disabled | -| **Prefix Header ID** | Define a prefix to add to header IDs. | None | -| **Raw Header ID** | Whether to remove spaces, `'`, and `"` from header IDs, including prefixes, replacing them with `-` (enabled) or not (disabled). | Disabled | -| **Raw Prefix Header ID** | Whether to prevent n8n from modifying header prefixes (enabled) or not (disabled) | Disabled | -| **Simple Line Breaks** | Whether to create line breaks without a double space at the end of a line (enabled) or not (disabled). | Disabled | -| **Smart Indentation Fix** | Whether to try to smartly fix indentation problems related to ES6 template strings in indented code blocks (enabled) or not (disabled). | Disabled | -| **Spaces Indented Sublists** | Whether to remove the requirement to indent sublists four spaces (enabled) or not (disabled). | Disabled | -| **Split Adjacent Blockquotes** | Whether to split adjacent blockquote blocks (enabled) or not (disabled). If you don't enable this, n8n treats quotes (indicated by `>` at the start of the line) on separate lines as a single blockquote, even when separated by an empty line. | Disabled | -| **Strikethrough** | Whether to support strikethrough syntax (enabled) or not (disabled). When enabled, you can add a ~~strikethrough~~ effect using `~~` around the word or phrase. | Disabled | -| **Tables Header ID** | Whether to add an ID to table header tags (enabled) or not (disabled). | Disabled | -| **Tables Support** | Whether to support tables (enabled) or not (disabled). | Disabled | - -### HTML to Markdown - -| Option | Description | Default | -| ------ | ----------- | ------- | -| **Bullet Marker** | Specify the character to use for unordered lists. | * | -| **Code Block Fence** | Specify the characters to use for code blocks. | ``` | -| **Emphasis Delimiter** | Specify the character ``. | _ | -| **Global Escape Pattern** | Overrides the default character escape settings. You may want to use Text Replacement Pattern instead. | None | -| **Ignored Elements** | Ignore given HTML elements, and their children. | None | -| **Keep Images With Data** | Whether to keep images with data (enabled) or not (disabled). Support files up to 1MB. | Disabled | -| **Line Start Escape Pattern** | Overrides the default character escape settings. You may want to use Text Replacement Pattern instead. | None | -| **Max Consecutive New Lines** | Number. Specify the maximum number of consecutive new lines allowed. | 3 | -| **Place URLs At The Bottom** | Whether to place URLs at the bottom of the page and format using link reference definitions (enabled) or not (disabled). | Disabled | -| **Strong Delimiter** | Specify the characters for ``. | ** | -| **Style For Code Block** | Specify the styling for code blocks. Options are **Fence** and **Indented**. | Fence | -| **Text Replacement Pattern** | Define a text replacement pattern using regex. | None | -| **Treat As Blocks** | Specify HTML elements to treat as blocks (surround with blank lines) | None | - -## Parsers - -n8n uses the following parsers: - -* To convert from HTML to Markdown: [node-html-markdown](https://www.npmjs.com/package/node-html-markdown) -* To convert from Markdown to HTML: [Showdown](https://www.npmjs.com/package/showdown). Some options allow you to extend your Markdown with [GitHub Flavored Markdown](https://github.github.com/gfm/). - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.merge.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.merge.md deleted file mode 100644 index 3c1e34db7..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.merge.md +++ /dev/null @@ -1,197 +0,0 @@ -# Merge - -Use the Merge node to combine data from two streams, once data of both streams is available. - -!!! note "Major changes in 0.194.0" - This node was overhauled in n8n 0.194.0. This document reflects the latest version of the node. If you're using an older version of n8n, you can find the previous version of this document [here](https://github.com/n8n-io/n8n-docs/blob/4ff688642cc9ee7ca7d00987847bf4e4515da59d/docs/integrations/builtin/core-nodes/n8n-nodes-base.merge.md){:target=_blank .external-link}. - -## Merge mode - -You can specify how the Merge node should combine data from different branches. The following options are available: - -### Append - -Keep data from both inputs. The output contains items from Input 1, followed by all items from Input 2. - -![Diagram](/_images/integrations/builtin/core-nodes/merge/append-diagram.png) - -### Combine - -Combine data from both inputs. Choose a **Combination Mode** to control how n8n merges the data. - -#### Merge by fields - -Compare items by field values. Enter the fields you want to compare in **Fields to Match**. - -n8n's default behavior is to keep matching items. You can change this using the **Output Type** setting: - -* Keep matches: merge items that match. -* Keep non-matches: merge items that don't match. -* Enrich Input 1: keep all data from Input 1, and add matching data from Input 2. -* Enrich Input 2: keep all data from Input 2, and add matching data from Input 1. - -![Diagram](/_images/integrations/builtin/core-nodes/merge/merge-by-field-diagram.png) - - -##### Field value clashes - ---8<-- "_snippets/integrations/builtin/core-nodes/merge/field-value-clash.md" - -##### Multiple matches - -Matching by field can generate multiple matches if the inputs contain duplicate data. To handle this, select **Add Option > Multiple Matches**. Then choose: - -* **Include All Matches**: output multiple items (one for each match). -* **Include First Match Only**: keep the first item, discard subsequent items. - - -#### Merge by position - -Combine items based on their order. The item at index 0 in Input 1 merges with the item at index 0 in Input 2, and so on. - -![Diagram](/_images/integrations/builtin/core-nodes/merge/merge-by-position-diagram.png) - -##### Inputs with different numbers of items - -If there are more items in one input than the other, the default behavior is to leave out the items without a match. Choose **Add Option** > **Include Any Unpaired Items** to keep the unmatched items. - -##### Field value clashes - ---8<-- "_snippets/integrations/builtin/core-nodes/merge/field-value-clash.md" - -#### Multiplex - -Output all possible item combinations, while merging fields with the same name. - -![Diagram](/_images/integrations/builtin/core-nodes/merge/multiplex-diagram.png) - -##### Field value clashes - ---8<-- "_snippets/integrations/builtin/core-nodes/merge/field-value-clash.md" - -### Choose branch - -Choose which input to keep. This option always waits until the data from both inputs is available. You can keep the data from Input 1 or Input 2, or you can output a single empty item. The node outputs the data from the chosen input, without changing it. - -## Merging branches with uneven numbers of items - -The items passed into Input 1 of the Merge node will take precedence. For example, if the Merge node receives five items in Input 1 and 10 items in Input 2, it only processes five items. The remaining five items from Input 2 aren't processed. - -## Branch execution with If and Merge nodes - ---8<-- "_snippets/integrations/builtin/core-nodes/merge/if-merge-branch-execution.md" - - -## Try it out: a step by step example - -Create a simple workflow with some example input data to try out the Merge node. - -### Set up sample data using the Function nodes - -1. Add a Function node to the canvas and connect it to the Start node. -2. Paste the following JavaScript code snippet in the **JavaScript Code** field: -```js -return [ - { - json: { - name: 'Stefan', - language: 'de', - } - }, - { - json: { - name: 'Jim', - language: 'en', - } - }, - { - json: { - name: 'Hans', - language: 'de', - } - } -]; -``` -3. Add a second Function node, and connect it to the Start node. -4. Paste the following JavaScript code snippet in the **JavaScript Code** field: -```js -return [ - { - json: { - greeting: 'Hello', - language: 'en', - } - }, - { - json: { - greeting: 'Hallo', - language: 'de', - } - } -]; -``` - -### Try out different merge modes - -Add the Merge node. Connect the first Function node to **Input 1**, and the second Function node to **Input 2**. Run the workflow to load data into the Merge node. - -The final workflow should look like the following image. - -![Simple merge workflow with two function nodes](/_images/integrations/builtin/core-nodes/merge/workflow.png) - -Now try different options in **Mode** to see how it affects the output data. - -#### Append - -Select **Mode** > **Append**, then select **Execute node**. - -Output data in table view: - -![Append mode output](/_images/integrations/builtin/core-nodes/merge/append-mode.png) - - -#### Merge by fields - -You can merge these two data inputs so that each person gets the correct greeting for their language. - -1. Select **Mode** > **Merge By Fields**. -2. In both **Input 1 Field** and **Input 2 Field**, enter `language`. This tells n8n to combine the data by matching the values in the `language` field in each data set. -3. Select **Execute node**. - -Output in table view: - -![Merge by Fields mode output](/_images/integrations/builtin/core-nodes/merge/merge-by-fields-mode.png) - - -#### Merge by position - -Select **Mode** > **Merge By Position**, then select **Execute node**. - -Default output in table view: - -![Merge by Position mode output](/_images/integrations/builtin/core-nodes/merge/merge-by-position-mode-default.png) - - -##### Keep unpaired items - -If you want to keep all items, select **Add Option** > **Include Any Unpaired Items**, then enable **Include Any Unpaired Items**. - -Output with unpaired items in table view: - -![Merge by Position mode with unpaired items output](/_images/integrations/builtin/core-nodes/merge/merge-by-position-include-unpaired.png) - - -#### Multiplex - -Select **Mode** > **Multiplex**, then select **Execute node**. - -Output in table view: - -![Merge by Multiplex mode output](/_images/integrations/builtin/core-nodes/merge/multiplex-mode.png) - - -## Try it out: load a workflow - -n8n provides an example workflow that demonstrates key Merge node concepts. - -Go to [Joining different datasets](https://n8n.io/workflows/1747/){:target=_blank .external-link} and select **Use workflow** to copy the example workflow. You can then paste it into your n8n instance. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.moveBinaryData.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.moveBinaryData.md deleted file mode 100644 index ad70e50af..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.moveBinaryData.md +++ /dev/null @@ -1,72 +0,0 @@ -# Move Binary Data - -The Move Binary Data node is useful to move data between binary and JSON properties. - -!!! note "Hint" - If you need to convert an entire CSV file to JSON, use the [Spreadsheet File](/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetFile/) node. - - -## Node Reference - -- ***Mode:*** This field specifies from where and to the data should be moved. - - Binary to JSON - - JSON to Binary -- ***Set all Data:*** If set to active, all JSON data is replaced with the data retrieved from binary key. If it is not set to active, the data will be written to a single key. This field is displayed when 'Binary to JSON' is selected from the ***Mode*** dropdown list. -- ***Source Key:*** The name of the binary key to get data from. It is also possible to define deep keys by using dot-notation. For example, "level1.level2.currentKey". This field is displayed when 'Binary to JSON' is selected from the ***Mode*** dropdown list. -- ***Destination Key:*** The name the JSON key to copy data to. It is also possible to define deep keys by using dot-notation. For example, "level1.level2.newKey". This field is displayed when 'Binary to JSON' is selected from the ***Mode*** dropdown list. -- ***Convert all Data:*** If set to active all JSON data will be converted to binary. If it is not set to active only the data with one key will be converted. This field is displayed when 'JSON to Binary' is selected from the ***Mode*** dropdown list. -- ***Destination Key:*** The name of the binary key to copy data to. It is also possible to define deep keys by using dot-notation. For example, "level1.level2.newKey". This field is displayed when 'JSON to Binary' is selected from the ***Mode*** dropdown list. - -- ***Options*** - - ***Keep Source:*** Keep the source key. By default it gets deleted. - - ***Encoding:*** Set the encoding of the data stream. - - The following are the options when 'Binary to JSON' is selected from the ***Mode*** dropdown list. - - ***JSON Parse:*** Run JSON parse on the data to get proper object data. This field is displayed when ***Set all Data*** is set to 'false'. - - ***Keep As Base64:*** Keeps the binary data as base64 string. This field is displayed when ***Set all Data*** is set to 'false'. - - ***Strip BOM:*** Strip the byte order mark (BOM) from the string. This field is displayed when ***Encoding*** is selected. - - The following are the options when 'JSON to Binary' is selected from the ***Mode*** dropdown list. - - ***Add BOM:*** Add the byte order mark (BOM) to the string. This field is displayed when ***Encoding*** is selected. - - ***File Name:*** The file name to set. - - ***Mime Type:*** The mime-type to set. By default the JSON mime-type will be set. - - ***Use Raw Data:*** Use data as is and do not stringify it. - - ***Data is Base64:*** Keeps the binary data as base64 string. This field is displayed when ***Convert all Data*** is set to 'false'. - - -## Example Usage - -This workflow allows you to store the JSON data received from the [CocktailDB API](https://www.thecocktaildb.com/) to your machine. You can also find the [workflow](https://n8n.io/workflows/652) 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/) -- [Write Binary Data](/integrations/builtin/core-nodes/n8n-nodes-base.writeBinaryFile/) - -The final workflow should look like the following image. - -![A workflow with the Move Binary Data node](/_images/integrations/builtin/core-nodes/movebinarydata/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. HTTP Request node (GET) - -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. - -![Get random cocktail data from CocktailDB API using the HTTP Request node](/_images/integrations/builtin/core-nodes/movebinarydata/httprequest_node.png) - - -### 3. Move Binary Data node (JSON to Binary) - -1. Select 'JSON to Binary' from the ***Mode*** dropdown list. -2. Click on ***Execute Node*** to run the node. - -![Convert JSON to binary using the Move Binary Data node](/_images/integrations/builtin/core-nodes/movebinarydata/movebinarydata_node.png) - - -### 4. Write Binary File node - -1. Enter the file name in the ***File Name*** field. -2. Click on ***Execute Node*** to run the node. - -![Writing a file to the disk using the Write Binary File node](/_images/integrations/builtin/core-nodes/movebinarydata/writebinaryfile_node.png) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.n8n.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.n8n.md deleted file mode 100644 index a4f20560f..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.n8n.md +++ /dev/null @@ -1,32 +0,0 @@ -# n8n - -A node to integrate with n8n itself. This node allows you to consume the [n8n API](/api/) in your workflows. - -## Related resources - -### Credentials - -Refer to the [API authentication](/api/authentication/) documentation for guidance on getting your n8n credentials. - -### Examples - -Refer to the [n8n node on the website](https://n8n.io/integrations/n8n/) for a list of examples. - -## Operations - -* Credential - * Create - * Delete - * Get Schema -* Execution - * Get - * Get Many - * Delete -* Workflow - * Activate - * Create - * Deactivate - * Delete - * Get - * Get Many - * Update diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.n8nTrigger.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.n8nTrigger.md deleted file mode 100644 index 53e47960d..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.n8nTrigger.md +++ /dev/null @@ -1,47 +0,0 @@ -# n8n Trigger - -The n8n Trigger node gets triggered when the n8n instance is started or restarted. The n8n Trigger node can be used to notify when the n8n instance starts. - -## Node Reference - -- Events - - ***Instance started:*** Triggers when the n8n instance is started or restarted - -## Example Usage - -This workflow allows you to receive a message on Mattermost when your n8n instance starts. You can also find the [workflow](https://n8n.io/workflows/1058) on n8n.io. This example usage workflow uses the following nodes. -- [n8n Trigger]() -- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/) - -The final workflow should look like the following image. - -![A workflow with the Webhook node](/_images/integrations/builtin/core-nodes/n8ntrigger/workflow.png) - -### 1. n8n Trigger node - -The n8n Trigger node will trigger the workflow whenever n8n starts. - -1. Select 'Instance started' from the ***Events*** dropdown list. - -In the screenshot below, you will notice that the node triggers the workflow when the n8n instance starts. - -![Using the n8n Trigger node to trigger the workflow](/_images/integrations/builtin/core-nodes/n8ntrigger/n8ntrigger_node.png) - -### 2. Mattermost node (post: message) - -This node will send a message in the `workflow` channel on Mattermost. - -1. First of all, you'll have to enter credentials for the Mattermost node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/mattermost/). -2. Select a channel from the ***Channel ID*** dropdown list. -3. Click on the gears icon next to the ***Message*** field click on ***Add Expression***. - -4. Enter the following message in the ***Expression*** field: `Your n8n instance started at {{$json["timestamp"]}}.`. -5. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that the node sends a message to Mattermost. - -![Using the Mattermost node to send a message to a channel](/_images/integrations/builtin/core-nodes/n8ntrigger/mattermost_node.png) - -!!! note "Activate workflow for production" - This example workflow uses the n8n Trigger 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. - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.noOp.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.noOp.md deleted file mode 100644 index 208cba990..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.noOp.md +++ /dev/null @@ -1,8 +0,0 @@ -# No Operation, do nothing - -The No Operation, do nothing node is used when you don't want to perform any operations. The purpose of this node is to make the workflow easier to read and understand where the flow of data stops. This can sometimes help others with a better understanding of the workflow, visually. - - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile.md deleted file mode 100644 index b0f56927b..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile.md +++ /dev/null @@ -1,35 +0,0 @@ -# Read Binary File - -The Read Binary File node is used to read a file from the host machine that runs n8n. - -!!! note "Keep in mind" - 1. If you are running n8n in Docker, your command will run on the n8n container and not the Docker host. - - 2. This node will look for files relative to the n8n install path. It is recommended to use absolute file paths to prevent any errors. - - -## Node Reference - -1. **File Path** field: This field specifies the path to the file. -2. **Property Name** field: Name of the binary property to which to write the data of the read file. - -## Example Usage - -This workflow allows you to read a file from the host machine using the Read Binary File node. You can also find the [workflow](https://n8n.io/workflows/577) on the website. This example usage workflow would use the following two nodes. - -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Read Binary File]() - - -The final workflow should look like the following image. - -![A workflow with the Read Binary File node](/_images/integrations/builtin/core-nodes/readbinaryfile/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Read Binary File node - -1. Enter the path to the file you want to read in the **File Path** field. -2. Click on **Execute Node** to run the workflow. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFiles.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFiles.md deleted file mode 100644 index cc843eb03..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFiles.md +++ /dev/null @@ -1,39 +0,0 @@ -# Read Binary Files - -The Read Binary Files node is used to read multiple files from the host machine that runs n8n. - -!!! note "Keep in mind" - 1. If you are running n8n in Docker, your command will run on the n8n container and not the Docker host. -2. This node will look for files relative to the n8n install path. It is recommended to use absolute file paths to prevent any errors. - - -## Node Reference - -1. *File Selector* field: This is a field that is used to specify the type of files to be read. For example, `*.jpg`. -2. *Property Name* field: Name of the binary property to which to write the data of the read files. - -It is also possible to select files from a certain directory, by specifying the path in the *File Selector* field. For example, `/data/folder/*.jpg`. - -## Example Usage - -This workflow allows you to read multiple files from the host machine using the Read Binary Files node. You can also find the [workflow](https://n8n.io/workflows/578) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Read Binary Files]() - - -The final workflow should look like the following image. - -![A workflow with the Read Binary Files node](/_images/integrations/builtin/core-nodes/readbinaryfiles/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Read Binary Files node - -1. Enter the type of files you want to read in the *File Selector* field. -2. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.readPDF.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.readPDF.md deleted file mode 100644 index 073ef923e..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.readPDF.md +++ /dev/null @@ -1,37 +0,0 @@ -# Read PDF - -The Read PDF node is used to read data from PDF documents and extract its content as text. - -!!! note "Keep in mind" - You will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to pass the image file as a data property to the Read PDF node. - - -## Node Reference - -The Read PDF node has one property: - -1. *Binary Property* field: This field specifies the name of the data property used to read the PDF file in n8n. - -## Example Usage - -This workflow allows you to read a PDF file using the Read PDF node. You can also find the [workflow](https://n8n.io/workflows/585) on the website. This example usage workflow would use the following three nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) -- [PDF Read]() - - -The final workflow should look like the following image. - -![A workflow with the Read PDF node](/_images/integrations/builtin/core-nodes/readpdf/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Read Binary File -1. Enter the path to the PDF file you want to read in the *File Path* field. - -### 3. Read PDF node - -1. Enter the *Property Name* you used in the previous node in the *Binary Property* field. -2. Click on *Execute Node* to run the workflow. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.renameKeys.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.renameKeys.md deleted file mode 100644 index 009d79f35..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.renameKeys.md +++ /dev/null @@ -1,41 +0,0 @@ -# Rename Keys -The Rename Keys node is used to rename the keys of a key-value pair in n8n. - - -## Node Reference - -You can rename one or multiple keys using the Rename Keys node. Click on the *Add new key* button to rename a key. - -There are two properties in the Rename Keys node. - -- ***Current Key Name*** field: The current name of the key that you would like to rename. -- ***New Key Name*** field: The new name that you would like to assign to the key. - - -## Example Usage - -This workflow allows you to rename a key using the Rename Keys node. You can also find the [workflow](https://n8n.io/workflows/582) on the website. This example usage workflow would use the following three nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Rename Keys]() - - -The final workflow should look like the following image. - -![A workflow with the Rename Keys node](/_images/integrations/builtin/core-nodes/renamekeys/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Set node - -1. Click on the ***Add Value*** button and select the 'String' option from the dropdown list. -2. Enter a name for the key in the ***Name*** field and enter a value in the ***Value*** field. - -### 3. Rename Keys node - -1. Click on the ***Add new key*** button. -2. Enter the name of the key you created in the previous step in the ***Current Key Name*** field. -3. Enter the new name that you would like to give the key in the ***New Key Name*** field. -4. Click on ***Execute Node*** to run the workflow. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.respondToWebhook.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.respondToWebhook.md deleted file mode 100644 index 38a477e60..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.respondToWebhook.md +++ /dev/null @@ -1,65 +0,0 @@ -# Respond to Webhook - -The *Respond to Webhook* node can be used in workflows with a [Webhook](/integrations/builtin/core-nodes/n8n-nodes-base.webhook/) node. It allows controlling the response to incoming webhooks. In the Webhook node, the **Using 'Respond to Webhook' node** option would need to be selected in the **Response** dropdown for the *Respond to Webhook* node to work. - -!!! note "Expressions" - When using [expressions](/code-examples/expressions/), the *Respond to Webhook* node will only run for the first item in the input data - - -## Node reference - -The node supports the following modes through the **Respond With** field: - -- **First Incoming Item**: Respond with the first incoming item's JSON. -- **Text**: Respond with a text defined in the **Response Body** field. -- **JSON**: Respond with a JSON object defined in the **Response Body** field. -- **Binary**: Respond with a binary file defined in the **Response Data Source** field. -- **No Data**: No response payload is sent. - -Available options: - -- **Response Code**: Set the [response code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status) to be used. -- **Response Headers**: Define response headers to be sent. - -## Workflow behaviour - -When using the *Respond to Webhook* node, workflows will behave as follows: - -- When the workflow finishes without executing the *Respond to Webhook* node, a standard message is returned with a 200 status. -- If a second *Respond to Webhook* node is executed after the first one, it is ignored. -- If the workflow errors before the first *Respond to Webhook* node is executed, an error message is returned with a 500 status. -- If a *Respond to Webhook* node is executed but there was no webhook, the *Respond to Webhook* node is ignored. - -## Example Usage - -This workflow allows serves an HTML page when receiving a GET requests. You can find the complete workflow [here on n8n.io](https://n8n.io/workflows/1306). The example workflow uses the following nodes: - -- [Webhook](/integrations/builtin/core-nodes/n8n-nodes-base.webhook/) -- [Respond to Webhook]() - -![The workflow using the Respond to Webhook node](/_images/integrations/builtin/core-nodes/respondtowebhook/workflow.png) - -### 1. Webhook node - -This node will receive incoming requests (for example, when the webhook URL is opened with a browser). - -1. Enter a human-readable value in the **path** field, for example `my-form`. -2. Choose the **Using 'Respond to Webhook' node** option **Response** dropdown. -3. Click on **Execute Node** to run the node. -4. Open the URL shown in the **Test URL** field under **Webhook URLs** in a new browser tab. - -![The Webhook node](/_images/integrations/builtin/core-nodes/respondtowebhook/webhook_node.png) - -### 2. Respond to Webhook node - -This node will define the response to the request received in the previous step. - -1. Connect the *Webhook* node from the previous step to the new *Respond to Webhook* node. -2. Choose the **Text** option in the **Respond With** dropdown. -3. Enter some basic HTML into the **Response Body** field (for example the [Bootstrap Starter template](https://getbootstrap.com/docs/5.1/getting-started/introduction/#starter-template)). -4. Click **Add Option** > **Response Headers** > **Add Response Header** to add a header to the response. -5. Enter `Content-Type` in the **Name** field and `text/html; charset=UTF-8` in the value field of the new header. -6. Close the *Respond to Webhook* modal and click the **Execute Workflow** button. -7. Open the **Test URL** from the *Webhook* node in a new browser tab. The browser should now show the page added defined in the **Response Body** field of the *Respond to Webhook* node. - -![The Respond to Webhook node](/_images/integrations/builtin/core-nodes/respondtowebhook/respond_to_webhook_node.png) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.rssFeedRead.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.rssFeedRead.md deleted file mode 100644 index 992b42d7a..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.rssFeedRead.md +++ /dev/null @@ -1,33 +0,0 @@ -# RSS Read - -The RSS Read node is used to read data from RSS feeds published on the internet. - -## Node Reference - -The RSS Read node has only one property: - -- *URL* field: This field is used to specify the web address of the RSS publication. - -## Example Usage - -This workflow allows you to read an RSS Feed using the RSS Read node. You can also find the [workflow](https://n8n.io/workflows/583) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [RSS Read]() - - -The final workflow should look like the following image. - -![A workflow with the RSS Read node](/_images/integrations/builtin/core-nodes/rssfeedread/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. RSS Read node - -1. Enter the URL of the RSS feed that you want to read in the *URL* field. -2. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.scheduletrigger.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.scheduletrigger.md deleted file mode 100644 index d0e52bd85..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.scheduletrigger.md +++ /dev/null @@ -1,52 +0,0 @@ -# Schedule Trigger - -Use the Schedule Trigger node run workflows at fixed intervals and times. This works in a similar way to the cron software utility in Unix-like systems. - -!!! note "Cron node" - The Code node replaces the Cron node from version 0.199.0 onwards. If you're using an older version of n8n, you can still view the [Cron node documentation](https://github.com/n8n-io/n8n-docs/blob/67935ad2528e2e30d7984ea917e4af2910a096ec/docs/integrations/builtin/core-nodes/n8n-nodes-base.cron.md){:target=_blank .external-link}. - -!!! note "Keep in mind" - 1. If a workflow uses the Schedule node as a trigger, make sure that you save and activate the workflow. - 2. Set the timezone correctly for the n8n instance (or the workflow). - - -## Schedule your workflow - -Select an interval in **Trigger Interval**. Once you select an interval, n8n displays more options to customize that interval. - -### Example - -In this example, schedule a workflow to run once a quarter, at the end of the quarter, at 09:00. - -1. In **Trigger Interval**, select **Months**. -2. Change **Months Between Triggers** to `3`. -3. To run the workflow at the end of the month, change **Trigger at Day of Month** to `28`. -4. Change **Trigger at Hour** to **9am**. Leave **Trigger at Minute** as its default, `0`. - -Note that the Schedule Trigger uses the workflow timezone if available. Otherwise it uses the n8n instance timezone. - -## Generate a custom cron expression - -If you need a custom time setting, select **Trigger Interval** > **Custom (Cron)**. - -To generate a cron expression, you can use [crontab guru](https://crontab.guru){:target=_blank .external-link}. Paste the cron expression that you generated using crontab guru in the **Expression** field in n8n. - -### Examples - -If you want to trigger your workflow every day at 04:08:30, enter the following in the **Cron Expression** field. -``` -30 8 4 * * * -``` - -If you want to trigger your workflow every day at 04:08, enter the following in the **Cron Expression** field. -``` -8 4 * * * -``` - -### Why there are six asterisks (*) in the cron expression? - -The sixth asterisk in the cron expression represents seconds. Setting this is optional. The node will execute even if you don't set the value for seconds. - -| * | * | * | * | * | * | -|---|---|---|---|---|---| -|second|minute|hour|day|week|month| diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.sendEmail.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.sendEmail.md deleted file mode 100644 index 728bfd984..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.sendEmail.md +++ /dev/null @@ -1,55 +0,0 @@ -# Send Email - -The Send Email node is used to send an email via an SMTP email server. - -!!! note "Credential" - You can find authentication information for this node [here](/integrations/builtin/credentials/sendEmail/). - - -!!! note "Keep in mind" - 1. Before sending, ensure that you have already created email addresses that are approved for sending on your SMTP service. -2. The Send Email node merely sends an email via your SMTP server and plays no part in email deliverability. -3. To attach a file, you will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to pass a file as a data property. - - -## Basic Operations - -- Send an email - -## Node Reference - -- **From Email:** The email address you are sending from. -- **To Email:** The recipient email address. Multiple recipients can be separated using a comma. -- **CC Email:** A field that can be used to specify an email address for a carbon copy of the email. -- **BCC Email:** A field that can be used to specify an email address for a blind carbon copy of the email. -- **Subject:** The subject of your message. -- **Text:** Your message, in plaintext. -- **HTML:** Your message, in HTML. -- **Attachments:** A field that can be used to attach any attachments as data properties. - -## Example Usage - -This workflow allows you to send an email using the Send Email node. You can also find the [workflow](https://n8n.io/workflows/584) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Send Email]() - -The final workflow should look like the following image. - -![A workflow with the Send Email node](/_images/integrations/builtin/core-nodes/sendemail/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Send Email node - -1. First of all, you'll have to enter credentials for the Send Email node. You can find out how to do that [here](/integrations/builtin/credentials/sendEmail/). -2. Enter the email address you want to send from in the *From Email* field. -3. Enter the recipient email address in the *To Email* field. -4. Enter a subject for your message in the *Subject* field. -5. Enter your message in the *Text* field. -6. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.set.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.set.md deleted file mode 100644 index e950af2f2..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.set.md +++ /dev/null @@ -1,57 +0,0 @@ -# Set - -The Set node allows you to set workflow data. This node can set completely new data as well as overwrite data that already exists. This node is crucial in workflows which expect incoming data from previous nodes, such as when inserting values to Google Sheets or databases. - - -## Example Usage - -This workflow allows you to assign values to variables using the Set node. You can also find the [workflow](https://n8n.io/workflows/526) on the website. This example usage workflow would use the following two nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Set]() - - -The final workflow should look like the following image. - -![A workflow with the Set node](/_images/integrations/builtin/core-nodes/set/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Set node - -1. Click on the *Add Value* button and select 'Number' from the dropdown list. -2. Enter `number`in the *Name* field. -3. Enter the value for the above field in the *Value* field. -4. Click on the *Add Value* button and select 'String' from the dropdown list. -5. Enter `string`in the *Name* field. -6. Enter the value for the above field in the *Value* field. -7. Click on the *Add Value* button and select 'Boolean' from the dropdown list. -8. Enter `boolean`in the *Name* field. -9. Toggle the value for the above field in the *Value* field. -10. Click on *Execute Node* to run the workflow. - - -## Node Reference - -### Keep Only Set - -There's an option to toggle the *Keep Only Set* field. Setting this to true ensures that only the values set on this node should be kept, and the values from all the previous nodes are removed. - -### Dot Notation - -By default, the node follows the dot notation for the *Name* field. That means if you set the name in the *Name* field as `number.one` and the value in the *Value* field as `20`, the resulting JSON would look like the following: - -```json -{ "number": { "one": 20} } -``` - -You can deactivate this behaviour by clicking on the *Add Option* button and setting the *Dot Notion* field to off. Now the resulting JSON would look like the following: - -```json -{ "number.one": 20 } -``` - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.splitInBatches.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.splitInBatches.md deleted file mode 100644 index 33476629a..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.splitInBatches.md +++ /dev/null @@ -1,90 +0,0 @@ -# Split In Batches - -The Split In Batches node saves the original incoming data, and with each iteration, it returns a predefined amount of data. This node can be used to loop through the data. - -## Node Reference - -- **Batch Size:** The number of items to return with each call. -- ***Options*** - - ***Reset:*** If set to true, the node will reset. - -!!! warning - n8n natively processes incoming items. You may not need the Split In Batches node in your workflow. To learn more about how n8n handles multiple items, refer to the documentation on [Looping in n8n](/flow-logic/looping/). - - -## Example Usage - -This workflow allows you to read RSS feed from two different sources using the Split In Batches node. The Split in Batches node is needed in the workflow since the RSS Read node only processes the first item it receives. You can also find the [workflow](https://n8n.io/workflows/687) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Function](/integrations/builtin/core-nodes/n8n-nodes-base.function/) -- [Split In Batches]() -- [RSS Feed Read](/integrations/builtin/core-nodes/n8n-nodes-base.rssFeedRead/) - -The final workflow should look like the following image. - -![A workflow with the Split In Batches node](/_images/integrations/builtin/core-nodes/splitinbatches/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. Function node - -1. Paste the following JavaScript code snippet in the ***Function*** field. - -```js -return [ - { - json: { - url: 'https://medium.com/feed/n8n-io', - } - }, - { - json: { - url: 'https://dev.to/feed/n8n', - } - } -]; -``` -2. Click on ***Execute Node*** to run the node. - - -![Using the Function node to return URLs](/_images/integrations/builtin/core-nodes/splitinbatches/function_node.png) - - -### 3. SplitInBatches node - -1. Set the batch size to `1` in the ***Batch Size*** field. -2. Click on ***Execute Node*** to run the node. - - -![Using the Split In Batches node to split the data](/_images/integrations/builtin/core-nodes/splitinbatches/splitinbatches_node.png) - - -### 4. RSS Read node - -1. Click on the gears icon next to the ***URL*** field and click on ***Add Expression***. -2. Select the following in the ***Variable Selector*** section: Nodes > SplitInBatches > Output Data > JSON > url. You can also add the following expression: `{{$node["SplitInBatches"].json["url"]}}`. -3. Click on ***Execute Node*** to run the workflow. - - -![Using the RSS Read node to read data from RSS feed](/_images/integrations/builtin/core-nodes/splitinbatches/rssfeedread_node.png) - -## FAQs - -### How to identify that no items are left to be processed by the node? - -To identify if items are left to be processed by node use the following expression: `{{$node["SplitInBatches"].context["noItemsLeft"]}}`. This expression returns a boolean value. If there is data yet to be processed, the expression will return `false`, otherwise `true`. - -Refer to this [workflow](https://n8n.io/workflows/995) to try it out. - -### How to get the current running index of the node? - -To get the current running index of the node, use the following expression: `{{$node["SplitInBatches"].context["currentRunIndex"];}}`. - -Refer to this [workflow](https://n8n.io/workflows/996) to try it out. - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetFile.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetFile.md deleted file mode 100644 index 49a6cb63b..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetFile.md +++ /dev/null @@ -1,60 +0,0 @@ -# Spreadsheet File - -The Spreadsheet File node is used to access data from spreadsheet files. - -!!! note "Keep in mind" - You will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to pass the image file as a data property to the Spreadsheet File node. - - -## Basic Operations - -- Read from file -- Write to file - -## Node Reference - -When writing to a spreadsheet file, the *File Format* field can be used to specify the format of the file to save the data as. - -- ***File Format*** - - CSV (Comma-separated values) - - HTML (HTML Table) - - ODS (OpenDocument Spreadsheet) - - RTF (Rich Text Format) - - XLS (Excel) - - XLSX (Excel) - -- ***Binary Property*** field: Name of the binary property in which to save the binary data of the spreadsheet file. - -- ***Options*** - - ***Sheet Name*** field: This field specifies the name of the sheet from which the data should be read or written to. - - ***Read As String*** field: This toggle enables you to parse all input data as strings. - - ***RAW Data*** field: This toggle enables you to skip the parsing of data. - - ***File Name*** field: This field can be used to specify a custom file name when writing a spreadsheet file to disk. - -## Example Usage - -This workflow allows you to read a spreadsheet file using the Spreadsheet File node. You can also find the [workflow](https://n8n.io/workflows/586) on the website. This example usage workflow would use the following three nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) -- [Spreadsheet File]() - - -The final workflow should look like the following image. - -![A workflow with the Spreadsheet File node](/_images/integrations/builtin/core-nodes/spreadsheetfile/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. Read Binary File -1. Enter the path to the spreadsheet file you want to read in the *File Path* field. - -### 3. Spreadsheet File node - -1. Enter the *Property Name* you used in the previous node in the *Binary Property* field. -2. Click on *Execute Node* to run the workflow. - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.sseTrigger.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.sseTrigger.md deleted file mode 100644 index f5e386b12..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.sseTrigger.md +++ /dev/null @@ -1,22 +0,0 @@ -# SSE Trigger - -Server-Sent Events (SSE) is a server push technology enabling a client to receive automatic updates from a server via HTTP connection. The SSE Trigger node is used to receive server-sent events and is a trigger node. - -## Node Reference - -***URL***: This field specifies the URL from which to receive the server-sent events. - -## Example Usage - -This workflow allows you to receive server-sent events using the SSE Trigger node. You can also find the [workflow](https://n8n.io/workflows/639) on n8n.io. This example usage workflow would use the following node. -- [SSE Trigger]() - -The final workflow should look like the following image. - -![A workflow with the SSE Trigger node](/_images/integrations/builtin/core-nodes/ssetrigger/workflow.png) - - -### 1. SSE Trigger node - -1. Enter the URL in the ***URL*** field. -2. Click on ***Execute Node*** to run the node. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.ssh.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.ssh.md deleted file mode 100644 index b84e7a206..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.ssh.md +++ /dev/null @@ -1,53 +0,0 @@ -# SSH - -The SSH node is useful for executing commands via the Secure Shell Protocol. - -!!! note "Credential" - You can find authentication information for this node [here](/integrations/builtin/credentials/ssh/). - - -## Basic Operations - -- Execute a command -- Download a file -- Upload a file - -**Note:** To attach a file for upload, you will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to pass the file as a data property. - -## Node Reference - -- ***Authentication:*** A dropdown list to choose between Password or Private Key authentication. -- ***Resource:*** A dropdown list used to specify if you are executing a command or processing a file. -- ***Operation:*** A dropdown list to select the action to be performed. When selecting **Command** as the ***Resource***, only **Execute** is available. For a **File** ***Resource*** you can select either **Upload** or **Download**. -- ***Command:*** Only visible for **Command** resources. The command to execute on the remote machine. -- ***Working Directory:*** Only visible for **Command** resources. The directory where the command should be executed. -- ***Path:*** Only visible for **Download** operation on file resources. The path where the desired file is found. -- ***Binary Property:*** Only visible for file resources. The name of the binary property which contains the data for the file to be uploaded. -- ***Target Directory:*** Only visible for **Upload** operations on file resources. The directory to upload the file to. The name of the file does not need to be specified, it's taken from the binary data file name. To override this behavior, set the parameter **File Name** under options. - - -## Example Usage - -This workflow allows you to remotely connect to your computer via SSH. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [SSH]() - -The final workflow should look like the following image. - -![A workflow with the SSH node](/_images/integrations/builtin/core-nodes/ssh/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - -### 2. SSH node - -1. From the SSH Credentials dropdown, select ***Create New*** or an existing [credential](/integrations/builtin/credentials/ssh/). -2. Select ***Password*** from the ***Authentication*** dropdown list. -3. Select ***Command*** from the ***Resource*** dropdown list. -4. The ***Execute*** option is automatically selected as the ***Operation***. -5. In the ***Command*** field enter the command to execute. Here we used `ls` just to see the local directory contents. -6. In the ***Working Directory*** field you can enter where the command should be executed. Here we ran it in the root directory. -7. Click on ***Execute Node*** to run the node. - -![SSH Node](/_images/integrations/builtin/core-nodes/ssh/ssh_node.png) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.start.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.start.md deleted file mode 100644 index ec76180d1..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.start.md +++ /dev/null @@ -1,21 +0,0 @@ -# Start - -!!! warning "Deprecated" - The Start node was removed from n8n in 0.199.0. It is still available in legacy workflows. - -The start node is the first node in a workflow. It exists by default when you create a new workflow and looks like the following image. - -![A new workflow with the Start node](/_images/integrations/builtin/core-nodes/start/workflow.png) - -In case there is no Trigger node in the workflow, the workflow always starts from the Start node. The Start node cannot be deleted. Even if a workflow contains a Trigger node, there would still be a Start node. - - -## FAQs - -### When is it necessary to use the Start node? - -When using the *Execute Workflow* node in workflow A to execute workflow B, the *Start* node will act as the trigger node in workflow B. The second node in workflow B needs to be connected to the Start node for the workflow to execute correctly. - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.stopAndError.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.stopAndError.md deleted file mode 100644 index 8f49a9c68..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.stopAndError.md +++ /dev/null @@ -1,8 +0,0 @@ -# Stop And Error - -The Stop And Error node is used to throw an exception in workflows, enabling an error message or object to be displayed. - -## Basic operations - -* Error Message -* Error Object diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.switch.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.switch.md deleted file mode 100644 index 2bd734e80..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.switch.md +++ /dev/null @@ -1,146 +0,0 @@ -# Switch - -The Switch node is used to route a workflow conditionally based on comparison operations. It is similar to the [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/) node, but supports up to four conditional routes. - -## Node Reference - -***Mode***: This dropdown is used to select whether the conditions will be defined as rules in the node, or as an expression, programmatically. - -You can add comparison conditions using the ***Add Routing Rule*** dropdown. Conditions can be created based on the data type. The available comparison operations vary for each data type. - -- Boolean - - Equal - - Not Equal -- Number - - Smaller - - Smaller Equal - - Equal - - Not Equal - - Larger - - Larger Equal -- String - - Contains - - Equal - - Not Contains - - Not Equal - - Regex - -You can route a workflow when none of the specified conditions are met using ***Fallback Output*** dropdown list. - - -## Example Usage - -This workflow executes four different Set nodes based on the output given by a Switch node. You can also find the [workflow](https://n8n.io/workflows/688) on n8n.io. This example usage workflow would use the following nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Function](/integrations/builtin/core-nodes/n8n-nodes-base.function/) -- [Switch]() -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [NoOp](/integrations/builtin/core-nodes/n8n-nodes-base.noOp/) - - -The final workflow should look like the following image. - -![A workflow with the Switch node](/_images/integrations/builtin/core-nodes/switch/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. Function node - -1. Enter the following code in the ***Function*** field. -``` -return [ - { - json: { - id: 0, - } - }, - { - json: { - id: 1, - } - }, - { - json: { - id: 2, - } - } -]; -``` -2. Click on ***Execute Node*** to run the workflow. - -![Using the Function node to send data to the Switch node](/_images/integrations/builtin/core-nodes/switch/function_node.png) - - -### 3. Switch node - - -1. Click on the gears icon next to the ***Value 1*** field and click on ***Add Expression***. -2. Select the following in the ***Variable Selector*** section: Nodes > Function > Output Data > JSON > id. You can also add the following expression: `{{$node["Function"].json["id"]}}`. -3. Click on the ***Add Routing Rule*** button. -4. From the ***Operation*** dropdown list, select 'Equal'. -5. Enter '0' in the ***Value 2*** and the ***Output*** fields. -6. Click on the ***Add Routing Rule*** button. -7. From the ***Operation*** dropdown list, select 'Equal'. -8. Enter '1' in the ***Value 2*** and the ***Output*** fields. -9. Click on the ***Add Routing Rule*** button. -10. From the ***Operation*** dropdown list, select 'Equal'. -11. Enter '2' in the ***Value 2*** and the ***Output*** fields. -12. Select '3' from the ***Fallback Output*** dropdown list. -13. Click on ***Execute Node*** to run the node. - - -![Using the Switch node to conditionally execute based on the input](/_images/integrations/builtin/core-nodes/switch/switch_node.png) - - -### 4. Set node (for '0' route) - -1. Create a ***Set*** node connected to the '0' output of the Switch node. -2. Click on the ***Add Value*** button and select 'String' from the dropdown list. -3. Enter `name` in the ***Name*** field. -4. Enter `n8n` in the ***Value*** field. -5. Click on ***Execute Node*** to run the node. - -**Note:** Notice that only the id with the value 0 made its way to this ***Set*** node. - -![Using the Set node to set value for route 1](/_images/integrations/builtin/core-nodes/switch/set_node.png) - - -### 5. Set1 node (for '1' route) - -1. Create a ***Set*** node connected to the '1' output of the Switch node. -2. Click on the ***Add Value*** button and select 'String' from the dropdown list. -3. Enter `name` in the ***Name*** field. -4. Enter `nodemation` in the ***Value*** field. -5. Click on ***Execute Node*** to run the node. - -**Note:** Notice that only the id with the value 1 made its way to this ***Set*** node. - -![Using the Set node to set value for route 1](/_images/integrations/builtin/core-nodes/switch/set1_node.png) - -### 6. Set2 node (for '2' route) - -1. Create a ***Set*** node connected to the '2' output of the Switch node. -2. Click on the ***Add Value*** button and select 'String' from the dropdown list. -3. Enter `name` in the ***Name*** field. -4. Enter `nathan` in the ***Value*** field. -5. Click on ***Execute Node*** to run the node. - -**Note:** Notice that only the id with the value 2 made its way to this ***Set*** node. - -![Using the Set node to set value for route 2](/_images/integrations/builtin/core-nodes/switch/set2_node.png) - -### 7. NoOp node (for '3' route) - -1. Create a ***NoOp*** node connected to the '3' output of the Switch node. -2. Click on ***Execute Node*** to run the node. - -**Note:** Notice that none of the ids made their way to this node since the values of the all the ids were either 0, 1, or 2. - -![Using the NoOp node for route 3](/_images/integrations/builtin/core-nodes/switch/noop_node.png) - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.wait.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.wait.md deleted file mode 100644 index d4d519dbf..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.wait.md +++ /dev/null @@ -1,126 +0,0 @@ -# Wait - -The Wait node is used to create a pause of any desired duration in your workflows. When the workflow is paused the execution data is offloaded to the database, and when the resume condition is met it is reloaded and the execution continues. - -The Wait node can be set to resume on the following conditions: - -* [**After time interval**](#time-interval) -* [**At specified time**](#specified-time) -* [**On webhook call**](#webhook-call) - -!!! note "Keep in mind" - For the time-based resume operations, note that: -* For wait times less than 65 seconds, execution data is not offloaded to the database to resume later but rather the process continues to run and execution resumes after the specified interval passes. -* The n8n server time is always used regardless of the timezone setting. Workflow timezone settings, and any changes made to them, do not affect the Wait node interval or specified time. - - -## Time interval - -Use the ***After time interval*** resume operation to set a desired interval after which the execution will resume. - -Set the desired *Amount* and the corresponding *Unit* for the Wait operation. Decimals can be used for fractional units, for example `1.5` minutes instead of `90` seconds. - -To automatically resume workflow execution after 15 minutes, the Wait node configuration would look like this: - -![Wait node time interval](/_images/integrations/builtin/core-nodes/wait/wait_time_interval.png) - -## Specified time - -Use the ***At specified time*** resume operation to set a particular date and time in the future when the workflow execution should resume. - -For example, if you want the workflow execution to continue at midnight of New Year's Day 2022 the Wait node configuration would look like this: - -![Wait node specified time](/_images/integrations/builtin/core-nodes/wait/wait_specific_time.png) - -## Webhook call - -The resume **On webhook call** option enables your workflows to resume when an HTTP call is received. - -The webhook URL that will resume the execution when called is only generated at runtime. The Wait node provides the `$resumeWebhookUrl` variable so that you can reference and send (the yet to be generated URL) wherever needed, for example to a third-party service or in an email (see example below). - -When the workflow executes, the resume URL is generated and the webhook(s) in your workflow using the `$resumeWebhookUrl` reference become functional. This generated URL is unique to each execution, meaning that your workflow can contain multiple Wait nodes and as the webhook URL is called it will resume each Wait node sequentially. - -### Reference - -See the [Webhook node](/integrations/builtin/core-nodes/n8n-nodes-base.webhook/) documentation to learn more about the Authentication, Method, and Response parameters when configuring the Wait node to resume on a webhook call. - -In addition to the parameters shared with the Webhook mode, the Wait node has the following additional configuration options: - -* **Limit wait time**: Set the maximum amount of time to wait before the execution is resumed by default (i.e. even with no webhook call received). -* **Add Option** > **Webhook Suffix**: Provide a suffix that you want to appended to the resume URL. This is useful for creating unique webhook URLs for each Wait node when a workflow contains multiple Wait nodes. - - **Note**: The generated `$resumeWebhookUrl` will not automatically include this suffix, you must manually append it to the webhook URL before exposing it. - -### Limitations - -There are a few functional limitations to keep in mind when working with the *On Webhook Call* operations of the Wait node: - -* Partial executions of your workflow will change the `$resumeWebhookUrl`, so be sure that the node being used to send this URL to your desired third-party runs in the same execution as the Wait node. -* When testing your workflow via the Editor UI, you cannot see the rest of the execution following the Wait node. To inspect the execution results ensure you have enabled *Save Manual Executions* in you [workflow settings](/workflows/workflows/#workflow-settings) to be able to review the execution results there. - -## Example usage - -This workflow allows you to complete a user sign-up flow by adding their details contact details in an Airtable, sending a confirmation email, and updating the Airtable record after they have confirmed their email address. - -For our example here, we assume there is an existing workflow/webpage where new users sign-up and this workflow begins when they hit "Submit" there. - -This example workflow uses the following nodes. -- [Wait]() -- [Webhook](/integrations/builtin/core-nodes/n8n-nodes-base.webhook/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Send Email](/integrations/builtin/core-nodes/n8n-nodes-base.sendEmail/) -- [Airtable](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/) - -The final workflow should look like the following image. - -![A workflow with the Wait node](/_images/integrations/builtin/core-nodes/wait/workflow.png) - -### 1. Webhook node - -This node is triggered when a new user submits their details in your contact form. It is configured as displayed below: - -![Submit Webhook node configuration](/_images/integrations/builtin/core-nodes/wait/webhook_node_1.png) - -### 2. Set node - -This node is used to set the values submitted by the user (first name, last name, and email address) as values corresponding to what you want to enter in the Airtable. - -![Set node configuration](/_images/integrations/builtin/core-nodes/wait/set_node_1.png) - -Note that expressions are used based on the input data received from the previous Webhook node: - -![Set node expression](/_images/integrations/builtin/core-nodes/wait/set_node_expression.png) - -### 3. Airtable node - -In this node we add the new users contact details to the desired table, Newsletter in our example: - -![Airtable node configuration](/_images/integrations/builtin/core-nodes/wait/airtable_node_1.png) - -### 4. Send Email node - -This node uses your desired email address (via SMTP) to send a confirmation email to the user: - -![Send Email node configuration](/_images/integrations/builtin/core-nodes/wait/email_node_1.png) - -This is where the `$resumeWebhookUrl` is passed, meaning the workflow will wait until the user clicks the confirmation link in this email before resuming execution: - -![Send Email expression configuration](/_images/integrations/builtin/core-nodes/wait/email_node_2.png) - -### 5. Wait node - -The Wait node will resume execution once the new user clicks the confirmation link in their email (containing the `$resumeWebhookUrl`): - -![Wait node](/_images/integrations/builtin/core-nodes/wait/wait_node.png) - -### 6. Set node - -In this node set the `id` of the user and new **Verified** boolean value to true: - -![Set node 2](/_images/integrations/builtin/core-nodes/wait/set_node_2.png) - -### 7. Airtable node - -Finally you update the table to reflect this newly created *Verified* field: - -![Airtable node configuration](/_images/integrations/builtin/core-nodes/wait/airtable_node_2.png) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.webhook.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.webhook.md deleted file mode 100644 index ff1980097..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.webhook.md +++ /dev/null @@ -1,232 +0,0 @@ -# Webhook - -The Webhook node is one of the most powerful nodes in n8n. It allows you to create [webhooks](https://en.wikipedia.org/wiki/Webhook) which can be used to receive data from apps and services when an event occurs. It is a Trigger node, which means that it serves as the starting point for an n8n workflow. This allows several different services to connect to n8n and run a workflow when data is received. - -!!! note "Keep in mind" - 1. When using the Webhook node on the localhost, ensure that n8n is running with the tunnel mode: [npm with tunnel](/hosting/installation/npm/#n8n-with-tunnel) or [Docker with tunnel](/hosting/installation/docker/#n8n-with-tunnel). -2. When working with a Production webhook, please ensure that you have saved and activated the workflow. Don't forget that the data flowing through the webhook won't be visible in the Editor UI with the Production webhook. - - -Webhook nodes can be used as triggers for workflows when we want to receive data and run a workflow based on the data. The Webhook node also supports returning the data generated at the end of a workflow. This makes it very useful to build a workflow to process data and return the results, like an API endpoint. - -While building or testing a workflow, we recommend that you use a test webhook URL. Using a test webhook ensures that you can view the incoming data in the Editor UI, which is useful for debugging. Make sure that you click on the *Execute Node* button to register the webhook before sending the data to the test webhook. The test webhook stays active for 120 seconds. - - -🎥 The following playlist will help you learn how to use the Webhook node in n8n. - -
- -
- -## Node Reference - -First of all, in the parameters section, we have the Webhook URLs. Clicking on that will reveal the URLs for the webhook. Here you have two options, let's understand the difference between them. - -1. **Webhook URLs** - - **Production**: A Production webhook is only registered when a workflow has been activated (via the switch on the top right of the page). You will never see its data in the Editor UI. To save the executions, you can either set that as a global default or you can specify that on a per-workflow basis in the workflow settings. You will then see the data from the workflow under ‘Past Executions'. - - - **Test**: A Test webhook is only registered in the time between executing a workflow via the UI and until the first call gets made (when it displays “waiting for Webhook call”). After the Test webhook gets called for the first time, it displays the data in the Editor UI, and then gets deactivated. - -2. **Authentication:** The Webhook node supports two methods of authenticating a request that it receives. - - [**Basic Auth**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication) — A method of authentication where the specified username and password must be passed along with the request. - - [**Header Auth**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Authorization) — A method of authentication where the specified header parameter must be passed along with the request. This method can be used when you want to authenticate using an API key or an access token, for example. - !!! tip Keep in mind - The **Credential Data** required for Header Auth credentials will vary on the type used. For example, if you need to provide an `Authorization: Bearer ` header, the Credential Data `Name` would be `Authorization` and the `Value` would be `Bearer `. - - -3. **HTTP Method:** The Webhook node supports receiving two types of [HTTP Requests](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods). - - [**GET Request**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/GET) — GET requests are typically used to request data from a resource. This type of request is typically used to retrieve data from a service. - - [**POST Request**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST) — POST requests are typically used to send data to a resource for a create/update operation. This type of request is typically used to send data to a service. - -4. **Path:** By default, this field contains a randomly generated webhook URL path, to avoid conflicts with other webhook nodes. You can also manually specify a URL path if necessary. A good example would be if you were using n8n to prototype an API; and wanted consistent endpoint URLs. - -5. **Response Code:** Allows you to customize the [HTTP response code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status) that the Webhook node will return upon successful execution. - -6. **Response When:** This dropdown list allows you to select between two response modes. - - **Webhook received:** When this option is selected, the Webhook node will return the specified response code along with the message “Workflow got started.”. - - **Last node finishes:** When this option is selected, the Webhook node will return the specified response code along with the data output from the last node executed in the workflow. - -**Optional Parameters:** The Webhook node also supports several optional methods that can be used during configuration. - -- [**Response Headers**](https://developer.mozilla.org/en-US/docs/Glossary/Response_header) — This option allows you to specify additional headers in the Webhook response. -- **Raw Body** — This option is used to specify when the Webhook node will receive data in a RAW format, such as JSON or XML. -- **Binary Data** — This option is available only when the Webhook node is set to receive POST requests. Setting this to ‘true' lets the Webhook node know that it will receive binary data (such as an image/audio). You can use this option when you expect to receive a file via your Webhook node. - -**Conditional Parameters:** The Webhook node also supports several other parameters, that are used only in certain configurations. - -- **Response Data:** This option is available only when set to respond when ‘Last node finishes'. It allows you to choose which data to return: - - **All Entries** — Choose this option to return all the data generated by the last node in the workflow, as an array. - - **First Entry JSON** — Choose this option to return the first data entry of the last node in the workflow, as a JSON object. - - **First Entry Binary** — Choose this option to return the binary data of the first entry of the last node in the workflow, as a binary file. - -## Example Usage - -This workflow allows you to receive the weather information of a city using the Webhook and the OpenWeatherMap nodes. You can also find the [workflow](https://n8n.io/workflows/807) on n8n.io. This example usage workflow uses the following nodes. -- [Webhook]() -- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) - -The final workflow should look like the following image. - -![A workflow with the Webhook node](/_images/integrations/builtin/core-nodes/webhook/workflow.png) - -### 1. Webhook node - -This node will trigger the workflow. We will make a GET request to the Test URL and pass on a query parameter `city`. We will use the value of this query parameter in the next node in the workflow. - -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. Select 'Last Node' from the ***Response Mode***. This will return the data from the last executed node. -4. Select 'All Entries' from the ***Response Data***. This will return all the entries of the last executed node. -5. Save the workflow to register the webhook. -6. Click on ***Execute Node*** to run the node. -7. In a new browser tab, paste the URL you copied in the previous step and append it with `?city=Berlin`. Your URL should look similar to the following URL:`https://your-n8n.url/webhook/path?city=Berlin`. We are passing a query parameter `city` and assigning it the value `Berlin`. -8. 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/core-nodes/webhook/webhook_node.png) - -### 2. OpenWeatherMap node (Current Weather) - -This node will return data about the current weather for the city that we received in the previous node. - -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. Click on the gears icon next to the ***City*** field and click on ***Add Expression***. - -3. Select the following in the ***Variable Selector*** section: Nodes > Webhook > Output Data > JSON > query > city. You can also add the following expression: `{{$node["Webhook"].json["query"]["city"]}}`. -4. 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/core-nodes/webhook/openweathermap_node.png) - -### 3. Set node - -We will use the Set node to ensure that only the data that we set in this node gets returned to the workflow. We will set the value of `temp` and `description` in this node. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `temp` in the ***Name*** 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 > OpenWeatherMap > Output Data > JSON > main > temp. You can also add the following expression: `{{$node["OpenWeatherMap"].json["main"]["temp"]}}`. -5. Click on ***Add Value*** and select 'String' from the dropdown list. -6. Enter `description` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > OpenWeatherMap > Output Data > JSON > weather > [Item: 0] > description. You can also add the following expression: `{{$node["OpenWeatherMap"].json["weather"][0]["description"]}}`. -9. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -10. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sets the values of `temp` and `description`. - -![Using the Set node to set the values for temp and description](/_images/integrations/builtin/core-nodes/webhook/set_node.png) - -Save the workflow and execute it again by clicking on the ***Execute Workflow*** button in the Editor UI. This time you will receive the temperature and description as the response in the browser. - -!!! 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. - - - -## FAQs - -### Where to find the Webhook URLs? - -The Webhook node has two URLs - Test URL and Production URL. -To get these URLs, follow the steps mentioned below. -1. Click on ***Webhook URLs***. By default, the node displays the Production URL. -2. If you want the Test URL, click on the ***Test*** tab. -3. To copy the URL, click on the displayed URL. - -Here is a GIF demonstrating how to retrieve the test and production webhook URLs in n8n. - -![Retrieving the Test and Production URLs from the Webhook node](/_images/integrations/builtin/core-nodes/webhook/webhook-url.gif) - -### How to use the HTTP Request node to trigger the Webhook node? - -The [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node is used to make HTTP requests to the URL you specify. To use the HTTP Request node to trigger the Webhook node, follow the steps mentioned below. -1. Create a new workflow. -2. Add the HTTP Request node to the workflow. -3. Select the appropriate method from the ***Request Method*** dropdown list. For example, if you have selected GET as the HTTP method in your Webhook node, select GET as the request method in the HTTP Request node. -4. Copy the URL from the Webhook node, and paste it in the ***URL*** field in the HTTP Request node. -5. Execute the workflow with the Webhook node if you're using the Test URL. -6. Execute the HTTP Request node. - -Here is a video demonstrating how to send a request to a Webhook based workflow using the HTTP Request node: - -
- -
- -### How to use route parameters? - -You can add route parameters to the webhook URL path. This is useful when you are creating an API. The *Path* field can take the following values: - -- `/:variable` -- `/path/:variable` -- `/:variable/path` -- `/:variable1/path/:variable2` -- `/:variable1/:variable2` - -### How to use cURL to trigger the Webhook node? - -You can use [cURL](https://curl.se/) to make HTTP requests that will trigger the Webhook node. To use cURL, make sure that you have installed it on your machine. You can follow [this guide](https://www.booleanworld.com/curl-command-tutorial-examples/) to install cURL on your machine. -Based on your use-case, you can make an HTTP request with or without any parameters. You can also send files with the HTTP request using cURL. - -**Note:** In the following commands, replace `https://your-n8n.url/webhook/path` with your webhook URL. - -- #### Make an HTTP request without any parameters - To make a GET request without any parameters, use the following command in your terminal. - -```sh -curl --request GET https://your-n8n.url/webhook/path -``` - -To make a POST request, use the following command. - -```bash -curl --request POST https://your-n8n.url/webhook/path -``` - -- #### Make an HTTP request with body parameter - -To make an HTTP request with a body parameter, use the following command. - -```sh -curl --request GET https://your-n8n.url/webhook/path --data 'key=value' -``` - -- #### Make an HTTP request with header parameter - -To make an HTTP request with a header parameter, use the following command. - -```sh -curl --request GET https://your-n8n.url/webhook/path --header 'key=value' -``` - -- #### Make an HTTP request to send a file - -To send a file with the HTTP request, use the following command. - -```sh -curl --request GET https://your-n8n.url/webhook/path --from 'key=@/path/to/file' -``` -Replace `/path/to/file` with the path of the file you want to send. - -### How to send a response of type `string`? -To send a response of type string, follow the steps mentioned below. -1. Select 'Last Node' from the ***Response Mode*** dropdown list. -2. Select 'First Entry JSON' from the ***Response Data*** dropdown list. -3. Click on 'Add Option' and select 'Property Name' from the dropdown list. -4. Enter the name of the property that contains the response. -5. Connect a Set node to the Webhook node. -6. In the Set node, click on 'Add Value' and select 'String'. -7. Enter the name of the property in the ***Name*** field. The name should match the property name from step 4. -8. Enter the string value in the ***Value*** field. -9. Toggle ***Keep Only Set*** to `true`. - -When the Webhook gets called, it will send the string response that was set in the Set node. - - - - - diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.workflowTrigger.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.workflowTrigger.md deleted file mode 100644 index 91db74f40..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.workflowTrigger.md +++ /dev/null @@ -1,52 +0,0 @@ -# Workflow Trigger - -The Workflow Trigger node gets triggered when a workflow is updated or activated. - -!!! note "Keep in mind" - If you want to use the Workflow Trigger node for a workflow, add the node to the workflow. You don't have to create a separate workflow. - - -The Workflow Trigger node gets triggered for the workflow that it gets added to. The Workflow Trigger node can be used to trigger a workflow to notify the state of the workflow. - -## Node Reference - -- Events - - ***Active Workflow Updated:*** Triggers when this workflow is updated - - ***Workflow Activated:*** Triggers when this workflow is activated - -## Example Usage - -This workflow allows you to receive a message on Mattermost when a workflow is updated. You can also find the [workflow](https://n8n.io/workflows/1059) on n8n.io. This example usage workflow uses the following nodes. -- [Workflow Trigger]() -- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/) - -The final workflow should look like the following image. - -![A workflow with the Webhook node](/_images/integrations/builtin/core-nodes/workflowtrigger/workflow.png) - -### 1. Workflow Trigger node - -Open the workflow where you want to add the Workflow Trigger workflow. Add the Workflow Trigger node to the workflow. - -The Workflow Trigger node will trigger the workflow when the workflow gets updated. - -1. Select 'Active Workflow Updated' from the ***Events*** dropdown list. - -In the screenshot below, you will notice that the node triggers the workflow when the workflow gets updated. - -![Using the Workflow Trigger node to trigger the workflow](/_images/integrations/builtin/core-nodes/workflowtrigger/workflowtrigger_node.png) - -### 2. Mattermost node (post: message) - -This node will send a message in the `workflow` channel on Mattermost. - -1. First of all, you'll have to enter credentials for the Mattermost node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/mattermost/). -2. Select a channel from the ***Channel ID*** dropdown list. -3. Click on the gears icon next to the ***Message*** field click on ***Add Expression***. - -4. Enter the following message in the ***Expression*** field: `The workflow {{$workflow.name}}, was updated.`. `$workflow.name` returns the name of the workflow. -5. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that the node sends a message to Mattermost. - -![Using the Mattermost node to send a message to a channel](/_images/integrations/builtin/core-nodes/workflowtrigger/mattermost_node.png) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.writeBinaryFile.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.writeBinaryFile.md deleted file mode 100644 index ebe8e76a8..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.writeBinaryFile.md +++ /dev/null @@ -1,44 +0,0 @@ -# Write Binary File - -The Write Binary File node is used to write a file to the host machine that runs n8n. - -!!! note "Keep in mind" - 1. If you are running n8n in Docker, your command will run on the n8n container and not the Docker host. -2. This node will look for files relative to the n8n install path. It is recommended to use absolute file paths to prevent any errors. - - -## Node Reference - -1. ***File Name*** field: This field specifies the path to which the file should be written, along with the file name. -2. ***Property Name*** field: Name of the binary property to which to write the data of the read file. - -## Example Usage - -This workflow allows you to write a file to the host machine using the Write Binary File node. You can also find the [workflow](https://n8n.io/workflows/590) on the website. This example usage workflow would use the following three nodes. -- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [Write Binary File]() - - -The final workflow should look like the following image. - -![A workflow with the Write Binary File node](/_images/integrations/builtin/core-nodes/writebinaryfile/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. HTTP Request node - -1. Enter `https://docs.n8n.io/assets/img/n8n-logo.png` in the ***URL*** field. -2. Select the 'File' option from the ***Response Format*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -![Using the HTTP Request node to get an image](/_images/integrations/builtin/core-nodes/writebinaryfile/httprequest_node.png) - - -### 3. Write Binary File node - -1. Enter the path to which the file should be written along with the file name in the ***File Name*** field. -2. Click on ***Execute Node*** to run the node. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.xml.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.xml.md deleted file mode 100644 index 00206076c..000000000 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.xml.md +++ /dev/null @@ -1,56 +0,0 @@ -# XML - -The XML node is useful to convert data from and to XML. - -## Node Reference - -- **Mode:** The format the data should be converted from and to. - - ***JSON to XML:*** Converts data from JSON to XML - - ***XML to JSON:*** Converts data from XML to JSON -- ***Property Name:*** The name of the property which contains the data to convert. -- ***Options*** - - ***Allow Surrogate Chars:*** Allows using characters from the Unicode surrogate blocks. This field is displayed when 'JSON to XML' is selected from the ***Mode*** dropdown list. - - ***cdata:*** Wrap text nodes instead of escaping when necessary. This field is displayed when 'JSON to XML' is selected from the ***Mode*** dropdown list. - - ***Headless:*** Omit the XML header. This field is displayed when 'JSON to XML' is selected from the ***Mode*** dropdown list. - - ***Root Name:*** Root element name to be used. This field is displayed when 'JSON to XML' is selected from the ***Mode*** dropdown list. - - ***Explicit Array:*** Always put child nodes in an array if true; otherwise an array is created. This field is displayed when 'XML to JSON' is selected from the ***Mode*** dropdown list. - - ***Explicit Root:*** Set this if you want to get the root node in the resulting object. This field is displayed when 'XML to JSON' is selected from the ***Mode*** dropdown list. - - ***Ignore Attributes:*** Ignore all XML attributes and only create text nodes. This field is displayed when 'XML to JSON' is selected from the ***Mode*** dropdown list. - - ***Merge Attributes:*** Merge attributes and child elements as properties of the parent, instead of keying attributes off a child attribute object. This option is ignored if 'Ignore Attribute' is true. This field is displayed when 'XML to JSON' is selected from the ***Mode*** dropdown list. - - ***Normalize:*** Trim whitespaces inside the text nodes. This field is displayed when 'XML to JSON' is selected from the ***Mode*** dropdown list. - - ***Normalize Tags:*** Normalize all tag names to lowercase. This field is displayed when 'XML to JSON' is selected from the ***Mode*** dropdown list. - - ***Trim:*** Trim the whitespace at the beginning and end of text nodes. This field is displayed when 'XML to JSON' is selected from the ***Mode*** dropdown list. - - ***Attribute Key:*** Prefix that is used to access the attributes. - - ***Character Key:*** Prefix that is used to access the character content. - - -## Example Usage - -This workflow allows you to convert the JSON data received from the [CocktailDB API](https://www.thecocktaildb.com/) to XML. You can also find the [workflow](https://n8n.io/workflows/661) 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/) -- [XML]() - -The final workflow should look like the following image. - -![A workflow with the XML node](/_images/integrations/builtin/core-nodes/xml/workflow.png) - -### 1. Start node - -The start node exists by default when you create a new workflow. - - -### 2. HTTP Request node (GET) - -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. - -![Get random cocktail data from CocktailDB API using the HTTP Request node](/_images/integrations/builtin/core-nodes/xml/httprequest_node.png) - - -### 3. XML node (JSON to XML) - -1. Select 'JSON to XML' from the ***Mode*** dropdown list. -2. Click on ***Execute Node*** to run the node. - -![Convert JSON to XML using the XML node](/_images/integrations/builtin/core-nodes/xml/xml_node.png) diff --git a/docs/integrations/builtin/credentials/actionnetwork.md b/docs/integrations/builtin/credentials/actionnetwork.md deleted file mode 100644 index 4a339ff84..000000000 --- a/docs/integrations/builtin/credentials/actionnetwork.md +++ /dev/null @@ -1,23 +0,0 @@ -# Action Network - -You can use these credentials to authenticate the following nodes: - -- [Action Network](/integrations/builtin/app-nodes/n8n-nodes-base.actionNetwork/) - -## Prerequisites - -- Create an [Action Network](https://actionnetwork.org/) account. -- [Contact](https://actionnetwork.org/contact) Action Network to become a partner and enable API access. - -## Using API key - -After becoming an Action Network partner: - -1. Open your Action Network dashboard. -2. From the **Start Organizing** menu navigate to **Details** > **API & Sync**. -3. Use the dropdown to select the list you want to generate a key for, your personal list or that of any groups you are an administrator of. -4. From the **Your API Key** section, generate a new API key: - -![API & Sync Page](/_images/integrations/builtin/credentials/actionnetwork/action_network_api_key.png) - -5. Copy your new key and use it with your Action Network node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/activecampaign.md b/docs/integrations/builtin/credentials/activecampaign.md deleted file mode 100644 index 55b01da59..000000000 --- a/docs/integrations/builtin/credentials/activecampaign.md +++ /dev/null @@ -1,22 +0,0 @@ -# ActiveCampaign - -You can use these credentials to authenticate the following nodes with ActiveCampaign. - -- [ActiveCampaign](/integrations/builtin/app-nodes/n8n-nodes-base.activeCampaign/) -- [Active Campaign Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.activeCampaignTrigger/) - - -## Prerequisites - -Create an [ActiveCampaign](https://www.activecampaign.com/) account. - -## Using Access Token - -1. Open your ActiveCampaign dashboard. -2. Click on the gears icon on the bottom left to open the Settings. -3. Click on the Developer option under the Settings panel. -4. In the Developer Settings, copy the 'Key' and 'URL' under the ‘API Access' panel. -5. Use these credentials with your ActiveCampaign node credentials in n8n. - - -![Getting ActiveCampaign credentials](/_images/integrations/builtin/credentials/activecampaign/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/acuityscheduling.md b/docs/integrations/builtin/credentials/acuityscheduling.md deleted file mode 100644 index 6d34d461d..000000000 --- a/docs/integrations/builtin/credentials/acuityscheduling.md +++ /dev/null @@ -1,39 +0,0 @@ -# Acuity Scheduling - -You can use these credentials to authenticate the following nodes with Acuity Scheduling. - -- [Acuity Scheduling Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.acuitySchedulingTrigger/) - -## Prerequisites - -Create an [Acuity Scheduling](https://acuityscheduling.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Acuity Scheduling account to n8n. - - -1. Visit the [Acuity OAuth2 Account Registration page](https://acuityscheduling.com/oauth2/register). -2. Enter a name in the ***Account Name*** field. -3. Enter your email address in the ***Email Address*** field. -4. Enter your URL in the ***Website*** field. -5. Enter a description in the ***Application Description*** field. -6. Copy your OAuth Callback URL from the 'Create New Credentials' screen in n8n and paste in the ***Callback URIs*** section. -7. Click on the ***Register*** button. -8. Use the provided ***Client ID*** and the ***Client Secret*** with your Acuity Scheduling OAuth2 API credentials in n8n. -9. Click on the circle button in the OAuth section to connect your Acuity Scheduling account to n8n. -10. Click the ***Save*** button to save your credentials. - -![Getting Acuity Scheduling OAuth2 credentials](/_images/integrations/builtin/credentials/acuityscheduling/using-oauth.gif) - - -## Using Access Token - -1. Open your Acuity Scheduling dashboard. -2. Click on 'Integrations' in the left sidebar. -3. Scroll down and click on 'view credentials' under the API section. -4. Copy the ***User ID*** and ***API Key*** from the pop-up that is displayed. -5. Use these credentials with your Acuity Scheduling node credentials in n8n. - -![Getting Acuity Scheduling credentials](/_images/integrations/builtin/credentials/acuityscheduling/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/adalo.md b/docs/integrations/builtin/credentials/adalo.md deleted file mode 100644 index 36ea6edca..000000000 --- a/docs/integrations/builtin/credentials/adalo.md +++ /dev/null @@ -1,19 +0,0 @@ -# Adalo - -You can use these credentials to authenticate the following nodes with Adalo: - -* [Adalo node](/integrations/builtin/app-nodes/n8n-nodes-base.adalo/) - -## Prerequisites - -* An Adalo account -* An API key. Follow [Adalo's API documentation](https://help.adalo.com/integrations/the-adalo-api/collections){:target=_blank .external-link} to get your key. -* Your Adalo app ID. - -## API key - ---8<-- "_snippets/integrations/builtin/credentials/open-credential-modal-list.md" - -1. Copy the API key from Adalo into **API Key**. -1. Copy the App ID for your Adalo app into **App ID**. -1. Select **Save**. n8n tests your credentials and confirms that they work. diff --git a/docs/integrations/builtin/credentials/affinity.md b/docs/integrations/builtin/credentials/affinity.md deleted file mode 100644 index 9cdbad9e2..000000000 --- a/docs/integrations/builtin/credentials/affinity.md +++ /dev/null @@ -1,24 +0,0 @@ -# Affinity - -You can use these credentials to authenticate the following nodes with Affinity. - -- [Affinity](/integrations/builtin/app-nodes/n8n-nodes-base.affinity/) -- [Affinity Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.affinityTrigger/) - - - -## Prerequisites - -Create an [Affinity](https://www.affinity.co/) account. - -## Using Access Token - -1. Open your Affinity dashboard. -2. Open hamburger menu on the top left. -3. Click on Settings. -4. Click on API. -5. Click on 'Generate an API Key' button. -6. Use the API key with your Affinity node credentials in n8n. - - -![Getting Affinity credentials](/_images/integrations/builtin/credentials/affinity/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/agilecrm.md b/docs/integrations/builtin/credentials/agilecrm.md deleted file mode 100644 index a703453d2..000000000 --- a/docs/integrations/builtin/credentials/agilecrm.md +++ /dev/null @@ -1,21 +0,0 @@ -# Agile CRM - -You can use these credentials to authenticate the following nodes with Agile CRM. - -- [Agile CRM](/integrations/builtin/app-nodes/n8n-nodes-base.agileCrm/) - - -## Prerequisites - -Create an [Agile CRM](https://www.agilecrm.com/) account. - -## Using Access Token - -1. Open your Agile CRM dashboard. -2. Click on your user icon in the top right of the window. -3. Click on the Admin Settings button. -4. Click on the 'Developers & Api' button in the bottom left. -5. Use the REST API key, your registered email and your Agile CRM subdomain (for instance, n8n) with your Agile CRM node credentials in n8n. - - -![Getting AgileCrm credentials](/_images/integrations/builtin/credentials/agilecrm/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/airtable.md b/docs/integrations/builtin/credentials/airtable.md deleted file mode 100644 index fa1069f06..000000000 --- a/docs/integrations/builtin/credentials/airtable.md +++ /dev/null @@ -1,27 +0,0 @@ -# Airtable - -You can use these credentials to authenticate the following nodes with Airtable. - -- [Airtable](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/) -- [Airtable Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.airtableTrigger/) - -## Prerequisites - -Create an [Airtable](https://airtable.com/) account. - -## Using API Key - -1. Open your Airtable [dashboard](https://airtable.com/). -2. Click on the user icon on the top right and select 'Account' from the dropdown list. -3. Under the ***API*** section, click on the ***Generate API key*** button. -4. Copy the displayed API key. -5. Enter a name for your credentials in the ***Credentials Name*** field in the 'Airtable API' credentials in n8n. -6. Paste the API key in the ***API Key*** field in the 'Airtable API' credentials in n8n. -7. Click on the ***Create*** button to create the credentials. - - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/amqp.md b/docs/integrations/builtin/credentials/amqp.md deleted file mode 100644 index 1d6e71615..000000000 --- a/docs/integrations/builtin/credentials/amqp.md +++ /dev/null @@ -1,16 +0,0 @@ -# AMQP - -You can use these credentials to authenticate the following nodes with AMQP. - -- [AMQP Sender](/integrations/builtin/app-nodes/n8n-nodes-base.amqp/) -- [AMQP Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.amqpTrigger/) - -## Prerequisites - -You need to have a AMQP 1.0 compatible message broker installed. - -## Using ActiveMQ connection - -Use your Hostname, Port, User, and Password as the AMQP Sender credential data in n8n. - -**Note:** The default username for ActiveMQ is `admin` and the default password is `admin`. diff --git a/docs/integrations/builtin/credentials/apitemplateio.md b/docs/integrations/builtin/credentials/apitemplateio.md deleted file mode 100644 index 933998aed..000000000 --- a/docs/integrations/builtin/credentials/apitemplateio.md +++ /dev/null @@ -1,25 +0,0 @@ -# APITemplate.io - -You can use these credentials to authenticate the following nodes with APITemplate.io. - -- [APITemplate.io](/integrations/builtin/app-nodes/n8n-nodes-base.apiTemplateIo/) - -## Prerequisites - -Create an [APITemplate.io](https://apitemplate.io/) account. - -## Using API Key - -1. Open your APITemplate.io [dashboard](https://app.apitemplate.io). -2. Click on ***API Integration*** on the left sidebar. -3. Click on the ***Copy text*** button to copy the API key. -4. Enter a name for your credentials in the ***Credentials Name*** field in the 'APITemplate.io API' credentials in n8n. -5. Paste the API key in the ***API Key*** field in the 'APITemplate.io API' credentials in n8n. -6. Click on the ***Create*** button to create the credentials. - - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/asana.md b/docs/integrations/builtin/credentials/asana.md deleted file mode 100644 index 5df968522..000000000 --- a/docs/integrations/builtin/credentials/asana.md +++ /dev/null @@ -1,45 +0,0 @@ -# Asana - -You can use these credentials to authenticate the following nodes with Asana. - -- [Asana](/integrations/builtin/app-nodes/n8n-nodes-base.asana/) -- [Asana Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.asanaTrigger/) - - -## Prerequisites - -Create an [Asana](https://www.Asana.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Asana account to n8n. - - -1. Open your Asana dashboard. -2. Click on your user icon in the top right. -3. Click on ***My Profile Settings...*** -4. Click on the ***Apps*** tab. -5. Click on ***Manage Developer Apps***. -6. Click on ***New App***. -7. Enter a name, accept the *API terms and conditions*, and click on ***Create app***. -8. Copy the ***OAuth Callback URL*** from n8n and paste it in the ***Redirect URLs*** field and click ***Add***. -9. Use the provided ***Client ID*** and ***Client secret*** with your Asana OAuth2 API credentials in n8n. -10. Click on the circle button in the OAuth section to connect an Asana account to n8n. -11. Click the ***Save*** button to save your credentials in n8n. - -![Getting Asana credentials](/_images/integrations/builtin/credentials/asana/using-oauth.gif) - -## Using Access Token - -1. Open your Asana dashboard. -2. Click on your user icon in the top right of the window. -3. Click on ***My Profile Settings***. -4. Click on the ***Apps*** tab. -5. Click on ***Manage Developer Apps***. -6. Click on ***New access token*** under the ***Personal access tokens*** section. -7. Enter a name for the access token and agree to the API terms and conditions. -8. Click on the ***Create token*** button. -9. Copy the token and use it with your Asana node credentials in n8n. - -![Getting Asana credentials](/_images/integrations/builtin/credentials/asana/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/automizy.md b/docs/integrations/builtin/credentials/automizy.md deleted file mode 100644 index ac266801f..000000000 --- a/docs/integrations/builtin/credentials/automizy.md +++ /dev/null @@ -1,17 +0,0 @@ -# Automizy - -You can use these credentials to authenticate the following nodes with Automizy. - -- [Automizy](/integrations/builtin/app-nodes/n8n-nodes-base.automizy/) - -## Prerequisites - -Create an [Automizy](https://automizy.com/) account. - -## Using API Token - -1. Access the [Automizy dashboard](https://app.automizy.com/dashboard). -2. Click on ***Settings*** in the bottom left corner and select 'API Token'. -3. Click on the ***CREATE TOKEN*** button. -4. Click on the ***COPY & CLOSE*** button to copy the API token. -5. Use this API token with your Auotmizy node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/autopilot.md b/docs/integrations/builtin/credentials/autopilot.md deleted file mode 100644 index fc375e3b9..000000000 --- a/docs/integrations/builtin/credentials/autopilot.md +++ /dev/null @@ -1,27 +0,0 @@ -# Autopilot - -You can use these credentials to authenticate the following nodes with Autopilot. - -- [Autopilot](/integrations/builtin/app-nodes/n8n-nodes-base.autopilot/) -- [Autopilot Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.autopilotTrigger/) - -## Prerequisites - -Create an [Autopilot](https://app.autopilothq.com) account. - -## Using API Key - -1. Open your Autopilot [dashboard](https://app.autopilothq.com). -2. Click on the gears icon on the left sidebar to open the ***Settings*** menu. -3. Click on ***Autopilot API***. -4. Click on the ***Generate*** button to create the API key. -5. Copy the displayed API key. -6. Enter a name for your credentials in the ***Credentials Name*** field in the 'Autopilot API' credentials in n8n. -7. Paste the API key in the ***API Key*** field in the 'Autopilot API' credentials in n8n. -8. Click on the ***Create*** button to create the credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/aws.md b/docs/integrations/builtin/credentials/aws.md deleted file mode 100644 index 694fdb99f..000000000 --- a/docs/integrations/builtin/credentials/aws.md +++ /dev/null @@ -1,41 +0,0 @@ -# AWS - -You can use these credentials to authenticate the following nodes with AWS. - -- [AWS Certificate Manager](/integrations/builtin/app-nodes/n8n-nodes-base.awsCertificateManager/) -- [AWS DynamoDB](/integrations/builtin/app-nodes/n8n-nodes-base.awsDynamoDb/) -- [AWS Elastic Load Balancing](/integrations/builtin/app-nodes/n8n-nodes-base.awsElb/) -- [AWS Lambda](/integrations/builtin/app-nodes/n8n-nodes-base.awsLambda/) -- [AWS Rekognition](/integrations/builtin/app-nodes/n8n-nodes-base.awsRekognition/) -- [AWS S3](/integrations/builtin/app-nodes/n8n-nodes-base.awsS3/) -- [AWS SES](/integrations/builtin/app-nodes/n8n-nodes-base.awsSes/) -- [AWS SNS](/integrations/builtin/app-nodes/n8n-nodes-base.awsSns/) -- [AWS SNS Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.awsSnsTrigger/) -- [AWS SQS](/integrations/builtin/app-nodes/n8n-nodes-base.awsSqs/) -- [AWS Textract](/integrations/builtin/app-nodes/n8n-nodes-base.awsTextract/) -- [AWS Transcribe](/integrations/builtin/app-nodes/n8n-nodes-base.awsTranscribe/) - -## Prerequisites - -Create an [AWS](https://aws.amazon.com/){:target=_blank .external-link} account. - -## Using Access Token - -1. Open your [AWS Management Console](https://console.aws.amazon.com){:target=_blank .external-link}. -2. Click on your name on the top right and select 'My Security Credentials' from the dropdown. -3. Click on the **Create New Access Key** button, under the **Access keys (access key ID and secret access key)** section -4. Click on the **Show Access Key** button. -5. Copy the displayed Access Key ID. -6. Enter the name for your credentials in the **Credentials Name** field in the 'AWS' credentials in n8n. -7. Paste the Access Key ID in the **Access Key ID** field in the 'AWS' credentials in n8n. -8. Copy the secret access key from your AWS console. -9. Paste the secret access key in the **Secret Access Key** field in the 'AWS' credentials in n8n. -10. Click the **Create** button to save your credentials in n8n. - -**Note:** If you're running your AWS instance in a different region, please update the **Region** field accordingly. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/bamboohr.md b/docs/integrations/builtin/credentials/bamboohr.md deleted file mode 100644 index 95362c467..000000000 --- a/docs/integrations/builtin/credentials/bamboohr.md +++ /dev/null @@ -1,18 +0,0 @@ -# BambooHR - -You can use these credentials to authenticate the following nodes with BambooHR. - -- [BambooHR](/integrations/builtin/app-nodes/n8n-nodes-base.bambooHr/) - -## Prerequisites - -Create a [BambooHR](https://www.bamboohr.com/) account. - -## Using Access Token - -1. Log into your BambooHR account and click on the profile image in the upper right corner. -2. Click on *API Keys*. -3. Click on *Add New Key*, enter any name for your new key and hit *Generate Key*. -4. Copy the key provided by BambooHR into the *API Key* field of n8n's credentials modal. -5. Enter your subdomain (the part between `https://` and `.bamboohr.com`) in the *Subdomain* field of n8n's credentials modal. -6. Click on *Save*. diff --git a/docs/integrations/builtin/credentials/bannerbear.md b/docs/integrations/builtin/credentials/bannerbear.md deleted file mode 100644 index 86a2ce7ee..000000000 --- a/docs/integrations/builtin/credentials/bannerbear.md +++ /dev/null @@ -1,22 +0,0 @@ -# Bannerbear - -You can use these credentials to authenticate the following nodes with Bannerbear. - -- [Bannerbear](/integrations/builtin/app-nodes/n8n-nodes-base.bannerbear/) - - -## Prerequisites - -Create a [BannerBear](https://www.BannerBear.com/) account. - -## Using Access Token - -1. Open your BannerBear dashboard. -2. Click on "Create New Project". -3. Enter Project name and save. -4. Click on Projects tab and enter the newly creatted project. -5. Click on "Settings / API Key". -6. Use API key in your Bannerbear node credentials in n8n. - - -![Getting Bannerbear credentials](/_images/integrations/builtin/credentials/bannerbear/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/baserow.md b/docs/integrations/builtin/credentials/baserow.md deleted file mode 100644 index d8b6e30d3..000000000 --- a/docs/integrations/builtin/credentials/baserow.md +++ /dev/null @@ -1,21 +0,0 @@ -# Baserow - -You can use these credentials to authenticate the following node: - -- [Baserow](/integrations/builtin/app-nodes/n8n-nodes-base.baserow/) - -## Prerequisites - -Create a [Baserow](https://baserow.io/) account on any hosted Baserow instance -or a self hosted instance. - -## Using User Account - -1. In n8n, open the **Credentials** menu item and click on **New** -2. In the **Add new credential** dialogue, select **Baserow API** and click on the **Continue** button -3. If using the online version of Baserow, leave the **Host** as `https://api.baserow.io`, otherwise set it to your self-hosted instance API URL. -4. Enter your Baserow username in the **Username** field -5. Enter your Baserow password in the **Password** field -6. Click on the **Save** button - -You can now use this credential in your Baserow nodes. diff --git a/docs/integrations/builtin/credentials/beeminder.md b/docs/integrations/builtin/credentials/beeminder.md deleted file mode 100644 index 5941f6f32..000000000 --- a/docs/integrations/builtin/credentials/beeminder.md +++ /dev/null @@ -1,27 +0,0 @@ -# Beeminder - -You can use these credentials to authenticate the following nodes with Beeminder. - -- [Beeminder](/integrations/builtin/app-nodes/n8n-nodes-base.beeminder/) - -## Prerequisites - -Create a [Beeminder](https://Beeminder.io/account) account. - -## Using API Key - -1. Open your [Beeminder dashboard](https://beeminder.com/home). -2. Click on your avatar at the top-right corner. -3. Select 'ACCOUNT SETTINGS' from the dropdown list. -4. Scroll up and click on the ***APPS & API*** tab. -5. Copy the ***Auth Token*** displayed in the ***API*** section. -6. Enter the name for your credentials in the ***Credentials Name*** field in the 'Beeminder API' credentials in n8n. -7. Enter your username in the ***User*** field. -8. Paste the Auth Token in the ***Auth Token*** field. -9. Click on the ***Save*** button to save your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/bitbucket.md b/docs/integrations/builtin/credentials/bitbucket.md deleted file mode 100644 index 4315c31a6..000000000 --- a/docs/integrations/builtin/credentials/bitbucket.md +++ /dev/null @@ -1,14 +0,0 @@ -# Bitbucket - -You can use these credentials to authenticate the following nodes with Bitbucket. - -- [Bitbucket Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.bitbucketTrigger/) - - -## Prerequisites - -Create an [Bitbucket](https://www.Bitbucket.com/) account. - -## Using Username and Password - -Use the username and application password. diff --git a/docs/integrations/builtin/credentials/bitly.md b/docs/integrations/builtin/credentials/bitly.md deleted file mode 100644 index 4a71c598d..000000000 --- a/docs/integrations/builtin/credentials/bitly.md +++ /dev/null @@ -1,38 +0,0 @@ -# Bitly - -You can use these credentials to authenticate the following nodes with Bitly. - -- [Bitly](/integrations/builtin/app-nodes/n8n-nodes-base.bitly/) - -## Prerequisites - -Create a [Bitly](https://www.bitly.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Bitly account to n8n. - - -1. Open your Bitly dashboard. -2. Click on your account button in the top right. -3. Click on "Profile Settings". -4. Click on "Registered OAuth Applications". -5. Click on "GET REGISTRATION CODE". -6. Use Client Secret and Client ID in your Bitly node credentials in n8n. -7. Enter n8n provided redirect URL. Redirect URL Explanation [here](/). - - -![Getting Bitly credentials](/_images/integrations/builtin/credentials/bitly/using-oauth.gif) - -## Using Access Token - -1. Open your Bitly dashboard. -2. Click on your account button in the top right. -3. Click on "Profile Settings". -4. Click on "Generate Access Token". -5. Enter password. -6. Use the access token in your Bitly node credentials in n8n. - - -![Getting Bitly credentials](/_images/integrations/builtin/credentials/bitly/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/bitwarden.md b/docs/integrations/builtin/credentials/bitwarden.md deleted file mode 100644 index f60ba2bce..000000000 --- a/docs/integrations/builtin/credentials/bitwarden.md +++ /dev/null @@ -1,32 +0,0 @@ -# Bitwarden - -You can use these credentials to authenticate the following nodes with Bitwarden. - -- [Bitwarden](/integrations/builtin/app-nodes/n8n-nodes-base.bitwarden/) - -## Prerequisites - -Create a [Bitwarden](https://vault.bitwarden.com/#/register?org=teams) organisation account. - -## Using API Key - -1. Open your Bitwarden [vault](https://vault.bitwarden.com/). -2. Click on your organisation under the ***ORGANISATIONS*** section. -3. Click on the ***Settings*** tab. -4. Click on the ***View API key*** button under the ***API key*** section. -5. Enter your master password in the ***Master password*** field. -6. Click on the ***View API key*** button. -7. Copy the displayed client id. -8. Enter the name for your credentials in the ***Credentials Name*** field in the 'Bitwarden API' credentials in n8n. -9. Paste the client id in the ***Client ID*** field in the 'Bitwarden API' credentials in n8n. -10. Copy the client secret from Bitwarden. -11. Paste the client secret in the ***Client Secret*** field in the 'Bitwarden API' credentials in n8n. -12. Click on the ***Create*** button to create your credentials. - -**Note:** If you're hosting Bitwarden on your server, select 'Self-hosted' from the ***Environment*** dropdown list. You also need to enter the domain of your hosted instance in the ***Self-hosted domain*** field. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/box.md b/docs/integrations/builtin/credentials/box.md deleted file mode 100644 index 46a7ff0bb..000000000 --- a/docs/integrations/builtin/credentials/box.md +++ /dev/null @@ -1,28 +0,0 @@ -# Box - -You can use these credentials to authenticate the following nodes with Box. - -- [Box](/integrations/builtin/app-nodes/n8n-nodes-base.box/) -- [Box Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.boxTrigger/) - -## Prerequisites - -Create a [Box](https://www.box.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Box account to n8n. - - -1. Access the [Box Developers Console](https://app.box.com/developers/console). -2. Click on the *Create New App* button. -3. Select 'Custom App' and click *Next*. -4. Select 'Standard OAuth 2.0 (User Authentication)'and click *Next*. -5. Enter any other necessary information and click on the *Create App* button. -6. Copy the 'OAuth Callback URL' provided in the Box OAuth2 API credentials in n8n and paste it in the 'Redirect URI' field in the Box app page. -7. Click the *Save Changes* button and use the displayed 'Client ID' and the 'Client Secret' with your Box OAuth2 API credentials in n8n. -10. Click on the circle button in the OAuth section to connect a Box account to n8n. -11. Click the *Save* button to save your credentials in n8n. - -![Getting Box credentials](/_images/integrations/builtin/credentials/box/using-oauth.gif) diff --git a/docs/integrations/builtin/credentials/brandfetch.md b/docs/integrations/builtin/credentials/brandfetch.md deleted file mode 100644 index 3ef0a95bf..000000000 --- a/docs/integrations/builtin/credentials/brandfetch.md +++ /dev/null @@ -1,18 +0,0 @@ -# Brandfetch - -You can use these credentials to authenticate the following nodes with Brandfetch. - -- [Brandfetch](/integrations/builtin/app-nodes/n8n-nodes-base.Brandfetch/) - -## Prerequisites - -Create a [Brandfetch](https://brandfetch.io/account) account. - -## Using API Key - -1. Access your [Brandfetch dashboard](https://brandfetch.io/dashboard). -2. Click on ***API*** on the left sidebar. -3. Select a plan and click on the ***Get API Key*** button. -4. Use the ***App Key*** with your Brandfetch API credentials in n8n. - -![Getting Brandfetch credentials](/_images/integrations/builtin/credentials/brandfetch/using-api.gif) diff --git a/docs/integrations/builtin/credentials/bubble.md b/docs/integrations/builtin/credentials/bubble.md deleted file mode 100644 index 1eb97cd47..000000000 --- a/docs/integrations/builtin/credentials/bubble.md +++ /dev/null @@ -1,34 +0,0 @@ -# Bubble - -You can use these credentials to authenticate the following nodes with Bubble. - -- [Bubble](/integrations/builtin/app-nodes/n8n-nodes-base.bubble/) - -## Prerequisites - -Create a [Bubble](https://bubble.io) account. - -**Note:** You need a Personal or a higher plan to get access to the Bubble API. - -## Using API Key - -1. Open your Bubble [dashboard](https://bubble.io/home) page. -2. Select an app under the ***My apps*** section to open the app. -3. Click on ***Settings*** on the left-sidebar. -4. Click on the ***API*** tab. -5. Click on the ***Generate a new API token*** button. -6. Enter a token name in the ***API Token Label*** field. -7. Copy the displayed Private Key. -8. Enter the name for your credentials in the ***Credentials Name*** field in the 'Bubble API' credentials in n8n. -9. Paste the Private Key in the ***API Token*** field in the 'Bubble API' credentials in n8n. -10. Enter the app name in the ***APP Name*** field. -11. Select 'Development' from the ***Environment*** dropdown list. If you want to use the 'Live' environment, select 'Live' instead. -12. Click on the ***Create*** button to create your credentials. - -**Note:** If you're self-hosting your Bubble app, select 'Self-hosted' from the ***Hosting*** dropdown list. You will also need to enter the domain of your hosted instance in the ***Domain*** field. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/cal.md b/docs/integrations/builtin/credentials/cal.md deleted file mode 100644 index 75d37d5fb..000000000 --- a/docs/integrations/builtin/credentials/cal.md +++ /dev/null @@ -1,21 +0,0 @@ -# Cal - -You can use these credentials to authenticate the following nodes with Cal. - -- [Cal Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.calTrigger/) - -## Prerequisites - -Create a [Cal](https://www.cal.com/) pro account. - -## Using API keys - -Your API requests are authenticated using API keys. Any request that doesn't include an API key will return an error. - -1. Log into your Cal account. -2. Click on **Settings**. -3. There you will find the API keys section which allows you to generate a key for use. More information on this can be found on the [Cal Authentication](https://developer.cal.com/api/authentication){:target=_blank} page. -4. Use API key in your Cal trigger node credentials in n8n. - - -![Getting Cal credentials](/_images/integrations/builtin/credentials/cal/getting-api-key.gif) diff --git a/docs/integrations/builtin/credentials/calendly.md b/docs/integrations/builtin/credentials/calendly.md deleted file mode 100644 index 01b5a6939..000000000 --- a/docs/integrations/builtin/credentials/calendly.md +++ /dev/null @@ -1,18 +0,0 @@ -# Calendly - -You can use these credentials to authenticate the following nodes with Calendly. - -- [Calendly Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.calendlyTrigger/) - -## Prerequisites - -Create a [Calendly](https://www.calendly.com/) premium account. - -## Using Access Token - -1. Open your Calendly dashboard. -2. Click on "Integrations". -3. Use API key in your Calendly node credentials in n8n. - - -![Getting Calendly credentials](/_images/integrations/builtin/credentials/calendly/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/chargebee.md b/docs/integrations/builtin/credentials/chargebee.md deleted file mode 100644 index 4bea0fae9..000000000 --- a/docs/integrations/builtin/credentials/chargebee.md +++ /dev/null @@ -1,21 +0,0 @@ -# Chargebee - -You can use these credentials to authenticate the following nodes with Chargebee. - -- [Chargebee](/integrations/builtin/app-nodes/n8n-nodes-base.chargebee/) -- [Chargebee Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.chargebeeTrigger/) - -## Prerequisites - -Create a [Chargebee](https://www.chargebee.com/) account. - -## Using Access Token - -1. Open your Chargebee dashboard. -2. Click on "Settings". -3. Click on "Configure Chargebee". -4. Scroll down and click on "API Keys". -5. Use selected API key and Account name in your Chargebee node credentials in n8n. - - -![Getting Chargebee credentials](/_images/integrations/builtin/credentials/chargebee/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/circleci.md b/docs/integrations/builtin/credentials/circleci.md deleted file mode 100644 index 965b36e71..000000000 --- a/docs/integrations/builtin/credentials/circleci.md +++ /dev/null @@ -1,20 +0,0 @@ -# CircleCI - -You can use these credentials to authenticate the following nodes with CircleCI. - -- [CircleCI](/integrations/builtin/app-nodes/n8n-nodes-base.circleCi/) - - -## Prerequisites - -Create a [CircleCI](https://circleci.com/) account. - -## Using Access Token - -1. Access your CircleCI User Settings. -2. Visit the [Personal API Tokens](https://app.circleci.com/settings/user/tokens) section. -3. Click on the *Create New Token* button. -4. Type in a name for your token and click on the *Add API Token* button. -5. Copy the generated API Token and use it with your CircleCI API node credentials in n8n. - -![Getting CircleCI credentials](/_images/integrations/builtin/credentials/circleci/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/ciscowebex.md b/docs/integrations/builtin/credentials/ciscowebex.md deleted file mode 100644 index 8499f0449..000000000 --- a/docs/integrations/builtin/credentials/ciscowebex.md +++ /dev/null @@ -1,42 +0,0 @@ -# Webex by Cisco - -You can use these credentials to authenticate the following nodes: - -- [Webex by Cisco](/integrations/builtin/app-nodes/n8n-nodes-base.ciscoWebex/) -- [Webex by Cisco Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.ciscoWebexTrigger/) - -## Prerequisites - -Create a [Webex by Cisco](https://www.webex.com/) account. - -## Using OAuth - -1. Navigate to [Webex for Developers](https://developer.webex.com/) and sign in using your Webex by Cisco account. -2. From the user menu select **My Webex Apps**, then **Create a New App**. -3. From the ***Create a New App*** page select **Create an Integration**. -4. Complete the following required fields for your new integration: - * ***Integration Name***: Provide a name for your Webex app. - * ***Contact Email***: Enter your email address. - * ***Icon***: Provide an icon for your app or select one of the available defaults. - * ***Description***: Enter a brief description of your app. - * ***Redirect URIs***: Enter the **OAuth Callback URL** from the n8n credentials modal. - * ***Scopes***: Enable the following scopes: - * `spark:rooms_read` - * `spark:messages_write` - * `spark:messages_read` - * `spark:membership_read` - * `spark_membership_write` - * `meeting:recordings_write` - * `meeting:recordings_read` - * `meeting:preferences_read` - * `meeting:schedules_write` - * `meeting:schedules_read` -5. Click **Add Integration** to create your app. -6. Copy the ***Client ID*** and ***Client Secret*** for this new app. - -From n8n: - -7. Enter a descriptive ***Credentials Name***. -8. Under ***Credential Data***, enter the ***Client ID*** and ***Client Secret*** obtained above. -9. Under ***OAuth***, click the circle button to initiate authentication. A popup may appear prompting you to login to your Webex by Cisco account. -10. After authentication is complete, click **Create** to save your new credentials. diff --git a/docs/integrations/builtin/credentials/citrixadc.md b/docs/integrations/builtin/credentials/citrixadc.md deleted file mode 100644 index 3cf9ac12e..000000000 --- a/docs/integrations/builtin/credentials/citrixadc.md +++ /dev/null @@ -1,11 +0,0 @@ -# Citrix ADC - -You can use these credentials to authenticate the following nodes with Citrix ADC: - -* [Citrix ADC node](/integrations/builtin/app-nodes/n8n-nodes-base.citrixAdc/) - -Enter the following information in the **Citrix ADC account** credentials modal: - -* The URL of your Citrix ADC instance -* Username -* Password diff --git a/docs/integrations/builtin/credentials/clearbit.md b/docs/integrations/builtin/credentials/clearbit.md deleted file mode 100644 index 51b8a96a1..000000000 --- a/docs/integrations/builtin/credentials/clearbit.md +++ /dev/null @@ -1,21 +0,0 @@ -# Clearbit - -You can use these credentials to authenticate the following nodes with Clearbit. - -- [Clearbit](/integrations/builtin/app-nodes/n8n-nodes-base.clearbit/) - - -## Prerequisites - -Create a [Clearbit](https://www.clearbit.com/) account. - - -## Using Access Token - -1. Open your Clearbit dashboard. -2. Click on "API". -3. Click on "Configure Chargebee". -4. Use selected API key in your Clearbit node credentials in n8n. - - -![Getting Clearbit credentials](/_images/integrations/builtin/credentials/clearbit/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/clickup.md b/docs/integrations/builtin/credentials/clickup.md deleted file mode 100644 index 500d57eb9..000000000 --- a/docs/integrations/builtin/credentials/clickup.md +++ /dev/null @@ -1,60 +0,0 @@ -# ClickUp - -You can use these credentials to authenticate the following nodes with ClickUp. - -- [ClickUp](/integrations/builtin/app-nodes/n8n-nodes-base.clickUp/) -- [ClickUp Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.clickUpTrigger/) - -## Prerequisites - -Create a [ClickUp](https://www.clickup.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your ClickUp account to n8n. - - -1. Open your ClickUp [dashboard](https://app.clickup.com). -2. Click on your profile icon in the bottom left. -3. Click on **Integrations** under your workspace profile. -4. Click on **ClickUp API**. -5. Click on the **+ Create an App** button under the **ClickUp API** section. -6. Enter the name of your app in the **App Name** field. -7. Copy the 'OAuth Callback URL' provided in the 'ClickUp OAuth2 API' credentials in n8n. -8. Paste it in the **Redirect URL(s)** field. -9. Click on the **Create App** button. -10. Copy the displayed client ID. -11. Enter a name for your credentials in the **Credentials Name** field in the 'ClickUp OAuth2 API' credentials in n8n. -12. Paste the client ID in the **Client ID** field in the 'ClickUp OAuth2 API' credentials in n8n. -13. Copy the client secret from ClickUp. -14. Paste the client secret in the **Client Secret** field in the 'ClickUp OAuth2 API' credentials in n8n. -15. Click on the circle button in the OAuth section to connect a ClickUp account to n8n. -16. Click the **Save** button to save your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
- -The following video demonstrates the steps to authenticate the ClickUp node on [n8n.cloud](https://n8n.cloud). - -
- -
- -## Using Access Token - -1. Open the ClickUp [dashboard](https://app.clickup.com). -2. Click on your profile icon in the bottom left. -3. Click on ***Apps*** under your user profile. -4. Click on the ***Generate*** button under the ***API Token*** section. -5. Click on the ***Copy*** button to copy the token. -6. Enter a name for your credentials in the ***Credentials Name*** field in the 'ClickUp API' credentials in n8n. -7. Paste the token in the ***Access Token*** field in the 'ClickUp API' credentials in n8n. -8. Click on the ***Create*** button to create the credentials. - -
- -
diff --git a/docs/integrations/builtin/credentials/clockify.md b/docs/integrations/builtin/credentials/clockify.md deleted file mode 100644 index 952c9840a..000000000 --- a/docs/integrations/builtin/credentials/clockify.md +++ /dev/null @@ -1,21 +0,0 @@ -# Clockify - -You can use these credentials to authenticate the following nodes with Clockify. - -- [Clockify](/integrations/builtin/app-nodes/n8n-nodes-base.clockify/) -- [Clockify Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.clockifyTrigger/) - -## Prerequisites - -Create a [Clockify](https://www.clockify.com/) account. - -## Using Access Token - -1. Open your Clockify dashboard. -2. Click on your profile. -3. Click on "Profile Settings". -4. Scroll down and click on "Generate" under API. -5. Use selected API key in your Clockify node credentials in n8n. - - -![Getting Clockify credentials](/_images/integrations/builtin/credentials/clockify/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/cloudflare.md b/docs/integrations/builtin/credentials/cloudflare.md deleted file mode 100644 index e372b001d..000000000 --- a/docs/integrations/builtin/credentials/cloudflare.md +++ /dev/null @@ -1,9 +0,0 @@ -# Cloudflare - -You can use these credentials to authenticate the following nodes with Cloudflare: - -* [Cloudflare node](/integrations/builtin/app-nodes/n8n-nodes-base.cloudflare/) - -Follow the [Cloudflare documentation to create an API token](https://developers.cloudflare.com/api/get-started/create-token/){:target=_blank .external-link}. - -Enter your token in the **Cloudflare account** credentials modal. diff --git a/docs/integrations/builtin/credentials/cockpit.md b/docs/integrations/builtin/credentials/cockpit.md deleted file mode 100644 index 499a48978..000000000 --- a/docs/integrations/builtin/credentials/cockpit.md +++ /dev/null @@ -1,20 +0,0 @@ -# Cockpit - -You can use these credentials to authenticate the following nodes with Cockpit. - -- [Cockpit](/integrations/builtin/app-nodes/n8n-nodes-base.cockpit/) - -## Prerequisites - -Create a [Cockpit](https://www.getcockpit.com/) account. - -## Using Access Token - -1. Open your Cockpit dashboard. -2. Click on your profile in the top right. -3. Click on "Account". -4. Scroll down and copy API key. -5. Use selected API key and your Cockpit URL in your Cockpit node credentials in n8n. - - -![Getting Cockpit credentials](/_images/integrations/builtin/credentials/cockpit/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/coda.md b/docs/integrations/builtin/credentials/coda.md deleted file mode 100644 index a161f953b..000000000 --- a/docs/integrations/builtin/credentials/coda.md +++ /dev/null @@ -1,20 +0,0 @@ -# Coda - -You can use these credentials to authenticate the following nodes with Coda. - -- [Coda](/integrations/builtin/app-nodes/n8n-nodes-base.coda/) - -## Prerequisites - -Create a [Coda](https://www.coda.com/) account. - -## Using Access Token - -1. Open your Coda dashboard. -2. Click on your profile in the top right. -3. Click on the 3 dots and then Account settings.. -4. Scroll down and click on "Generate" under API. -5. Use selected API access token in your Coda node credentials in n8n. - - -![Getting Coda credentials](/_images/integrations/builtin/credentials/coda/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/contentful.md b/docs/integrations/builtin/credentials/contentful.md deleted file mode 100644 index d7cc2273c..000000000 --- a/docs/integrations/builtin/credentials/contentful.md +++ /dev/null @@ -1,21 +0,0 @@ -# Contentful - -You can use these credentials to authenticate the following nodes with Contentful. - -- [Contentful](/integrations/builtin/app-nodes/n8n-nodes-base.contentful/) - -## Prerequisites - -Create a [Contentful](https://www.contentful.com/) account. - -## Using Access Token - -1. Open your Contentful dashboard. -2. Open the 'Settings' dropdown list on the top bar. -3. Click on ***API keys***. -4. Click on the ***Add API key*** button in the top right. -5. Enter a name for the API key in the ***Name*** field and click ***Save***. -6. Use the displayed ***Space ID***, ***Content Delivery API - access token***, and ***Content Preview API - access token*** with your Contentful node API credentials in n8n. -7. Click on the ***Save*** button to save your credentials. - -![Getting Contentful credentials](/_images/integrations/builtin/credentials/contentful/using-api-key.gif) diff --git a/docs/integrations/builtin/credentials/convertkit.md b/docs/integrations/builtin/credentials/convertkit.md deleted file mode 100644 index 01ff59aaf..000000000 --- a/docs/integrations/builtin/credentials/convertkit.md +++ /dev/null @@ -1,20 +0,0 @@ -# ConvertKit - -You can use these credentials to authenticate the following nodes with ConvertKit. - -- [ConvertKit](/integrations/builtin/app-nodes/n8n-nodes-base.convertKit/) -- [ConvertKit Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.convertKitTrigger/) - -## Prerequisites - -Create a [ConvertKit](https://convertkit.com/) account. - -## Using Access Token - -1. Access your ConvertKit dashboard. -2. Click on the user icon in the top right and select ***Account settings***. -3. Click on ***Show*** in the ***API Secret*** section to reveal the access token. -4. Use the access token in the ***API Secret*** section with your ConvertKit API credentials in n8n. -5. Click on the ***Save*** button to save your credentials. - -![Getting ConvertKit access token](/_images/integrations/builtin/credentials/convertkit/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/copper.md b/docs/integrations/builtin/credentials/copper.md deleted file mode 100644 index 346ce6f2a..000000000 --- a/docs/integrations/builtin/credentials/copper.md +++ /dev/null @@ -1,28 +0,0 @@ -# Copper - -You can use these credentials to authenticate the following nodes with Copper. - -- [Copper](/integrations/builtin/app-nodes/n8n-nodes-base.copper/) -- [Copper Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.copperTrigger/) - -## Prerequisites - -Create a [Copper](https://www.copper.com/) account. - -## Using Access Token - -1. Open your Copper dashboard. -2. Click on the ***Settings*** tab on the left-sidebar. -3. Click on ***Integrations*** and select ***API Keys***. -4. Click on the ***GENERATE API KEY*** button. -5. Copy the displayed API key. -6. Enter the name for your credentials in the ***Credentials Name*** field in the 'Copper API' credentials in n8n. -7. Paste the API key in the ***API Key*** field in the 'Copper API' credentials in n8n. -8. Enter the email address in the ***Email*** field in the 'Copper API' credentials in n8n. -9. Click the ***Create*** button to create your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/cortex.md b/docs/integrations/builtin/credentials/cortex.md deleted file mode 100644 index 10921ab11..000000000 --- a/docs/integrations/builtin/credentials/cortex.md +++ /dev/null @@ -1,17 +0,0 @@ - -You can use these credentials to authenticate the following nodes with Cortex. - -- [Cortex](/integrations/builtin/app-nodes/n8n-nodes-base.cortex/) - -## Prerequisites - -Install [Cortex](https://github.com/TheHive-Project/CortexDocs/blob/master/installation/install-guide.md) on your server. - -## Using API Key - -1. Access your Cortex dashboard. -2. Click on your user icon on the top right corner and select 'Settings'. -3. Scroll down to the ***API Key*** section and click on the ***Reveal*** button. -4. Use the ***API Key*** and your ***Cortex instance URL*** with your Cortex node credentials in n8n. - -![Getting Cortex credentials](/_images/integrations/builtin/credentials/cortex/using-api.gif) diff --git a/docs/integrations/builtin/credentials/cratedb.md b/docs/integrations/builtin/credentials/cratedb.md deleted file mode 100644 index 9668ca323..000000000 --- a/docs/integrations/builtin/credentials/cratedb.md +++ /dev/null @@ -1,14 +0,0 @@ -# CrateDB - -You can use these credentials to authenticate the following nodes with CrateDB. - -- [CrateDB](/integrations/builtin/app-nodes/n8n-nodes-base.crateDb/) - -## Prerequisites - -An available instance of CrateDB. - -## Using Database Connection - -1. Retrieve your CrateDB credentials and connection parameters. -2. Use the credentials and connection parameters with your CrateDB node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/customerio.md b/docs/integrations/builtin/credentials/customerio.md deleted file mode 100644 index a992ce68e..000000000 --- a/docs/integrations/builtin/credentials/customerio.md +++ /dev/null @@ -1,45 +0,0 @@ -# Customer.io - -You can use these credentials to authenticate the following nodes with Customer.io. - -- [Customer.io](/integrations/builtin/app-nodes/n8n-nodes-base.customerIo/) -- [Customer.io Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.customerIoTrigger/) - -## Prerequisites - -Create a [Customer.io](https://customer.io/) account. - -## Using Access Token - -1. Open your Customer.io [dashboard](https://fly.customer.io). -2. Click on the user icon in the top right and select ***Account settings***. -3. Click on ***API Credentials***. -4. Click on the ***Create Tracking API Key*** button. -5. Enter a name for the Tracking API Key in the ***Name***. -6. Select a workspace from the ***Workspace*** dropdown list. -7. Click on the ***Create Tracking API Key*** button. -8. Copy the displayed 'Site ID'. -9. Enter the name for your credentials in the ***Credentials Name*** field in the 'Customer.io API' credentials in n8n. -10. Paste the Site ID in the ***Tracking Site ID*** field in the 'Customer.io API' credentials in n8n. -11. Copy the 'API Key' from the Manage API Credentials page. -12. Paste the API key in the ***Tracking API Key*** field in the 'Customer.io API' credentials in n8n. -13. Click on the ***App API Keys*** tab on the Manage API Credentials page. -14. Click on the ***Create App API Key*** button. -15. Enter a name for the App API Key in the ***Name*** field. -16. Select a workspace from the ***Workspace*** dropdown list. -17. Click on the ***Create App API Key*** button. -18. Copy the displayed API key. -19. Paste the API key in the ***App API Key*** field in the 'Customer.io API' credentials in n8n. -20. Click on the ***Create*** button to create your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
- -## FAQs - -### Why do I need the Tracking API Key and the App API Key? - -Customer.io uses different API Keys for different endpoints. Based on the operation you want to perform, n8n uses the correct API key to connect to your Customer.io account. diff --git a/docs/integrations/builtin/credentials/deepl.md b/docs/integrations/builtin/credentials/deepl.md deleted file mode 100644 index 696df0753..000000000 --- a/docs/integrations/builtin/credentials/deepl.md +++ /dev/null @@ -1,25 +0,0 @@ -# DeepL - -You can use these credentials to authenticate the following nodes with DeepL. - -- [DeepL](/integrations/builtin/app-nodes/n8n-nodes-base.deepL/) - - -## Prerequisites - -Create a DeepL [developer](https://www.deepl.com/pro/change-plan#developer) account. - -## Using API Key - -1. Open your DeepL [account](https://www.deepl.com/pro-account) page. -2. Scroll down to the ***Authentication Key for DeepL API*** section. -3. Copy the displayed 'API Key'. -4. Enter the name for your credentials in the ***Credentials Name*** field in the 'DeepL API' credentials in n8n. -5. Paste the API key in the ***API Key*** field in the 'DeepL API' credentials in n8n. -6. Click on the ***Create*** button to create your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/demio.md b/docs/integrations/builtin/credentials/demio.md deleted file mode 100644 index 2841f9346..000000000 --- a/docs/integrations/builtin/credentials/demio.md +++ /dev/null @@ -1,29 +0,0 @@ -# Demio - -You can use these credentials to authenticate the following nodes with Demio. - -- [Demio](/integrations/builtin/app-nodes/n8n-nodes-base.demio/) - - -## Prerequisites - -Create a [Demio](https://demio.com/) account. - -## Using API Key - -1. Open your Demio [dashboard](https://my.demio.com/manage/dashboard). -2. Click on your user icon in the top right. -3. Click on ***Settings***. -4. Click on the ***API*** tab. -5. Copy the displayed 'API Key'. -6. Enter the name for your credentials in the ***Credentials Name*** field in the 'Demio API' credentials in n8n. -7. Paste the API key in the ***API Key*** field in the 'Demio API' credentials in n8n. -8. Copy the 'API Secret' from Demio. -9. Paste the API secret in the ***API Secret*** field in the 'Demio API' credentials in n8n. -10. Click the ***Create*** button to save your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/dhl.md b/docs/integrations/builtin/credentials/dhl.md deleted file mode 100644 index 1e988b7e2..000000000 --- a/docs/integrations/builtin/credentials/dhl.md +++ /dev/null @@ -1,20 +0,0 @@ -# DHL - -You can use these credentials to authenticate the following nodes with DHL. - -- [DHL](/integrations/builtin/app-nodes/n8n-nodes-base.dhl/) - -## Prerequisites - -- Create a [DHL Developer](https://developer.dhl.com/user/register) account. - -## Using Access Token - -1. Navigate to the apps page of the [DHL Developer](https://developer.dhl.com/user/apps) portal. -2. Click the ***+ Create App*** button. -3. Enter a descriptive name in the ***App name*** field. -4. In the ***Select APIs*** section, search for `Shipment Tracking - Unified` in the ***API's name*** field. -5. Below ***Add API to app***, click the ***Plus (+)*** button next to the entry for `Shipment Tracking - Unified`. -6. Click on the ***Add app*** button. -7. Back on the apps page, click on your newly created app. -8. Click the ***Show key*** link to reveal your access token. Use the token with your DHL credentials in n8n. diff --git a/docs/integrations/builtin/credentials/discord.md b/docs/integrations/builtin/credentials/discord.md deleted file mode 100644 index 82e0cdac9..000000000 --- a/docs/integrations/builtin/credentials/discord.md +++ /dev/null @@ -1,30 +0,0 @@ -# Discord -You can follow these instructions to create a webhook in Discord to use with the following nodes. - -- [Discord](/integrations/builtin/app-nodes/n8n-nodes-base.discord/) - - -## Prerequisites - -Create a [Discord](https://www.discord.com/) account. - -## Creating a webhook in Discord - -1. To create a webhook in Discord that sends content to your channel, go to the settings of your channel. -2. Select 'Integrations' from the sidebar. -3. Click on the ***Create Webhook*** button. -4. Name your bot, and click on the ***Copy Webhook URL*** button to copy the webhook URL. -5. Back in n8n, use the copied webhook URL in your Discord node. - -![How to create a webhook in Discord](/_images/integrations/builtin/credentials/discord/create-webhook.gif) - - diff --git a/docs/integrations/builtin/credentials/discourse.md b/docs/integrations/builtin/credentials/discourse.md deleted file mode 100644 index a7f69dbbc..000000000 --- a/docs/integrations/builtin/credentials/discourse.md +++ /dev/null @@ -1,35 +0,0 @@ -# Discourse - -You can use these credentials to authenticate the following nodes with Discourse. - -- [Discourse](/integrations/builtin/app-nodes/n8n-nodes-base.discourse/) - - -## Prerequisites - - - Host an instance of [Discourse](https://discourse.org/) - - Create an account on your hosted instance and make sure that you are an admin - -## Using API Key - -1. Open your Discourse dashboard. -2. Click on the ***API*** tab. -3. Click on the ***+ New API Key*** button. -4. Enter a description in the ***Description*** field. -5. Based on your use-case, do one of the following: - - If you want to create the API key for a single user, select 'Single User' from the ***User Level*** dropdown list. Enter the username in the ***User*** field and select the user from the dropdown list. - - If you want to create the API key for all your users, select 'All Users' from the ***User Level*** dropdown list. -6. If you want to select all the scopes, check the ***Global Key (allowed all actions)*** checkbox. Otherwise, select scopes individually under the ***Scopes*** section. -7. Click on the ***Save*** button. -8. Copy the displayed API key. -9. Enter the name for your credentials in the ***Credentials Name*** field in the 'Discourse API' credentials in n8n. -10. Enter the URL of your Discourse instance in the ***URL*** field in the 'Discourse API' credentials in n8n. For example, `https://community.n8n.io`. -11. Paste the API key in the ***API Key*** field in the 'Discourse API' credentials in n8n. -12. Enter your Discourse username in the ***Username*** field in the 'Discourse API' credentials in n8n. -13. Click the ***Create*** button to create your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/disqus.md b/docs/integrations/builtin/credentials/disqus.md deleted file mode 100644 index b28f2a807..000000000 --- a/docs/integrations/builtin/credentials/disqus.md +++ /dev/null @@ -1,17 +0,0 @@ -# Disqus - -You can use these credentials to authenticate the following nodes with Disqus. - -- [Disqus](/integrations/builtin/app-nodes/n8n-nodes-base.disqus/) - -## Prerequisites - -Create a [Disqus](https://www.disqus.com/) account. - -## Using Access Token - -1. Access the [Disqus Application Registration Page](https://disqus.com/api/applications/register/). -2. Fill out the application information and click on ***Register my application***. -3. Click on ***Details*** at the top and use the provided 'API Key' with your Disqus node credentials in n8n. - -![Getting Disqus credentials](/_images/integrations/builtin/credentials/disqus/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/drift.md b/docs/integrations/builtin/credentials/drift.md deleted file mode 100644 index d4f286a31..000000000 --- a/docs/integrations/builtin/credentials/drift.md +++ /dev/null @@ -1,38 +0,0 @@ -# Drift - -You can use these credentials to authenticate the following nodes with Drift. - -- [Drift](/integrations/builtin/app-nodes/n8n-nodes-base.drift/) - -## Prerequisites - -Create a [Drift](https://www.drift.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Drift account to n8n. - - -1. Access your [Drift apps](https://dev.drift.com/apps) page. -2. Click on the ***Build Your App*** button. You can also select an existing app if you already have one. -3. Enter a name in the ***App name*** field. -4. Click on 'Oauth & Scopes' in the sidebar. -5. Copy your OAuth Callback URL from the 'Create New Credentials' screen in n8n, paste in the ***Add Redirect URL*** field, and click on the ***Add*** button. -6. Click on 'App Credentials' in the sidebar. -7. Use the ***Client ID*** and ***Secret ID*** with your Drift OAuth2 API node credentials in n8n. -8. Click on the circle button in the OAuth section to connect your Drift account to n8n. -9. Click the ***Save*** button to save your credentials. - -![Getting Drift OAuth credentials](/_images/integrations/builtin/credentials/drift/using-oauth.gif) - - -## Using Access Token - -1. Access [your Drift apps](https://dev.drift.com/apps). -2. Select your App (or create a new one). -3. Click on "Manage". -4. Click on "Installing to Drift". -5. Use token with your Drift Node credentials in n8n. - -![Getting Drift credentials](/_images/integrations/builtin/credentials/drift/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/dropbox.md b/docs/integrations/builtin/credentials/dropbox.md deleted file mode 100644 index 500053780..000000000 --- a/docs/integrations/builtin/credentials/dropbox.md +++ /dev/null @@ -1,47 +0,0 @@ -# Dropbox - -You can use these credentials to authenticate the following nodes with Dropbox. - -- [Dropbox](/integrations/builtin/app-nodes/n8n-nodes-base.dropbox/) - -## Prerequisites - -Create a [Dropbox](https://www.dropbox.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Dropbox account to n8n. - - -1. Access the [Dropbox app creation](https://www.dropbox.com/developers/apps/create) page. -2. Select 'Scoped access' under the ***Choose an API*** section. -3. Select an access type under the ***Choose the type of access you need***. You can read more about the access type [here](https://www.dropbox.com/developers/reference/developer-guide). -4. In the ***Name your app*** section, enter a name for your app. -5. Click on the ***Create app*** button. -6. Click on the ***Permissions*** tab and give all the permissions under the ***Files and folders*** section. -7. Click on the ***Submit*** button. -8. Click on the ***Settings*** tab. -9. Copy your OAuth Callback URL from the 'Create New Credentials' screen in n8n and paste in the ***Redirect URIs*** field under the ***OAuth 2*** section. -10. Click on the ***Add*** button. -11. Enter the provided ***App key*** and the ***App secret*** in the ***Client ID*** and ***Client Secret*** field, respectively, in your Dropbox OAuth2 API credentials in n8n. -12. Click on the circle button in the OAuth section to connect your Dropbox account to n8n. -13. Click on the ***Save*** button to save your credentials. - -![Getting Dropbox credentials](/_images/integrations/builtin/credentials/dropbox/using-oauth.gif) - -## Using Access Token - -1. Access the [Dropbox app creation](https://www.dropbox.com/developers/apps/create) page. -2. Select 'Scoped access' under the ***Choose an API*** section. -3. Select an access type under the ***Choose the type of access you need***. You can read more about the access type [here](https://www.dropbox.com/developers/reference/developer-guide). -4. In the ***Name your app*** section, enter a name for your app. -5. Click on the ***Create app*** button. -6. Click on the ***Permissions*** tab and give all the permissions under the ***Files and folders*** section. -7. Click on the ***Submit*** button. -8. Click on the ***Settings*** tab. -9. Scroll down to the ***OAuth 2*** section and select 'No expiration' from the ***Access token expiration*** dropdown list. -10. Click on the ***Generate*** button. -11. Use the displayed ***Generated access token*** with your Dropbox credentials in n8n. - -![Getting Dropbox credentials](/_images/integrations/builtin/credentials/dropbox/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/dropcontact.md b/docs/integrations/builtin/credentials/dropcontact.md deleted file mode 100644 index ff81dd715..000000000 --- a/docs/integrations/builtin/credentials/dropcontact.md +++ /dev/null @@ -1,19 +0,0 @@ -# Dropcontact - -You can use these credentials to authenticate the following nodes with Dropcontact. - -- [Dropcontact](/integrations/builtin/app-nodes/n8n-nodes-base.dropcontact/) - -## Prerequisites - -Create an account on a [Dropcontact](https://www.dropcontact.com/) app. - -## Using API Key - -1. Open your Dropcontact [dashboard](https://app.dropcontact.io/app/). -2. Select ***API*** from the left sidebar. -3. Click on the ***Copy*** button to copy the API key. -4. Paste the API key in the ***API Key*** field in the 'Credential for Dropcontact API' fields in n8n. -5. Click on the ***Save*** button to create your credentials. - -![Getting Dropcontact API credentials](/_images/integrations/builtin/credentials/dropcontact/apikeydropcontact.png) diff --git a/docs/integrations/builtin/credentials/egoi.md b/docs/integrations/builtin/credentials/egoi.md deleted file mode 100644 index fc21fc045..000000000 --- a/docs/integrations/builtin/credentials/egoi.md +++ /dev/null @@ -1,17 +0,0 @@ -# E-goi - -You can use these credentials to authenticate the following nodes with E-goi. - -- [E-goi](/integrations/builtin/app-nodes/n8n-nodes-base.egoi/) - -## Prerequisites - -Create an [E-goi](https://www.e-goi.com/) account. - -## Using API Key - -1. Access your E-goi dashboard. -2. Click on your name on the top right corner and select 'Integrations'. -3. Copy the ***API key*** that is displayed and use it with your E-goi node credentials in n8n. - -![Getting E-goi API credentials](/_images/integrations/builtin/credentials/egoi/using-api.gif) diff --git a/docs/integrations/builtin/credentials/elasticsearch.md b/docs/integrations/builtin/credentials/elasticsearch.md deleted file mode 100644 index c4b08fde5..000000000 --- a/docs/integrations/builtin/credentials/elasticsearch.md +++ /dev/null @@ -1,26 +0,0 @@ -# Elasticsearch - -You can use these credentials to authenticate the following nodes: - -- [Elasticsearch](/integrations/builtin/app-nodes/n8n-nodes-base.elasticsearch/) - -## Prerequisites - -- Create an [Elasticsearch](https://www.elastic.co/) account. -- [Deploy](https://www.elastic.co/guide/en/cloud/current/ec-create-deployment.html) an application. - -## Using Basic Auth - -**From Elasticsearch**: - -1. Navigate to your ***Dashboard*** > ***Deployments*** section and open the dashboard for the desired deployment. -2. From the ***Applications*** section, copy the endpoint of the Elasticsearch application. - -**From n8n**: - -1. Enter a descriptive ***Credentials Name***. -2. In the ***Credential Data*** section, enter your: - * Username - * Password - * Base URL: The Elasticsearch application endpoint obtained above. -3. Click ***Create*** to save your credentials. diff --git a/docs/integrations/builtin/credentials/elasticsecurity.md b/docs/integrations/builtin/credentials/elasticsecurity.md deleted file mode 100644 index 93c21f211..000000000 --- a/docs/integrations/builtin/credentials/elasticsecurity.md +++ /dev/null @@ -1,25 +0,0 @@ -# Elastic Security - -You can use these credentials to authenticate the following nodes: - -- [Elastic Security](/integrations/builtin/app-nodes/n8n-nodes-base.elasticSecurity/) - -## Prerequisites - -- Create an [Elastic Security](https://www.elastic.co/security) account. -- [Deploy](https://www.elastic.co/guide/en/cloud/current/ec-create-deployment.html) an application. - -## Using Basic Auth - -**From Elastic Security**: - -1. Navigate to your ***Dashboard*** > ***Deployments*** section and open the dashboard for the desired deployment. -2. From the ***Applications*** section, copy the endpoint of your application. - -**From n8n**: - -1. In the ***Credential Data*** section, enter your: - * Username - * Password - * Base URL: The application endpoint obtained above. -2. Click ***Save*** to save your credentials. diff --git a/docs/integrations/builtin/credentials/emelia.md b/docs/integrations/builtin/credentials/emelia.md deleted file mode 100644 index 836058ecc..000000000 --- a/docs/integrations/builtin/credentials/emelia.md +++ /dev/null @@ -1,26 +0,0 @@ -# Emelia - -You can use these credentials to authenticate the following nodes with Emelia. - -- [Emelia](/integrations/builtin/app-nodes/n8n-nodes-base.emelia/) -- [Emelia Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.emeliaTrigger/) - -## Prerequisites - -Create a [Emelia](https://emelia.io) account. - -## Using API Key - -1. Open the Emelia [dashboard](https://app.emelia.io/) page. -2. Click on the avatar on the top-right and select 'API Keys'. -3. Click on the ***Generate new API key*** button. -4. Click on the menu icon and select 'Copy API Key' from the dropdown list. -5. Enter a name for your credentials in the ***Credentials Name*** field in the 'Emelia API' credentials in n8n. -6. Paste the API key in the ***API Key*** field in the 'Emelia API' credentials in n8n. -7. Click the ***Create*** button to create your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/erpnext.md b/docs/integrations/builtin/credentials/erpnext.md deleted file mode 100644 index 91693aabf..000000000 --- a/docs/integrations/builtin/credentials/erpnext.md +++ /dev/null @@ -1,36 +0,0 @@ -# ERPNext - -You can use these credentials to authenticate the following nodes with Emelia. - -- [ERPNext](/integrations/builtin/app-nodes/n8n-nodes-base.erpNext/) - -## Prerequisites - -- Create a [ERPNext](https://erpnext.com) account. - -## Using API Key - -1. Open your ERPNext dashboard page. -2. Click on ***Settings*** on the top and select 'My Settings'. -3. Scroll down to the bottom of the page and click on ***API Access***. -4. Click on the ***Generate Keys*** button. -5. Copy the displayed API Secret. -6. Enter a name for your credentials in the ***Credentials Name*** field in the 'ERPNext API' credentials in n8n. -7. Paste the API Secret in the ***API Secret*** field in the 'ERPNext API' credentials in n8n. -8. Copy the API Key from ERPNext. -**Note:** You might have to refresh the ERPNext window to view the API Key. -9. Paste the API Key in the ***API Key*** field in the 'ERPNext API' credentials in n8n. -10. Enter the subdomain of your ERPNext account in the ***Subdomain*** field in the 'ERPNext API' credentials in n8n. Refer to the [FAQs](#how-to-find-the-subdomain-of-an-erpnext-account) to learn how to get your subdomain. -11. Click on the ***Create*** button to create your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
- -## FAQs - -### How to find the subdomain of an ERPNext account? - -In the address bar of your browser, you can find the subdomain. The string between `https://` and `.erpnext.com` is your subdomain. For example, if the URL in the address bar is `https://n8n.erpnext.com`, the subdomain will be `n8n`. diff --git a/docs/integrations/builtin/credentials/eventbrite.md b/docs/integrations/builtin/credentials/eventbrite.md deleted file mode 100644 index fb69d1df8..000000000 --- a/docs/integrations/builtin/credentials/eventbrite.md +++ /dev/null @@ -1,38 +0,0 @@ -# Eventbrite - -You can use these credentials to authenticate the following nodes with Eventbrite. - -- [Eventbrite Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.eventbriteTrigger/) - -## Prerequisites - -Create a [Eventbrite](https://www.eventbrite.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Eventbrite account to n8n. - - -1. Log in to your Eventbrite account. -2. Click on the user icon in the top right. -3. Select Account Settings in the drop down menu. -4. Click on Developer links > API keys in the sidebar. -5. Click on the *Create API Key* button. -6. Copy the 'OAuth Callback URL' provided in the Eventbrite OAuth API credentials in n8n and paste it in the 'OAuth Redirect URI' field in the Eventbrite API creation page. -7. Fill out any other information that is necessary and click 'Create Key'. -8. Find your API key in the 'API Keys' page and click on 'Show API key, client secret and tokens'. -9. Click on 'Show API key, client secret and tokens' and use the 'API key' and the 'Client secret' with your Eventbrite OAuth API credentials in n8n. -10. Click on the circle button in the OAuth section to connect an Eventbrite account to n8n. -11. Click the *Save* button to save your credentials. - -![Getting Eventbrite OAuth credentials](/_images/integrations/builtin/credentials/eventbrite/using-oauth.gif) - -## Using Access Token - -1. Log in to your Eventbrite account. -2. Visit [your API keys page](https://www.eventbrite.com/platform/api-keys). -3. Copy your private token. -4. Use provided key with your Eventbrite node credentials in n8n. - -![Getting Eventbrite credentials](/_images/integrations/builtin/credentials/eventbrite/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/facebookapp.md b/docs/integrations/builtin/credentials/facebookapp.md deleted file mode 100644 index b079b73e0..000000000 --- a/docs/integrations/builtin/credentials/facebookapp.md +++ /dev/null @@ -1,27 +0,0 @@ -# Facebook App - -You can use these credentials to authenticate the following nodes with Facebook. - -- [Facebook Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.facebookTrigger/) - -**Note:** If you want to create credentials for the [Facebook Graph API](/integrations/builtin/app-nodes/n8n-nodes-base.facebookGraphAPI/) node, follow the instructions mentioned in the [Facebook Graph API](/integrations/builtin/credentials/facebookGraph/) credentials documentation. - -## Prerequisites - -Create a [Facebook](https://www.facebook.com/) account. - -## Using App Access Token - -1. Access the [Facebook for Developers portal](https://developers.facebook.com/). -2. Click on ***My Apps*** on the top right corner. -3. Access your app. Create an app if you don't already have one. -4. Add the ***Webhooks*** product from the ***Add a Product*** section on the dashboard. -5. Click on ***Settings*** in the left sidebar and select 'Basic'. -6. Click on the ***Show*** button and login with your Facebook account. -7. Copy the App Secret displayed on the page. -8. Access the [Facebook Graph API Explorer](https://developers.facebook.com/tools/explorer/). -9. Select your app from the ***Facebook App*** dropdown list on the right sidebar. -10. Select 'Get App Token' from the ***User or Page*** dropdown list on the right sidebar. -11. Use the app secret and the generated access token with your Facebook node credentials in n8n. - -![Getting Facebook App credentials](/_images/integrations/builtin/credentials/facebookapp/using-app-access-token.gif) diff --git a/docs/integrations/builtin/credentials/facebookgraph.md b/docs/integrations/builtin/credentials/facebookgraph.md deleted file mode 100644 index dc661ed25..000000000 --- a/docs/integrations/builtin/credentials/facebookgraph.md +++ /dev/null @@ -1,23 +0,0 @@ -# Facebook Graph API - -You can use these credentials to authenticate the following nodes with Facebook. - -- [Facebook Graph API](/integrations/builtin/app-nodes/n8n-nodes-base.facebookGraphAPI/) - -**Note:** If you want to create credentials for the [Facebook Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.facebookTrigger/) node, follow the instructions mentioned in the [Facebook App](/integrations/builtin/credentials/facebookApp/) credentials documentation. - -## Prerequisites - -Create a [Facebook](https://www.facebook.com/) account. - -## Using Access Token - -1. Access [Facebook for Developers portal](https://developers.facebook.com/). -2. Click on "My Apps". -3. Access your app. Create an app if you don't already have one. -4. Access the [Facebook Graph API Explorer](https://developers.facebook.com/tools/explorer/). -5. Select your app under the *Facebook App* dropdown list on the right sidebar. -6. Click on the 'Generate Access Token' button and login with your facebook account. -6. Use generated access token with your Facebook node credentials in n8n. - -![Getting Facebook credentials](/_images/integrations/builtin/credentials/facebookgraphapi/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/figma.md b/docs/integrations/builtin/credentials/figma.md deleted file mode 100644 index d4c10d7cb..000000000 --- a/docs/integrations/builtin/credentials/figma.md +++ /dev/null @@ -1,18 +0,0 @@ -# Figma - -You can use these credentials to authenticate the following nodes: - -- [Figma Trigger (Beta)](/integrations/builtin/trigger-nodes/n8n-nodes-base.figmaTrigger/) - -## Prerequisites - -Create a [Figma](https://www.figma.com/) account. - -## Using API Key - -1. Log in to [Figma](https://www.figma.com/). -2. Click on the avatar on the top-right and select **Settings**. -3. Scroll down to **Personal access tokens**, enter a name for your token in the input field and confirm by pressing Enter. -4. Click on **Copy this token**. -6. Paste the API key in the **Access Token** field of the **Figma API** credentials screen in n8n. -7. Click the **Save** button to save your credentials in n8n. diff --git a/docs/integrations/builtin/credentials/filemaker.md b/docs/integrations/builtin/credentials/filemaker.md deleted file mode 100644 index d9ab39cd4..000000000 --- a/docs/integrations/builtin/credentials/filemaker.md +++ /dev/null @@ -1,15 +0,0 @@ -# FileMaker - -You can use these credentials to authenticate the following nodes with FileMaker. - -- [FileMaker](/integrations/builtin/app-nodes/n8n-nodes-base.filemaker/) - -## Prerequisites - -Create an user account on a FileMaker server. - -## Using Database Connection - -1. Retrieve your FileMaker credentials and connection parameters. -2. Use the credentials and connection parameters with your FileMaker node credentials in n8n. -3. Click on the ***Save*** button to save your credentials. diff --git a/docs/integrations/builtin/credentials/flow.md b/docs/integrations/builtin/credentials/flow.md deleted file mode 100644 index e30e1af97..000000000 --- a/docs/integrations/builtin/credentials/flow.md +++ /dev/null @@ -1,21 +0,0 @@ -# Flow - -You can use these credentials to authenticate the following nodes with Flow. - -- [Flow](/integrations/builtin/app-nodes/n8n-nodes-base.flow/) -- [Flow Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.flowTrigger/) - -## Prerequisites - -Create a [Flow](https://www.getflow.com/) account. - -## Using Access Token - -1. Access your Flow dashboard. -2. Click on your Organisation icon in the top left. -3. Click on Account Preferences. -4. Click on the *Create a Personal Access Token* button. -5. As you generate your access token, you will also receive an organisation ID. -6. Use provided access token and organisation ID with your Flow node credentials in n8n. - -![Getting Flow credentials](/_images/integrations/builtin/credentials/flow/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/formiotrigger.md b/docs/integrations/builtin/credentials/formiotrigger.md deleted file mode 100644 index 694ad5ebd..000000000 --- a/docs/integrations/builtin/credentials/formiotrigger.md +++ /dev/null @@ -1,19 +0,0 @@ -# Form.io Trigger - -You can use these credentials to authenticate the following nodes: - -- [Form.io Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.formIoTrigger/) - -## Prerequisites - -Create a [Form.io](https://www.form.io/) account. - -## Using Basic auth - -After creating your Form.io account, from n8n: - -1. Enter a descriptive ***Credentials Name***. -2. Select whether your ***Environment*** is **Cloud-hosted** or **Self-hosted**. -3. Enter your Form.io account ***Email***. -4. Enter your Form.io account ***Password***. -5. Click **Create** to save your new credentials. diff --git a/docs/integrations/builtin/credentials/formstacktrigger.md b/docs/integrations/builtin/credentials/formstacktrigger.md deleted file mode 100644 index 9e4b7bdd8..000000000 --- a/docs/integrations/builtin/credentials/formstacktrigger.md +++ /dev/null @@ -1,53 +0,0 @@ -# Formstack Trigger - -You can use these credentials to authenticate the following nodes: - -- [Formstack Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.formstackTrigger/) - -## Prerequisites - -Create a [Formstack](https://www.formstack.com/) account. - -## Using Access token - -After creating your Formstack account: - -1. From the user menu select **API**. -2. Select **New Application**. -3. In the *Create Application* window enter the following: - * *Application Name*: Provide a descriptive name. - * *Redirect URI*: Enter the OAuth callback URL for your n8n instance in the format `http:///rest/oauth2-credential/callback`. For example `http://localhost:5678/rest/oauth2-credential/callback`. - * *Description*: Enter a brief description. - * *Platform*: Select **Website**. -4. Click **Create Application**. -5. Copy the *Access Token* for your new application. - -From n8n: - -6. Enter a descriptive ***Credentials Name***. -7. Enter your Formstack ***Access Token***. -8. Click **Create** to save your new credentials. - -## Using OAuth2 - -After creating your Formstack account: - -1. From the user menu select **API**. -2. Select **New Application**. -3. In the *Create Application* window enter the following: - * *Application Name*: Provide a descriptive name. - * *Redirect URI*: Enter the OAuth callback URL for your n8n instance in the format `http:///rest/oauth2-credential/callback`. For example `http://localhost:5678/rest/oauth2-credential/callback`. - * *Description*: Enter a brief description. - * *Platform*: Select **Website**. -4. Click **Create Application**. -5. Select your new application to view the *Application Details*. -6. Copy the *Client ID* and *Client Secret*. - -From n8n: - -7. Enter a descriptive ***Credentials Name***. -8. Enter your Formstack ***Client ID***. -9. Enter your Formstack ***Client Secret***. -10. Click the circle button to initiate the OAuth2 flow. -11. In the modal window select **Authorize**. -12. Click **Create** to save your new credentials. diff --git a/docs/integrations/builtin/credentials/freshdesk.md b/docs/integrations/builtin/credentials/freshdesk.md deleted file mode 100644 index 080c283f8..000000000 --- a/docs/integrations/builtin/credentials/freshdesk.md +++ /dev/null @@ -1,19 +0,0 @@ -# Freshdesk - -You can use these credentials to authenticate the following nodes with Freshdesk. - -- [Freshdesk](/integrations/builtin/app-nodes/n8n-nodes-base.freshdesk/) - -## Prerequisites - -Create a [Freshdesk](https://freshdesk.com/) account. - -## Using Access Token - -1. Access your Freshdesk dashboard. -2. Click on your Organisation icon in the top right. -3. Click on Profile Settings. -4. Find your API key on the right panel. -5. Use provided API key and your subdomain (i.e n8n) with your Freshdesk node credentials in n8n. - -![Getting Freshdesk credentials](/_images/integrations/builtin/credentials/freshdesk/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/freshservice.md b/docs/integrations/builtin/credentials/freshservice.md deleted file mode 100644 index fe2e23141..000000000 --- a/docs/integrations/builtin/credentials/freshservice.md +++ /dev/null @@ -1,25 +0,0 @@ -# Freshservice - -You can use these credentials to authenticate the following nodes: - -- [Freshservice](/integrations/builtin/app-nodes/n8n-nodes-base.freshservice/) - -## Prerequisites - -Create a [Freshservice](https://freshservice.com/) account. - -## Using API Key - -From Freshservice: - -1. Access your Freshservice dashboard. -2. Click on your User icon in the top right and select **Settings**. -3. Click on **API Settings**. -4. Copy your API key. - -From n8n: - -5. Enter a descriptive ***Credentials Name***. -6. Under ***Credential Data***, enter the API Key obtained above in the corresponding field. -7. In the ***Domain*** field enter the subdomain of your Freshservice account. This is part of the URL, for example `https://.freshservice.com/`. -8. Click **Save** to create your new credentials. diff --git a/docs/integrations/builtin/credentials/freshworkscrm.md b/docs/integrations/builtin/credentials/freshworkscrm.md deleted file mode 100644 index 3d4e44d28..000000000 --- a/docs/integrations/builtin/credentials/freshworkscrm.md +++ /dev/null @@ -1,25 +0,0 @@ -# Freshworks CRM - -You can use these credentials to authenticate the following nodes: - -- [Freshworks CRM](/integrations/builtin/app-nodes/n8n-nodes-base.freshworksCrm/) - -## Prerequisites - -Create a [Freshworks CRM](https://www.freshworks.com/freshsales-crm/) account. - -## Using API Key - -From Freshworks CRM: - -1. Access your Freshworks CRM dashboard. -2. Click on your User icon in the top right and select **Settings**. -3. Click on **API Settings**. -4. Copy your API key. - -From n8n: - -5. Enter a descriptive ***Credentials Name***. -6. Under ***Credential Data***, enter the API Key obtained above in the corresponding field. -7. In the ***Domain*** field enter the subdomain of your Freshworks CRM account. This is part of the URL, for example `https://.myfreshworks.com/`. -8. Click **Save** to create your new credentials. diff --git a/docs/integrations/builtin/credentials/ftp.md b/docs/integrations/builtin/credentials/ftp.md deleted file mode 100644 index 82bfa605a..000000000 --- a/docs/integrations/builtin/credentials/ftp.md +++ /dev/null @@ -1,15 +0,0 @@ -# FTP - -You can use these credentials to authenticate the following nodes with FTP. - -- [FTP](/integrations/builtin/core-nodes/n8n-nodes-base.ftp/) - -## Prerequisites - -Create an account on an FTP server. - -## Using FTP/SFTP - -1. Retrieve your login credentials, FTP/SFTP host, and port parameters. -2. Use the login credentials, FTP/SFTP host, and port parameters with your FTP node credentials in n8n. -3. Click on the ***Save*** button to save your credentials. diff --git a/docs/integrations/builtin/credentials/getresponse.md b/docs/integrations/builtin/credentials/getresponse.md deleted file mode 100644 index 7d7afdc04..000000000 --- a/docs/integrations/builtin/credentials/getresponse.md +++ /dev/null @@ -1,77 +0,0 @@ -# GetResponse - -You can use these credentials to authenticate the following nodes with GetResponse. - -- [GetResponse](/integrations/builtin/app-nodes/n8n-nodes-base.getResponse/) -- [GetResponse Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.getResponseTrigger/) - -## Prerequisites - -Create a [GetResponse](https://www.getresponse.com/) account. - -## Using OAuth - -!!! note "Callback URL with GetResponse" - **Note:** The Redirect URL should be a URL in your domain. For example, `https://mytemplatemaker.example.com/gr_callback`. GetResponse doesn't accept the localhost callback URL. Refer to the [FAQs](#_1-how-to-configure-the-oauth-credentials-for-the-local-environment) to learn to configure the credentials for the local environment. - - -1. Open your [GetResponse dashboard](https://app.getresponse.com/dashboard). -2. Click on ***Menu*** and select 'Integrations and API'. -3. Click on the ***Custom apps*** tab. -4. Click on the ***Register your app*** button. -5. Enter all the necessary information. -6. Copy your OAuth Callback URL from the 'Create New Credentials' screen in n8n and paste it in the ***Redirect URL*** field. -7. Click on the ***Add*** button. -8. Click on the app you created to get the ***Client ID*** and the ***Client Secret***. -9. Copy the displayed ***Client ID***. -10. Enter a name for your credentials in the ***Credentials Name*** field in the 'GetResponse OAuth2 API' credentials in n8n. -11. Paste the Client ID in the ***Client ID*** field in the 'GetResponse OAuth2 API' credentials in n8n. -12. Copy the ***Client secret key*** from GetResponse. -13. Paste it in the ***Client Secret*** field in the 'GetResponse OAuth2 API' credentials in n8n. -14. Click on the circle button in the OAuth section to connect a GetResponse account to n8n. -15. Click on the ***Save*** button to save your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
- -## Using API Key - -1. Open your [GetResponse dashboard](https://app.getresponse.com/dashboard). -2. Click on ***Menu*** and select 'Integrations and API'. -3. Click on the ***API*** tab. -4. Click on the ***Generate API key*** button. -5. Enter a name for your key. -6. Click on the ***Generate*** button. -7. Copy the displayed ***API key***. -8. Enter a name for your credentials in the ***Credentials Name*** field in the 'GetResponse API' credentials in n8n. -9. Paste the API key in the ***API Key*** field in the 'GetResponse API' credentials in n8n. -10. Click the ***Create*** button to create your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
- -## FAQs - -### How to configure the OAuth credentials for the local environment? -GetResponse doesn't accept the localhost callback URL. However, you can follow the steps mentioned below to configure the OAuth credentials for the local environment: -1. We will use [ngrok](https://ngrok.com/) to expose the local server running on port `5678` to the internet. In your terminal, run the following command: -```sh -ngrok http 5678 -``` -2. Run the following command in a new terminal. Replace `` with the URL that you get from the previous step. -```sh -export WEBHOOK_URL= -``` -3. Start your n8n instance. -4. Follow the instructions mentioned in the [Using OAuth](#using-oauth) section to configure your credentials. - -## Further Reference - -- [OAuth 2.0 - Authorization Code](https://apidocs.getresponse.com/v3/case-study/oauth2-authorization-code) -- [Authentication - API key](https://apireference.getresponse.com/#section/Authentication) diff --git a/docs/integrations/builtin/credentials/ghost.md b/docs/integrations/builtin/credentials/ghost.md deleted file mode 100644 index 8ad283e37..000000000 --- a/docs/integrations/builtin/credentials/ghost.md +++ /dev/null @@ -1,29 +0,0 @@ -# Ghost - -You can use these credentials to authenticate the following nodes with Ghost. - -- [Ghost](/integrations/builtin/app-nodes/n8n-nodes-base.ghost/) - -## Prerequisites - -Create a [Ghost](https://ghost.org/) account. - -## Using Admin API - -1. Access your Ghost Admin dashboard. -2. Click on ***Integrations*** in the left sidebar. -3. Click on ***+ Add custom integration*** under the ***CUSTOM INTEGRATIONS*** section. -4. Enter a name for the integration in the ***Name*** field. -5. Click on the ***Create*** button. -6. Use this ***URL*** and ***Admin API Key*** with your Ghost node credentials in n8n. - -## Using Content API - -1. Access your Ghost Admin dashboard. -2. Click on ***Integrations*** in the left sidebar. -3. Click on ***+ Add custom integration*** under the ***CUSTOM INTEGRATIONS*** section. -4. Enter a name for the integration in the ***Name*** field. -5. Click on the ***Create*** button. -6. Use this ***URL*** and ***Content API Key*** with your Ghost node credentials in n8n. - -![Getting Ghost credentials](/_images/integrations/builtin/credentials/ghost/using-api.gif) diff --git a/docs/integrations/builtin/credentials/git.md b/docs/integrations/builtin/credentials/git.md deleted file mode 100644 index f0864e672..000000000 --- a/docs/integrations/builtin/credentials/git.md +++ /dev/null @@ -1,22 +0,0 @@ -# Git - -You can use these credentials to authenticate the following nodes with Git. - -- [Git](/integrations/builtin/core-nodes/n8n-nodes-base.git/) - -## Prerequisites - -Create an account on [GitHub](https://github.com), [GitLab](https://about.gitlab.com/), or similar platforms. - -## Using Username and Password - -1. Enter a name for your credentials in the ***Credentials Name*** field in the 'Git' credentials in n8n. -2. Enter your GitHub, GitLab (or similar platforms) username in the ***Username*** field in the 'Git' credentials in n8n. -3. Enter your GitHub, GitLab (or similar platforms) password in the ***Password*** field in the 'Git' credentials in n8n. -4. Click the ***Create*** button to create your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/github.md b/docs/integrations/builtin/credentials/github.md deleted file mode 100644 index 6f6d359de..000000000 --- a/docs/integrations/builtin/credentials/github.md +++ /dev/null @@ -1,70 +0,0 @@ -# GitHub - -You can use these credentials to authenticate the following nodes with GitHub. - -- [GitHub](/integrations/builtin/app-nodes/n8n-nodes-base.github/) -- [GitHub Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.githubTrigger/) - - -## Prerequisites - -Create a [GitHub](https://github.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your GitHub account to n8n. - - -1. Open your GitHub [dashboard](https://github.com). -2. Click on your user icon in the top right. -3. Click on ***Settings***. -4. Click on ***Developer settings***. -5. Select ***OAuth Apps***. -6. Click on the ***Register a new application*** button. -7. Enter the ***Application name*** and ***Homepage URL***. -8. Copy the ***OAuth Callback URL*** from n8n and paste it in the ***Authorization callback URL*** field. -9. Click on the ***Register application*** button. -10. Copy the displayed 'Client ID'. -11. Enter the name for your credentials in the ***Credentials Name*** field in the 'Github OAuth2 API' credentials in n8n. -12. Paste the client ID in the ***Client ID*** field in the 'Github OAuth2 API' credentials in n8n. -13. On your application page, click on the ***Generate a new client secret*** button. -14. Copy the displayed 'Client Secret'. -15. Paste the client secret in the ***Client Secret*** field in the 'Github OAuth2 API' credentials in n8n. -16. Click on the circle button in the OAuth section to connect a GitHub account to n8n. -17. Click the ***Save*** button to save your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
- -The following video demonstrates the steps to authenticate the GitHub node on [n8n Cloud](https://n8n.io/cloud/){:target=_blank .external-link}. - -
- -
- -## Using Access Token - -1. Open your GitHub [dashboard](https://github.com). -2. Click on your user icon in the top right. -3. Click on ***Settings***. -4. Click on ***Developer settings***. -5. Select ***Personal access tokens***. -6. Click on ***Generate new token***. -7. Enter a note in the ***Note*** field. -8. Select the relevant scopes from the ***Select scopes*** section. -9. Scroll down to the bottom and click on the ***Generate token*** button. -10. Copy the displayed 'Personal access token'. -11. Enter the name for your credentials in the ***Credentials Name*** field in the 'Github API' credentials in n8n. -12. Enter your GitHub username in the ***User*** field in the 'Github API' credentials in n8n. -13. Paste the access token in the ***Access Token*** field in the 'Github API' credentials in n8n. -14. Click the ***Create*** button to save your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/gitlab.md b/docs/integrations/builtin/credentials/gitlab.md deleted file mode 100644 index 87a10fe4c..000000000 --- a/docs/integrations/builtin/credentials/gitlab.md +++ /dev/null @@ -1,44 +0,0 @@ -# GitLab - -You can use these credentials to authenticate the following nodes with GitLab. - -- [GitLab](/integrations/builtin/app-nodes/n8n-nodes-base.gitlab/) -- [GitLab Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.gitlabTrigger/) - -## Prerequisites - -Create a [GitLab](https://gitlab.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your GitLab account to n8n. - - -1. Access your GitLab dashboard. -2. Click on your user icon in the top right. -3. Click on 'Settings'. -4. Click on 'Applications' in the sidebar. -5. Enter a name in the ***Name*** field. -6. Copy the 'OAuth Callback URL' provided in the 'Gitlab OAuth2 API' credentials in n8n and paste it in the ***Redirect URI*** field in the GitLab app creation page. -7. Select any scopes you plan to use and then click on ***Save application***. -8. Use the ***Application ID*** and ***Secret*** with your GitLab OAuth2 API credentials in n8n. -9. Click on the circle button in the OAuth section to connect a GitLab account to n8n. -10. Click on the ***Save*** button to save your credentials. - -![Getting GitLab OAuth credentials](/_images/integrations/builtin/credentials/gitlab/using-oauth.gif) - - -## Using Access Token - -1. Access your GitLab dashboard. -2. Click on your user icon in the top right. -3. Click on 'Settings'. -4. Click on 'Access Tokens' in the sidebar. -5. Enter a name in the ***Name*** field. -6. Fill out the required information to receive the access token. -7. Select any scopes you plan to use and then click on ***Create personal access token***. -8. Use the generated access token with your GitLab node credentials in n8n. -9. Click on the ***Save*** button to save your credentials. - -![Getting GitLab access token](/_images/integrations/builtin/credentials/gitlab/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/google/index.md b/docs/integrations/builtin/credentials/google/index.md deleted file mode 100644 index 58f8f6949..000000000 --- a/docs/integrations/builtin/credentials/google/index.md +++ /dev/null @@ -1,53 +0,0 @@ -# Google - -This section contains: - -* [OAuth2 single service](/integrations/builtin/credentials/google/oauth-single-service/): create an OAuth2 credential for a specific service node, such as the Gmail node. -* [OAuth2 generic](/integrations/builtin/credentials/google/oauth-generic/): create an OAuth2 credential for use with [custom operations](/integrations/custom-operations/). -* [Service Account](/integrations/builtin/credentials/google/service-account/): create a Service Account credential. - -## OAuth2 and Service Account - -There are two authentication methods available for Google services nodes, [OAuth2](https://developers.google.com/identity/protocols/oauth2){:target=_blank .external-link} and [Service Account](https://cloud.google.com/iam/docs/understanding-service-accounts){:target=_blank .external-link}. n8n recommends using OAuth. It's more widely available, and easier to set up. Refer to the [Google documentation: Understanding service accounts](https://cloud.google.com/iam/docs/understanding-service-accounts){:target=_blank .external-link} for guidance on when you need service account. - -## Compatible nodes - -Once configured, you can use your credentials to authenticate the following nodes. Most nodes are compatible with OAuth2 authentication. Support for Service Account authentication is limited. - -??? Details "Compatibility" - | Node | OAuth | Service Account | - | :--- | :---: | :-------------: | - | [G Suite Admin](/integrations/builtin/app-nodes/n8n-nodes-base.gSuiteAdmin/) | :white_check_mark: | :x: | - | [Google Ads](/integrations/builtin/app-nodes/n8n-nodes-base.googleAds/) | :white_check_mark: | :x: | - | [Gmail](/integrations/builtin/app-nodes/n8n-nodes-base.gmail/) | :white_check_mark: | :white_check_mark: | - | [Google Analytics](/integrations/builtin/app-nodes/n8n-nodes-base.googleAnalytics/) | :white_check_mark: | :x: | - | [Google BigQuery](/integrations/builtin/app-nodes/n8n-nodes-base.googleBigQuery/) | :white_check_mark: | :x: | - | [Google Books](/integrations/builtin/app-nodes/n8n-nodes-base.googleBooks/) | :white_check_mark: | :white_check_mark: | - | [Google Calendar](/integrations/builtin/app-nodes/n8n-nodes-base.googleCalendar/) | :white_check_mark: | :x: | - | [Google Chat](/integrations/builtin/app-nodes/n8n-nodes-base.googleChat/) | :x: | :white_check_mark: | - | [Google Cloud Storage](/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudStorage/) | :white_check_mark: | :x: | - | [Google Contacts](/integrations/builtin/app-nodes/n8n-nodes-base.googleContacts/) | :white_check_mark: | :x: | - | [Google Cloud Firestore](/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudFirestore/) | :white_check_mark: | :x: | - | [Google Cloud Natural Language](/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudNaturalLanguage/) | :white_check_mark: | :x: | - | [Google Cloud Realtime Database](/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudRealtimeDatabase/) | :white_check_mark: | :x: | - | [Google Docs](/integrations/builtin/app-nodes/n8n-nodes-base.googleDocs/) | :white_check_mark: | :white_check_mark: | - | [Google Drive](/integrations/builtin/app-nodes/n8n-nodes-base.googleDrive/) | :white_check_mark: | :white_check_mark: | - | [Google Drive Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.googleDriveTrigger/) | :white_check_mark: | :white_check_mark: | - | [Google Perspective](/integrations/builtin/app-nodes/n8n-nodes-base.googlePerspective/) | :white_check_mark: | :x: | - | [Google Sheets](/integrations/builtin/app-nodes/n8n-nodes-base.googleSheets/) | :white_check_mark: | :white_check_mark: | - | [Google Slides](/integrations/builtin/app-nodes/n8n-nodes-base.googleSlides/) | :white_check_mark: | :white_check_mark: | - | [Google Tasks](/integrations/builtin/app-nodes/n8n-nodes-base.googleTasks/) | :white_check_mark: | :x: | - | [Google Translate](/integrations/builtin/app-nodes/n8n-nodes-base.googleTranslate/) | :white_check_mark: | :white_check_mark: | - | [YouTube](/integrations/builtin/app-nodes/n8n-nodes-base.youTube/) | :white_check_mark: | :x: | - -!!! note "Note for n8n Cloud users" - For the following nodes, you can authenticate by entering the **Credentials Name** and selecting **Sign in with Google** in the OAuth section to connect your Google account to n8n: - - * [Google Calendar](/integrations/builtin/app-nodes/n8n-nodes-base.googleCalendar/) - * [Google Contacts](/integrations/builtin/app-nodes/n8n-nodes-base.googleContacts/) - * [Google Sheets](/integrations/builtin/app-nodes/n8n-nodes-base.googleSheets/) - * [Google Tasks](/integrations/builtin/app-nodes/n8n-nodes-base.googleTasks/) - - - - diff --git a/docs/integrations/builtin/credentials/google/oauth-generic.md b/docs/integrations/builtin/credentials/google/oauth-generic.md deleted file mode 100644 index 214c2d32c..000000000 --- a/docs/integrations/builtin/credentials/google/oauth-generic.md +++ /dev/null @@ -1,97 +0,0 @@ -# Google: OAuth2 generic - -This document contains instructions for creating a generic OAuth2 Google credential for use with [custom operations](/integrations/custom-operations/). - -## Prerequisites - -* [Google Cloud](https://cloud.google.com/){:targe=_blank .external-link} account -* [Google Cloud Platform project](https://developers.google.com/workspace/marketplace/create-gcp-project){:targe=_blank .external-link} -* If using Google Perspective: [Request API Access](https://developers.perspectiveapi.com/s/docs-get-started){:targe=_blank .external-link} -* If using Google Ads: [Developer Token](https://developers.google.com/google-ads/api/docs/first-call/dev-token){:targe=_blank .external-link} - -## Set up OAuth - -### Create a new credential in n8n - -1. Follow the steps to [Create a credential](/credentials/add-edit-credentials/). If you create a credential by selecting **Create new** in the credentials dropdown in a node, n8n automatically creates the correct credential type for that node. If you select **Credentials > New**, you must browse for the credential type. To create a credential for a [custom API call](/integrations/custom-operations/), select **Google OAuth2 API**. This allows you to create a generic credential, then set its scopes. -2. Note the **OAuth Redirect URL** from the node credential modal. You'll need this in the next section. - - ??? Details "View screenshot" - ![OAuth Callback URL](/_images/integrations/builtin/credentials/google/oauth_callback.png) - -3. You must provide the scopes for this credential. Refer to [Scopes](#scopes) for more information. - -### Set up OAuth in Google Cloud - -1. Go to [Google Cloud Console](https://console.cloud.google.com/apis/credentials){:target=_blank .external-link} and make sure you're in the project you want to use. - - ??? Details "View screenshot" - ![Google project dropdown](/_images/integrations/builtin/credentials/google/check-google-project.png) - -2. Select **+ CREATE CREDENTIALS > OAuth client ID**. If you're creating OAuth credentials for the first time, you must [configure the consent screen](https://support.google.com/cloud/answer/10311615?hl=en&ref_topic=3473162){:target=_blank .external-link}. - - ??? Details "View screenshot" - ![Create credentials](/_images/integrations/builtin/credentials/google/create-credentials.png) - -3. In the **Application type** dropdown, select **Web application**. Google automatically generates a name. -4. Under **Authorizes redirect URIs**, select **+ ADD URI**. Paste in the OAuth redirect URL from the previous step. - - ??? Details "View screenshot" - ![Web application](/_images/integrations/builtin/credentials/google/application-web-application.png) - -5. Select **CREATE**. -6. Enable each Google service API that you want to use: - --8<-- "_snippets/integrations/builtin/credentials/google/enable-apis.md" - -### Create and test your connection - -In n8n: - -1. Enter your new **Client ID** and **Client Secret** from Google Cloud Console in the credentials modal. -2. Select **Sign in with Google** to complete your Google authentication. -3. **Save** your new credentials. - -The following video demonstrates the steps described above: - -
- -
- -## Scopes - -Many Google services have multiple possible access scopes. A scope limits what a user can do. Refer to [OAuth 2.0 Scopes for Google APIs](https://developers.google.com/identity/protocols/oauth2/scopes){:target=_blank .external-link} for a list of scopes for all services. - -n8n doesn't support all scopes. When creating a generic Google OAuth2 API credential, you can enter scopes from the list. If you enter a scope that n8n doesn't already support, it won't work. - -??? Details "Supported scopes" - | Service | Available scopes | - | ------- | ---------------- | - | Gmail | https://www.googleapis.com/auth/gmail.labels
https://www.googleapis.com/auth/gmail.addons.current.action.compose
https://www.googleapis.com/auth/gmail.addons.current.message.action
https://mail.google.com/
https://www.googleapis.com/auth/gmail.modify
https://www.googleapis.com/auth/gmail.compose | - | Google Ads | https://www.googleapis.com/auth/adwords | - | Google Analytics | https://www.googleapis.com/auth/analytics
https://www.googleapis.com/auth/analytics.readonly | - | Google Big Query | https://www.googleapis.com/auth/bigquery | - | Google Books | https://www.googleapis.com/auth/books | - | Google Calendar | https://www.googleapis.com/auth/calendar
https://www.googleapis.com/auth/calendar.events | - | Google Cloud Natural Language | https://www.googleapis.com/auth/cloud-language
https://www.googleapis.com/auth/cloud-platform | - | Google Cloud Storage | https://www.googleapis.com/auth/cloud-platform
https://www.googleapis.com/auth/cloud-platform.read-only
https://www.googleapis.com/auth/devstorage.full_control
https://www.googleapis.com/auth/devstorage.read_only
https://www.googleapis.com/auth/devstorage.read_write | - | Google Contacts | https://www.googleapis.com/auth/contacts | - | Google Docs | https://www.googleapis.com/auth/documents
https://www.googleapis.com/auth/drive
https://www.googleapis.com/auth/drive.file | - | Google Drive | https://www.googleapis.com/auth/drive
https://www.googleapis.com/auth/drive.appdata
https://www.googleapis.com/auth/drive.photos.readonly | - | Google Firebase Cloud Firestore | https://www.googleapis.com/auth/datastore
https://www.googleapis.com/auth/firebase | - | Google Firebase Realtime Database | https://www.googleapis.com/auth/userinfo.email
https://www.googleapis.com/auth/firebase.database
https://www.googleapis.com/auth/firebase | - | Google Perspective | https://www.googleapis.com/auth/userinfo.email | - | Google Sheets | https://www.googleapis.com/auth/drive.file
https://www.googleapis.com/auth/spreadsheets | - | Google Slide | https://www.googleapis.com/auth/drive.file
https://www.googleapis.com/auth/presentations | - | Google Tasks | https://www.googleapis.com/auth/tasks | - | Google Translate | https://www.googleapis.com/auth/cloud-translation | - | GSuite Admin | https://www.googleapis.com/auth/admin.directory.group
https://www.googleapis.com/auth/admin.directory.user
https://www.googleapis.com/auth/admin.directory.domain.readonly
https://www.googleapis.com/auth/admin.directory.userschema.readonly | - -## Troubleshooting - -### Google hasn't verified this app - -If using the OAuth authentication method, you might see the warning **Google hasn't verified this app**. To avoid this, you can create OAuth credentials from the same account you want to authenticate. However, if you're using credentials that were generated by another account (by a developer or another third party), do the following in Google Cloud: - -1. Select**Advanced**. -2. Select **Go to CREDENTIALS_NAME (unsafe)**. `CREDENTIALS_NAME` is the name of the credentials created by the third party. -3. Grant the requested permissions. diff --git a/docs/integrations/builtin/credentials/google/oauth-single-service.md b/docs/integrations/builtin/credentials/google/oauth-single-service.md deleted file mode 100644 index da9d2d5c2..000000000 --- a/docs/integrations/builtin/credentials/google/oauth-single-service.md +++ /dev/null @@ -1,64 +0,0 @@ -# Google: OAuth2 single service - -This document contains instructions for creating a Google credential for a single service. They're also available as a video. - -
- -
- -!!! note "Note for n8n Cloud users" - For the following nodes, you can authenticate by entering the **Credentials Name** and selecting **Sign in with Google** in the OAuth section to connect your Google account to n8n: - - * [Google Calendar](/integrations/builtin/app-nodes/n8n-nodes-base.googleCalendar/) - * [Google Contacts](/integrations/builtin/app-nodes/n8n-nodes-base.googleContacts/) - * [Google Sheets](/integrations/builtin/app-nodes/n8n-nodes-base.googleSheets/) - * [Google Tasks](/integrations/builtin/app-nodes/n8n-nodes-base.googleTasks/) - - -## Set up OAuth - -You need a [Google Cloud Platform project](https://developers.google.com/workspace/marketplace/create-gcp-project){:targe=_blank .external-link} for these steps. - -1. Go to [Google Cloud Console](https://console.cloud.google.com/apis/credentials){:target=_blank .external-link} and make sure you're in the project you want to use. - - ??? Details "View screenshot" - ![Google project dropdown](/_images/integrations/builtin/credentials/google/check-google-project.png) - -2. Select **+ CREATE CREDENTIALS > OAuth client ID**. If you're creating OAuth credentials for the first time, you must [configure the consent screen](https://support.google.com/cloud/answer/10311615?hl=en&ref_topic=3473162){:target=_blank .external-link}. - - ??? Details "View screenshot" - ![Create credentials](/_images/integrations/builtin/credentials/google/create-credentials.png) - -3. In the **Application type** dropdown, select **Web application**. Google automatically generates a name. - - ??? Details "View screenshot" - ![Web application](/_images/integrations/builtin/credentials/google/application-web-application.png) - -4. Under **Authorizes redirect URIs**, select **+ ADD URI**. Paste in the OAuth redirect URL from the previous step. - - ??? Details "View screenshot" - ![OAuth Callback URL](/_images/integrations/builtin/credentials/google/oauth_callback.png) - ![Add URI](/_images/integrations/builtin/credentials/google/add-uri.png) - -5. Select **CREATE**. -6. Enable each Google service API that you want to use: - - 1. If using Google Perspective or Google Ads: [Request API Access for Perspective](https://developers.perspectiveapi.com/s/docs-get-started){:targe=_blank .external-link} or a [Developer Token for Ads](https://developers.google.com/google-ads/api/docs/first-call/dev-token){:targe=_blank .external-link}. - --8<-- "_snippets/integrations/builtin/credentials/google/enable-apis.md" - -In n8n: - -1. Enter your new **Client ID** and **Client Secret** from Google Cloud Console in the credentials modal. -2. Select **Sign in with Google** to complete your Google authentication. -3. **Save** your new credentials. - - -## Troubleshooting - -### Google hasn't verified this app - -If using the OAuth authentication method, you might see the warning **Google hasn't verified this app**. To avoid this, you can create OAuth credentials from the same account you want to authenticate. However, if you're using credentials that were generated by another account (by a developer or another third party), do the following in Google Cloud: - -1. Select **Advanced**. -2. Select **Go to CREDENTIALS_NAME (unsafe)**. `CREDENTIALS_NAME` is the name of the credentials created by the third party. -3. Grant the requested permissions. diff --git a/docs/integrations/builtin/credentials/google/service-account.md b/docs/integrations/builtin/credentials/google/service-account.md deleted file mode 100644 index aa0102963..000000000 --- a/docs/integrations/builtin/credentials/google/service-account.md +++ /dev/null @@ -1,82 +0,0 @@ -# Google: Service Account - -Using service accounts is more complex than OAuth2. Before you begin: - -* Check if your node is [compatible](/integrations/builtin/credentials/google/#compatible-nodes) with Service Account. -* Make sure you need to use service account. For most use cases, OAuth2 is a better option. -* Read the Google documentation on [Creating and managing service accounts](https://cloud.google.com/iam/docs/creating-managing-service-accounts){:target=_blank .external-link}. - - -## Prerequisites - -* [Google Cloud](https://cloud.google.com/){:targe=_blank .external-link} account -* [Google Cloud Platform project](https://developers.google.com/workspace/marketplace/create-gcp-project){:targe=_blank .external-link} - -## Set up Service Account - -### Create a new credential in n8n - -1. Follow the steps to [Create a credential](/credentials/add-edit-credentials/). - - !!! note "Generic and specific credentials" - If you create a credential by selecting **Create new** in the credentials dropdown in a node, n8n automatically creates the correct credential type for that node. If you select **Credentials > New**, you must browse for the credential type: - - * To connect with a specific service, using resources and operations supported by n8n, choose that service. For example, to create a credential for use in the Gmail node, search for `Gmail`. - * To create a credential for a [custom API call](/integrations/custom-operations/), select **Google API**. - -2. Note the **Private Key** from the node credential modal. You'll need this in the next section. - -### Set up service account in Google Cloud - -In your [Google Cloud Console](https://console.cloud.google.com){:target=_blank .external-link} dashboard: - -1. Select the hamburger menu **> APIs & Services > Credentials**. Google takes you to your **Credentials** page. - - ??? Details "View screenshot" - ![Access the Credentials page for APIs and services](/_images/integrations/builtin/credentials/google/service-account-api-services-credentials.png) - -2. Select **+ CREATE CREDENTIALS > Service account**. - - ??? Details "View screenshot" - ![Access the Credentials page for APIs and services](/_images/integrations/builtin/credentials/google/service-account-create-credentials.png) - -3. Enter a name in **Service account name**, and an ID in **Service account ID**. Refer to [Creating a service account](https://cloud.google.com/iam/docs/creating-managing-service-accounts?hl=en#creating){:target=_blank .external-link} for more information. -4. Select **CREATE AND CONTINUE**. -5. Based on your use-case, you may want to **Select a role** and **Grant users access to this service account** using the corresponding sections. -6. Select **DONE**. -7. Select your newly created service account under the **Service Accounts** section. Open the **KEYS** tab. -8. Select **ADD KEY > Create new key**. - - ??? Details "View screenshot" - ![Create a new key](/_images/integrations/builtin/credentials/google/service-account-create-key.png) - -9. In the modal that appears, select **JSON**, then select **CREATE**. Google saves the file to your computer. -10. Enable each Google service API that you want to use: - --8<-- "_snippets/integrations/builtin/credentials/google/enable-apis.md" - -### Create and test your connection - -In n8n: - -1. In the **Service Account Email** field, enter the email associated with your new Service Account (you can find this in the **Details** tab in Google Cloud). -2. Enter the **Private Key** from the downloaded JSON file. If you're running an n8n version older than 0.156.0: replace all instances of `\n` in the JSON file with new lines. -3. **Optional**: Click the toggle to enable [**Impersonate a User**](https://developers.google.com/identity/protocols/oauth2/service-account#delegatingauthority){:target=_blank .external-link} and enter the email. -4. **Save** your credentials. - -The following video demonstrates the steps described above. - -
- -
- -## Troubleshooting - -### Service Account cannot access Google Drive files - -A Service Account can't access Google Drive files and folders that weren't shared with its associated user email. - -1. Access your [Google Cloud Console](https://console.cloud.google.com){:target=_blank .external-link} and copy your Service Account email. -2. Access your [Google Drive](https://drive.google.com){:target=_blank .external-link} and go to the designated file or folder. -3. Right-click on the file or folder and select **Share**. -4. Paste your Service Account email into **Add People and groups**. -5. Select **Editor** for read-write access or **Viewer** for read-only access. diff --git a/docs/integrations/builtin/credentials/gotify.md b/docs/integrations/builtin/credentials/gotify.md deleted file mode 100644 index 9b26f13f9..000000000 --- a/docs/integrations/builtin/credentials/gotify.md +++ /dev/null @@ -1,27 +0,0 @@ -# Gotify - -You can use these credentials to authenticate the following nodes with Gotify. - -- [Gotify](/integrations/builtin/app-nodes/n8n-nodes-base.gotify/) - -## Prerequisites - -Install [Gotify](https://gotify.net/docs/install) on your server. - -## Using API Token - -***Note:*** To create a message, the ***App API Token*** is required. To delete or retrieve all messages, you need the ***Client API Token***. - -1. Access your Gotify dashboard. -2. Click on ***APPS*** in the navigation menu. -3. Click on the ***CREATE APPLICATION*** button. -4. Enter an application name in the ***Name*** field. -5. Click on the ***CREATE*** button. -6. Click on ***CLIENTS*** in the navigation menu. -7. Click on the ***CREATE CLIENT*** button. -8. Enter a name for the client in the ***Name*** field. -9. Click on the ***CREATE*** button. -10. Use the App Token, Client Token, and the Host URL with your Gotify API credentials in n8n. -11. Click the ***Save*** button to save your credentials in n8n. - -![Getting Gotify credentials](/_images/integrations/builtin/credentials/gotify/using-api.gif) diff --git a/docs/integrations/builtin/credentials/gotowebinar.md b/docs/integrations/builtin/credentials/gotowebinar.md deleted file mode 100644 index 5ab4d4a37..000000000 --- a/docs/integrations/builtin/credentials/gotowebinar.md +++ /dev/null @@ -1,38 +0,0 @@ -# GoToWebinar - -You can use these credentials to authenticate the following nodes with GoToWebinar. - -- [GoToWebinar](/integrations/builtin/app-nodes/n8n-nodes-base.goToWebinar/) - -## Prerequisites - -Create a [GoToWebinar](https://gotowebinar.com/) account. - -## Using OAuth - - - -1. Sign in to the [GoTo Developer Center](https://developer.goto.com/) page. -2. Click on the ***OAuth Clients*** tab. -3. Click on the ***Create a client*** button. -4. Enter a name in the ***Client name*** field. -5. Copy the 'OAuth Callback URL' provided in the 'GoToWebinar OAuth2 API' credentials in n8n. -6. Paste the URL in the ***Redirect URIs*** field and click on the ***Next*** button. -7. Based on your use-case, select the required scopes. -8. Click on the ***Save*** button. -9. Copy the displayed ***Client ID***. -10. Enter a name for your credentials in the ***Credentials Name*** field in the 'GoToWebinar OAuth2 API' credentials in n8n. -11. Paste the client ID in the ***Client ID*** field in the 'GoToWebinar OAuth2 API' credentials in n8n. -12. Copy the displayed ***Client secret*** from the GoTo Client Management Portal. -13. Accept the ***I have stored the client secret*** option and click on the ***Done*** button. -14. Paste the client secret in the ***Client Secret*** field in the 'GoToWebinar OAuth2 API' credentials in n8n. -15. Click on the circle button in the OAuth section to connect a GoToWebinar account to n8n. -16. Click the ***Save*** button to save your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/grafana.md b/docs/integrations/builtin/credentials/grafana.md deleted file mode 100644 index cdc6498be..000000000 --- a/docs/integrations/builtin/credentials/grafana.md +++ /dev/null @@ -1,17 +0,0 @@ -# Grafana - -You can use these credentials to authenticate the following nodes with Grafana. - -- [Grafana](/integrations/builtin/app-nodes/n8n-nodes-base.grafana/) - -## Prerequisites - -- Create a [Grafana](https://grafana.com/) account. - -## Using Access Token - -1. In Grafana, click the gears icon in the sidebar on the left and select the ***API Keys*** option. -2. Click the "Add API key" button and enter any ***Key name***. -3. Click ***Add*** and copy the key shown. -4. Use the key with your Grafana credentials in n8n. -5. Enter the base URL of your instance (e.g. `https://n8n.grafana.net`) in n8n. diff --git a/docs/integrations/builtin/credentials/grist.md b/docs/integrations/builtin/credentials/grist.md deleted file mode 100644 index 716c733d3..000000000 --- a/docs/integrations/builtin/credentials/grist.md +++ /dev/null @@ -1,24 +0,0 @@ -# Grist - -You can use these credentials to authenticate the following nodes: - -* [Grist](/integrations/builtin/app-nodes/n8n-nodes-base.grist/). - -## Prerequisites - -Create a [Grist](https://getgrist.com/) account. - -## API key - -From Grist: - -1. Navigate to your **Profile Settings**. -2. In the *Api key* section click **Create**. -3. Copy the generated API key for use in n8n. - -From n8n: - -3. Enter the **API Key** obtained above. -4. Use the dropdown to select if your are using a *Free* or *Paid* plan. -5. For *Paid* plans, enter your **Custom Subdomain** (e.g. `.getgrist.com`). -6. Click on the ***Create*** button to create the credentials. diff --git a/docs/integrations/builtin/credentials/gumroad.md b/docs/integrations/builtin/credentials/gumroad.md deleted file mode 100644 index 4f1a8c8a9..000000000 --- a/docs/integrations/builtin/credentials/gumroad.md +++ /dev/null @@ -1,21 +0,0 @@ -# Gumroad - -You can use these credentials to authenticate the following nodes with Gumroad. - -- [Gumroad Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.gumroadTrigger/) - -## Prerequisites - -Create a [Gumroad](https://gumroad.com/) account. - -## Using Access Token - -1. Access your Gumroad dashboard. -2. Click on your user icon on the top right. -3. Click on Settings. -4. Click on the Advanced tab. -5. Scroll down and fill out the required fields and create a new application.. -6. From here, you have access the ability to generate an access token. -7. Use provided access token with your Gumroad node credentials in n8n. - -![Getting Gumroad credentials](/_images/integrations/builtin/credentials/gumroad/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/halopsa.md b/docs/integrations/builtin/credentials/halopsa.md deleted file mode 100644 index f57db16b5..000000000 --- a/docs/integrations/builtin/credentials/halopsa.md +++ /dev/null @@ -1,29 +0,0 @@ -# HaloPSA - -You can use these credentials to authenticate the following nodes with HaloPSA. - -- [HaloPSA](/integrations/builtin/app-nodes/n8n-nodes-base.haloPSA/) - -## Prerequisites - -Create a [HaloPSA](https://halopsa.com/) account. - -## Allow your application to use the API: - -1. Access your HaloPSA dashboard. -2. Click on the **Configuration** link in the left panel. -3. Under the **Integrations** menu entry, click on **HaloPSA API**. -4. In the **API Details** section you find the values **Resource Server**, **Authorisation Server**, and **Tenant**. -5. In the **Applications** section click on the **View Applications** button. -6. Click on the **New** button to register a new application or click on an existing one and then the **Edit** button to edit it. -7. Enter a name for your application (for example `n8n`). -8. Choose `Client ID and Secret (Services)` as the **Authentication Method**. -9. Make a note of both the **Client ID** and the **Client Secret**. The Client Secret will only be shown once and you will need to generate a new one when lost. -10. Select `Agent` as your **Login Type** and one of your agents in the **Agent to log in as** field. -11. On the **Permissions** tab, tick `all` and hit the **Save** button. -12. On n8n's HaloPSA credentials screen, fill in the values obtained in the previous steps. The **Tenant** field will be accessible only when the **Hosting Type** is set to `Hosted Solution of Halo`. - -![A workflow with the HaloPSA node](/_images/integrations/builtin/credentials/halopsa/halopsa-n8n-credentials.jpg) - -!['Resource Server', 'Authorisation Server', 'and Tenant'](/_images/integrations/builtin/credentials/halopsa/halopsa-credentials-1.jpg) -!['Cliend ID' and 'Client Secret'](/_images/integrations/builtin/credentials/halopsa/halopsa-credentials-2.jpg) diff --git a/docs/integrations/builtin/credentials/harvest.md b/docs/integrations/builtin/credentials/harvest.md deleted file mode 100644 index 5494f1f50..000000000 --- a/docs/integrations/builtin/credentials/harvest.md +++ /dev/null @@ -1,32 +0,0 @@ -# Harvest - -You can use these credentials to authenticate the following nodes with Harvest. - -- [Harvest](/integrations/builtin/app-nodes/n8n-nodes-base.harvest/) - -## Prerequisites - -Create a [Harvest](https://www.getharvest.com/) account. - -## Using OAuth - -1. Access the [Harvest Developer](https://id.getharvest.com/developers) portal. -2. Click on the ***Create New OAuth2 Application*** button. -3. Enter an application name in the ***Name*** field. -4. Copy the 'OAuth Callback URL' provided in the Harvest OAuth2 API credentials in n8n and paste it in the ***Redirect URL*** field. -5. Click on the ***Create Application*** button. -6. Copy the ***Client ID*** and ***Client Secret*** provided by the new Harvest app that you created and paste it in the Harvest OAuth2 API credentials in n8n. -7. Click on the circle button in the OAuth section to connect your Harvest account to n8n. -8. Click on the ***Save*** button to save your credentials. - -![Getting Harvest OAuth2 credentials](/_images/integrations/builtin/credentials/harvest/using-oauth.gif) - -## Using Access Token - -1. Access the [Harvest Developer](https://id.getharvest.com/developers) portal. -2. Click on the ***Create New Personal Access Token*** button. -3. Enter a token name in the ***Name*** field. -4. Click on the ***Create Personal Access Token*** button. -5. Use the token with Harvest node credentials in n8n. - -![Getting Harvest Access Token credentials](/_images/integrations/builtin/credentials/harvest/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/helpscout.md b/docs/integrations/builtin/credentials/helpscout.md deleted file mode 100644 index ebad343d0..000000000 --- a/docs/integrations/builtin/credentials/helpscout.md +++ /dev/null @@ -1,29 +0,0 @@ -# Help Scout - -You can use these credentials to authenticate the following nodes with Help Scout. - -- [Help Scout](/integrations/builtin/app-nodes/n8n-nodes-base.helpScout/) -- [Help Scout Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.helpScoutTrigger/) - -## Prerequisites - -Create a [Help Scout](https://www.helpscout.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Help Scout account to n8n. - - -1. Log in to your Help Scout account. -2. Click on the user icon in the top right. -3. Select 'Your Profile' in the drop down menu. -4. Click on 'My Apps' in the sidebar. -5. Click on the *Create My App* button. -6. Copy the 'OAuth Callback URL' provided in the HelpScout OAuth2 API credentials in n8n and paste it in the 'Redirection URL' field in Help Scout. -7. Fill out any other information that is necessary and click 'Create'. -8. Click on the *Save* button and use the 'App ID' and the 'App Secret' with your HelpScout OAuth2 API credentials in n8n. -9. Click on the circle button in the OAuth section to connect a Help Scout account to n8n. -10. Click the *Save* button to save your credentials. - -![Getting Help Scout OAuth credentials](/_images/integrations/builtin/credentials/helpscout/using-oauth.gif) diff --git a/docs/integrations/builtin/credentials/highlevel.md b/docs/integrations/builtin/credentials/highlevel.md deleted file mode 100644 index f6a656a85..000000000 --- a/docs/integrations/builtin/credentials/highlevel.md +++ /dev/null @@ -1,15 +0,0 @@ -# HighLevel - -You can use these credentials to authenticate the following nodes with HighLevel: - -* [HighLevel node](/integrations/builtin/app-nodes/n8n-nodes-base.highLevel/) - -## Prerequisites - -Sign up for a HighLevel account. - -## Using an API key - -1. Follow the guidance in the [HighLevel documentation](https://help.gohighlevel.com/support/solutions/articles/48001060529-highlevel-api){:target=_blank .external-link} to get your API key. -2. Copy the key into the **API Key** field in your n8n HighLevel credentials. - diff --git a/docs/integrations/builtin/credentials/homeassistant.md b/docs/integrations/builtin/credentials/homeassistant.md deleted file mode 100644 index e02e54b2e..000000000 --- a/docs/integrations/builtin/credentials/homeassistant.md +++ /dev/null @@ -1,18 +0,0 @@ -# Home Assistant - -You can use these credentials to authenticate the following nodes with Home Assistant. - -- [Home Assistant](/integrations/builtin/app-nodes/n8n-nodes-base.homeAssistant/) - -## Prerequisites - -- [Install](https://www.home-assistant.io/installation/) Home Assistant -- Create a [Home Assistant](https://www.home-assistant.io/getting-started/onboarding) account. -- Review the Home Assistant [Autentication API](https://developers.home-assistant.io/docs/auth_api) documentation - -## Using access token - -1. Access your Home Assistant UI, for example `homeassistant.local:8123`. -2. Open your user profile page and navigate to the **Long-Lived Access Tokens** section. -3. Generate a new token and copy it. -4. Use that token with your Home Assistant node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/httprequest.md b/docs/integrations/builtin/credentials/httprequest.md deleted file mode 100644 index 8274cce8f..000000000 --- a/docs/integrations/builtin/credentials/httprequest.md +++ /dev/null @@ -1,77 +0,0 @@ -# HTTP Request - -You can use these credentials to authenticate the following nodes: - -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) - -## Prerequisites - -You must use the authentication method required by the app or service you want to query. - -### Existing credential types - -n8n recommends using this option whenever there's a credential type available for the service you want to connect to. It offers an easier way to set up and manage credentials, compared to configuring generic credentials. - -You can use [Predefined credential types](/integrations/custom-operations/#predefined-credential-types) to perform custom operations with some APIs where n8n has a node for the platform. For example, n8n has an Asana node, and supports using your Asana credentials in the HTTP Request node. Refer to [Custom operations](/integrations/custom-operations/) for more information. - -### Generic authentication - -The following generic authentication methods are available: - -* Basic Auth -* Digest Auth -* Header Auth -* OAuth1 -* OAuth2 -* None - -You can learn more about HTTP authentication [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication#see_also){:target=_blank .external-link}. - - -## Using an existing credential type - ---8<-- "_snippets/integrations/predefined-credential-type-how-to.md" - -Refer to [Custom API operations](/integrations/custom-operations/) for more information. - -## Using Basic Auth or Digest Auth - -1. Update the credential name. -2. Enter the **Username** and **Password** for the app or service your HTTP Request is targeting. -3. Select **Save** to save your credentials. - -## Using Header Auth - -1. Update the credential name. -2. Enter the header **Name** and **Value** required for the app or service your HTTP Request is targeting. Read more about [HTTP headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers#authentication){:target=_blank .external-link}. -3. Select **Save** to save your credentials. - -## Using OAuth1 - -1. Update the credential name. -2. Enter the following authentication details: - * **Authorization URL** - * **Access Token URL** - * **Consumer Key** - * **Consumer Secret** - * **Request Token URL** - * **Signature Method** -3. Select **Save** to save your credentials. - -Read more about [OAuth1](https://oauth.net/1/){:target=_blank .external-link}. - -## Using OAuth2 - -1. Update the credential name. -2. Enter the following authentication details: - * **Authorization URL** - * **Access Token URL** - * **Client ID** - * **Client Secret** - * **Scope** - * **Auth URI Query Parameters** - * **Authentication** -3. Select **Save** to save your credentials. - -Read more about [OAuth2](https://oauth.net/2/){:target=_blank .external-link}. - diff --git a/docs/integrations/builtin/credentials/hubspot.md b/docs/integrations/builtin/credentials/hubspot.md deleted file mode 100644 index c8c71a9fe..000000000 --- a/docs/integrations/builtin/credentials/hubspot.md +++ /dev/null @@ -1,83 +0,0 @@ -# HubSpot - -You can use these credentials to authenticate the following nodes with HubSpot. - -- [HubSpot](/integrations/builtin/app-nodes/n8n-nodes-base.hubspot/) -- [HubSpot Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.hubSpotTrigger/) - -## Prerequisites - -Create a [HubSpot](https://www.hubspot.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your HubSpot account to n8n. - - -!!! warning "⚠ HubSpot old accounts" - Some HubSpot accounts don't have access to all the scopes. HubSpot is migrating accounts gradually. If you can't' find all the scopes in your current HubSpot developer account, try creating a fresh developer account. - - -1. Access your [HubSpot Developer Home](https://developers.hubspot.com/). -2. Click on the **Manage apps** button. -3. Click on the **Create app** button in the top right. -4. Specify an app name in the **Public app name** field. -5. Click on the 'Auth' tab. -6. Use the provided **Client ID** and the **Client secret** with your HubSpot OAuth2 API credentials in n8n. -7. If you are using the [HubSpot Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.hubSpotTrigger/) node, copy the **App ID** along with the information in the previous step. -8. Copy your OAuth Callback URL from the 'Create New Credentials' screen in n8n and paste in the **Redirect URL** section. - - !!! note "Exact scope needed" - If you grant access to more or less scopes than listed below, this might cause an issue with the authentication step. Make sure to only include what is listed below. - -9. In the Scopes section, select the following scopes in the **Find a scope** search box: - * Trigger node: - * oauth - * crm.objects.contacts (read), - * crm.schemas.contacts (read), - * crm.objects.companies (read), - * crm.schemas.companies (read), - * crm.objects.deals (read), - * crm.schemas.deals (read), - * Regular node: - * oauth - * crm.schemas.deals (read), - * crm.objects.owners (read), - * crm.objects.contacts (write), - * crm.objects.companies (write), - * crm.objects.companies (read), - * crm.objects.deals (read), - * crm.schemas.contacts (read), - * crm.objects.deals (write), - * crm.objects.contacts (read), - * crm.schemas.companies (read), - * forms, - * tickets, -10. Click on the **Save** button to save your settings in HubSpot. -11. Back in n8n, click on the circle button in the OAuth section to connect your HubSpot account to n8n. -12. Click the **Save** button to save your credentials. - - -## Using API key - -1. Access your HubSpot dashboard. -2. Click on the gear icon on the top right. -3. Click on **Integrations** and then **API key**. -4. Click on the **Create key** button. -5. Use the key with HubSpot node credentials in n8n. - - -## Using APP Token - -1. Follow the instructions in the [Private Apps Documentation](https://developers.hubspot.com/docs/api/private-apps) to get your access token. -2. Set the access token as the key in your HubSpot credentials in n8n. - - -## Using Developer API Key (for HubSpot Trigger node) - -1. Access your [HubSpot Developer Home](https://developers.hubspot.com/). -2. Click on **Apps** in the top bar. -3. Click on the **Get HubSpot API key** button. -4. Click on the **Show key** button. -5. Use the displayed Developer API key with your HubSpot Trigger node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/humanticai.md b/docs/integrations/builtin/credentials/humanticai.md deleted file mode 100644 index 234c48e0e..000000000 --- a/docs/integrations/builtin/credentials/humanticai.md +++ /dev/null @@ -1,17 +0,0 @@ -# Humantic AI - -You can use these credentials to authenticate the following nodes with Humantic AI. - -- [Humantic AI](/integrations/builtin/app-nodes/n8n-nodes-base.humanticAi/) - -## Using API - -1. Access the [Humantic AI API](https://api.humantic.ai/) page. -2. Enter your email address in the ***Business Email*** field. -3. Click on the ***GET API KEY*** button. -4. Enter all the necessary information. -5. Click on the ***Get API Key*** button. -6. Set a password for your account and click on the ***SET PASSWORD*** button. -7. Use the provided ***api key*** with your Humantic AI API credentials in n8n. - -![Getting Humantic AI credentials](/_images/integrations/builtin/credentials/humanticai/using-api-key.gif) diff --git a/docs/integrations/builtin/credentials/hunter.md b/docs/integrations/builtin/credentials/hunter.md deleted file mode 100644 index 1a1839891..000000000 --- a/docs/integrations/builtin/credentials/hunter.md +++ /dev/null @@ -1,18 +0,0 @@ -# Hunter - -You can use these credentials to authenticate the following nodes with Hunter. - -- [Hunter](/integrations/builtin/app-nodes/n8n-nodes-base.hunter/) - -## Prerequisites - -Create a [Hunter](https://www.hunter.io/) account. - -## Using Access Token - -1. Access your Hunter dashboard. -2. Click on your profile icon on the top right. -3. Click on API. -4. Use the key with Hunter node credentials in n8n. - -![Getting Hunter credentials](/_images/integrations/builtin/credentials/hunter/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/imap.md b/docs/integrations/builtin/credentials/imap.md deleted file mode 100644 index 9d5703817..000000000 --- a/docs/integrations/builtin/credentials/imap.md +++ /dev/null @@ -1,104 +0,0 @@ -# IMAP - -You can use these credentials to authenticate the following nodes with IMAP. - -- [IMAP Email](/integrations/builtin/core-nodes/n8n-nodes-base.emailimap/) - -## Prerequisites - -Create an email account on a service with IMAP support. - -## Using IMAP - -1. Retrieve your login credentials and IMAP connection parameters. -2. Use the login credentials and IMAP connection parameters with your IMAP Email node credentials in n8n. -3. Click on the ***Save*** button to save your credentials. - - -## Using Gmail - -1. Access your [Gmail](https://mail.google.com) account. -2. Click on the gears icon on the top and click on ***See all settings***. -3. Click on the ***Forwarding and POP/IMAP*** tab. -4. Under the ***IMAP access*** section, select 'Enable IMAP'. -5. Click on the ***Save Changes*** button. -6. Go to your [Google Account](https://myaccount.google.com) page. -7. Click on ***Security*** on the left sidebar. -8. Click on ***2-Step Verification*** under the ***Signing in to Google*** section. -9. Set up your 2-Step Verification method. -10. Click on ***App passwords*** under the ***Signing in to Google*** section. -11. Select 'Mail' from the ***Select app*** dropdown list. -12. Select 'Other' from the ***Select device*** dropdown list. -13. Enter a name in the text field. -14. Click on the ***GENERATE*** button. -15. Copy the displayed password. -16. In the IMAP node credentials, enter your email address in the ***User*** field. For example, `example@gmail.com`. -17. Paste the App password you copied in **Step 15** in the ***Password*** field. -18. Enter `imap.gmail.com` in the ***Host*** field. -19. Toggle ***SSL/TLS*** to `true`. -20. Click on ***Save*** to save your credentials. - -**Note:** Before executing the node, set the ***Ignore SSL Issues*** option to true as the Gmail certificate is self-signed. - -
- -
- -## Using Yahoo Mail - -1. Open your [Yahoo Mail](https://mail.yahoo.com) account. -2. Click on your avatar on the top right and select 'Account info'. -3. Click on the ***Account security*** tab in the left sidebar. -4. Scroll down to the bottom and click on ***Generate app password***. -5. Select 'Other app' from the ***Select your app*** dropdown list. -6. Enter the name of the app in the ***Enter custom name*** field. -7. Click on the ***Generate*** button. -8. Copy the displayed password. -9. Enter the name for your credentials in the ***Credentials Name*** field in the 'IMAP' credentials in n8n. -10. Enter your email address in the ***User*** field. -11. Paste the password you copied earlier in the ***Password*** field. -12. Enter `imap.mail.yahoo.com` in the ***Host*** field. -13. Toggle ***SSL/TLS*** to `true`. -14. Click on ***Save*** to save your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
- -## Using Outlook.com - -1. Enter the name for your credentials in the ***Credentials Name*** field in the 'IMAP' credentials in n8n. -2. Enter your email address in the ***User*** field. -3. Enter your account password in the ***Password*** field. -4. Enter `outlook.office365.com` in the ***Host*** field. -5. Toggle ***SSL/TLS*** to `true`. -6. Click on ***Create*** to create your credentials. - -**Note** If you get a connection error, please follow the steps mentioned in the [FAQs](#how-to-solve-the-connection-error-when-connecting-to-outlook-com). - -The following video demonstrates the steps mentioned above. - -
- -
- -## FAQs - -### How to solve the connection error when connecting to Outlook.com? - -If you receive a connection error while configuring the credentials for your Outlook account, follow the steps mentioned below: -1. Go to [account.live.com/activity](https://account.live.com/activity). -2. Sign in using the email address and password of your account. -3. Under the ***Recent activity*** section, find the Session Type event that matches the most recent time you received the connection error and click to expand it. -4. Select ***This was me*** to let the system know you authorize the IMAP connection. - - - - -- [Set up IMAP for Gmail account](https://support.google.com/mail/answer/7126229?hl=en) -- [Sign in with App Passwords for your Gmail Account](https://support.google.com/accounts/answer/185833?hl=en) -- [Set up IMAP for Yahoo mail account](https://help.yahoo.com/kb/sln4075.html) -- [Sign in with App Passwords for your Yahoo mail Account](https://help.yahoo.com/kb/generate-manage-third-party-passwords-sln15241.html) -- [POP, IMAP, and SMTP settings for Outlook.com](https://support.microsoft.com/en-us/office/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040) diff --git a/docs/integrations/builtin/credentials/index.md b/docs/integrations/builtin/credentials/index.md deleted file mode 100644 index 0bf70430a..000000000 --- a/docs/integrations/builtin/credentials/index.md +++ /dev/null @@ -1,6 +0,0 @@ -# Credentials library - -This section contains step-by-step information about authenticating the different nodes in n8n. - -To learn more about creating, managing, and sharing credentials, refer to [Manage credentials](/credentials/). - diff --git a/docs/integrations/builtin/credentials/intercom.md b/docs/integrations/builtin/credentials/intercom.md deleted file mode 100644 index 81a097bb4..000000000 --- a/docs/integrations/builtin/credentials/intercom.md +++ /dev/null @@ -1,23 +0,0 @@ -# Intercom - -You can use these credentials to authenticate the following nodes with Intercom. - -- [Intercom](/integrations/builtin/app-nodes/n8n-nodes-base.intercom/) - - -## Prerequisites - -Create a [Intercom](https://www.intercom.com/) account. - - - -## Using Access Token - -1. Create an app in your workspace. -2. Click on Configure, then Authentication within the Developer hub. -3. Use the Access Token with the Intercom node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/invoiceninja.md b/docs/integrations/builtin/credentials/invoiceninja.md deleted file mode 100644 index 4ff7c8cd6..000000000 --- a/docs/integrations/builtin/credentials/invoiceninja.md +++ /dev/null @@ -1,20 +0,0 @@ -# Invoice Ninja - -You can use these credentials to authenticate the following nodes with Invoice Ninja. - -- [Invoice Ninja](/integrations/builtin/app-nodes/n8n-nodes-base.invoiceNinja/) -- [Invoice Ninja Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.invoiceNinjaTrigger/) - -## Prerequisites - -Create an [Invoice Ninja](https://www.invoiceninja.com/) account. - -## Using Access Token - -1. Access your Invoice Ninja dashboard. -2. Click on Settings in the bottom left. -3. Scroll down to API keys. -4. Add new token. -5. Use the key and your instance URL with Invoice Ninja node credentials in n8n. - -![Getting Invoice Ninja credentials](/_images/integrations/builtin/credentials/invoiceninja/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/iterable.md b/docs/integrations/builtin/credentials/iterable.md deleted file mode 100644 index c57c106b3..000000000 --- a/docs/integrations/builtin/credentials/iterable.md +++ /dev/null @@ -1,21 +0,0 @@ -# Iterable - -You can use these credentials to authenticate the following nodes with Iterable. - -- [Iterable](/integrations/builtin/app-nodes/n8n-nodes-base.iterable/) - -## Prerequisites - -Create an [Iterable](https://iterable.com) account. - -## Using API Key - -1. Access the [Iterable dashboard](https://app.iterable.com/). -2. Click on ***Integrations*** and select 'API keys'. -3. Click on the ***NEW API KEY*** button. -4. Enter a name in the ***Name*** field. -5. Click on the ***Create*** button. -6. Click on the ***Copy*** button to copy the API key. -7. Use this ***API key*** with your Iterable node credentials in n8n. - -![Getting Iterable credentials](/_images/integrations/builtin/credentials/iterable/using-api-key.gif) diff --git a/docs/integrations/builtin/credentials/jenkins.md b/docs/integrations/builtin/credentials/jenkins.md deleted file mode 100644 index da1c9ca49..000000000 --- a/docs/integrations/builtin/credentials/jenkins.md +++ /dev/null @@ -1,18 +0,0 @@ -# Jenkins - -You can use these credentials to authenticate the following nodes with CircleCI. - -- [Jenkins](/integrations/builtin/app-nodes/n8n-nodes-base.jenkins/) - - -## Prerequisites - -Create an account on a [Jenkins](https://www.jenkins.io/) instance. - -## Using Access Token - -1. Access your Jenkins User. -2. Visit the *Configure* section. -3. Click on the *Add new Token* button. -4. Type in a name for your token and click on the *Generate* button. -5. Copy the generated API Token and use it with your Jenkins API node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/jira.md b/docs/integrations/builtin/credentials/jira.md deleted file mode 100644 index 733f67af2..000000000 --- a/docs/integrations/builtin/credentials/jira.md +++ /dev/null @@ -1,20 +0,0 @@ -# Jira - -You can use these credentials to authenticate the following nodes with Jira. - -- [Jira](/integrations/builtin/app-nodes/n8n-nodes-base.jira/) -- [Jira Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.jiraTrigger/) - -## Prerequisites - -Create a [Jira](https://www.JIRA.com/) account. - -## Using Access Token - -1. Access your Jira dashboard. -2. Click on your user icon in the top right. -3. Click on Account Settings. -4. Click on Security tab. -5. Click on Manage API Tokens. -6. Create API token. -7. Use the API token with Jira node credentials in n8n. Your email and the domain under which the Jira account is under must also be included. diff --git a/docs/integrations/builtin/credentials/jotform.md b/docs/integrations/builtin/credentials/jotform.md deleted file mode 100644 index 191d98bf1..000000000 --- a/docs/integrations/builtin/credentials/jotform.md +++ /dev/null @@ -1,19 +0,0 @@ -# JotForm - -You can use these credentials to authenticate the following nodes with JotForm. - -- [JotForm Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.jotFormTrigger/) - -## Prerequisites - -Create a [JotForm](https://www.jotform.com/) account. - -## Using Access Token - -1. Access your [JotForm account](https://www.jotform.com/myaccount/). -2. Click on the ***API*** tab on the left. -3. Click on the ***Create New Key*** button. -4. Change the Permissions to 'Full Access'. -5. Use the key with JotForm node credentials in n8n. - -![Getting JotForm credentials](/_images/integrations/builtin/credentials/jotform/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/kafka.md b/docs/integrations/builtin/credentials/kafka.md deleted file mode 100644 index 799c9adec..000000000 --- a/docs/integrations/builtin/credentials/kafka.md +++ /dev/null @@ -1,16 +0,0 @@ -# Kafka - -You can use these credentials to authenticate the following nodes with Kafka. - -- [Kafka](/integrations/builtin/app-nodes/n8n-nodes-base.kafka/) -- [Kafka Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.kafkaTrigger/) - -## Prerequisites - -Have Kafka up and running. You can refer to the official [documentation](https://kafka.apache.org/quickstart) to learn how to do that. - -## Using Kafka - -1. Enter a client ID in the ***Client ID*** field. -2. Retrieve the Kafka Brokers and credentials (if any). -3. Use the ***Client ID***, ***Brokers*** (comma separated), ***Username***, and ***Password*** with your Kafka node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/keap.md b/docs/integrations/builtin/credentials/keap.md deleted file mode 100644 index 7e66e0917..000000000 --- a/docs/integrations/builtin/credentials/keap.md +++ /dev/null @@ -1,26 +0,0 @@ -# Keap - -You can use these credentials to authenticate the following nodes with Keap. - -- [Keap](/integrations/builtin/app-nodes/n8n-nodes-base.keap/) -- [Keap Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.keapTrigger/) - -## Prerequisites - -Create a [Keap](https://keap.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Keap account to n8n. - - -1. Access your [Keap Developer Console](https://keys.developer.keap.com/my-apps). -2. Click on your email address in the top right corner and select 'Apps' from the dropdown list. -3. Click on the 'New App' button. -4. Enter any necessary information, enable the 'Keap 150k' API and click on the *Create* button. -6. Use the 'Key' and the 'Secret' displayed with your Keap OAuth2 API credentials in n8n. -7. Click on the circle button in the OAuth section to connect a Keap account to n8n. -8. Click the *Save* button to save your credentials. - -![Getting Keap credentials](/_images/integrations/builtin/credentials/keap/getting-oauth-credentials.gif) diff --git a/docs/integrations/builtin/credentials/kitemaker.md b/docs/integrations/builtin/credentials/kitemaker.md deleted file mode 100644 index e501dede2..000000000 --- a/docs/integrations/builtin/credentials/kitemaker.md +++ /dev/null @@ -1,28 +0,0 @@ -# Kitemaker - -You can use these credentials to authenticate the following nodes with Kitemaker. - -- [Kitemaker](/integrations/builtin/app-nodes/n8n-nodes-base.kitemaker/) - -## Prerequisites - -Create an account on [Kitemaker](https://www.kitemaker.co/). - -## Using Access Token - -1. Open your Kitemaker [work item board](https://toil.kitemaker.co/). -2. Click on the settings icon next to the organization name in the left sidebar. -3. Select 'Developer settings' from the dropdown list. -4. Click on ***Add new personal access token*** under the ***Personal access tokens*** section. -5. Enter a name for your token in the ***Personal access token name*** field. -6. Click on the ***Create token*** button. -7. Copy the displayed token. -8. Enter the name for your credentials in the ***Credentials Name*** field in the 'Kitemaker API' credentials in n8n. -9. Paste the token in the ***Personal Access Token*** field in the 'Kitemaker API' credentials in n8n. -10. Click on the ***Create*** button to create your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/kobotoolbox.md b/docs/integrations/builtin/credentials/kobotoolbox.md deleted file mode 100644 index 6ef3f9a0e..000000000 --- a/docs/integrations/builtin/credentials/kobotoolbox.md +++ /dev/null @@ -1,12 +0,0 @@ -# KoBo Toolbox - -You can use these credentials to authenticate the following nodes: - -* [KoBo Toolbox trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.koBoToolboxTrigger/) -* [KoBo Toolbox](/integrations/builtin/app-nodes/n8n-nodes-base.koBoToolbox/) - -KoBo Toolbox uses an API key for authentication: - -1. Sign up for a [KoBo Toolbox](https://www.kobotoolbox.org/) account. -2. Follow the [KoBo Toolbox API documentation](https://support.kobotoolbox.org/api.html) to get your API token. -3. Copy your new key and use it with your KoBo Toolbox node credentials in n8n. \ No newline at end of file diff --git a/docs/integrations/builtin/credentials/lemlist.md b/docs/integrations/builtin/credentials/lemlist.md deleted file mode 100644 index b46a824ac..000000000 --- a/docs/integrations/builtin/credentials/lemlist.md +++ /dev/null @@ -1,26 +0,0 @@ -# Lemlist - -You can use these credentials to authenticate the following nodes with Lemlist. - -- [Lemlist](/integrations/builtin/app-nodes/n8n-nodes-base.lemlist/) -- [Lemlist Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.lemlistTrigger/) - -## Prerequisites - -Create an account on a [Lemlist](https://www.lemlist.com/) instance. - -## Using API Key - -1. Open your Lemlist [dashboard](https://app.lemlist.com/). -2. Click on the menu on the top left and select 'Settings' from the dropdown list. -3. Click on ***Integrations*** under the ***Misc*** section from the left sidebar. -4. Copy the API key displayed under the ***API*** section. -5. Enter the name for your credentials in the ***Credentials Name*** field in the 'Lemlist API' credentials in n8n. -6. Paste the API key in the ***API Key*** field in the 'Lemlist API' credentials in n8n. -7. Click on the ***Create*** button to create your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/line.md b/docs/integrations/builtin/credentials/line.md deleted file mode 100644 index baf8477d1..000000000 --- a/docs/integrations/builtin/credentials/line.md +++ /dev/null @@ -1,28 +0,0 @@ -# Line - -You can use these credentials to authenticate the following nodes with Line. - -- [Line](/integrations/builtin/app-nodes/n8n-nodes-base.line/) - -## Prerequisites - -Create a [Line](https://line.me/en/) account. - -## Using OAuth - -1. Access the [LINE Notify](https://notify-bot.line.me/en/) page. -2. Click on your name on the top right corner and select 'Manage registered services' from the dropdown list. -3. Click on the ***Add service*** button. -4. Enter all the necessary information. -5. Copy your OAuth Callback URL from the 'Create New Credentials' screen in n8n and paste it in the ***Callback URL*** field. -6. Click on the ***Agree and continue*** button. -7. Click on the ***Add*** button. -8. Check your inbox for the verification email. -9. Click on the link under the ***LINE Notify Registration URL*** in your email. -10. On the LINE Notify page, click on the ***My services*** button. -11. Click on the new service you created. -12. Use the provided ***Client ID*** and ***Client Secret*** with your Line Notify OAuth2 API credentials in n8n. -13. Click on the circle button in the OAuth section to connect a Line account to n8n. -14. Click the ***Save*** button to save your credentials in n8n. - -![Getting Line credentials](/_images/integrations/builtin/credentials/line/using-oauth.gif) diff --git a/docs/integrations/builtin/credentials/linear.md b/docs/integrations/builtin/credentials/linear.md deleted file mode 100644 index 73ffa7cda..000000000 --- a/docs/integrations/builtin/credentials/linear.md +++ /dev/null @@ -1,16 +0,0 @@ -# Linear - -You can use these credentials to authenticate the following nodes with Linear. - -* [Linear Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.linearTrigger/) -* [Linear](/integrations/builtin/app-nodes/n8n-nodes-base.linear/) - -## Prerequisites - -Create a [Linear](https://linear.app/) account. - -## Using the Linear API - -1. Open the [Linear API settings](https://linear.app/settings/api). -2. Click on the **Create key** button. -3. Copy the key into **API Key** field of the credentials screen in n8n. diff --git a/docs/integrations/builtin/credentials/lingvanex.md b/docs/integrations/builtin/credentials/lingvanex.md deleted file mode 100644 index 6ed3e3ada..000000000 --- a/docs/integrations/builtin/credentials/lingvanex.md +++ /dev/null @@ -1,26 +0,0 @@ -# LingvaNex - -You can use these credentials to authenticate the following nodes with LingvaNex. - -- [LingvaNex](/integrations/builtin/app-nodes/n8n-nodes-base.lingvaNex/) - -## Prerequisites - -Create a [LingvaNex](https://lingvanex.com) account. - -## Using API - -1. Open your LingvaNex [account](https://lingvanex.com/account/) page. -2. Click on the ***Cloud API*** tab. -3. Click on ***Payment / Subscription***. Note that you can use the limited Translation API without having to subscribe or add a payment method. -4. Scroll to the ***Translation API*** section. -5. Copy the displayed API key. -6. Enter the name for your credentials in the ***Credentials Name*** field in the 'LingvaNex API' credentials in n8n. -7. Paste the API key in the ***API Key*** field in the 'LingvaNex API' credentials in n8n. -8. Click on the ***Create*** button to create your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/linkedin.md b/docs/integrations/builtin/credentials/linkedin.md deleted file mode 100644 index 9d929fc1a..000000000 --- a/docs/integrations/builtin/credentials/linkedin.md +++ /dev/null @@ -1,48 +0,0 @@ -# LinkedIn - -You can use these credentials to authenticate the following nodes with LinkedIn. - -- [LinkedIn](/integrations/builtin/app-nodes/n8n-nodes-base.linkedIn/) - -## Prerequisites - -Create a [LinkedIn](https://www.linkedin.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your LinkedIn account to n8n. - - -1. Access the [LinkedIn app creation page](https://www.linkedin.com/developers/apps/new). -2. Enter a name in the ***App name*** field. -3. Enter your LinkedIn Page/Profile in the ***LinkedIn Page*** field. -4. Add a logo by clicking on the ***Upload a logo*** button. -5. Agree to the terms and conditions in the ***Legal agreement*** section and click the ***Create app*** button at the bottom of the page. -6. Verify your application. You can find instructions on how to verify your LinkedIn application in the FAQs below. -7. Enable APIs for your application. You can find instructions on how and which APIs to enable for your LinkedIn application in the FAQs below. -8. Back in the LinkedIn application creation page, click on the ***Auth*** tab. -9. Copy the 'OAuth Callback URL' provided in the LinkedIn OAuth2 API credentials in n8n and add it in the 'Authorized redirect URLs for your app' section in the LinkedIn application creation page. -10. Use the displayed ***Client ID*** and the ***Client Secret*** with your LinkedIn OAuth API credentials in n8n. -11. Click on the circle button in the OAuth section to connect a LinkedIn account to n8n. -12. Click the ***Save*** button to save your credentials in n8n. - -![Getting LinkedIn credentials](/_images/integrations/builtin/credentials/linkedin/using-oauth.gif) - -## FAQs - -### How do I verify my LinkedIn application? - -1. Open the application's page on the LinkedIn developers portal. -2. Click on the ***Verify*** button. -3. Click on the ***Generate URL*** button under the ***Verification URL*** section. -4. Copy the generated URL and open it in your web browser. -5. Click on the ***Verify*** button to verify your LinkedIn OAuth application. - -### How do I enable APIs for my LinkedIn application? - -1. Click on the ***Products*** tab in your LinkedIn application page. -2. Click the ***Select*** button next to the API you want to enable in the ***Products*** section. -3. Click the checkbox to accept the terms and conditions and then click on the ***Add product*** button. - -**Note:** You will need to enable the ***Share on LinkedIn*** and ***Sign In with LinkedIn*** products to connect with n8n. If you would like to connect an organizational LinkedIn account to n8n, then you also additionally need to enable the ***Marketing Developer Platform*** product. diff --git a/docs/integrations/builtin/credentials/magento2.md b/docs/integrations/builtin/credentials/magento2.md deleted file mode 100644 index 64ba43e72..000000000 --- a/docs/integrations/builtin/credentials/magento2.md +++ /dev/null @@ -1,28 +0,0 @@ -# Magento 2 - -You can use these credentials to authenticate the following nodes: - -- [Magento 2](/integrations/builtin/app-nodes/n8n-nodes-base.magento2/) - -## Prerequisites - -Create a [Magento](https://magento.com/) account. - -## Using Access Token - -From your Magento [admin](https://docs.magento.com/user-guide/stores/admin.html) panel: - -1. Navigate to **System** > **Extensions** > **Integrations**. -2. Select **Add New Integration**. -3. Enter a name for your n8n integration and your admin password. -4. Navigate to the **API** tab and select the Magento resources this n8n integration should be able to access. -5. Select **Save** to confirm your selections. -6. From the **Integrations** page, click **Activate** for the new n8n integration. -7. Select **Allow** to display a dialog screen with the credentials. -8. Copy the **Access Token** value to use in n8n. - -From n8n: - -1. Enter the **Host** address of your Magento store. -2. Enter the **Access Token** obtained above. -3. Click **Save** to create the credentials. diff --git a/docs/integrations/builtin/credentials/mailcheck.md b/docs/integrations/builtin/credentials/mailcheck.md deleted file mode 100644 index d6c1bffca..000000000 --- a/docs/integrations/builtin/credentials/mailcheck.md +++ /dev/null @@ -1,28 +0,0 @@ -# Mailcheck - -You can use these credentials to authenticate the following nodes with Mailcheck. - -- [Mailcheck](/integrations/builtin/app-nodes/n8n-nodes-base.mailcheck/) - -## Prerequisites - -Create a [Mailcheck](https://app.mailcheck.co/) account. - -## Using API Key - -1. Open the Mailcheck [dashboard](https://app.mailcheck.co/dashboard) page. -2. Click on the API on the top menu. -3. Enter a key name in the ***Enter the key name*** field. -4. Click on the ***Create Key*** button. -5. Click on the ***Copy*** button to copy the API key. -6. Enter a name for your credentials in the ***Credentials Name*** field in the 'Mailcheck API' credentials in n8n. -7. Paste the API key in the ***API Key*** field in the 'Mailcheck API' credentials in n8n. -8. Click on the ***Create*** button to create your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
- -Please reach out to Mailcheck support should you have any questions [support@mailcheck.co](mailto:support+n8n@mailcheck.co) diff --git a/docs/integrations/builtin/credentials/mailchimp.md b/docs/integrations/builtin/credentials/mailchimp.md deleted file mode 100644 index d3fb7e278..000000000 --- a/docs/integrations/builtin/credentials/mailchimp.md +++ /dev/null @@ -1,40 +0,0 @@ -# Mailchimp - -You can use these credentials to authenticate the following nodes with Mailchimp. - -- [Mailchimp](/integrations/builtin/app-nodes/n8n-nodes-base.mailchimp/) -- [Mailchimp Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.mailchimpTrigger/) - -## Prerequisites - -Create a [Mailchimp](https://www.mailchimp.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Mailchimp account to n8n. - - -1. Access your Mailchimp dashboard. -2. Click on your user icon on the top right. -3. Click on 'Account' in the dropdown list. -4. Click on the *Extras* dropdown list and then select 'Registered apps'. -5. Click on the *Register An App* button. -6. Copy the 'OAuth Callback URL' from your n8n Mailchimp OAuth2 API credentials and paste it in the 'Redirect URI' field of the Mailchimp form. -7. Fill out any other necessary details and click on the *Create* button. -8. Use the generated Client ID and Client secret with your Mailchimp OAuth2 API node credentials in n8n. -9. Click on the circle button in the OAuth section to connect your Mailchimp account to n8n. -10. Click the *Save* button to save your credentials. - -![Getting Mailchimp credentials](/_images/integrations/builtin/credentials/mailchimp/using-oauth.gif) - -## Using Access Token - -1. Access your Mailchimp dashboard. -2. Click on your user icon on the top right. -3. Click on 'Account' in the dropdown list. -4. Click on the *Extras* dropdown list and then select 'API Keys'. -5. Scroll down and create a new key by clicking on 'Create a Key' under the 'Your API keys' section. -6. Use the API key with your Mailchimp node credentials in n8n. - -![Getting Mailchimp credentials](/_images/integrations/builtin/credentials/mailchimp/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/mailerlite.md b/docs/integrations/builtin/credentials/mailerlite.md deleted file mode 100644 index 926766e2a..000000000 --- a/docs/integrations/builtin/credentials/mailerlite.md +++ /dev/null @@ -1,20 +0,0 @@ -# MailerLite - -You can use these credentials to authenticate the following nodes with MailerLite. - -- [MailerLite](/integrations/builtin/app-nodes/n8n-nodes-base.mailerLite/) -- [MailerLite Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.mailerLiteTrigger/) - -## Prerequisites - -Create a [MailerLite](https://MailerLite.com) account. - -## Using API Key - -1. Access the [MailerLite](https://app.mailerlite.com/dashboard/) dashboard. -2. Click on the profile icon on the top right corner. -3. Select 'Integrations' from the dropdown list. -4. Click on 'Developer API' in the ***MailerLite API*** section. -5. Copy the ***API key*** that is displayed and use it with your MailerLite node credentials in n8n. - -![Getting MailerLite credentials](/_images/integrations/builtin/credentials/mailerlite/using-api-key.gif) diff --git a/docs/integrations/builtin/credentials/mailgun.md b/docs/integrations/builtin/credentials/mailgun.md deleted file mode 100644 index 45ac517ed..000000000 --- a/docs/integrations/builtin/credentials/mailgun.md +++ /dev/null @@ -1,19 +0,0 @@ -# Mailgun - -You can use these credentials to authenticate the following nodes with Mailgun. - -- [Mailgun](/integrations/builtin/app-nodes/n8n-nodes-base.mailgun/) - -## Prerequisites - -Create a [Mailgun](https://www.mailgun.com/) account. - -## Using Access Token - -1. Access your Mailgun dashboard. -2. Click on Settings on the left panel. -3. Click on API Keys. -4. Click on the eye icon to uncover your API key. -5. Use the API key with Mailgun node credentials in n8n. - -![Getting Mailgun credentials](/_images/integrations/builtin/credentials/mailgun/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/mailjet.md b/docs/integrations/builtin/credentials/mailjet.md deleted file mode 100644 index ce59d239a..000000000 --- a/docs/integrations/builtin/credentials/mailjet.md +++ /dev/null @@ -1,20 +0,0 @@ -# Mailjet - -You can use these credentials to authenticate the following nodes with Mailjet. - -- [Mailjet](/integrations/builtin/app-nodes/n8n-nodes-base.mailjet/) -- [Mailjet Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.mailjetTrigger/) - -## Prerequisites - -Create a [Mailjet](https://www.mailjet.com/) account. - -## Using Access Token - -1. Access your Mailjet dashboard. -2. Click on your user icon in the top right. -3. Click on 'Account Settings'. -4. Under REST API, click on 'Master API Key & Sub API key management'. -5. Use the API key and Secret Key with Mailjet node credentials in n8n. - -![Getting Mailjet credentials](/_images/integrations/builtin/credentials/mailjet/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/mandrill.md b/docs/integrations/builtin/credentials/mandrill.md deleted file mode 100644 index 5922ac7d4..000000000 --- a/docs/integrations/builtin/credentials/mandrill.md +++ /dev/null @@ -1,18 +0,0 @@ -# Mandrill - -You can use these credentials to authenticate the following nodes with Mandrill. - -- [Mandrill](/integrations/builtin/app-nodes/n8n-nodes-base.mandrill/) - -## Prerequisites - -Create a [Mandrill](https://mandrillapp.com/login/) account. - -## Using Access Token - -1. Access your Mandrill dashboard. -2. Click on the Settings icon in the sidebar. -3. Click on the *+ New API Key* button and create a new API Key. -4. Use the key with your Mandrill API credentials in n8n. - -![Getting Mandrill credentials](/_images/integrations/builtin/credentials/mandrill/using-api-key.gif) diff --git a/docs/integrations/builtin/credentials/marketstack.md b/docs/integrations/builtin/credentials/marketstack.md deleted file mode 100644 index e8e2d6ce4..000000000 --- a/docs/integrations/builtin/credentials/marketstack.md +++ /dev/null @@ -1,22 +0,0 @@ -# Marketstack - -You can use these credentials to authenticate the following nodes: - -- [Marketstack](/integrations/builtin/app-nodes/n8n-nodes-base.marketstack/) - -## Prerequisites - -Create an account on [Marketstack](https://marketstack.com/). - -## Using API Key - -From Marketstack: - -1. Access your Marketstack dashboard. -2. Copy the key provided in the ***Your API Access Key*** field. - -From n8n: - -3. Enter a descriptive ***Credentials Name***. -4. Under ***Credential Data***, enter the key obtained above in the corresponding field. -5. Click **Save** to create your new credentials. diff --git a/docs/integrations/builtin/credentials/matrix.md b/docs/integrations/builtin/credentials/matrix.md deleted file mode 100644 index 555018fac..000000000 --- a/docs/integrations/builtin/credentials/matrix.md +++ /dev/null @@ -1,20 +0,0 @@ -# Matrix - -You can use these credentials to authenticate the following nodes with Matrix. - -- [Matrix](/integrations/builtin/app-nodes/n8n-nodes-base.matrix/) - -## Prerequisites - -Create an account on a Matrix server. - -## Using Access Token - -1. Access the Matrix server. -2. Click on your username in the top left corner. -3. Select 'All settings' from the dropdown list. -4. Click on ***Help & About*** in the left sidebar. -5. Scroll down to the ***Advanced*** section. -6. Click on ***click to reveal*** next to 'Access Token'. -7. Copy the 'Homeserver URL' under the ***Advanced*** section if you are using a custom server. -8. Use this Homeserver URL and Access Token with your Matrix node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/mattermost.md b/docs/integrations/builtin/credentials/mattermost.md deleted file mode 100644 index e964991eb..000000000 --- a/docs/integrations/builtin/credentials/mattermost.md +++ /dev/null @@ -1,50 +0,0 @@ -# Mattermost - -You can use these credentials to authenticate the following nodes with Mattermost. - -- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/) - -## Prerequisites - -- Create a [Mattermost](https://www.mattermost.com/) account. - -**Note:** A system administrator has to grant permission to the user to generate an access token. Refer to the [FAQs](#_1-how-to-grant-permissions-to-the-users-to-generate-access-tokens) to learn how a system administrator can grant this permission. - -## Using Access Token - -1. Click on your username on the top left corner and select 'Account Settings' from the dropdown list. -2. Click on the ***Security*** tab. -3. Click on ***Edit*** in the ***Personal Access Tokens*** section. -4. Click on the ***Create Token*** button. -5. Enter a description in the ***Token Description*** field. -6. Click on the ***Save*** button. -7. Click on the ***Yes, Create*** button. -8. Use this ***Acess Token*** with your Mattermost node credentials in n8n. - -![Generating Access Token](/_images/integrations/builtin/credentials/mattermost/using-access-token.gif) - -## FAQs - -### How to grant permissions to the users to generate access tokens? - -A system admin has to grant permissions to the users for the user to create access tokens. If you're a system admin, follow the steps mentioned below. - -1. Click on your username on the top left corner and select 'System Console' from the dropdown list. -2. Click on ***Integration Management*** under the ***INTEGRATIONS*** section on the left sidebar. -3. Go to Integration Management. -4. Scroll down to the ***Enable Personal Access Tokens*** and enable personal access tokens. -5. Click on the ***Save*** button. -6. Click on ***Users*** under the ***USER MANAGEMENT*** section on the left sidebar. -7. Personal access tokens are generated for individual users, so they must be enabled for each user. Click on ***Member*** next to the user you want to grant permission to, and select 'Manage Roles' from the dropdown list. -8. Check the ***Allow this account to generate personal access tokens*** checkbox. -9. Select any additional permissions you want to grant the user and click on the ***Save*** button. - -**Note:** You may also create a bot account and apply the same for it. - -The user can now generate a personal access token by going to their account settings and following the steps mentioned [above](#using-access-token). - -![Granting permission to user](/_images/integrations/builtin/credentials/mattermost/granting-permission.gif) - - - -- [Personal Access Tokens](https://docs.mattermost.com/developer/personal-access-tokens.html) diff --git a/docs/integrations/builtin/credentials/mautic.md b/docs/integrations/builtin/credentials/mautic.md deleted file mode 100644 index 45cad51d8..000000000 --- a/docs/integrations/builtin/credentials/mautic.md +++ /dev/null @@ -1,54 +0,0 @@ -# Mautic - -You can use these credentials to authenticate the following nodes with Mautic. - -- [Mautic](/integrations/builtin/app-nodes/n8n-nodes-base.mautic/) -- [Mautic Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.mauticTrigger/) - -## Prerequisites - -Create an account on a [Mautic](https://www.mautic.org/) instance. - -## Using OAuth - -1. Open your Mautic dashboard. -2. Click on the gear icon on the top right and select ***API Credentials***. -3. Click on the ***+ New*** button on the top right. -4. Select 'OAuth 2' from the ***Authorization Protocol*** dropdown list. -5. Enter the name of the credentials in the ***Name*** field. -6. Copy the 'OAuth Callback URL' provided in the 'Mautic OAuth2 API' credentials in n8n. -7. Paste it in the ***Redirect URI*** field on the Mautic credentials page. -8. Click on the ***Apply*** button. -9. Enter the name for your credentials in the ***Credentials Name*** field in the 'Mautic OAuth2 API' credentials in n8n. -10. Copy the ***Client ID*** from the Mautic credentials page. -11. Paste it in the ***Client ID*** field in the 'Mautic OAuth2 API' credentials in n8n. -12. Copy the ***Client Secret*** from the Mautic credentials page. -13. Paste it in the ***Client Secret*** field in the 'Mautic OAuth2 API' credentials in n8n. -14. Enter the URL of your Mautic instance in the ***URL*** field. -15. Click on the circle button in the OAuth section to connect a Mautic account to n8n. -16. Click on the ***Save*** button to save your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
- -## Using Credentials - -1. Open your Mautic dashboard. -2. Click on the gear icon on the top right and select ***Configuration***. -3. Select 'API Settings' from the left sidebar. -4. Select 'Yes' under the ***Enable HTTP basic auth?*** section. -5. Click on the ***Apply*** button. -6. Enter the name for your credentials in the ***Credentials Name*** field in the 'Mautic API' credentials in n8n. -7. Enter the URL of your Mautic instance in the ***URL*** field in the 'Mautic API' credentials in n8n. -8. Enter your Mautic username in the ***Username*** field in the 'Mautic API' credentials in n8n. -9. Enter your Mautic password in the ***Password*** field in the 'Mautic API' credentials in n8n. -10. Click on the ***Create*** button to create your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/medium.md b/docs/integrations/builtin/credentials/medium.md deleted file mode 100644 index d574a256e..000000000 --- a/docs/integrations/builtin/credentials/medium.md +++ /dev/null @@ -1,42 +0,0 @@ -# Medium - -You can use these credentials to authenticate the following nodes with Medium. - -- [Medium](/integrations/builtin/app-nodes/n8n-nodes-base.medium/) - -## Prerequisites - -- Create an account on [Medium](https://www.medium.com/). -- Request access to credentials by emailing [yourfriends@medium.com](mailto:yourfriends@medium.com). - - -## Using OAuth - -1. Log in to your Medium account. -2. Click on the avatar on the top right corner. -3. Select '[Settings](https://medium.com/me/settings)' in the drop-down menu. -4. Select 'Developers' from the menu on the left. -5. Click on the 'Manage applications' button. -6. Click on the 'New application' button. -7. Give your application a Name, and provide a Description. -8. Select the 'OAuth 2' option from the *Authorization Protocol* dropdown list. -9. Copy the 'OAuth Callback URL' provided in the Medium OAuth2 API credentials in n8n and paste it in the 'Callback URLs' field in the Medium application page. -10. Click on 'Save' to generate the credentials. -11. Copy and paste ***Client ID*** and ***Client Secret*** in the Medium OAuth2 API credentials in n8n. -12. Click on the circle button in the OAuth section to connect a Medium account to n8n. -13. Click the ***Save*** button to save your credentials in n8n. - -![Getting Medium OAuth credentials](/_images/integrations/builtin/credentials/medium/using-oauth.gif) - -## Using Access Token - -1. Log in to your Medium account. -2. Click on the avatar on the top right corner. -3. Select '[Settings](https://medium.com/me/settings)' in the drop-down menu. -4. Select 'Integration tokens' from the menu on the left. -5. Enter a description for your token in the field. -6. Click on the 'Get integration token' button. -7. Copy and paste ***Token*** in the Medium API credentials in n8n. -8. Click the ***Save*** button to save your credentials in n8n. - -![Getting Medium Access Token](/_images/integrations/builtin/credentials/medium/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/messagebird.md b/docs/integrations/builtin/credentials/messagebird.md deleted file mode 100644 index ecbb7fbe0..000000000 --- a/docs/integrations/builtin/credentials/messagebird.md +++ /dev/null @@ -1,19 +0,0 @@ -# MessageBird - -You can use these credentials to authenticate the following nodes with MessageBird. - -- [MessageBird](/integrations/builtin/app-nodes/n8n-nodes-base.messageBird/) - -## Prerequisites - -Create a [MessageBird](https://www.messagebird.com/en/) account. - -## Using Access Token - -1. Access your MessageBird dashboard. -2. Go to the [Developers section](https://dashboard.messagebird.com/en/developers/access). -3. Click on API access. -4. Click on 'Add access key' and create a new API key. -5. Use this API key with your MessageBird API node credentials in n8n. - -![Getting MessageBird API credentials](/_images/integrations/builtin/credentials/messagebird/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/metabase.md b/docs/integrations/builtin/credentials/metabase.md deleted file mode 100644 index 31516f8b3..000000000 --- a/docs/integrations/builtin/credentials/metabase.md +++ /dev/null @@ -1,8 +0,0 @@ -# Metabase - -You can use these credentials to authenticate the [Metabase node](/integrations/builtin/app-nodes/n8n-nodes-base.metabase/). - -To connect to Metabase, enter your Metabase username, password, and the base URL of your Metabase instance. - - - diff --git a/docs/integrations/builtin/credentials/microsoft.md b/docs/integrations/builtin/credentials/microsoft.md deleted file mode 100644 index a4a76e213..000000000 --- a/docs/integrations/builtin/credentials/microsoft.md +++ /dev/null @@ -1,47 +0,0 @@ -# Microsoft - -You can use these credentials to authenticate the following nodes with Microsoft. - -- [Microsoft Dynamics CRM](/integrations/builtin/app-nodes/n8n-nodes-base.microsoftDynamicsCrm/) -- [Microsoft Excel](/integrations/builtin/app-nodes/n8n-nodes-base.microsoftExcel/) -- [Microsoft Graph Security](/integrations/builtin/app-nodes/n8n-nodes-base.microsoftGraphSecurity/) -- [Microsoft OneDrive](/integrations/builtin/app-nodes/n8n-nodes-base.microsoftOneDrive/) -- [Microsoft Outlook](/integrations/builtin/app-nodes/n8n-nodes-base.microsoftOutlook/) -- [Microsoft Teams](/integrations/builtin/app-nodes/n8n-nodes-base.microsoftTeams/) -- [Microsoft To Do](/integrations/builtin/app-nodes/n8n-nodes-base.microsoftToDo/) - -## Prerequisites - -Create a [Microsoft Azure](https://azure.microsoft.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Microsoft account to n8n. - - -1. Access the [Microsoft Application Registration Portal](https://aka.ms/appregistrations). -2. Click on the ***Register an application*** button. -3. Enter a name for your app in the ***Name*** field. -4. Select 'Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (eg. Skype, Xbox)' under the ***Supported account types*** section. -5. Copy the 'OAuth Callback URL' provided in the Microsoft node credentials in n8n. -6. Paste it in the ***Redirect URI (optional)*** field on the ***Register an application*** page. -7. Click on the ***Register*** button. -8. Copy the ***Application (client) ID***. -9. Enter the name for your credentials in the ***Credentials Name*** field in the Microsoft node credentials in n8n. -10. Paste the Application ID in the ***Client ID*** field in the Microsoft node credentials in n8n. -11. On your Microsoft application page, click on ***Certificates & secrets*** in the left sidebar. -12. Click on the ***+ New client secret*** button under the ***Client secrets*** section. -13. Enter a description in the ***Description*** field. -14. Click on the ***Add*** button. -15. Copy the displayed secret under the ***Value*** column. -16. Paste the secret in the ***Client Secret*** field in the Microsoft node credentials in n8n. -17. Click on the circle button in the OAuth section to connect a Microsoft account to n8n. -18. Login to your Microsoft account and allow the app to access your info. -19. Click on the ***Save*** button in the Microsoft node credentials in n8n to save your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/microsoftsql.md b/docs/integrations/builtin/credentials/microsoftsql.md deleted file mode 100644 index 8049d1f61..000000000 --- a/docs/integrations/builtin/credentials/microsoftsql.md +++ /dev/null @@ -1,14 +0,0 @@ -# Microsoft SQL - -You can use these credentials to authenticate the following nodes with Microsoft SQL. - -- [Microsoft SQL](/integrations/builtin/app-nodes/n8n-nodes-base.microsoftSQL/) - -## Prerequisites - -Create an user account on a Microsoft SQL server. - -## Using Database Connection - -1. Retrieve your Microsoft SQL credentials and connection parameters. -2. Use the credentials and connection parameters with your Microsoft SQL node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/mindee.md b/docs/integrations/builtin/credentials/mindee.md deleted file mode 100644 index c955d6bb8..000000000 --- a/docs/integrations/builtin/credentials/mindee.md +++ /dev/null @@ -1,22 +0,0 @@ -# Mindee - -You can use these credentials to authenticate the following nodes with Mindee. - -- [Mindee](/integrations/builtin/app-nodes/n8n-nodes-base.mindee/) - -## Prerequisites - -Create a [Mindee](https://mindee.com) account. - -## Using API Key - -1. Access the [Mindee APIs Hub](https://platform.mindee.net/apishub). -2. Click on the API card that you want to use. -3. Click on the ***Try for free*** button under the ***Pricing*** section. -4. Click on ***API Keys*** in the left sidebar. -5. Click on the ***Add key*** button. -6. Enter a name for the token. -7. Click on ***Add new key***. -8. Use this API key with your Mindee node credentials in n8n. - -![Getting Mindee credentials](/_images/integrations/builtin/credentials/mindee/using-api-key.gif) diff --git a/docs/integrations/builtin/credentials/misp.md b/docs/integrations/builtin/credentials/misp.md deleted file mode 100644 index 3489d2ebe..000000000 --- a/docs/integrations/builtin/credentials/misp.md +++ /dev/null @@ -1,21 +0,0 @@ -# MISP - -You can use these credentials to authenticate the following nodes: - -- [MISP](/integrations/builtin/app-nodes/n8n-nodes-base.misp/) - -## Prerequisites - -Install and run a [MISP](https://misp.github.io/MISP/) instance. - -## Using API Key - -From your MISP UI: -1. Navigate to the **Event Actions** > **Automation** menu. -2. Copy the API Key provided there. - -From n8n: - -3. Enter your API key and application Base URL. -4. Use the toggle to select if you want to **Allow Unauthorized Certificates**. -5. Click **Save** to create your credentials. diff --git a/docs/integrations/builtin/credentials/mocean.md b/docs/integrations/builtin/credentials/mocean.md deleted file mode 100644 index 6c2798d75..000000000 --- a/docs/integrations/builtin/credentials/mocean.md +++ /dev/null @@ -1,17 +0,0 @@ -# Mocean - -You can use these credentials to authenticate the following nodes with Mocean. - -- [Mocean](/integrations/builtin/app-nodes/n8n-nodes-base.mocean/) - -## Prerequisites - -Create a [Mocean](https://dashboard.moceanapi.com/register?fr=n8n) account. - -## Using Access Token - -1. Access your Mocean Dashboard. -2. Your API key and secret will be visible. -3. Use the API key and secret in your Mocean node credentials in n8n. - -![Getting Mocean credentials](/_images/integrations/builtin/credentials/mocean/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/mondaycom.md b/docs/integrations/builtin/credentials/mondaycom.md deleted file mode 100644 index fac074331..000000000 --- a/docs/integrations/builtin/credentials/mondaycom.md +++ /dev/null @@ -1,18 +0,0 @@ -# monday.com - -You can use these credentials to authenticate the following nodes with monday.com. - -- [monday.com](/integrations/builtin/app-nodes/n8n-nodes-base.mondayCom/) - -## Prerequisites - -Create a [monday.com](https://monday.com/) account. - -## Using Access Token -1. Access your monday.com dashboard. -2. Click on the user icon in the bottom left. -3. Click on Admin. -4. Click on API and generate an API V2 Token. -5. Use the token in your monday.com node credentials in n8n. - -![Getting Monday.com credentials](/_images/integrations/builtin/credentials/mondaycom/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/mongodb.md b/docs/integrations/builtin/credentials/mongodb.md deleted file mode 100644 index 20998d1c7..000000000 --- a/docs/integrations/builtin/credentials/mongodb.md +++ /dev/null @@ -1,14 +0,0 @@ -# MongoDB - -You can use these credentials to authenticate the following nodes with MongoDB. - -- [MongoDB](/integrations/builtin/app-nodes/n8n-nodes-base.mongoDb/) - -## Prerequisites - -Create an user account with the appropriate permissions on a MongoDB server. - -## Using Access Token - -1. Retrieve your MongoDB credentials and connection parameters. -2. Use the credentials and connection parameters with your MongoDB node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/monicacrm.md b/docs/integrations/builtin/credentials/monicacrm.md deleted file mode 100644 index c520c0090..000000000 --- a/docs/integrations/builtin/credentials/monicacrm.md +++ /dev/null @@ -1,26 +0,0 @@ -# Monica CRM - -You can use these credentials to authenticate the following nodes: - -- [Monica CRM](/integrations/builtin/app-nodes/n8n-nodes-base.monicaCrm/) - -## Prerequisites - -Sign up for a [Monica CRM](https://www.monicahq.com/) account or self-host an instance. - -## Using Access Token - -From Monica CRM: - -1. Access your dashboard and navigate to the ***Settings** menu. -2. From the ***API*** tab select **Create New Token**. -3. Enter a name for your new token and click **Create**. -4. Copy the access token that is displayed in the popup window. - -From n8n: - -5. Enter a descriptive ***Credentials Name***. -6. From the ***Credential Data*** section, select your environment type: **Cloud-hosted** or **Self-hosted**. -7. (Self-hosted Only) Enter the domain of your Monica CRM instance. -8. In the ***API Token** field enter the token created above. -9. Click **Create** to save your new credentials. diff --git a/docs/integrations/builtin/credentials/mqtt.md b/docs/integrations/builtin/credentials/mqtt.md deleted file mode 100644 index 3dd0eea82..000000000 --- a/docs/integrations/builtin/credentials/mqtt.md +++ /dev/null @@ -1,16 +0,0 @@ -# MQTT - -You can use these credentials to authenticate the following nodes with MQTT. - -- [MQTT](/integrations/builtin/app-nodes/n8n-nodes-base.mqtt/) -- [MQTT Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.mqttTrigger/) - -## Prerequisites - -You need to have a MQTT broker installed. - -## Using MQTT - -Use your Protocol, Host, Port, Username, and Password as the MQTT Trigger credential data in n8n. - -Optionally, you can enable SSL and provide a CA or Client certificate. diff --git a/docs/integrations/builtin/credentials/msg91.md b/docs/integrations/builtin/credentials/msg91.md deleted file mode 100644 index ff2c69fca..000000000 --- a/docs/integrations/builtin/credentials/msg91.md +++ /dev/null @@ -1,18 +0,0 @@ -# MSG91 - -You can use these credentials to authenticate the following nodes with MSG91. - -- [MSG91](/integrations/builtin/app-nodes/n8n-nodes-base.msg91/) - -## Prerequisites - -Create a [MSG91](https://msg91.com/) account. - -## Using Access Token -1. Login to your account. -2. Click on the dashboard button on the lop left. -3. Click on 'Developer Platform'. -3. Click on 'Authkey' in the left panel. -4. Click on *Create New*. -5. Enter the details and click on the *Add* button. -6. Use the token in your MSG91 node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/mysql.md b/docs/integrations/builtin/credentials/mysql.md deleted file mode 100644 index 4e4c12849..000000000 --- a/docs/integrations/builtin/credentials/mysql.md +++ /dev/null @@ -1,16 +0,0 @@ -# MySQL - -You can use these credentials to authenticate the following nodes with MySQL. - -- [MySQL](/integrations/builtin/app-nodes/n8n-nodes-base.mySql/) - -## Prerequisites - -Create an user account on a MySQL server. - -## Using Database Connection - -1. Retrieve your MySQL credentials and connection parameters. -2. Use the credentials and connection parameters with your MySQL node credentials in n8n. - -![Getting MySQL credentials](/_images/integrations/builtin/credentials/mySql/using-database-connection.gif) diff --git a/docs/integrations/builtin/credentials/nasa.md b/docs/integrations/builtin/credentials/nasa.md deleted file mode 100644 index 6b176c94a..000000000 --- a/docs/integrations/builtin/credentials/nasa.md +++ /dev/null @@ -1,15 +0,0 @@ -# NASA - -You can use these credentials to authenticate the following nodes with NASA. - -- [NASA](/integrations/builtin/app-nodes/n8n-nodes-base.nasa/) - -## Using an API key - -1. Access the [NASA Open APIs](https://api.nasa.gov/) page. -2. Scroll down to the **Generate API Key** section. -3. Enter the required information. -3. Click on the **Signup** button. -4. Use this **API Key** with your NASA node credentials in n8n. - -![Getting NASA credentials](/_images/integrations/builtin/credentials/nasa/using-api.gif) diff --git a/docs/integrations/builtin/credentials/netlify.md b/docs/integrations/builtin/credentials/netlify.md deleted file mode 100644 index 86d2d1550..000000000 --- a/docs/integrations/builtin/credentials/netlify.md +++ /dev/null @@ -1,23 +0,0 @@ -# Netlify - -You can use these credentials to authenticate the following nodes: - -- [Netlify](/integrations/builtin/app-nodes/n8n-nodes-base.netlify/) -- [Netlify Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.netlifyTrigger/) - -## Prerequisites - -Create a [Netlify](https://netlify.com/) account. - -## Using Access Token - -From the Netlify UI: - -1. Navigate to **User Settings** > **Personal Access Tokens**. -2. Select **New access token**. -3. Enter a description and select **Generate token**. - -From n8n: - -4. Enter the access token obtained above. -5. Click **Save** to create your credentials. diff --git a/docs/integrations/builtin/credentials/nextcloud.md b/docs/integrations/builtin/credentials/nextcloud.md deleted file mode 100644 index 94a48870c..000000000 --- a/docs/integrations/builtin/credentials/nextcloud.md +++ /dev/null @@ -1,29 +0,0 @@ -# Nextcloud - -You can use these credentials to authenticate the following nodes with Nextcloud. - -- [Nextcloud](/integrations/builtin/app-nodes/n8n-nodes-base.nextCloud/) - -## Prerequisites - -Create a [Nextcloud](https://nextcloud.com/) account. - -## Using OAuth - -1. Log in to your Nextcloud account. -2. Click on the user icon in the top right. -3. Select 'Settings' in the drop down menu. -4. Click on 'Security' under Administration in the sidebar. -5. Copy the 'OAuth Callback URL' provided in the Nextcloud OAuth2 API credentials in n8n and paste it in the *Redirection URI* field under the 'OAuth 2.0 clients' section in the Nextcloud page. -6. Fill out any other information that is necessary and click on the 'Add' button. -7. Click on the eye icon to reveal the Secret and use the 'Client Identifier' and the 'Secret' with your Nextcloud OAuth2 API credentials in n8n. -8. Replace your domain in the samples for the *Authorization URL* and *Access Token URL* fields. -9. Enter your [Web DAV URL](https://docs.nextcloud.com/server/stable/user_manual/en/files/access_webdav.html) in the *Web DAV URL* field. -10. Click on the circle button in the OAuth section to connect a Nextcloud account to n8n. -11. Click the *Save* button to save your credentials. - -![Getting Nextcloud OAuth credentials](/_images/integrations/builtin/credentials/nextcloud/using-oauth.gif) - -## Using Username and Password - -Use your [Web DAV URL](https://docs.nextcloud.com/server/stable/user_manual/en/files/access_webdav.html) along with your Nextcloud username and password in the node credentials. diff --git a/docs/integrations/builtin/credentials/nocodb.md b/docs/integrations/builtin/credentials/nocodb.md deleted file mode 100644 index e917bb725..000000000 --- a/docs/integrations/builtin/credentials/nocodb.md +++ /dev/null @@ -1,38 +0,0 @@ -# NocoDB - -You can use these credentials to authenticate the following nodes: - -- [NocoDB](/integrations/builtin/app-nodes/n8n-nodes-base.nocoDb/) - -## Prerequisites - -* Install [NocoDB](https://www.nocodb.com/) -* Optional: Enable [API Access](https://docs.nocodb.com/developer-resources/api-tokens) - -## Using Auth Token - -From NocoDB Project: - -1. Click the rightmost button and click **Copy auth token**. - -![NocoDB Auth](/_images/integrations/builtin/app-nodes/nocodb/xc-auth.png) - -From n8n: - -1. Enter a descriptive **Credentials Name**. -2. In the **Credentials Data** section enter the following: - * **API Token**: The authentication token for your NocoDB project. - * **Host**: The host of your NocoDB instance, for example `http://localhost:8080`. -3. Click **Create** to save your new credentials. - -## Using API Token - -From NocoDB Project: Enable [API Access](https://docs.nocodb.com/developer-resources/api-tokens) - -From n8n: - -1. Enter a descriptive **Credentials Name**. -2. In the ***Credentials Data*** section enter the following: - * ***API Token***: The authentication token for your NocoDB project, obtained when enabling API access (above). - * ***Host***: The host of your NocoDB instance, for example `http://localhost:8080`. -3. Click **Create** to save your new credentials. diff --git a/docs/integrations/builtin/credentials/notion.md b/docs/integrations/builtin/credentials/notion.md deleted file mode 100644 index 6699d44e4..000000000 --- a/docs/integrations/builtin/credentials/notion.md +++ /dev/null @@ -1,33 +0,0 @@ -# Notion - -You can use these credentials to authenticate the following nodes with Notion. - -- [Notion](/integrations/builtin/app-nodes/n8n-nodes-base.notion/) -- [Notion Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.notionTrigger/) - -## Prerequisites - -Create a [Notion](https://notion.so) account. - -## Using API Key - -1. Open your Notion [workspace](https://notion.so/). -2. Click on ***Settings & Members*** in the left-sidebar. -3. Select ***Integrations*** and click on ***Develop your own integrations***. -4. Click on the ***+ New integration*** button or the ***Create new integration*** card. -5. Enter a name for your app in the ***Name*** field. -6. Select a workspace to install the integration from the ***Associated workspace*** dropdown list. -7. Click on the ***Submit*** button. -8. Click on ***Show*** next to the ***Internal Integration Token*** field. -9. Click on ***Copy*** to copy the displayed token. -10. Enter the name for your credentials in the ***Credentials Name*** field in the 'Notion API' credentials in n8n. -11. Paste the token in the ***API Key*** field in the 'Notion API' credentials in n8n. -12. Click on the ***Create*** button to create your credentials. - -**Note:** Share the specific pages with the app for those pages to be accessed using the API. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/odoo.md b/docs/integrations/builtin/credentials/odoo.md deleted file mode 100644 index 117d9651b..000000000 --- a/docs/integrations/builtin/credentials/odoo.md +++ /dev/null @@ -1,16 +0,0 @@ -# Odoo credentials - -You can use these credentials to authenticate the following nodes with Odoo: - -- [Odoo](/integrations/builtin/app-nodes/n8n-nodes-base.odoo/) - -1. Sign up for Odoo and create an API key or password. Refer to Odoo's documentation for more information: [External API](https://www.odoo.com/documentation/15.0/developer/misc/api/odoo.html). Note that some Odoo modules and settings require API keys, not passwords. -2. In n8n, create a new credential. You can either: - * Click **Credentials** > **New**, then search for **Odoo API**. After selecting **Odoo API**, click **Continue**. - * In an Odoo node, click the **Credential for Odoo API** dropdown, then click **Create new**. -3. Enter your Odoo information: - * **Site URL**: the domain of your Odoo instance. - * **Username**: username as displayed on the user's **Change password** screen in Odoo. - * **Database name**: the name of the Odoo instance. - * **Password or API key**: the credential you created in step one. -4. Click **Save**. n8n tests the key to check it can connect to Odoo. diff --git a/docs/integrations/builtin/credentials/onesimpleapi.md b/docs/integrations/builtin/credentials/onesimpleapi.md deleted file mode 100644 index 377a68ae3..000000000 --- a/docs/integrations/builtin/credentials/onesimpleapi.md +++ /dev/null @@ -1,21 +0,0 @@ -# One Simple API - -You can use these credentials to authenticate the following nodes with Nextcloud. - -- [One Simple API](/integrations/builtin/app-nodes/n8n-nodes-base.oneSimpleApi/) - -## Prerequisites - -Create a [One Simple API](https://onesimpleapi.com/register) account. - -## Using an API Token - -1. [Log in](https://onesimpleapi.com/login) to your One Simple API account. -2. Create a new API token on the [API Tokens](https://onesimpleapi.com/user/api-tokens) page. -3. Check the required permissions for your new API token. -4. Click the **Create** button. -5. Copy the API token provided by One Simple API. -![The API token shown on the One Simple API website](/_images/integrations/builtin/credentials/onesimpleapi/one_simple_api_website.png) -6. Paste the API token into the API Token field of n8n. -![The API token field in n8n](/_images/integrations/builtin/credentials/onesimpleapi/one_simple_api_n8n_credentials.png) -7. Click the **Save** button. diff --git a/docs/integrations/builtin/credentials/onfleet.md b/docs/integrations/builtin/credentials/onfleet.md deleted file mode 100644 index e02f0783d..000000000 --- a/docs/integrations/builtin/credentials/onfleet.md +++ /dev/null @@ -1,16 +0,0 @@ -# Onfleet credentials - -You can use these credentials to authenticate the following nodes with Onfleet: - -- [Onfleet](/integrations/builtin/app-nodes/n8n-nodes-base.onfleet/) -- [Onfleet Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.onfleetTrigger/) - -1. Sign up for Onfleet and create an API key. Refer to Onfleet's documentation for more information: - * [Creating an API key](https://support.onfleet.com/hc/en-us/articles/360045763292-API) - * [Getting started with the Onfleet API](https://docs.onfleet.com/reference#setup-tutorial) -2. In n8n, create a new credential. You can either: - * Click **Credentials** > **New**, then search for **Onfleet API**. After selecting **Onfleet API**, click **Continue**. - * In an Onfleet node, click the **Credential for Onfleet API** dropdown, then click **Create new**. -3. In the **Onfleet account** modal, paste your Onfleet API key into **API key**. -4. By default, this credential is available to both the Onfleet and Onfleet Trigger nodes. You can change this using the settings on the **Details** tab. -5. After entering the key and editing the credential details, click **Save**. n8n tests the key to check it can connect to Onfleet. diff --git a/docs/integrations/builtin/credentials/openweathermap.md b/docs/integrations/builtin/credentials/openweathermap.md deleted file mode 100644 index 5ce04a98b..000000000 --- a/docs/integrations/builtin/credentials/openweathermap.md +++ /dev/null @@ -1,18 +0,0 @@ -# OpenWeatherMap - -You can use these credentials to authenticate the following nodes with OpenWeatherMap. - -- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/) - -## Prerequisites - -Create a [OpenWeatherMap](https://openweathermap.org/) account. - -## Using Access Token - -1. Access your OpenWeatherMap [account page](https://home.openweathermap.org/api_keys). -2. In the 'Create key' section, type a name and click on the *Generate* button. -3. Copy the API Key that you just generated. -4. Use this API key with your OpenWeatherMap API node credentials in n8n. - -![Getting OpenWeatherMap API credentials](/_images/integrations/builtin/credentials/openweathermap/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/orbit.md b/docs/integrations/builtin/credentials/orbit.md deleted file mode 100644 index bfd64612a..000000000 --- a/docs/integrations/builtin/credentials/orbit.md +++ /dev/null @@ -1,22 +0,0 @@ -# Orbit - -You can use these credentials to authenticate the following nodes with Orbit. - -- [Orbit](/integrations/builtin/app-nodes/n8n-nodes-base.orbit/) - -## Prerequisites - -Create an [Orbit](https://app.orbit.love/) account. - -## Using API Token - -1. Access the [Account Settings page](https://app.orbit.love/user/edit). -2. Scroll down to the ***API Token*** section. -3. Click on the ***Copy*** button to copy the API Token. -4. Use this ***API Token*** in with your Orbit node credentials in n8n. - -![Getting Orbit credentials](/_images/integrations/builtin/credentials/orbit/using-api.gif) - -## Further Reference - -- [Orbit API Documentation](https://www.notion.so/Orbit-API-Documentation-41ed7911e070400b99cfebb296813670#cb4111e0436e420c8c05af078496ff30) diff --git a/docs/integrations/builtin/credentials/oura.md b/docs/integrations/builtin/credentials/oura.md deleted file mode 100644 index a4b409656..000000000 --- a/docs/integrations/builtin/credentials/oura.md +++ /dev/null @@ -1,24 +0,0 @@ -# Oura - -You can use these credentials to authenticate the following nodes with Oura. - -- [Oura](/integrations/builtin/app-nodes/n8n-nodes-base.oura/) - -## Prerequisites - -Create a [Oura](https://www.ouraring.com/) account. - -## Using Access Token - -1. Open the [Personal Access Tokens](https://cloud.ouraring.com/personal-access-tokens) page. -2. On the top-right corner of the page, click on the ***Create A New Personal Access Token*** button. -3. Enter a note for the new Personal Access Token you are about to generate. -4. Click on the ***Create Personal Access Token*** to create the Personal Access Token. -5. Copy the displayed Personal Access Token. -6. Enter a name for your credentials in the ***Credentials Name*** field in the 'Oura API' credentials in n8n. -7. Paste the Personal Access Token in the ***Personal Access Token*** field in the 'Oura API' credentials in n8n. -8. Click on the ***Create*** button to create your credentials. - - - -- [Oura API Documentation](https://cloud.ouraring.com/docs/authentication) diff --git a/docs/integrations/builtin/credentials/paddle.md b/docs/integrations/builtin/credentials/paddle.md deleted file mode 100644 index 732da5386..000000000 --- a/docs/integrations/builtin/credentials/paddle.md +++ /dev/null @@ -1,20 +0,0 @@ -# Paddle - -You can use these credentials to authenticate the following nodes with Paddle. - -- [Paddle](/integrations/builtin/app-nodes/n8n-nodes-base.paddle/) - -## Prerequisites - -Create a [Paddle](https://paddle.com/) account. - -## Using Access Token - -1. Open your Paddle dashboard. -2. Open the ***Developer Tools*** dropdown list in the sidebar and select ***Authentication***. -3. Enter a name and description in the ***Generate Auth Code*** section and click on ***Generate Key***. -4. Click on the ***Reveal Auth Code*** button to reveal the access token. -5. Use the displayed ***vendor_id*** and ***Auth Code*** with your Paddle API credentials in n8n. -6. Click on the ***Save*** button to save your credentials. - -![Getting Paddle credentials](/_images/integrations/builtin/credentials/paddle/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/pagerduty.md b/docs/integrations/builtin/credentials/pagerduty.md deleted file mode 100644 index 428f8ad84..000000000 --- a/docs/integrations/builtin/credentials/pagerduty.md +++ /dev/null @@ -1,40 +0,0 @@ -# PagerDuty - -You can use these credentials to authenticate the following nodes with PagerDuty. - -- [PagerDuty](/integrations/builtin/app-nodes/n8n-nodes-base.pagerDuty/) - -## Prerequisites - -Create a [PagerDuty](https://pagerduty.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your PagerDuty account to n8n. - - -1. Access your PagerDuty dashboard. -2. Select 'Developer Mode' from the number pad icon in the top right. -3. Click on the ***Create New App*** button. -4. Enter a name in the ***App Name*** field, and a description in the ***Brief Description*** field. -5. Select 'Infrastructure Automation' from the ***Category*** dropdown list. -6. Choose the appropriate option for the publication of your app and click on the ***Save*** button. -7. Click on the ***Add*** button in the 'OAuth 2.0' section. -8. Copy the 'OAuth Callback URL' provided in the 'PagerDuty OAuth2 API' credentials in n8n and paste it in the ***Redirect URL*** field in the PagerDuty app creation page. -9. Use the provided ***Client ID*** and ***Client Secret*** with your PagerDuty OAuth2 API credentials in n8n. -10. Select 'Read/Write' from the ***Set Permission Scopes*** dropdown list and then click on ***Save***. -11. Click on the circle button in the OAuth section of n8n to connect a PagerDuty account to n8n. -12. Click on the ***Save*** button to save your credentials. - -![Getting PagerDuty OAuth credentials](/_images/integrations/builtin/credentials/pagerduty/using-oauth.gif) - -## Using Access Token - -1. Access your PagerDuty dashboard. -2. Click on configuration. -3. Click on API access. -4. Create a new API key. -5. Use this API key with your PagerDuty node credentials in n8n. - -![Getting PagerDuty credentials](/_images/integrations/builtin/credentials/pagerduty/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/paypal.md b/docs/integrations/builtin/credentials/paypal.md deleted file mode 100644 index 85b4420fe..000000000 --- a/docs/integrations/builtin/credentials/paypal.md +++ /dev/null @@ -1,23 +0,0 @@ -# PayPal - -You can use these credentials to authenticate the following nodes with PayPal. - -- [PayPal](/integrations/builtin/app-nodes/n8n-nodes-base.payPal/) -- [PayPal Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.payPalTrigger/) - -## Prerequisites - -Create a [PayPal](https://paypal.com/) account. - -## Using OAuth - -1. Access your [PayPal dashboard](https://developer.paypal.com/developer/applications/). -2. Click on *Log in to Dashboard*. -3. Enter your PayPal account credentials. -4. In the section 'REST API apps', click on *Create app*. -5. Enter a name for your app in *App Name* and click on *Create App*. -6. Return to n8n and enter the Client ID and Client Secret in your PayPal API credentials. -7. Choose the environment: sandbox or live. - -![Getting PayPal credentials](/_images/integrations/builtin/credentials/paypal/using-oauth.gif) - diff --git a/docs/integrations/builtin/credentials/peekalink.md b/docs/integrations/builtin/credentials/peekalink.md deleted file mode 100644 index 1233353c1..000000000 --- a/docs/integrations/builtin/credentials/peekalink.md +++ /dev/null @@ -1,23 +0,0 @@ -# Peekalink - -You can use these credentials to authenticate the following nodes with Peekalink. - -- [Peekalink](/integrations/builtin/app-nodes/n8n-nodes-base.peekalink/) - -## Prerequisites - -Create a [Peekalink](https://www.peekalink.io/) account. - -## Using API Key - -1. Open your [Peekalink](https://www.peekalink.io/app/overview) dashboard. -2. Copy the API key displayed under the ***Your API Key*** section. -3. Enter a name for your credentials in the ***Credentials Name*** field in the 'Peekalink API' credentials in n8n. -4. Paste the API key in the ***API Key*** field in the 'Peekalink API' credentials in n8n. -5. Click on the ***Create*** button to create your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/phantombuster.md b/docs/integrations/builtin/credentials/phantombuster.md deleted file mode 100644 index 610e6eef9..000000000 --- a/docs/integrations/builtin/credentials/phantombuster.md +++ /dev/null @@ -1,19 +0,0 @@ -# Phantombuster - -You can use these credentials to authenticate the following nodes with Phantombuster. - -- [Phantombuster](/integrations/builtin/app-nodes/n8n-nodes-base.phantombuster/) - -## Prerequisites - -Create a [Phantombuster](https://www.phantombuster.com/) account. - -## Using API - -1. Access your [Phantombuster](https://phantombuster.com/) dashboard. -2. Click on your name on the top right and select 'Org settings'. -3. Scroll down to the ***Third party API keys*** section. -4. Click on the ***+ Add third party API key*** button. -5. Use this ***API Key*** with your Phantombuster node credentials in n8n. - -![Getting Phantombuster credentials](/_images/integrations/builtin/credentials/phantombuster/using-api.gif) diff --git a/docs/integrations/builtin/credentials/philipshue.md b/docs/integrations/builtin/credentials/philipshue.md deleted file mode 100644 index 72388e135..000000000 --- a/docs/integrations/builtin/credentials/philipshue.md +++ /dev/null @@ -1,23 +0,0 @@ -# Philips Hue - -You can use these credentials to authenticate the following nodes with Philips Hue. - -- [Philips Hue](/integrations/builtin/app-nodes/n8n-nodes-base.philipsHue/) - -## Prerequisites - -Create a [Philips Hue Developer](https://developers.meethue.com/) account. - -## Using OAuth - -1. Access the [Add new Hue Remote API app](https://developers.meethue.com/add-new-hue-remote-api-app/) page. -2. Enter a name in the ***App name*** field. -3. Enter a description in the ***Application description*** field. -4. Copy the 'OAuth Callback URL' provided in the Philips Hue OAuth2 API credentials in n8n and paste it in the ***Callback URL*** field in the *Add new Hue Remote API app* page. -5. Click on the ***Submit*** button. -6. Click on the ***AppId*** to reveal the credentials. -7. Use the displayed ***AppId***, ***ClientId*** and the ***ClientSecret*** with your Philips Hue OAuth2 API credentials in n8n. -8. Click on the circle button in the OAuth section to connect a Philips Hue account to n8n. -9. Click the ***Save*** button to save your credentials in n8n. - -![Getting Philips Hue credentials](/_images/integrations/builtin/credentials/philipshue/using-oauth.gif) diff --git a/docs/integrations/builtin/credentials/pipedrive.md b/docs/integrations/builtin/credentials/pipedrive.md deleted file mode 100644 index 2ed10b84c..000000000 --- a/docs/integrations/builtin/credentials/pipedrive.md +++ /dev/null @@ -1,61 +0,0 @@ -# Pipedrive - -You can use these credentials to authenticate the following nodes with Pipedrive. - -- [Pipedrive](/integrations/builtin/app-nodes/n8n-nodes-base.pipedrive/) -- [Pipedrive Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.pipedriveTrigger/) - -## Prerequisites - -Create a [Pipedrive](https://pipedrive.com/) account. - -## Using OAuth - - - -1. Create a [Developer Sandbox Account](https://pipedrive.readme.io/docs/developer-sandbox-account). -2. Open your Pipedrive Dashboard. -3. Click on your user profile in the top right and select 'Tools and integrations' from the dropdown list. -4. From the sidebar under the ***Tools*** section, select 'Marketplace manager'. -5. Click on the ***Create new app*** button. -6. Select either 'Yes' or 'No' when asked if you would like to publish your app on the Pipedrive marketplace. -7. Click on the ***Next*** button. -8. Enter the name of the app in the ***App name*** field. -9. Copy the 'OAuth Callback URL' provided in the 'Pipedrive OAuth2 API' credentials in n8n. -10. On the Pipedrive app creation page, scroll down to the ***OAuth & Access scopes*** section and paste the URL in the ***Callback URL*** field. -11. Based on your use-case, select the scopes from the ***Access scopes*** section. -12. Scroll up and click on the ***Save*** button on the top. -13. Select your app from the 'Marketplace manager' -14. Scroll down to ***OAuth & Access scopes*** section and copy the ***Client ID***. -15. Enter the name for your credentials in the ***Credentials Name*** field in the 'Pipedrive OAuth2 API' credentials in n8n. -16. Paste the client ID in the ***Client ID*** field in the 'Pipedrive OAuth2 API' credentials in n8n. -17. On the Pipedrive application page, click on the ***Show*** button next to ***Client Secret***. -18. Copy the ***Client Secret***. -19. Paste the client secret in the ***Client Secret*** field in the 'Pipedrive OAuth2 API' credentials in n8n. -20. Click on the circle button in the OAuth section to connect a Pipedrive account to n8n. -21. Click on the ***Save*** button to save your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
- -## Using API Token - -1. Open your Pipedrive Dashboard. -2. Click on your user profile in the top right. -3. Select 'Personal preferences' from the dropdown list. -4. Click on the ***API*** tab. -5. Click on the ***Copy*** button to copy the API Token. -6. Enter the name for your credentials in the ***Credentials Name*** field in the 'Pipedrive API' credentials in n8n. -7. Paste the API token in the ***API Token*** field in the 'Pipedrive API' credentials in n8n. -8. Click on the ***Create*** button to save your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/plivo.md b/docs/integrations/builtin/credentials/plivo.md deleted file mode 100644 index c1bf00fa0..000000000 --- a/docs/integrations/builtin/credentials/plivo.md +++ /dev/null @@ -1,25 +0,0 @@ -# Plivo - -You can use these credentials to authenticate the following nodes with Plivo. - -- [Plivo](/integrations/builtin/app-nodes/n8n-nodes-base.plivo/) - -## Prerequisites - -Create a [Plivo](https://console.plivo.com/accounts/register/) account. - -## Using Access Token - -1. Open your Plivo [console](https://console.plivo.com/dashboard/). -2. Copy the displayed Auth ID under the ***Account and Payments*** section. -3. Enter a name for your credentials in the ***Credentials Name*** field in the 'Plivo API' credentials in n8n. -4. Paste the Auth ID in the ***Auth ID*** field in the 'Plivo API' credentials in n8n. -5. Copy the Auth Token displayed on your Plivo console. -6. Paste the Auth Token in the ***Auth Token*** field in the 'Plivo API' credentials in n8n. -7. Click on the ***Create*** button to create your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/postgres.md b/docs/integrations/builtin/credentials/postgres.md deleted file mode 100644 index 7feae2949..000000000 --- a/docs/integrations/builtin/credentials/postgres.md +++ /dev/null @@ -1,16 +0,0 @@ -# Postgres - -You can use these credentials to authenticate the following nodes with Postgres. - -- [Postgres](/integrations/builtin/app-nodes/n8n-nodes-base.postgres/) - -## Prerequisites - -Create an user account on a Postgres server. - -## Using Database Connection - -1. Retrieve your Postgres credentials and connection parameters. -2. Use the credentials and connection parameters with your Postgres node credentials in n8n. - -![Getting Postgres credentials](/_images/integrations/builtin/credentials/postgres/using-database-connection.gif) diff --git a/docs/integrations/builtin/credentials/posthog.md b/docs/integrations/builtin/credentials/posthog.md deleted file mode 100644 index 3bd311835..000000000 --- a/docs/integrations/builtin/credentials/posthog.md +++ /dev/null @@ -1,27 +0,0 @@ -# PostHog - -You can use these credentials to authenticate the following nodes with PostHog. - -- [PostHog](/integrations/builtin/app-nodes/n8n-nodes-base.postHog/) - - -## Prerequisites - -Create a [PostHog](https://posthog.com/) account or host PostHog on your server. - -## Using API Key - -1. Open your PostHog dashboard. -2. Click on ***Project*** on the left sidebar. -3. Click on the ***Safety & Privacy*** tab. -4. Scroll down to the ***Project API Key*** section and copy the displayed API key. -5. Enter a name for your credentials in the ***Credentials Name*** field in the 'PostHog API' credentials in n8n. -6. If you're hosting PostHog on your own server, update the URL of your PostHog instance in the ***URL*** field. -7. Paste the API key in the ***API Key*** field in the 'PostHog API' credentials in n8n. -8. Click on the ***Create*** button to create your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/postmark.md b/docs/integrations/builtin/credentials/postmark.md deleted file mode 100644 index 1f6a3d3ac..000000000 --- a/docs/integrations/builtin/credentials/postmark.md +++ /dev/null @@ -1,19 +0,0 @@ -# Postmark - -You can use these credentials to authenticate the following nodes with Postmark. - -- [Postmark Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.postmarkTrigger/) - -## Prerequisites - -Create a [Postmark](https://postmarkapp.com/) account. - -## Using Access Token - -1. Access the [Postmark API Tokens page](https://account.postmarkapp.com/api_tokens). -2. Enter your postmark server name in the ***Search for a server*** field. -3. From the displayed dropdown list, select your server and click on the ***Get a server API token*** button. -4. Use the displayed ***Server API token*** with your Postmark API credentials in n8n. -5. Click the ***Save*** button to save your credentials in n8n. - -![Getting Postmark credentials](/_images/integrations/builtin/credentials/postmark/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/profitwell.md b/docs/integrations/builtin/credentials/profitwell.md deleted file mode 100644 index 8171625de..000000000 --- a/docs/integrations/builtin/credentials/profitwell.md +++ /dev/null @@ -1,19 +0,0 @@ -# ProfitWell - -You can use these credentials to authenticate the following nodes with ProfitWell. - -- [ProfitWell](/integrations/builtin/app-nodes/n8n-nodes-base.profitWell/) - -## Prerequisites - -Create a [ProfitWell](https://www.profitwell.com/) account. - -## Using API - -1. Access the [ProfitWell dashboard](https://www2.profitwell.com/app/dashboard) page. -2. Click on the gears icon on the left panel and select 'Integrations'. -3. Click on the ***API KEYS/DEV KIT*** tab. -4. Copy the ***YOUR PRIVATE KEY*** displayed. -5. Use this ***Private Key*** with your ProfitWell node credentials in n8n. - -![Getting ProfitWell credentials](/_images/integrations/builtin/credentials/profitwell/using-api.gif) diff --git a/docs/integrations/builtin/credentials/pushbullet.md b/docs/integrations/builtin/credentials/pushbullet.md deleted file mode 100644 index 53cb408c2..000000000 --- a/docs/integrations/builtin/credentials/pushbullet.md +++ /dev/null @@ -1,24 +0,0 @@ -# Pushbullet - -You can use these credentials to authenticate the following nodes with Pushbullet. - -- [Pushbullet](/integrations/builtin/app-nodes/n8n-nodes-base.pushbullet/) - -## Prerequisites - -Create a [Pushbullet](https://www.pushbullet.com/) account. - -## Using OAuth - -1. Access the [create client](https://www.pushbullet.com/create-client) page. -2. Enter an app name in the ***name*** field. -3. Copy your OAuth Callback URL from the 'Create New Credentials' screen in n8n and paste it in the ***redirect_uri*** field. -4. Click on the ***Add A New OAuth Client*** button. -5. Use the provided ***client_id*** and ***client_secret*** with your Pushbullet OAuth2 API credentials in n8n. -6. Click the ***Connect my account*** button to connect to Pushbullet and save your credentials in n8n. - -!!! note "Pushbullet OAuth Test Link" - Pushbullet does offer a test link during the client creation process described above. This link is not compatible with n8n. In order to verify the authentication works, simply use the ***Connect my account*** button in n8n. - - -![Getting Pushbullet credentials](/_images/integrations/builtin/credentials/pushbullet/using-oauth.gif) diff --git a/docs/integrations/builtin/credentials/pushcut.md b/docs/integrations/builtin/credentials/pushcut.md deleted file mode 100644 index dca572cfe..000000000 --- a/docs/integrations/builtin/credentials/pushcut.md +++ /dev/null @@ -1,20 +0,0 @@ -# Pushcut - -You can use these credentials to authenticate the following nodes with Pushcut. - -- [Pushcut](/integrations/builtin/app-nodes/n8n-nodes-base.pushcut/) -- [Pushcut Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.pushcutTrigger/) - -## Prerequisites - -Download the [Pushcut](https://www.pushcut.io) app. - -## Using API Key - -1. Access the Pushcut application on your device. -2. Click on the ***Account*** button. -3. Click on the ***Add API Key*** under the ***INTEGRATIONS*** section. -4. Click on the ***Generate*** button. -5. Use the ***API Key*** with your Pushcut node credentials in n8n. - -![Getting Pushcut credentials](/_images/integrations/builtin/credentials/pushcut/using-api-key.gif) diff --git a/docs/integrations/builtin/credentials/pushover.md b/docs/integrations/builtin/credentials/pushover.md deleted file mode 100644 index 61ca9d9e6..000000000 --- a/docs/integrations/builtin/credentials/pushover.md +++ /dev/null @@ -1,20 +0,0 @@ -# Pushover - -You can use these credentials to authenticate the following nodes with Pushover. - -- [Pushover](/integrations/builtin/app-nodes/n8n-nodes-base.pushover/) - -## Prerequisites - -Create a [Pushover](https://pushover.net) account. - -## Using API Key - -1. Access the [Pushover dashboard](https://pushover.net/). -2. Scroll down to the bottom and click on ***Create an Application/API Token***. -3. Enter the name of your application in the ***Name*** field. -4. Read the 'Terms of Services' and the 'Guide to Being Friendly to our API' and, if you agree to them, check the checkbox. -5. Click on the ***Create Application*** button. -6. Use this ***API Key*** with your Pushover node credentials in n8n. - -![Getting Pushover credentials](/_images/integrations/builtin/credentials/pushover/using-api-key.gif) diff --git a/docs/integrations/builtin/credentials/questdb.md b/docs/integrations/builtin/credentials/questdb.md deleted file mode 100644 index 39a87088a..000000000 --- a/docs/integrations/builtin/credentials/questdb.md +++ /dev/null @@ -1,14 +0,0 @@ -# QuestDB - -You can use these credentials to authenticate the following nodes with QuestDB. - -- [QuestDB](/integrations/builtin/app-nodes/n8n-nodes-base.questDB/) - -## Prerequisites - -An available instance of QuestDB. - -## Using Database Connection - -1. Retrieve your QuestDB credentials and connection parameters. -2. Use the credentials and connection parameters with your QuestDB node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/quickbase.md b/docs/integrations/builtin/credentials/quickbase.md deleted file mode 100644 index 58b0828cf..000000000 --- a/docs/integrations/builtin/credentials/quickbase.md +++ /dev/null @@ -1,27 +0,0 @@ -# Quick Base - -You can use these credentials to authenticate the following nodes with Quick Base. - -- [Quick Base](/integrations/builtin/app-nodes/n8n-nodes-base.quickbase/) - -## Prerequisites - -Create a [Quick Base](https://www.quickbase.com/) account. - -## Using API - -1. Access your Quick Base dashboard. -2. Click on your name on the top right and select 'My preferences' from the dropdown list. -3. Click on ***Manage my user tokens*** under the ***My User Information*** section. -4. Click on the ***+ New user token*** button. -5. Enter a name in the ***Name*** field. -6. Select an app from the ***Assign token to apps*** dropdown list. -7. Click on the ***Save*** button. -8. Copy the string of characters located between `https://` and `/db` in your Quick Base URL. This string is the hostname. -9. Use this ***Hostname*** and ***User Token*** with your Quick Base node credentials in n8n. - -![Getting Quick Base credentials](/_images/integrations/builtin/credentials/quickbase/using-api.gif) - -## Further Reference - -- [Quick Base API Portal](https://developer.quickbase.com/auth) diff --git a/docs/integrations/builtin/credentials/quickbooks.md b/docs/integrations/builtin/credentials/quickbooks.md deleted file mode 100644 index abb701f16..000000000 --- a/docs/integrations/builtin/credentials/quickbooks.md +++ /dev/null @@ -1,43 +0,0 @@ -# QuickBooks - -You can use these credentials to authenticate the following nodes with QuickBooks. - -- [QuickBooks](/integrations/builtin/app-nodes/n8n-nodes-base.quickbooks/) - -## Prerequisites - -Create a [Intuit developer](https://developer.intuit.com/) account. - -## Using OAuth - - - -1. Open the Intuit Developer [dashboard](https://developer.intuit.com/app/developer/dashboard) page. -2. Click on the ***+ Create an app*** button. -3. Select the ***QuickBooks Online and Payments*** platform. -4. Enter the name of the app in the ***What's your app name?*** field. -5. Select the required scopes under the ***Select Scope*** section. -6. Click on the ***Create app*** button. -7. Click on ***Keys & OAuth*** under the ***Development*** section. -8. Scroll down to the ***Redirect URIs*** section and click on the ***Add URI*** button. -9. Copy the 'OAuth Callback URL' provided in the 'QuickBooks OAuth2 API' credentials in n8n. -10. Paste the URL in the ***Link*** field. -11. Click on the ***Save*** button. -12. Copy the displayed ***Client ID***. -13. Enter a name for your credentials in the ***Credentials Name*** field in the 'QuickBooks OAuth2 API' credentials in n8n. -14. Paste the client ID in the ***Client ID*** field in the 'QuickBooks OAuth2 API' credentials in n8n. -15. Copy the displayed ***Client Secret*** from the Keys page. -16. Paste the client secret in the ***Client Secret*** field in the 'QuickBooks OAuth2 API' credentials in n8n. -17. Select 'Sandbox' from the ***Environment*** dropdown list in the 'QuickBooks OAuth2 API' credentials in n8n. -18. Click on the circle button in the OAuth section to connect a QuickBooks account to n8n. -19. Click the ***Save*** button to save your credentials in n8n. - -**Note:** To build the application in production, you will have to fulfill all the requirements mentioned by Intuit. You can learn more on Intuit's [documentation](https://developer.intuit.com/app/developer/qbo/docs/go-live). - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/rabbitmq.md b/docs/integrations/builtin/credentials/rabbitmq.md deleted file mode 100644 index cae7bc531..000000000 --- a/docs/integrations/builtin/credentials/rabbitmq.md +++ /dev/null @@ -1,14 +0,0 @@ -# RabbitMQ - -You can use these credentials to authenticate the following nodes with RabbitMQ. - -- [RabbitMQ](/integrations/builtin/app-nodes/n8n-nodes-base.rabbitmq/) -- [RabbitMQ Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.rabbitmqTrigger/) - -## Prerequisites - -You need to have a RabbitMQ broker installed. - -## Using RabbitMQ - -Use your Hostname, Port, Username, Password, and Vhost as the RabbitMQ credential data in n8n. diff --git a/docs/integrations/builtin/credentials/raindrop.md b/docs/integrations/builtin/credentials/raindrop.md deleted file mode 100644 index abf8959e8..000000000 --- a/docs/integrations/builtin/credentials/raindrop.md +++ /dev/null @@ -1,41 +0,0 @@ -# Raindrop - -You can use these credentials to authenticate the following nodes with Raindrop. - -- [Raindrop](/integrations/builtin/app-nodes/n8n-nodes-base.raindrop/) - -## Prerequisites - -Create a [Raindrop](https://raindrop.io/) account. - -## Using OAuth - - - -1. Open the [Raindrop dashboard](https://app.raindrop.io/my/0) page. -2. Click on your username on the top left and select 'Settings' from the dropdown list. -3. Click on the ***Integrations*** tab. -4. Click on ***+ Create new app*** under the ***For Developers*** section. -5. Enter the name of the app in the ***Name*** field. -6. Accept the ***Raindrop.io API Terms and Guidelines***. -7. Click on the ***Create*** button. -8. Under the ***For Developers*** section, select the app that you created. -9. Enter a description in the ***Description*** field. -10. Enter a URL in the ***Site*** field. -11. Copy the 'OAuth Callback URL' provided in the 'Raindrop OAuth2 API' credentials in n8n. -12. Paste the URL in the ***Redirect URI*** field and click on the ***Save*** button. -13. Copy the displayed ***Client ID***. -14. Enter a name for your credentials in the ***Credentials Name*** field in the 'Raindrop OAuth2 API' credentials in n8n. -15. Paste the client ID in the ***Client ID*** field in the 'Raindrop OAuth2 API' credentials in n8n. -16. Copy the displayed ***Client secret*** from the Raindrop. -17. Paste the client secret in the ***Client Secret*** field in the 'Raindrop OAuth2 API' credentials in n8n. -18. Click on the circle button in the OAuth section to connect a Raindrop account to n8n. -19. Click the ***Save*** button to save your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/reddit.md b/docs/integrations/builtin/credentials/reddit.md deleted file mode 100644 index d25890604..000000000 --- a/docs/integrations/builtin/credentials/reddit.md +++ /dev/null @@ -1,34 +0,0 @@ -# Reddit - -You can use these credentials to authenticate the following nodes with Reddit. - -- [Reddit](/integrations/builtin/app-nodes/n8n-nodes-base.reddit/) - - -## Prerequisites - -Create a [Reddit](https://reddit.com/) account. - -## Using OAuth - -1. Open [Reddit](https://reddit.com). -2. Click on your avatar on the top right and select 'User Settings'. -3. Click on the ***Safety & Privacy*** tab. -4. Scroll to the bottom and click on ***Manage third-party app authorization***. -5. Click on the ***are you a developer? create an app...*** button. -6. Enter the name of your application in the ***name*** field. -7. Copy the 'OAuth Callback URL' provided in the 'Reddit OAuth2 API' credentials in n8n. -8. Paste the URL in the ***redirect uri*** field. -9. Click on the ***create app*** button. -10. Copy the client ID displayed next to the app's icon. -11. Enter a name for your credentials in the ***Credentials Name*** field in the 'Reddit OAuth2 API' credentials in n8n. -12. Paste the client ID in the ***Client ID*** field in the 'Reddit OAuth2 API' credentials in n8n. -13. Copy the client secret from Reddit and paste it in the ***Client Secret*** field in the 'Reddit OAuth2 API' credentials in n8n. -14. Click on the circle button in the OAuth section to connect a Reddit account to n8n. -15. Click on the ***Save*** button to save your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/redis.md b/docs/integrations/builtin/credentials/redis.md deleted file mode 100644 index d0647e97c..000000000 --- a/docs/integrations/builtin/credentials/redis.md +++ /dev/null @@ -1,16 +0,0 @@ -# Redis - -You can use these credentials to authenticate the following nodes with Redis. - -- [Redis](/integrations/builtin/app-nodes/n8n-nodes-base.redis/) - -## Prerequisites - -Create an user account on a Redis server. - -## Using Database Connection - -1. Retrieve your Redis credentials and connection parameters. -2. Use the credentials and connection parameters with your Redis node credentials in n8n. - -![Getting Redis credentials](/_images/integrations/builtin/credentials/redis/using-database-connection.gif) diff --git a/docs/integrations/builtin/credentials/rocketchat.md b/docs/integrations/builtin/credentials/rocketchat.md deleted file mode 100644 index 732213001..000000000 --- a/docs/integrations/builtin/credentials/rocketchat.md +++ /dev/null @@ -1,22 +0,0 @@ -# Rocket.Chat - -You can use these credentials to authenticate the following nodes with Rocket.Chat. - -- [Rocket.Chat](/integrations/builtin/app-nodes/n8n-nodes-base.rocketchat/) - -## Prerequisites - -- Create a [Rocket.Chat](https://rocket.chat/) account. -- Have the necessary permission `create-personal-access-tokens` (from administrator) to be able to generate personal access tokens. - -## Using Access Token - -1. Access your Rocket.Chat instance. -2. Click on the profile icon in the top left. -3. Click on My Account. -4. Click on Personal Access Tokens from the panel on the left. -5. Enter a name for your Personal access token and click on the *Add* button. -6. Copy the *Token* and enter that in the *Auth Key* field in n8n. -7. Copy the *User Id* and enter that in the *User Id* field in n8n. - -![Getting Rocket.Chat credentials](/_images/integrations/builtin/credentials/rocketchat/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/rundeck.md b/docs/integrations/builtin/credentials/rundeck.md deleted file mode 100644 index 0b5e584a8..000000000 --- a/docs/integrations/builtin/credentials/rundeck.md +++ /dev/null @@ -1,20 +0,0 @@ -# Rundeck - -You can use these credentials to authenticate the following nodes with Rundeck. - -- [Rundeck](/integrations/builtin/app-nodes/n8n-nodes-base.rundeck/) - -## Prerequisites - -Create a [Rundeck](https://www.rundeck.com/) account. - -## Using Access Token - -1. Access your Rundeck dashboard. -2. Click on your user icon in the top right. -3. Click on 'Profile'. -4. Next to 'User API Tokens', click on the plus button and generate a new token. -5. Click on 'Show Token' to reveal the token you generated. -5. Use the API token with your Rundeck node credentials in n8n. - -![Getting Rundeck credentials](/_images/integrations/builtin/credentials/rundeck/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/s3.md b/docs/integrations/builtin/credentials/s3.md deleted file mode 100644 index a8de11b3a..000000000 --- a/docs/integrations/builtin/credentials/s3.md +++ /dev/null @@ -1,15 +0,0 @@ -# S3 - -You can use these credentials to authenticate the following nodes with S3. - -- [S3](/integrations/builtin/app-nodes/n8n-nodes-base.s3/) - -## Prerequisites - -Create an account on S3 compatible server. - -## Using Access Token - -1. Retrieve your S3 endpoint, access key ID, and secret access key from your S3 compatible server. -2. Use the S3 endpoint, access key ID, and the secret access key in your S3 node credentials in n8n. -3. Click on the ***Save*** button to save your credentials. diff --git a/docs/integrations/builtin/credentials/salesforce.md b/docs/integrations/builtin/credentials/salesforce.md deleted file mode 100644 index e39c01aea..000000000 --- a/docs/integrations/builtin/credentials/salesforce.md +++ /dev/null @@ -1,56 +0,0 @@ -# Salesforce - -You can use these credentials to authenticate the following nodes with Salesforce. - -- [Salesforce](/integrations/builtin/app-nodes/n8n-nodes-base.salesforce/) - -## Prerequisites - -Create a [Salesforce](https://www.salesforce.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name, Access Token URL, and click on the circle button in the OAuth section to connect your Salesforce account to n8n. You can find details on how to obtain the Access Token URL in the instructions below. - - -1. Access your Salesforce Dashboard. -2. Click on the gear icon in the top right and select ***Setup*** from the dropdown list. -3. In the ***Platform Tools*** category of the sidebar, select ***App Manager*** under the ***Apps*** section. -4. Click on the ***New Connected App*** button. -5. Enter any necessary information and click on the ***Enable OAuth Settings*** checkbox. -6. Copy the ***OAuth Callback URL*** provided in the 'Salesforce OAuth2 API' credentials in n8n. -7. On the Salesforce app creation page, paste the URL in the ***Callback URL*** field. -8. Add the "Perform requests on your behalf at any time (refresh_token, offline_access)" scope in the ***Selected OAuth Scopes*** section. -9. Add any other scopes you plan to use in the ***Selected OAuth Scopes*** section. -10. Click on the ***Save*** button at the bottom of the page. -11. On the ***New Connected App*** page, click on the ***Continue*** button. -12. In the 'API (Enable OAuth Settings)' section of the page, click on the ***Click to reveal*** button to reveal the consumer secret. -13. Copy the displayed ***Consumer Key*** and the ***Consumer Secret*** and use these with your Salesforce OAuth2 API credentials in n8n. -14. In the n8n credentials window select your ***Environment Type***, where Production or Sandbox. -15. Click on the circle button in the OAuth section to connect a Salesforce account to n8n. -16. Click on the ***Save*** button to save your credentials. - -![Getting Salesforce OAuth credentials](/_images/integrations/builtin/credentials/salesforce/using-oauth.gif) - -## Using OAuth JWT - -To use the OAuth JWT authentication method with the Salesforce node you need to create a private key. Follow the instructions mentioned in the documentation [here](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_key_and_cert.htm) to create a private key. - -1. Access your Salesforce Dashboard. -2. Click on the gear icon in the top right and select ***Setup*** from the dropdown list. -3. In the ***Platform Tools*** category of the sidebar, select ***App Manager*** under the ***Apps*** section. -4. Click on the ***New Connected App*** button. -5. Enter any necessary information and click on the ***Enable OAuth Settings*** checkbox. -6. Copy the ***OAuth Callback URL*** provided in the 'Salesforce OAuth2 API' credentials in n8n. -7. On the Salesforce app creation page, paste the URL in the ***Callback URL*** field. -8. Click on the ***Use digital signatures*** checkbox. -9. Upload the private key that you created earlier. -10. Add the "Perform requests on your behalf at any time (refresh_token, offline_access)" scope in the ***Selected OAuth Scopes*** section. -11. Add any other scopes you plan to use in the ***Selected OAuth Scopes*** section. -12. Click on the ***Save*** button at the bottom of the page. -13. On the ***New Connected App*** page, click on the ***Continue*** button. -14. Copy the displayed ***Consumer Key*** and paste it in the ***Client ID*** field in your Salesforce JWT API credentials in n8n. -15. Use your Salesforce username in the ***Username*** field. -16. Copy the private key that you created earlier and paste it in the ***Private Key*** field in your Salesforce JWT API credentials in n8n. -17. Click on the ***Save*** button to save your credentials. diff --git a/docs/integrations/builtin/credentials/salesmate.md b/docs/integrations/builtin/credentials/salesmate.md deleted file mode 100644 index 6489888bb..000000000 --- a/docs/integrations/builtin/credentials/salesmate.md +++ /dev/null @@ -1,20 +0,0 @@ -# Salesmate - -You can use these credentials to authenticate the following nodes with Salesmate. - -- [Salesmate](/integrations/builtin/app-nodes/n8n-nodes-base.salesmate/) - -## Prerequisites - -Create a [Salesmate](https://salesmate.io/) account. - -## Using Access Token - -1. Access your Salesmate Dashboard. -2. Click on your user icon in the top right. -3. Click on My Account. -4. Click on Access Key in the left panel. -5. Copy the session key. -6. Use session key and domain name for your Salesmate node credentials in n8n. - -![Getting Salesmate credentials](/_images/integrations/builtin/credentials/salesmate/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/seatable.md b/docs/integrations/builtin/credentials/seatable.md deleted file mode 100644 index dae2f3007..000000000 --- a/docs/integrations/builtin/credentials/seatable.md +++ /dev/null @@ -1,25 +0,0 @@ -# SeaTable - -You can use these credentials to authenticate the following nodes: - -- [SeaTable](/integrations/builtin/app-nodes/n8n-nodes-base.seaTable/) -- [SeaTable Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.seaTableTrigger/) - -## Prerequisites - -You need to have a [SeaTable](https://seatable.io/en/) instance or cloud account. - -## Using API key - -From your SeaTable dashboard: - -1. From the **Bases** menu select the base you want to enable access for. -2. Navigate to the base options > **Advanced** > **API Token**. -3. In the modal, enter a name for this token and select the **Read-Write** permission. -4. Click **Submit** and copy the new API token. - -From n8n: - -1. Select your environment type: **Cloud-hosted** or **Self-hosted**. -2. For **Self-hosted** environments enter the domain of your instance. -3. Enter the API token obtained above and click **Save** to create your credential. diff --git a/docs/integrations/builtin/credentials/securityscorecard.md b/docs/integrations/builtin/credentials/securityscorecard.md deleted file mode 100644 index 294b817ae..000000000 --- a/docs/integrations/builtin/credentials/securityscorecard.md +++ /dev/null @@ -1,27 +0,0 @@ -# SecurityScorecard - -You can use these credentials to authenticate the following nodes with SecurityScorecard. - -- [SecurityScorecard](/integrations/builtin/app-nodes/n8n-nodes-base.securityScorecard/) - - -## Prerequisites - -Create a [SecurityScorecard](https://securityscorecard.com/) account. - -## Using API - -1. Open your SecurityScorecard [dashboard](https://platform.securityscorecard.io/#/home). -2. Click on ***Integrations*** and select 'Get an API Key'. -3. Click on ***Generate new API token***. -4. Click on the ***Confirm*** button. -5. Copy the generated API key. -6. Enter a name for your credentials in the ***Credentials Name*** field in the 'SecurityScorecard API' credentials in n8n. -7. Paste the API key in the ***API Key*** field in the 'Security Scorecard API' credentials in n8n. -8. Click on the ***Create*** button to create your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/segment.md b/docs/integrations/builtin/credentials/segment.md deleted file mode 100644 index 14555ac73..000000000 --- a/docs/integrations/builtin/credentials/segment.md +++ /dev/null @@ -1,20 +0,0 @@ -# Segment - -You can use these credentials to authenticate the following nodes with Segment. - -- [Segment](/integrations/builtin/app-nodes/n8n-nodes-base.segment/) - -## Prerequisites - -Create a [Segment](https://segment.com/) account. - -## Using Access Token - -1. Access your Segment Dashboard. -2. Click on Sources, on the left panel. -3. Click on Add Source. -4. Select Node.js. -5. Copy write key. -6. Use session write key for your Segment node credentials in n8n. - -![Getting Segment credentials](/_images/integrations/builtin/credentials/segment/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/sendemail.md b/docs/integrations/builtin/credentials/sendemail.md deleted file mode 100644 index 51de640ea..000000000 --- a/docs/integrations/builtin/credentials/sendemail.md +++ /dev/null @@ -1,14 +0,0 @@ -# Send Email - -You can use these credentials to authenticate the following nodes with SMTP. - -- [Send Email](/integrations/builtin/core-nodes/n8n-nodes-base.sendEmail/) - -## Prerequisites - -Create an email account on a service with SMTP support. - -## Using SMTP - -1. Retrieve your login credentials and SMTP connection parameters. -2. Use the login credentials and SMTP connection parameters with your Send Email node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/sendgrid.md b/docs/integrations/builtin/credentials/sendgrid.md deleted file mode 100644 index 914b11b5e..000000000 --- a/docs/integrations/builtin/credentials/sendgrid.md +++ /dev/null @@ -1,29 +0,0 @@ -# SendGrid - -You can use these credentials to authenticate the following nodes with SendGrid. - -- [SendGrid](/integrations/builtin/app-nodes/n8n-nodes-base.sendGrid/) - - -## Prerequisites - -Create a [SendGrid](https://SendGrid.com/) account. - -## Using API Key - -1. Open your SendGrid [dashboard](https://app.sendgrid.com/). -2. Click on ***Settings*** on the left sidebar. -3. Click on ***API Keys***. -4. Click on the ***Create API Key*** button. -5. Enter the name of the key in the ***API Key Name*** field. -6. Click on the ***Create & View*** button. -7. Click on the displayed API key to copy the key. -8. Enter the name for your credentials in the ***Credentials Name*** field in the 'SendGrid API' credentials in n8n. -9. Paste the 'API Key' in the ***API Key*** field. -10. Click on the ***Create*** button to save your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/sendinblue.md b/docs/integrations/builtin/credentials/sendinblue.md deleted file mode 100644 index 231cbabf1..000000000 --- a/docs/integrations/builtin/credentials/sendinblue.md +++ /dev/null @@ -1,14 +0,0 @@ -# Sendinblue - -You can use these credentials to authenticate the following nodes with Sendinblue: - -* [Sendinblue node](/integrations/builtin/app-nodes/n8n-nodes-base.sendInBlue/) -* [Sendinblue trigger node](/integrations/builtin/trigger-nodes/n8n-nodes-base.sendInBlueTrigger/) - -## API key - -Sendinblue uses API keys for authorization/ - -1. Create a Sendinblue account. -2. Create a new API key to use with n8n. Refer to the [Sendinblue documentation](https://developers.sendinblue.com/docs){:target=_blank .external-class} for detailed guidance on creating a key. -3. In n8n's **Sendinblue account** page, paste your API key into the **API key** field. \ No newline at end of file diff --git a/docs/integrations/builtin/credentials/sendy.md b/docs/integrations/builtin/credentials/sendy.md deleted file mode 100644 index 49aa311d9..000000000 --- a/docs/integrations/builtin/credentials/sendy.md +++ /dev/null @@ -1,18 +0,0 @@ -# Sendy - -You can use these credentials to authenticate the following nodes with Sendy. - -- [Sendy](/integrations/builtin/app-nodes/n8n-nodes-base.sendy/) - -## Prerequisites - -Host a [Sendy](https://sendy.co/get-started) application. - -## Using API Key - -1. Access your Sendy application. -2. Click on the username on the top right corner and select 'Settings'. -3. Copy the API key displayed under the ***Your API key*** section. -4. Use this API key and the installation URL with your Sendy node credentials in n8n. - -![Getting Sendy credentials](/_images/integrations/builtin/credentials/sendy/using-api.gif) diff --git a/docs/integrations/builtin/credentials/sentryio.md b/docs/integrations/builtin/credentials/sentryio.md deleted file mode 100644 index a281d6d58..000000000 --- a/docs/integrations/builtin/credentials/sentryio.md +++ /dev/null @@ -1,36 +0,0 @@ -# Sentry.io - -You can use these credentials to authenticate the following nodes with Sentry.io. - -- [Sentry.io](/integrations/builtin/app-nodes/n8n-nodes-base.sentryIo/) - -## Prerequisites - -Create a [Sentry.io](https://sentry.io/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Sentry.io account to n8n. - - -1. Access your [Sentry.io Applications Page](https://sentry.io/settings/account/api/applications/). -2. Click on the ***Create New Application*** button in the top right. -3. Enter a name in the ***Name*** field. -4. Copy the 'OAuth Callback URL' provided in the 'Sentry.io OAuth2 API' credentials in n8n and paste it in the ***Authorized Redirect URIs*** field in the *Sentry.io Application Details* page. -5. Use the displayed ***Client ID*** and ***Client Secret*** with your Sentry.io OAuth2 API credentials in n8n. -6. Click on the circle button in the OAuth section to connect a Sentry.io account to n8n. -7. Click on the ***Save*** button to save your credentials. - -![Getting Sentry.io OAuth credentials](/_images/integrations/builtin/credentials/sentryio/using-oauth.gif) - - -## Using Access Token - -1. Access your [Sentry.io Auth Tokens page](https://sentry.io/settings/account/api/auth-tokens/). -2. Click on the ***Create New Token*** button in the top right. -3. Select any scopes you plan to use and then click on ***Create Token***. -4. Use the generated access token with your Sentry.io API credentials in n8n. -5. Click on the ***Save*** button to save your credentials. - -![Getting Sentry.io access token](/_images/integrations/builtin/credentials/sentryio/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/servicenow.md b/docs/integrations/builtin/credentials/servicenow.md deleted file mode 100644 index ff4bddfd9..000000000 --- a/docs/integrations/builtin/credentials/servicenow.md +++ /dev/null @@ -1,35 +0,0 @@ -# ServiceNow - -You can use these credentials to authenticate the following nodes with serviceNow. - -- [ServiceNow](/integrations/builtin/app-nodes/n8n-nodes-base.serviceNow/) - -## Prerequisites - -Create a [ServiceNow](https://servicenow.com/) account. - -## Using OAuth - -From your ServiceNow instance: - -1. Navigate to ***System OAuth*** > ***Application Registry***. -2. Click ***New*** button > ***Create an OAuth API endpoint for external clients***. - -![New Application Registry](/_images/integrations/builtin/credentials/servicenow/servicenow_instance.png) - -3. Complete the following fields: - * **Name**: Enter a descriptive name for the new endpoint. - * **Client ID**: Auto populated field, you will need this ID to configure your n8n credentials. - * **Client Secret**: Enter your desired secret or leave blank to auto generate a random string. You will need this to configure your n8n credentials. - * **Redirect URL**: Copy the ***OAuth Callback URL*** from the n8n credentials window and enter it here. -4. Click ***Submit*** to save and create your new endpoint. - -From n8n: - -5. Enter a descriptive ***Credentials Name***. -6. Under ***Credential Data*** complete the following fields: - * ***Client ID***: Enter the client ID generated above. - * ***Client Secret***: Enter your client secret created above. - * ***Subdomain***: Enter the subdomain of your ServiceNow instance. This can be seen in your instance URL: `https://.service-now.com/`. -7. From the ***OAuth*** section, click the circle button to establish the connection. -8. Click ***Save*** to finalize your n8n credentials. diff --git a/docs/integrations/builtin/credentials/shopify.md b/docs/integrations/builtin/credentials/shopify.md deleted file mode 100644 index 3ed884158..000000000 --- a/docs/integrations/builtin/credentials/shopify.md +++ /dev/null @@ -1,22 +0,0 @@ -# Shopify - -You can use these credentials to authenticate the following nodes with Shopify. - -- [Shopify](/integrations/builtin/app-nodes/n8n-nodes-base.shopify/) -- [Shopify Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.shopifyTrigger/) - -## Prerequisites - -Create a [Shopify](https://shopify.com/) account. - -## Using API Key - -1. Access the [Apps](https://www.shopify.com/admin/apps) section of your Shopify Store's admin console. -2. Click on 'Manage private apps' near the bottom of the page. -3. Click on the 'Create new private app' button and create a new app by entering any necessary information. Make sure that you set appropriate for the methods you plan to use under the 'Admin API' section. -4. Upon app creation, scroll down, and you will see your API key, Password, and Shared Secret. -5. Use your password, API key, secret, and shop subdomain with your Shopify node credentials in n8n. - -**Note:** Use the subdomain without `.myshopify.com` in n8n. - -![Getting Shopify credentials](/_images/integrations/builtin/credentials/shopify/using-oauth.gif) diff --git a/docs/integrations/builtin/credentials/signl4.md b/docs/integrations/builtin/credentials/signl4.md deleted file mode 100644 index be97475bd..000000000 --- a/docs/integrations/builtin/credentials/signl4.md +++ /dev/null @@ -1,14 +0,0 @@ -# SIGNL4 - -You can use these credentials to authenticate the following nodes with SIGNL4. - -- [SIGNL4](/integrations/builtin/app-nodes/n8n-nodes-base.signl4/) - -## Prerequisites - -Create a [SIGNL4](https://www.signl4.com/) account. - -## Using Access Token - -1. Open the '✅ Sign up complete' email you received when you signed up for SIGNL4. -2. Your team secret is the last part of the webhook URL. If your webhook URL is `https://connect.signl4.com/webhook/helloworld`, your team secret would be `helloworld`. diff --git a/docs/integrations/builtin/credentials/slack.md b/docs/integrations/builtin/credentials/slack.md deleted file mode 100644 index eb0315655..000000000 --- a/docs/integrations/builtin/credentials/slack.md +++ /dev/null @@ -1,80 +0,0 @@ -# Slack - -You can use these credentials to authenticate the following nodes: - -- [Slack](/integrations/builtin/app-nodes/n8n-nodes-base.slack/) - -## Prerequisites - -Create a [Slack](https://slack.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Slack account to n8n. - - -1. Open the [Slack API](https://api.slack.com/) page. -2. Click on the ***Create an app*** button and select **From scratch**. -3. Enter an ***App Name*** in the corresponding field. -4. ***Select a workspace*** for your app from the dropdown list. -5. Click on the ***Create App*** button. -6. Scroll down to the ***App Credentials*** section. -7. Copy and paste ***Client ID*** and ***Client Secret*** in the corresponding fields of your n8n credentials. -8. On the Basic Information page, navigate to ***Building Apps for Slack*** > ***Add features and functionality*** > ***Permissions***. -9. In the ***Redirect URLs*** section, click on ***Add New Redirect URL***. -10. Copy the ***OAuth Callback URL*** provided in n8n and paste it here. -11. Click on the ***Save URLs*** button. -12. Scroll down to the ***Scopes*** section. -13. Add the required scopes under the ***Bot Token Scopes*** section. You can refer to the list of scopes on the [Scopes and permissions](https://api.slack.com/scopes) documentation on Slack. -14. Click on the circle button in the OAuth section to connect a Slack account to n8n. -15. Click the ***Save*** button to save your credentials in n8n. -16. Return to the Slack OAuth & Permissions page, scroll up to the ***OAuth Tokens for Your Workspace*** section and click on ***Install to Workspace*** button. -17. Click on the ***Allow*** button. - - - -## Using Access Token - -1. Open the [Slack API](https://api.slack.com/) page. -2. Click on the ***Create an app*** button and select **From scratch**. -3. Enter an ***App Name*** in the corresponding field. -4. ***Select a workspace*** for your app from the dropdown list. -5. Click on the ***Create App*** button. -6. In the ***Add features and functionality*** section select **Permissions**. -7. Scroll down to the ***Scopes*** section and: - * If you want your app to act on behalf of users that authorize the app, add the required scopes under the ***User Token Scopes*** section. - * If you're building a bot, add the required scopes under the ***Bot Token Scopes*** section. - - !!! tip Scopes - You can refer to the list of scopes on the officials Slack [Scopes and permissions](https://api.slack.com/scopes) documentation. - - -8. From the ***OAuth Tokens for Your Workspace*** section click on the ***Install to Workspace*** button. -9. Click on the ***Allow*** button. -10. In n8n, enter the ***Access Token*** created above. -11. Click the ***Save*** button to save your credentials in n8n. - - - -## Privacy policy - -For details about how you data is collected and used, see the [n8n](https://n8n.io/legal/privacy) and [Slack](https://slack.com/intl/en-de/trust/privacy/privacy-policy) privacy policies. diff --git a/docs/integrations/builtin/credentials/sms77.md b/docs/integrations/builtin/credentials/sms77.md deleted file mode 100644 index dc9fe3ff0..000000000 --- a/docs/integrations/builtin/credentials/sms77.md +++ /dev/null @@ -1,18 +0,0 @@ -# sms77 - -You can use these credentials to authenticate the following nodes with sms77. - -- [sms77](/integrations/builtin/app-nodes/n8n-nodes-base.sms77/) - -## Prerequisites - -Create an [sms77](https://sms77.io/) account. - -## Using Access Token - -1. Access your sms77 dashboard. -2. Click on the gear icon in the bottom left. -3. Click on the HTTP API tab. -4. Use the API key provided with your sms77 node credentials in n8n. - -![Getting sms77 credentials](/_images/integrations/builtin/credentials/sms77/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/snowflake.md b/docs/integrations/builtin/credentials/snowflake.md deleted file mode 100644 index 7ea4c3209..000000000 --- a/docs/integrations/builtin/credentials/snowflake.md +++ /dev/null @@ -1,19 +0,0 @@ -# Snowflake - -You can use these credentials to authenticate the following nodes with Snowflake. - -- [Snowflake](/integrations/builtin/app-nodes/n8n-nodes-base.snowflake/) - -## Prerequisites - -Create a [Snowflake](https://www.snowflake.com/) account. - -## Using API Key - -1. Access your Snowflake instance. -2. Copy the string of characters located between `https://` and `snowflakecomputing.com` in your Snowflake URL. This string is the name of your Snowflake Account. For example, if the URL of your Snowflake account is `https://abc.eu-central-1.snowflakecomputing.com` then the name of your account is `sx48547.eu-central-1`. -3. Use this account name, database name, username, password, schema, and role with your Snowflake credentials in n8n. - -## Further Reference - -- [Snowflake API Documentation](https://api.Snowflake.com/) diff --git a/docs/integrations/builtin/credentials/splunk.md b/docs/integrations/builtin/credentials/splunk.md deleted file mode 100644 index dcc1924e2..000000000 --- a/docs/integrations/builtin/credentials/splunk.md +++ /dev/null @@ -1,23 +0,0 @@ -# Splunk - -You can use these credentials to authenticate the following nodes: - -- [Splunk](/integrations/builtin/app-nodes/n8n-nodes-base.splunk/) - -## Prerequisites - -- [Download and install](https://www.splunk.com/en_us/download/splunk-enterprise.html) Splunk Enterprise - -## Using API Key - -From your Splunk UI: - -1. Navigate to the **Settings** > **Tokens** menu. -2. Select **Enable Token Authentication** and create a **New Token**. -3. Copy the API Key provided there. - -From n8n: - -4. Enter your API key and application Base URL (e.g. `https://localhost:8089`). -5. Use the toggle to select if you want to **Allow Unauthorized Certificates**. -6. Click **Save** to create your credentials. diff --git a/docs/integrations/builtin/credentials/spontit.md b/docs/integrations/builtin/credentials/spontit.md deleted file mode 100644 index 66710fcff..000000000 --- a/docs/integrations/builtin/credentials/spontit.md +++ /dev/null @@ -1,24 +0,0 @@ -# Spontit - -You can use these credentials to authenticate the following nodes with Spontit. - -- [Spontit](/integrations/builtin/app-nodes/n8n-nodes-base.spontit/) - -## Prerequisites - -Create a [Spontit](https://www.spontit.com/) account. - -## Using API Key - -1. Access the [Spontit dashboard](https://www.spontit.com/). -2. On the navigation menu, click on ***API***, and select 'Get Secret Keys' from the dropdown list. -3. Click on ***+ Create New Key*** to generate a new API Key. -4. Click on the ***PROFILE*** tab on the navigation menu. -5. Copy the displayed username. -6. Use this ***API Key*** and ***Username*** with your Spontit credentials in n8n. - -![Getting Spontit credentials](/_images/integrations/builtin/credentials/spontit/using-api-key.gif) - -## Further Reference - -- [Spontit API Documentation](https://api.spontit.com/) diff --git a/docs/integrations/builtin/credentials/spotify.md b/docs/integrations/builtin/credentials/spotify.md deleted file mode 100644 index a8872ddf2..000000000 --- a/docs/integrations/builtin/credentials/spotify.md +++ /dev/null @@ -1,23 +0,0 @@ -# Spotify - -You can use these credentials to authenticate the following nodes with Spotify. - -- [Spotify](/integrations/builtin/app-nodes/n8n-nodes-base.spotify/) - - -## Prerequisites - -Create a [Spotify Developer](https://developer.spotify.com/dashboard/login) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Spotify account to n8n. - - -1. Access your [Spotify for Developers](https://developer.spotify.com/dashboard/login) dashboard. -2. Click the *Create an App* button at the top of your dashboard. Enter in the app's name and description and click *Create*. -3. Use provided Client Secret and Client ID with your Spotify node credentials in n8n. -4. Open the app settings and add the n8n provided redirect URL to the app's redirect URI list. Redirect URL Explanation [here](/). - -![The Spotify App Dashboard](/_images/integrations/builtin/credentials/spotify/dashboard.gif) diff --git a/docs/integrations/builtin/credentials/ssh.md b/docs/integrations/builtin/credentials/ssh.md deleted file mode 100644 index 0fe138e8e..000000000 --- a/docs/integrations/builtin/credentials/ssh.md +++ /dev/null @@ -1,34 +0,0 @@ -# SSH - -You can use these credentials to authenticate the following nodes: - -- [SSH](/integrations/builtin/core-nodes/n8n-nodes-base.ssh/) - -## Prerequisites - -Authentication for the SSH node requires that you have a username and password for connecting to the remote server, or an SSH key configured for the server or service you are connecting to. -See [Connecting to GitHub with SSH](https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh) for an example. - -## Using Password - -1. From the SSH Credentials dropdown, select ***Create New*** and complete the following fields: - - ***Credentials Name***: Enter a descriptive name, here we used `ssh_demo`. - - ***Host***: Enter the IP address of the server you are connecting to. Here we are using `192.168.1.8` for a local Mac set up for SSH access. - - ***Port***: Enter the port to use for this connection. SSH used port 22 by default. - - ***User***: Enter the your username for this server. - - ***Password***: Enter your password for the provided username. -2. Click ***Save*** to make these credentials available for use. - -![SSH Password credentials](/_images/integrations/builtin/credentials/ssh/ssh_credentials.png) - -## Using Private Key - -1. With ***Private Key*** selected in the ***Authentication*** field, from the SSH Credentials dropdown select ***Create New***. -2. Complete the following fields: - - ***Credentials Name***: Enter a descriptive name, here we used `ssh_demo`. - - ***Host***: Enter the IP address of the server you are connecting to. - - ***Port***: Enter the port to use for this connection. SSH used port 22 by default. - - ***Private Key***: Enter your SSH private key. - - ***Passphrase***: Enter your passphrase used to secure this key. - -![SSH Private Key credentials](/_images/integrations/builtin/credentials/ssh/private_key_credential.png) diff --git a/docs/integrations/builtin/credentials/stackby.md b/docs/integrations/builtin/credentials/stackby.md deleted file mode 100644 index b1faf8402..000000000 --- a/docs/integrations/builtin/credentials/stackby.md +++ /dev/null @@ -1,26 +0,0 @@ -# Stackby - -You can use these credentials to authenticate the following nodes with Stackby. - -- [Stackby](/integrations/builtin/app-nodes/n8n-nodes-base.stackby/) - -## Prerequisites - -Create a [Stackby](https://stackby.com/) account. - -## Using API Key - -1. Open your Stackby [dashboard](https://stackby.com/dashboard). -2. Click on the user icon on the top right and select 'Account' from the dropdown list. -3. Under the ***API*** section, click on the ***Create API key*** button. -4. Copy the displayed API key. -5. Enter a name for your credentials in the ***Credentials Name*** field in the 'Stackby API' credentials in n8n. -6. Paste the API key in the ***API Key*** field in the 'Stackby API' credentials in n8n. -7. Click on the ***Create*** button to create the credentials. - - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/storyblok.md b/docs/integrations/builtin/credentials/storyblok.md deleted file mode 100644 index 77304bfc6..000000000 --- a/docs/integrations/builtin/credentials/storyblok.md +++ /dev/null @@ -1,36 +0,0 @@ -# Storyblok - -You can use these credentials to authenticate the following nodes with Storyblok. - -- [Storyblok](/integrations/builtin/app-nodes/n8n-nodes-base.storyblok/) - -## Prerequisites - -Create a [Storyblok](https://www.storyblok.com/) account. - -## Using API Key to access the Content API - -1. Access the [spaces](https://app.storyblok.com/#!/me/spaces) page. -2. Select a space you want to use from the left sidebar. -3. Click on ***Settings*** in the left sidebar. -4. Select the ***API-Keys*** tab. -5. Select an access level from the ***Access Level*** dropdown list. -6. Click on the ***Create Token*** button. -7. Use this ***API Key*** with your Storyblok Content API credentials in n8n. - -![Getting Storyblok credentials for the Content API](/_images/integrations/builtin/credentials/storyblok/using-content-api.gif) - -## Using API Key to access the Management API - -1. Access the [My Account](https://app.storyblok.com/#!/me/account) page. -2. Scroll down to the ***Personal access tokens*** section. -3. Click on the ***Generate new Token*** button. -4. Use this ***API Key*** with your Storyblok Management API credentials in n8n. - -![Getting Storyblok credentials for the Management API](/_images/integrations/builtin/credentials/storyblok/using-management-api.gif) - - -## Further Reference - -- [Content API Documentation](https://www.storyblok.com/docs/api/content-delivery#topics/authentication) -- [Management API Documentation](https://www.storyblok.com/docs/api/management#topics/authentication) diff --git a/docs/integrations/builtin/credentials/strapi.md b/docs/integrations/builtin/credentials/strapi.md deleted file mode 100644 index eccdc59d1..000000000 --- a/docs/integrations/builtin/credentials/strapi.md +++ /dev/null @@ -1,27 +0,0 @@ -# Strapi - -You can use these credentials to authenticate the following nodes with Strapi. - -- [Strapi](/integrations/builtin/app-nodes/n8n-nodes-base.strapi/) - -## Prerequisites - -Install [Strapi](https://strapi.io/documentation/v3.x/getting-started/installation.html) on your server. - -## Using API - -1. Access your Strapi Admin dashboard. -2. Click on ***Settings*** in the left sidebar. -3. Click on ***Roles*** under the ***USERS & PERMISSIONS PLUGIN*** section. -4. Click on the pencil icon next to the role you want to edit. -5. In the ***Permissions*** section, give the required permissions. -6. Click on the ***Save*** button. -7. Click on ***Users*** in the left sidebar. -8. Click on the ***+ Add New user*** button. -9. Enter the required information. -10. Click on ***ON*** for the ***Confirmed*** field. -11. Select the role that you set the permissions for in the previous steps from the ***Role*** dropdown list. -12. Click on the ***Save*** button. -13. Use this email, password, and the URL of your Strapi instance with your Strapi node credentials in n8n. - -![Getting Strapi credentials](/_images/integrations/builtin/credentials/strapi/using-api.gif) diff --git a/docs/integrations/builtin/credentials/strava.md b/docs/integrations/builtin/credentials/strava.md deleted file mode 100644 index 623639d88..000000000 --- a/docs/integrations/builtin/credentials/strava.md +++ /dev/null @@ -1,24 +0,0 @@ -# Strava - -You can use these credentials to authenticate the following nodes with Strava. - -- [Strava](/integrations/builtin/app-nodes/n8n-nodes-base.strava/) -- [Strava Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.stravaTrigger/) - -## Prerequisites - -Create a [Strava](https://Strava.com) account. - -## Using OAuth - -1. Access the [My API Application page](https://www.strava.com/settings/api). -2. Enter the application name in the ***Application Name*** field. -3. Enter the website URL in the ***Website*** field. -4. Copy the string of characters between `https://` (or `http://`) and `/oauth2/callback` (or `/rest/oauth2-credential/callback`) from 'OAuth Callback URL' in n8n. Paste it in the ***Authorization Callback Domain*** in Strava. -5. Read 'Strava's API Agreement', and if you agree, check the checkbox. -6. Click on the ***Create*** button. -7. Click on ***App Icon*** and select an image from the browser window. -8. Click on the ***Save*** button. -9. Use this ***Client ID*** and ***Client Secret*** with your Strava node credentials in n8n. - -![Getting Strava credentials](/_images/integrations/builtin/credentials/strava/using-oauth.gif) diff --git a/docs/integrations/builtin/credentials/stripe.md b/docs/integrations/builtin/credentials/stripe.md deleted file mode 100644 index e9a602275..000000000 --- a/docs/integrations/builtin/credentials/stripe.md +++ /dev/null @@ -1,19 +0,0 @@ -# Stripe - -You can use these credentials to authenticate the following nodes with Stripe. - -- [Stripe Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.stripeTrigger/) -- [Stripe](/integrations/builtin/app-nodes/n8n-nodes-base.stripe/) - -## Prerequisites - -Create a [Stripe](https://stripe.com/) account. - -## Using Access Token - -1. Access your Stripe dashboard. -2. Click on the developers button in the left panel. -3. Click on API keys. -4. Use the secret key with your Stripe node credentials in n8n. - -![Getting Stripe credentials](/_images/integrations/builtin/credentials/stripe/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/supabase.md b/docs/integrations/builtin/credentials/supabase.md deleted file mode 100644 index aabe81238..000000000 --- a/docs/integrations/builtin/credentials/supabase.md +++ /dev/null @@ -1,18 +0,0 @@ -# Supabase - -You can use these credentials to authenticate the following nodes with Supabase. - -- [Supabase](/integrations/builtin/app-nodes/n8n-nodes-base.supabase/) - -## Prerequisites - -Create a [Supabase](https://supabase.com/) account. - -## Using Access Token - -1. In the [Supabase UI](https://app.supabase.io/), navigate to the project you would like to connect to. -2. Navigate to Settings page (through the gears button in the left sidebar). -3. Under *Project settings*, click on **API**. -4. Copy the value from the Supabase `URL` field into the `Host` field of your Supabase credentials in n8n. -5. Copy the value from the Supabase `service_role secret` field into the `Service Role Secret` field of your Supabase credentials in n8n. -6. Click `Save` on the n8n credentials screen. diff --git a/docs/integrations/builtin/credentials/surveymonkey.md b/docs/integrations/builtin/credentials/surveymonkey.md deleted file mode 100644 index 52cfae8e0..000000000 --- a/docs/integrations/builtin/credentials/surveymonkey.md +++ /dev/null @@ -1,34 +0,0 @@ -# SurveyMonkey - -You can use these credentials to authenticate the following nodes with SurveyMonkey. - -- [SurveyMonkey Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.surveyMonkeyTrigger/) - - -## Prerequisites - -Create a [SurveyMonkey](https://surveymonkey.com/) account. - -## Using OAuth - -1. Access your SurveyMonkey dashboard. -2. Click on the context menu in the top right. -3. Click on Integrations & Plug-ins -4. Click on Develop. -5. Click on My Apps in the top panel. -6. Create a new app, fill in details. -7. Once created, go to settings. -8. Use the client ID and client secret with your SurveyMonkey OAuth API credentials in n8n. - -## Using Access Token - -1. Access your SurveyMonkey dashboard. -2. Click on the context menu in the top right. -3. Click on Integrations & Plug-ins -4. Click on Develop. -5. Click on My Apps in the top panel. -6. Create a new app, fill in details. -7. Once created, go to settings. -8. Use the access token, client ID and client secret with your SurveyMonkey node credentials in n8n. - -![Getting SurveyMonkey credentials](/_images/integrations/builtin/credentials/surveymonkey/getting-credentials.gif) diff --git a/docs/integrations/builtin/credentials/syncromsp.md b/docs/integrations/builtin/credentials/syncromsp.md deleted file mode 100644 index d83a8c2b9..000000000 --- a/docs/integrations/builtin/credentials/syncromsp.md +++ /dev/null @@ -1,19 +0,0 @@ -# SyncroMSP - -You can use these credentials to authenticate the following nodes with SyncroMSP. - -- [SyncroMSP](/integrations/builtin/app-nodes/n8n-nodes-base.syncroMsp/) - -## Prerequisites - -Create a [SyncroMSP](https://syncromsp.com/) account. - -## Using Access Token - -1. With administrator privileges, navigate to the [API Tokens page in SyncroMSP](https://n8nchangelog.syncromsp.com/api_tokens). -2. Click on the `+ New Token` button. -3. On the `Custom Permissions` tab, enter a name for your new token and adjust the permissions to match your requirements. -4. Click `Create API Token` once done. -5. Copy the key shown by SyncroMSP into the `API Key` field of your SyncroMSP credentials in n8n. -6. Enter your SyncroMSP subdomain (the part between `https://` and `.syncromsp.com`) in the `Subdomain` field of your SyncroMSP credentials in n8n. -7. Click `Save` on the n8n credentials screen. diff --git a/docs/integrations/builtin/credentials/taiga.md b/docs/integrations/builtin/credentials/taiga.md deleted file mode 100644 index d3551e001..000000000 --- a/docs/integrations/builtin/credentials/taiga.md +++ /dev/null @@ -1,16 +0,0 @@ -# Taiga - -You can use these credentials to authenticate the following nodes with Taiga. - -- [Taiga](/integrations/builtin/app-nodes/n8n-nodes-base.taiga/) -- [Taiga Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.taigaTrigger/) - -## Prerequisites - -Create a [Taiga](https://taiga.io/) account. - -## Using Username and Password - -Use your username and password with the Taiga node credentials in n8n. - -**Note:** For self-hosted instances, you will have to additionally use your Taiga URL with the Taiga node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/tapfiliate.md b/docs/integrations/builtin/credentials/tapfiliate.md deleted file mode 100644 index 8f7f7e6ed..000000000 --- a/docs/integrations/builtin/credentials/tapfiliate.md +++ /dev/null @@ -1,26 +0,0 @@ -# Tapfiliate - -You can use these credentials to authenticate the following nodes with Tapfiliate. - -- [Tapfiliate](/integrations/builtin/app-nodes/n8n-nodes-base.tapfiliate/) - -## Prerequisites - -Create a [Tapfiliate](https://tapfiliate.com/) account. - -## Using API Key - -1. Open your Tapfiliate [dashboard](https://app.tapfiliate.com/dashboard/) page. -2. Click on your avatar on the bottom left of the window. -3. Select 'Profile Settings' from the dropdown list. -4. Scroll down to the ***API Key*** section. -5. Copy the displayed ***API Key***. -6. Enter a name for your credentials in the ***Credentials Name*** field in the 'Tapfiliate API' credentials in n8n. -7. Paste the API key in the ***API Key*** field in the 'Tapfiliate API' credentials in n8n. -8. Click the ***Create*** button to create your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/telegram.md b/docs/integrations/builtin/credentials/telegram.md deleted file mode 100644 index 4a66d7c22..000000000 --- a/docs/integrations/builtin/credentials/telegram.md +++ /dev/null @@ -1,16 +0,0 @@ -# Telegram - -You can use these credentials to authenticate the following nodes with Telegram. - -- [Telegram](/integrations/builtin/app-nodes/n8n-nodes-base.telegram/) -- [Telegram Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.telegramTrigger/) - -## Prerequisites - -Create a [Telegram](https://telegram.org/) account. - -## Using Bot Access Token - -1. Start a chat with the [Botfather](https://telegram.me/BotFather). -2. Enter `/newbot` and reply with your new bot's display name and username. -3. Copy the bot token and use it in the Telegram node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/thehive.md b/docs/integrations/builtin/credentials/thehive.md deleted file mode 100644 index 4374e1a57..000000000 --- a/docs/integrations/builtin/credentials/thehive.md +++ /dev/null @@ -1,18 +0,0 @@ -# TheHive - -You can use these credentials to authenticate the following nodes with The Hive. - -- [TheHive](/integrations/builtin/app-nodes/n8n-nodes-base.theHive/) - -## Prerequisites - -Install [TheHive](https://github.com/TheHive-Project/TheHiveDocs/blob/master/installation/install-guide.md) on your server. - -## Using API Key - -1. Access your TheHive dashboard. -2. Click on the ***Organization*** tab in the top right. -3. Click on the ***Create API Key*** button for the user you want to generate the API Key for. -4. Use this ***API Key*** and your instance ***URL*** with your TheHive node credentials in n8n. - -![Getting TheHive credentials](/_images/integrations/builtin/credentials/thehive/using-api.gif) diff --git a/docs/integrations/builtin/credentials/timescaledb.md b/docs/integrations/builtin/credentials/timescaledb.md deleted file mode 100644 index ac16c3272..000000000 --- a/docs/integrations/builtin/credentials/timescaledb.md +++ /dev/null @@ -1,14 +0,0 @@ -# TimescaleDB - -You can use these credentials to authenticate the following nodes with TimescaleDB. - -- [TimescaleDB](/integrations/builtin/app-nodes/n8n-nodes-base.timescaleDb/) - -## Prerequisites - -An available instance of TimescaleDB. - -## Using Database Connection - -1. Retrieve your TimescaleDB credentials and connection parameters. -2. Use the credentials and connection parameters with your TimescaleDB node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/todoist.md b/docs/integrations/builtin/credentials/todoist.md deleted file mode 100644 index 396281e17..000000000 --- a/docs/integrations/builtin/credentials/todoist.md +++ /dev/null @@ -1,35 +0,0 @@ -# Todoist - -You can use these credentials to authenticate the following nodes with Todoist. - -- [Todoist](/integrations/builtin/app-nodes/n8n-nodes-base.todoist/) - -## Prerequisites - -Create a [Todoist](https://todoist.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Todoist account to n8n. - - -1. Access your Todoist [App Management Console](https://developer.todoist.com/appconsole.html) -2. Enter a name in the ***App display name*** field and click on the ***Create app*** button. -3. Copy the ***OAuth Callback URL*** from n8n and paste it in the ***OAuth redirect URL*** field. -4. Click on the ***Save settings*** button. -5. Use the provided ***Client ID*** and ***Client secret*** with your Todoist OAuth2 API credentials in n8n. -6. Click on the circle button in the OAuth section to connect a Todoist account to n8n. -7. Click the ***Save*** button to save your credentials in n8n. - -![Getting Todoist OAuth credentials](/_images/integrations/builtin/credentials/todoist/using-oauth.gif) - -## Using Access Token - -1. Access your Todoist dashboard. -2. Click on the gear icon in the top right. -3. Select Integrations on the left panel. -4. Scroll down to see your API token. -5. Use the API token with your Todoist node credentials in n8n. - -![Getting Todoist credentials](/_images/integrations/builtin/credentials/todoist/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/toggl.md b/docs/integrations/builtin/credentials/toggl.md deleted file mode 100644 index 77aec49ab..000000000 --- a/docs/integrations/builtin/credentials/toggl.md +++ /dev/null @@ -1,13 +0,0 @@ -# Toggl - -You can use these credentials to authenticate the following nodes with Toggl. - -- [Toggl Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.togglTrigger/) - -## Prerequisites - -Create a [Toggl](https://toggl.com/) account. - -## Using Username and Password - -1. Use your Toggle username and password with your node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/travisci.md b/docs/integrations/builtin/credentials/travisci.md deleted file mode 100644 index 7311171c1..000000000 --- a/docs/integrations/builtin/credentials/travisci.md +++ /dev/null @@ -1,20 +0,0 @@ -# Travis CI - -You can use these credentials to authenticate the following nodes with Travis CI. - -- [Travis CI](/integrations/builtin/app-nodes/n8n-nodes-base.travisCI/) - -## Prerequisites - -Create a [Travis CI](https://travis-ci.org/) account. - -## Using Access Token - -1. Open your Travis CI dashboard. -2. Click on the user icon in the top right. -3. Click on 'Settings' in the dropdown list. -4. Click on the ***Settings*** tab on the page. -5. Copy the ***Token*** from the ***API authentication*** section and use it with your Travis API credentials in n8n. -6. Click on the ***Save*** button to save your credentials. - -![Getting Travis CI credentials](/_images/integrations/builtin/credentials/travisci/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/trello.md b/docs/integrations/builtin/credentials/trello.md deleted file mode 100644 index 739c9f649..000000000 --- a/docs/integrations/builtin/credentials/trello.md +++ /dev/null @@ -1,19 +0,0 @@ -# Trello - -You can use these credentials to authenticate the following nodes with Trello: - -- [Trello](/integrations/builtin/app-nodes/n8n-nodes-base.trello/) -- [Trello Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.trelloTrigger/) - -## Prerequisites - -Create a [Trello](https://trello.com/) account. - -## Using an access token - -1. Go to the [Trello API Key ](https://trello.com/app-key){:target_blank .external-link} portal. The page 404s if you're not signed into Trello. -1. Copy your API key at the top. -1. Select **generate a Token** to create your token. When prompted, allow it all the permissions it asks for. ---8<-- "_snippets/integrations/builtin/credentials/open-credential-modal-list.md" -1. Enter the API key and API token. -1. Select **Save**. n8n tests the connection. diff --git a/docs/integrations/builtin/credentials/twake.md b/docs/integrations/builtin/credentials/twake.md deleted file mode 100644 index fd2ff9b4e..000000000 --- a/docs/integrations/builtin/credentials/twake.md +++ /dev/null @@ -1,23 +0,0 @@ -# Twake - -You can use these credentials to authenticate the following nodes with Twake. - -- [Twake](/integrations/builtin/app-nodes/n8n-nodes-base.twake/) - -## Prerequisites - -Create a [Twake](https://twake.app/) account. - -## Using Access Token - -1. Access your [Twake](https://web.twake.app) workspace. -2. Click on ***Main*** in the top left corner. -3. Select 'Workspace settings' from the dropdown list. -4. Select ***Applications and connectors***. -5. Click on the ***Search applications...*** button. -6. Search for `n8n` and click on the ***Display*** button. -7. Click on ***Install*** and select ***Confirm***. -8. Click on ***Configure*** and copy the Workspace Key. -9. Use the Workspace Key with your Twake node credentials in n8n. - -![Getting Twake workspace key](/_images/integrations/builtin/credentials/twake/using-workspace-key.gif) diff --git a/docs/integrations/builtin/credentials/twilio.md b/docs/integrations/builtin/credentials/twilio.md deleted file mode 100644 index 185718d1c..000000000 --- a/docs/integrations/builtin/credentials/twilio.md +++ /dev/null @@ -1,49 +0,0 @@ -# Twilio - -You can use these credentials to authenticate the following nodes with Twilio. - -- [Twilio](/integrations/builtin/app-nodes/n8n-nodes-base.twilio/) - -## Prerequisites - -Create a [Twilio](https://twilio.com/) account. - -## Using Auth Token - -1. Open your Twilio project [dashboard](https://www.twilio.com/console). -2. Copy the displayed Account SID. -3. Enter a name for your credentials in the ***Credentials Name*** field in the 'Twilio API' credentials in n8n. -4. Paste the Account SID in the ***Account SID*** field in the 'Twilio API' credentials in n8n. -5. Copy the Auth Token from the Twilio project dashboard. -6. Paste the Auth Token in the ***Auth Token*** field in the 'Twilio API' credentials in n8n. -7. Click on the ***Create*** button to create the credentials. - -The following video demonstrates the steps mentioned above. - -
- -
- -## Using API Key - -1. Open your Twilio project [dashboard](https://www.twilio.com/console). -2. Copy the displayed Account SID. -3. Enter a name for your credentials in the ***Credentials Name*** field in the 'Twilio API' credentials in n8n. -4. Select 'API Key' from the ***Auth Type*** dropdown list. -5. Paste the Account SID in the ***Account SID*** field in the 'Twilio API' credentials in n8n. -6. Click on ***Settings*** in the left-sidebar. -7. Select ***API Keys*** under the ***Settings***. -8. Click on the ***Create new API Key*** button. -9. Enter a name in the ***Friendly Name*** field. -10. Click on the ***Create API Key*** button. -11. Copy the displayed SID. -12. Paste the SID in the ***API Key SID*** field in the 'Twilio API' credentials in n8n. -13. Copy the Secret from the Twilio dashboard. -14. Paste the Secret in the ***API Key Secret*** field in the 'Twilio API' credentials in n8n. -15. Click on the ***Create*** button to create the credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/twist.md b/docs/integrations/builtin/credentials/twist.md deleted file mode 100644 index 157ba6942..000000000 --- a/docs/integrations/builtin/credentials/twist.md +++ /dev/null @@ -1,48 +0,0 @@ -# Twist - -You can use these credentials to authenticate the following nodes with Twist. - -- [Twist](/integrations/builtin/app-nodes/n8n-nodes-base.twist/) - -## Prerequisites - -Create a [Twist](https://twist.com/) account. - -## Using OAuth - -!!! note "Callback URL with Twist" - **Note:** The Redirect URL should be a URL in your domain. For example, `https://mytemplatemaker.example.com/gr_callback`. Twist doesn't accept the localhost callback URL. Refer to the [FAQs](#how-to-configure-the-oauth-credentials-for-the-local-environment) to learn to configure the credentials for the local environment. - - -1. Access your [Twist](https://twist.com) workspace. -2. Click on your avatar in the top right corner. -3. Select 'Add integrations...' from the dropdown list. -4. Click on ***Build*** on the top. -5. Click on the ***Add a new integration*** button. -6. Enter a name in the ***Integration name*** field. -7. Enter a description in the ***Description*** field. -8. Select 'General integration' from the ***Integration type*** dropdown list. -9. Click on the ***Create my integration*** button. -10. Click on ***OAuth Authentication*** from the left sidebar. -11. Copy the 'OAuth Callback URL' provided in the Twist OAuth2 API credentials in n8n and paste it in the ***OAuth 2 redirect URL*** field on your Twist integration page. -12. Click on the ***Update integration*** button. -13. Use the ***Client ID*** and ***Client Secret*** with your Twist node credentials in n8n. -14. Click on the circle button in the OAuth section to connect a Twist account to n8n. -15. Click the ***Save*** button to save your credentials in n8n. - -![Getting Twist credentials](/_images/integrations/builtin/credentials/twist/using-oauth.gif) - -## FAQs - -### How to configure the OAuth credentials for the local environment? -Twist doesn't accept the localhost callback URL. However, you can follow the steps mentioned below to configure the OAuth credentials for the local environment: -1. We will use [ngrok](https://ngrok.com/) to expose the local server running on port `5678` to the internet. In your terminal, run the following command: -```sh -ngrok http 5678 -``` -2. Run the following command in a new terminal. Replace `` with the URL that you get from the previous step. -```sh -export WEBHOOK_URL= -``` -3. Start your n8n instance. -4. Follow the instructions mentioned in the [Using OAuth](#using-oauth) section to configure your credentials. diff --git a/docs/integrations/builtin/credentials/twitter.md b/docs/integrations/builtin/credentials/twitter.md deleted file mode 100644 index c5731619b..000000000 --- a/docs/integrations/builtin/credentials/twitter.md +++ /dev/null @@ -1,41 +0,0 @@ -# Twitter - -You can use these credentials to authenticate the following nodes with Twitter. - -- [Twitter](/integrations/builtin/app-nodes/n8n-nodes-base.twitter/) - -## Prerequisites - -Create a [Twitter developer account](https://developer.twitter.com/). - -## Using OAuth - -1. Access the [Twitter Developer](https://developer.twitter.com/en/portal/projects-and-apps) portal. -2. Fill out the questionnaire to gain essential access and click **Next** once done. -![Getting essential access to the Twitter API](/_images/integrations/builtin/credentials/twitter/essential-access.png) -3. Confirm the Developer agreement by checking the box and clicking **Submit** once done. -![The Twitter Developer Agreement](/_images/integrations/builtin/credentials/twitter/developer-agreement.png) -4. Twitter will now send you a confirmation email. Click the **Confirm your email** button in the email. -![Email Validation Email](/_images/integrations/builtin/credentials/twitter/email-validation.png) -5. After confirming your email, you are redirected to the [#Welcome to the Twitter Developer Platform](https://developer.twitter.com/en/portal/register/welcome) page. Enter a name for your Twitter application and click the **Get keys** button. -6. Copy the **API Key**, **API Key Secret** shown on the next page. -![API Keys provided by Twitter](/_images/integrations/builtin/credentials/twitter/api-keys.png) -7. Click the **Skip to dashboard** link at the bottom of the page and click the **Yes, I saved them** button. -8. Click the **Gear button** next to your newly created app to open it's **App settings**. -![The App settings button](/_images/integrations/builtin/credentials/twitter/app-settings-button.png) -9. In the Authentication settings sections, click **Edit**. -10. Turn on the **Enable 3-legged OAuth** switch and paste the URL shown in the **OAuth Redirect URL** of the n8n credentials screen into the **Callback URLs** field of your Twitter apps authentication settings. -11. Enter a valid Website URL in the respective field (for example https://n8n.io). -![The App settings button](/_images/integrations/builtin/credentials/twitter/oauth-settings.png) -12. Save your input by clicking the **Save** button at the bottom of the page. -13. Under App permissions, click **Edit** and choose the appropriate permissions for your app (pick **Read and write and Direct message** if you want to use all functions of the Twitter n8n in n8n) and click **Save** to confirm. -14. In the sidebar on the left, click on the Project your app has been created in (usually **Project 1**) and then on the **Apply for Elevated** button. -15. Fill out the questionnaire and confirm the inputs on each questionnaire page with a click on **Next** (**Submit** on the final page). -![Application process for elevated access to the Twitter API](/_images/integrations/builtin/credentials/twitter/elevated-access.png) -16. Once you receive confirmation that your application has been approved, you're ready to use the n8n Twitter node. -17. In the n8n credentials screen, paste your **API Key** from steps 6 above into the **Consumer Key** field, and your **API Key Secret** into the **Consumer Secret** field. -18. Click **Connect my account** and confirm the connection by clicking **Authorize app**. - -## Further Reference - -- [Application-only Authentication](https://developer.twitter.com/en/docs/authentication/oauth-2-0/application-only) diff --git a/docs/integrations/builtin/credentials/typeform.md b/docs/integrations/builtin/credentials/typeform.md deleted file mode 100644 index dca022e9b..000000000 --- a/docs/integrations/builtin/credentials/typeform.md +++ /dev/null @@ -1,42 +0,0 @@ -# Typeform - -You can use these credentials to authenticate the following nodes with Typeform. - -- [Typeform Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.typeFormTrigger/) - -## Prerequisites - -Create a [Typeform](https://typeform.com/) account. - -## Using OAuth - -1. Access your Typeform dashboard. -2. Go to your user profile in the top right. -3. Click on 'Settings' and then click on 'Developer apps' in the sidebar. -4. Click on the ***Register a new app*** button. -5. Copy the 'OAuth Callback URL' provided in the Typeform OAuth2 API credentials in n8n and paste it in the ***Redirect URI(s)*** section in the Typeform app registration page. -6. Enter any other information necessary and click on the ***Register app*** button. -7. Use the displayed ***Client ID*** and ***Client secret*** with your Typeform OAuth2 API credentials in n8n. -8. Click on the circle button in the OAuth section to connect a Typeform account to n8n. -9. Click the ***Save*** button to save your credentials. - -![Getting TypeForm OAuth credentials](/_images/integrations/builtin/credentials/typeform/using-oauth.gif) - -## Using Access Token - -1. Open the Typeform [dashboard](https://admin.typeform.com). -2. Click on your avatar on the top right and select 'Settings'. -3. Click on ***Personal tokens*** under the ***Profile*** section in the sidebar. -4. Click on the ***Generate a new token*** button. -5. Enter a name in the ***Token name*** field. -6. Click on the ***Generate token*** button. -7. Click on the ***Copy*** button to copy the access token. -9. Enter a name for your credentials in the ***Credentials Name*** field in the 'Typeform API' credentials in n8n. -10. Paste the access token in the ***Access Token*** field in the 'Typeform API' credentials in n8n. -11. Click the ***Create*** button to save your credentials in n8n. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/unleashedsoftware.md b/docs/integrations/builtin/credentials/unleashedsoftware.md deleted file mode 100644 index 05c12d703..000000000 --- a/docs/integrations/builtin/credentials/unleashedsoftware.md +++ /dev/null @@ -1,18 +0,0 @@ -# Unleashed Software - -You can use these credentials to authenticate the following nodes with Unleashed Software. - -- [Unleashed Software](/integrations/builtin/app-nodes/n8n-nodes-base.unleashedSoftware/) - -## Prerequisites - -Create an [Unleashed Software](https://www.unleashedsoftware.com/) account. - -## Using Access Token - -1. Access your Unleashed Software dashboard. -2. Click on ***Integration*** in the left sidebar and select ***Unleashed API Access***. -3. Use the displayed ***API Id*** and ***API Key*** with your Unleashed API credentials in n8n. -4. Click on the ***Save*** button to save your credentials. - -![Getting Unleashed Software credentials](/_images/integrations/builtin/credentials/unleashedsoftware/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/uplead.md b/docs/integrations/builtin/credentials/uplead.md deleted file mode 100644 index d33b590b4..000000000 --- a/docs/integrations/builtin/credentials/uplead.md +++ /dev/null @@ -1,19 +0,0 @@ -# UpLead - -You can use these credentials to authenticate the following nodes with UpLead. - -- [UpLead](/integrations/builtin/app-nodes/n8n-nodes-base.upLead/) - -## Prerequisites - -Create an [UpLead](https://uplead.com/) account. - -## Using Access Token - -1. Access your UpLead dashboard. -2. Click on your name in the bottom left. -3. Click on Profile. -4. Scroll down and click on the *Generate New API Key*. -5. Use the API Key with your UpLead node credentials in n8n. - -![Getting UpLead credentials](/_images/integrations/builtin/credentials/uplead/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/uproc.md b/docs/integrations/builtin/credentials/uproc.md deleted file mode 100644 index 8631cc907..000000000 --- a/docs/integrations/builtin/credentials/uproc.md +++ /dev/null @@ -1,18 +0,0 @@ -# uProc - -You can use these credentials to authenticate the following nodes with uProc. - -- [uProc](/integrations/builtin/app-nodes/n8n-nodes-base.uProc/) - -## Prerequisites - -Create a [uProc](https://uProc.io) account. - -## Using API Key - -1. Access the [uProc dashboard](https://app.uproc.io/#/dashboard). -2. Click on the ***Settings*** tab on the left sidebar. -3. Click on the ***Integrations*** tab. -4. Use the displayed ***Email*** and ***API Key (real)*** with your uProc node credentials in n8n. - -![Getting uProc credentials](/_images/integrations/builtin/credentials/uproc/using-api.gif) diff --git a/docs/integrations/builtin/credentials/uptimerobot.md b/docs/integrations/builtin/credentials/uptimerobot.md deleted file mode 100644 index 81042d773..000000000 --- a/docs/integrations/builtin/credentials/uptimerobot.md +++ /dev/null @@ -1,27 +0,0 @@ -# UptimeRobot - -You can use these credentials to authenticate the following nodes with UptimeRobot. - -- [UptimeRobot](/integrations/builtin/app-nodes/n8n-nodes-base.uptimeRobot/) - -## Prerequisites - -Create an [UptimeRobot](https://uptimeRobot.com/) account. - -## Using API Key - -1. Open your UptimeRobot [dashboard](https://uptimerobot.com/dashboard). -2. Click on ***My Settings*** in the navigation menu. -3. Scroll down to the ***API Settings*** at the bottom. -4. Click on ***Create the main API key*** under the ***Main API Key*** section. -4. Click on ***Create the main API key*** button. -5. Copy the displayed API key. -6. Enter the name for your credentials in the ***Credentials Name*** field in the 'UptimeRobot API' credentials in n8n. -7. Paste the API key in the ***API Key*** field in the 'UptimeRobot API' credentials in n8n. -8. Click on the ***Create*** button to create your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/urlscanio.md b/docs/integrations/builtin/credentials/urlscanio.md deleted file mode 100644 index b3b1ee549..000000000 --- a/docs/integrations/builtin/credentials/urlscanio.md +++ /dev/null @@ -1,24 +0,0 @@ -# urlscan.io - -You can use these credentials to authenticate the following nodes with UptimeRobot. - -- [urlscan.io](/integrations/builtin/app-nodes/n8n-nodes-base.urlScanIo/) - -## Prerequisites - -Create an [urlscan.io](https://urlscan.io/) account. - -## Using API key - -From urlscan.io: - -1. Navigate to your **Settings&API** page. -2. Under the API Keys section click **+ Create new API key**. -3. Enter a description for your new API key as prompted and click **+ Create API key**. -4. Copy the new API key for use in n8n. - -From n8n: - -5. Enter the **API Key** obtained above. -6. Click **Save** to create your credentials. - diff --git a/docs/integrations/builtin/credentials/venafitlsprotectcloud.md b/docs/integrations/builtin/credentials/venafitlsprotectcloud.md deleted file mode 100644 index b38ed59d1..000000000 --- a/docs/integrations/builtin/credentials/venafitlsprotectcloud.md +++ /dev/null @@ -1,11 +0,0 @@ -# Venafi TLS Protect Cloud - -You can use these credentials to authenticate the following nodes with Venafi TLS Protect Cloud: - -* [Venafi TLS Protect Cloud node](/integrations/builtin/app-nodes/n8n-nodes-base.venafiTlsProtectCloud/) -* [Venafi TLS Protect Cloud trigger node](/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectcloudtrigger/) - - -Follow the Venafi REST API documentation on [Obtaining an API Key](https://docs.venafi.cloud/api/obtaining-api-key/){:target=_blank .external-link}. - -Enter the API key in the **Venafi TLS Protect Cloud account** credentials modal. Refer to [Add and edit credentials](/credentials/add-edit-credentials/) for more information on working with credentials in n8n. diff --git a/docs/integrations/builtin/credentials/venafitlsprotectdatacenter.md b/docs/integrations/builtin/credentials/venafitlsprotectdatacenter.md deleted file mode 100644 index 767a3aede..000000000 --- a/docs/integrations/builtin/credentials/venafitlsprotectdatacenter.md +++ /dev/null @@ -1,10 +0,0 @@ -# Venafi TLS Protect Datacenter - -You can use these credentials to authenticate the following nodes with Venafi TLS Protect Datacenter: - -* [Venafi TLS Protect Datacenter node](/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectdatacenter/) -* [Venafi TLS Protect Datacenter trigger node](/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectdatacentertrigger/) - -Venafi provide a [PDF guide](/_downloads/venafi-tpp.pdf) to getting credentials. Follow the steps in the guide, making a note of the name and client ID you choose. When choosing scopes, make sure you choose the scopes needed for the operations you want to perform within n8n. For example, if you plan to work with certificates, including deleting them, include the **Certificate** scope in your Venafi credentials setup, with the **delete** option enabled. - -Enter the client ID, your username and password, and your Venafi domain, in the n8n **Venafi TLS Protect Datacenter account** modal. Refer to [Add and edit credentials](/credentials/add-edit-credentials/) for more information on working with credentials in n8n. diff --git a/docs/integrations/builtin/credentials/vero.md b/docs/integrations/builtin/credentials/vero.md deleted file mode 100644 index 6e89eb79e..000000000 --- a/docs/integrations/builtin/credentials/vero.md +++ /dev/null @@ -1,18 +0,0 @@ -# Vero - -You can use these credentials to authenticate the following nodes with Vero. - -- [Vero](/integrations/builtin/app-nodes/n8n-nodes-base.vero/) - -## Prerequisites - -Create a [Vero](https://getvero.com/) account. - -## Using Access Token - -1. Access your Vero dashboard. -2. Click on the cog icon in the bottom left. -3. Scroll down to see your Auth token. -4. Use the auth token with your Vero node credentials in n8n. - -![Getting Vero credentials](/_images/integrations/builtin/credentials/vero/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/vonage.md b/docs/integrations/builtin/credentials/vonage.md deleted file mode 100644 index b8a78b840..000000000 --- a/docs/integrations/builtin/credentials/vonage.md +++ /dev/null @@ -1,17 +0,0 @@ -# Vonage - -You can use these credentials to authenticate the following nodes with Vonage. - -- [Vonage](/integrations/builtin/app-nodes/n8n-nodes-base.vonage/) - -## Prerequisites - -Create a [Vonage](https://vonage.com) account. - -## Using API Key - -1. Access the [Vonage API dashboard](https://dashboard.nexmo.com/). -2. Copy the ***API key*** and the ***API Secret*** from the dashboard. -3. Use this ***API Key*** and ***API Secret*** with your Vonage node credentials in n8n. - -![Getting Vonage credentials](/_images/integrations/builtin/credentials/vonage/using-api.gif) diff --git a/docs/integrations/builtin/credentials/webflow.md b/docs/integrations/builtin/credentials/webflow.md deleted file mode 100644 index b45c52cea..000000000 --- a/docs/integrations/builtin/credentials/webflow.md +++ /dev/null @@ -1,45 +0,0 @@ -# Webflow - -You can use these credentials to authenticate the following nodes with Webflow. - -- [Webflow](/integrations/builtin/app-nodes/n8n-nodes-base.webflow/) -- [Webflow Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.webflowTrigger/) - -## Prerequisites - -Create a [Webflow](https://webflow.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Webflow account to n8n. - - -1. Access your Webflow dashboard. -2. Click on 'Account' on the top right corner. -3. Select 'Account Settings' from the dropdown list. -4. Click on the 'Integrations' tab. -5. Click on the ***+ Register New Application*** button in the 'My Applications' section. -6. Enter the name of your application in the ***Application Name*** field. -7. Enter the description of your application in the ***Application Description*** field. -8. Copy the 'OAuth Callback URL' provided in the 'Webflow OAuth2 API' credentials in n8n and paste it in the ***Redirect URI*** field in the Webflow integrations page. -9. Enter the homepage URL of your application in the ***Application Homepage*** field. -10. Click on the ***Create*** button. -11. Click on the ***View Details*** button to get the ***Client Id*** and ***Client Secret***. -12. Use these credentials with your 'Webflow OAuth2 API' credentials in n8n. -13. Click on the circle button in the OAuth section of n8n to connect a Webflow account to n8n. -14. Click on the ***Save*** button to save your credentials. - -![Getting Webflow OAuth credentials](/_images/integrations/builtin/credentials/webflow/using-oauth.gif) - -## Using Access Token - -1. Access your Webflow dashboard. -2. Click on your desired project. -3. Click on the W icon in the top left. -4. Click on Project Settings. -5. Click on the Integrations tab. -6. Scroll down and click generate API token. -7. Use the api token with your Webflow node credentials in n8n. - -![Getting Webflow credentials](/_images/integrations/builtin/credentials/webflow/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/wekan.md b/docs/integrations/builtin/credentials/wekan.md deleted file mode 100644 index 8c5ca454e..000000000 --- a/docs/integrations/builtin/credentials/wekan.md +++ /dev/null @@ -1,13 +0,0 @@ -# Wekan - -You can use these credentials to authenticate the following nodes with Wekan. - -- [Wekan](/integrations/builtin/app-nodes/n8n-nodes-base.wekan/) - -## Prerequisites - -Install [Wekan](https://github.com/wekan/wekan/wiki) on your server. - -## Using API Key - -1. Use the Wekan username, password, and URL with your Wekan node credentials in n8n. diff --git a/docs/integrations/builtin/credentials/whatsapp.md b/docs/integrations/builtin/credentials/whatsapp.md deleted file mode 100644 index d138ee4e9..000000000 --- a/docs/integrations/builtin/credentials/whatsapp.md +++ /dev/null @@ -1,8 +0,0 @@ -# WhatsApp Business - -You can use these credentials to authenticate with the [WhatsApp](/integrations/builtin/app-nodes/n8n-nodes-base.whatsapp/) node. - -Refer to the [WhatsApp documentation](https://developers.facebook.com/docs/whatsapp/){:target=_blank .external-link} to get your access token and business account ID. - - - diff --git a/docs/integrations/builtin/credentials/wise.md b/docs/integrations/builtin/credentials/wise.md deleted file mode 100644 index c296be988..000000000 --- a/docs/integrations/builtin/credentials/wise.md +++ /dev/null @@ -1,33 +0,0 @@ -# Wise - -You can use these credentials to authenticate the following nodes with Wise. - -- [Wise](/integrations/builtin/app-nodes/n8n-nodes-base.wise/) -- [Wise Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.wiseTrigger/) - -## Prerequisites - -Create a [Wise](https://wise.com/) account. - -## Using API Token - -1. Open your Wise [dashboard](https://wise.com/user/account/). -2. Click on the username on the top right and select 'Settings' from the dropdown list. -3. Scroll down to the bottom and click on ***API tokens***. -4. Click on the ***Add new token*** button. -5. Enter a name in the ***Name or description*** field. -6. Click on the ***Create token*** button. -7. Scroll down to the bottom and click on ***API tokens***. -8. Click on ***Reveal key*** to reveal the newly generated API key. -9. Enter your Wise account password in the ***Please enter your password*** field. -10. Copy the displayed API key. -11. Enter the name for your credentials in the ***Credentials Name*** field in the 'Wise API' credentials in n8n. -12. Paste the API key in the ***API Token*** field in the 'Wise API' credentials in n8n. -13. If you're using a Wise sandbox account, select 'Test' from the ***Environment*** dropdown list in the 'Wise API' credentials in n8n. -14. Click on the ***Create*** button to create your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
diff --git a/docs/integrations/builtin/credentials/woocommerce.md b/docs/integrations/builtin/credentials/woocommerce.md deleted file mode 100644 index 296e51c1f..000000000 --- a/docs/integrations/builtin/credentials/woocommerce.md +++ /dev/null @@ -1,24 +0,0 @@ -# WooCommerce - -You can use these credentials to authenticate the following nodes with WooCommerce. - -- [WooCommerce](/integrations/builtin/app-nodes/n8n-nodes-base.wooCommerce/) -- [WooCommerce Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.wooCommerceTrigger/) - -## Prerequisites - -Install the [WooCommerce](https://woocommerce.com/) plugin on your WordPress website. - -## Using Access Token - -1. Access your WordPress dashboard. -2. Select 'Settings' from the ***WooCommerce*** dropdown list. -3. Click on the ***Advanced*** tab. -4. Click on ***REST API***. -5. Click on the ***Create an API Key*** button. -6. Enter the necessary details. -7. Select 'Read/Write' from the ***Permissions*** dropdown list. -8. Click on the ***Generate API Key*** button. -9. Use your WooCommerce website URL, Consumer key & Consumer secret with your WooCommerce node credentials in n8n. - -![Getting WooCommerce credentials](/_images/integrations/builtin/credentials/woocommerce/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/wordpress.md b/docs/integrations/builtin/credentials/wordpress.md deleted file mode 100644 index 6af46ebd5..000000000 --- a/docs/integrations/builtin/credentials/wordpress.md +++ /dev/null @@ -1,22 +0,0 @@ -# WordPress - -You can use these credentials to authenticate the following nodes with WordPress. - -- [WordPress](/integrations/builtin/app-nodes/n8n-nodes-base.wordPress/) - -## Prerequisites - -- Create a [WordPress](https://wordpress.com/){:target=_blank .external-link} account or deploy WordPress on a server. - -## Using Username and Password - -1. Log in to your WordPress dashboard. -2. Select your profile image, then select **Profile**. -3. Scroll down to the **Application Password** section. -4. Enter an application name in the **New Application Password Name** field. -5. Select **Add New Application Password**. -6. Copy the displayed application password. -7. Enter your WordPress username in the **Username** field in the 'WordPress API' credentials in n8n. -8. Paste the application password in the **Password** field in the 'WordPress API' credentials in n8n. -9. Enter your WordPress website URL in the **WordPress URL** field in the 'WordPress API' credentials in n8n. -10. Select **Save** to save the credentials. diff --git a/docs/integrations/builtin/credentials/workable.md b/docs/integrations/builtin/credentials/workable.md deleted file mode 100644 index b3b90aa5f..000000000 --- a/docs/integrations/builtin/credentials/workable.md +++ /dev/null @@ -1,19 +0,0 @@ -# Workable - -You can use these credentials to authenticate the following nodes: - -- [Workable Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.workableTrigger/) - -## Prerequisites - -Create a [Workable](https://www.workable.com/) account. - -## Using API Key - -1. Log in to [Workable](https://www.workable.com/). -2. Click on the avatar on the top-right and select **Settings**, then **[Integrations](https://workable.com/backend/settings/integrations)**. -3. Scroll down to **Access Token** and click **Generate new token**. -4. Copy the newly generated token. -6. Paste the token in the **Access Token** field of the **Workable API** credentials screen in n8n. -7. Add the part between `https://` and `.workable.com` of your Workable subdomain in the Subdomain field of the n8n credentials screen. -8. Click the **Save** button to save your credentials in n8n. diff --git a/docs/integrations/builtin/credentials/wufoo.md b/docs/integrations/builtin/credentials/wufoo.md deleted file mode 100644 index 737144e58..000000000 --- a/docs/integrations/builtin/credentials/wufoo.md +++ /dev/null @@ -1,20 +0,0 @@ -# Wufoo - -You can use these credentials to authenticate the following nodes with Wufoo. - -- [Wufoo Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.wufooTrigger/) - -## Prerequisites - -Create a [Wufoo](https://wufoo.com) account. - -## Using API Key - -1. Access the [Wufoo Form Manager](https://app.wufoo.com/#/form-manager). -2. To the right of the form, click on ***...*** and select ***API Information*** from the dropdown list. -3. Copy the ***API Key***. -4. Click on ***Account*** from the top right corner and select 'My Account' from the dropdown list. -5. Copy the ***Subdomain***. -6. Use this ***API Key*** and ***Subdomain*** with your Wufoo Trigger node credentials in n8n. - -![Getting Wufoo credentials](/_images/integrations/builtin/credentials/wufoo/using-api-key.gif) diff --git a/docs/integrations/builtin/credentials/xero.md b/docs/integrations/builtin/credentials/xero.md deleted file mode 100644 index d42a83fbd..000000000 --- a/docs/integrations/builtin/credentials/xero.md +++ /dev/null @@ -1,21 +0,0 @@ -# Xero - -You can use these credentials to authenticate the following nodes with Xero. - -- [Xero](/integrations/builtin/app-nodes/n8n-nodes-base.xero/) - -## Prerequisites - -Create a [Xero](https://www.xero.com/) account. - -## Using OAuth - -1. Go to the [apps page](https://developer.xero.com/myapps) in the Xero developer portal. -2. Click on the *New app* button and fill in any necessary information. -3. Copy the 'OAuth Callback URL' provided in the Xero OAuth API credentials in n8n and paste it in the *OAuth 2.0 redirect URI* field in the Xero app creation page. -4. Click on the *Create app* button. -5. Click on *Generate a secret* and use the 'Client id' and the 'Client secret' with your Xero OAuth API credentials in n8n. -6. Click on the circle button in the OAuth section to connect a Xero account to n8n. -7. Click the *Save* button to save your credentials. - -![Getting Xero Oauth Credentials](/_images/integrations/builtin/credentials/xero/using-oauth.gif) diff --git a/docs/integrations/builtin/credentials/yourls.md b/docs/integrations/builtin/credentials/yourls.md deleted file mode 100644 index 44bb741a6..000000000 --- a/docs/integrations/builtin/credentials/yourls.md +++ /dev/null @@ -1,19 +0,0 @@ -# Yourls - -You can use these credentials to authenticate the following nodes with Yourls. - -- [Yourls](/integrations/builtin/app-nodes/n8n-nodes-base.yourls/) - -## Prerequisites - -Install [Yourls](https://github.com/YOURLS/YOURLS) on your server. - -## Using API - -1. Access your Yourls Admin dashboard. -2. Click on ***Tools*** on the top left. -3. Scroll down to the ***Secure passwordless API call*** section. -4. Copy the ***signature token***. -5. Use this ***Signature*** and the URL of your Yourls instance with your Yourls node credentials in n8n. - -![Getting Yourls credentials](/_images/integrations/builtin/credentials/yourls/using-api.gif) diff --git a/docs/integrations/builtin/credentials/zammad.md b/docs/integrations/builtin/credentials/zammad.md deleted file mode 100644 index aa6028d5c..000000000 --- a/docs/integrations/builtin/credentials/zammad.md +++ /dev/null @@ -1,23 +0,0 @@ -# Zammad - -You can use these credentials to authenticate the following nodes with Zammad. - -- [Zammad](/integrations/builtin/app-nodes/n8n-nodes-base.zammad/) - -## Prerequisites - -1. Create a hosted [Zammad](https://zammad.com/) account or set up your own Zammad instance. -2. For the token-based authentication make sure `Token Access` is enabled in the API section of your Zammad instance's System settings. - -## Basic Auth - -1. Enter the URL of your Zammad instance in the **Base URL** field of the n8n credentials screen. -2. Enter your Zammad email om the **Email** field and your password in the **Password** field. - -## Token Auth - -1. Log in to your Zammad instance -2. Click your avatar in the lower left corner, then click on **Profile** -3. Select **Token Access** and click **Create** -4. Enter a name for your new token and pick all required permissions. Click **Create** once done. -5. Copy the token shown into the **Access Token** field in n8n. Enter the URL of your Zammad instance in the **Base URL** field. diff --git a/docs/integrations/builtin/credentials/zendesk.md b/docs/integrations/builtin/credentials/zendesk.md deleted file mode 100644 index 7f0767ac3..000000000 --- a/docs/integrations/builtin/credentials/zendesk.md +++ /dev/null @@ -1,68 +0,0 @@ -# Zendesk - -You can use these credentials to authenticate the following nodes with Zendesk. - -- [Zendesk](/integrations/builtin/app-nodes/n8n-nodes-base.zendesk/) -- [Zendesk Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.zendeskTrigger/) - -## Prerequisites - -Create a [Zendesk](https://zendesk.com/) account. - -## Using OAuth - -1. Open your Zendesk dashboard. -2. Click on the gear icon on the left. -3. Click on 'API' under the ***CHANNELS*** section in the sidebar. -4. Click on the ***OAuth Clients*** tab. -5. Click on the ***Add OAuth client*** button. -6. Enter the client name in the ***Client Name*** field. -7. Enter a description in the ***Description*** field. -8. Copy the 'OAuth Callback URL' provided in the 'Zendesk OAuth2 API' credentials in n8n. -9. Paste it in the ***Redirect URLs*** field on the Zendesk API credentials page. -10. Click on the ***Save*** button. -11. Click on the ***OK*** button on the ***Please store the secret that will appear*** pop-up. -12. Scroll down to the ***Secret*** section and copy the displayed ***Secret***. -13. Paste this secret in the ***Client Secret*** field in the 'Zendesk OAuth2 API' credentials in n8n. -14. Copy the ***Unique identifier*** from the Zendesk API credentials page. -15. Paste it in the ***Client ID*** field in the 'Zendesk OAuth2 API' credentials in n8n. -16. Enter your Zendesk subdomain in the ***Subdomain*** field in the 'Zendesk OAuth2 API' credentials in n8n. Refer to the [FAQs](#how-do-i-get-my-zendesk-subdomain) to learn more about subdomain. -17. Enter the name for your credentials in the ***Credentials Name*** field in the 'Zendesk OAuth2 API' credentials in n8n. -18. Click on the circle button in the OAuth section to connect a Zendesk account to n8n. -19. Click on the ***Save*** button to save your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
- -## Using Access Token - -1. Open your Zendesk dashboard. -2. Click on the gear icon on the left. -3. Click on 'API' under the ***CHANNELS*** section in the sidebar. -4. If ***Token access*** is disabled, click on the switch to toggle it to 'Enabled'. -5. Click on the ***Add API token*** button. -6. Enter a description in the ***API token description*** field. -7. Click on the ***Copy*** button to copy the API token. -8. Click on the ***Save*** button. -9. Enter the name for your credentials in the ***Credentials Name*** field in the 'Zendesk API' credentials in n8n. -10. Enter your Zendesk subdomain in the ***Subdomain*** field. Refer to the [FAQs](#how-do-i-get-my-zendesk-subdomain) to learn more about subdomain. -11. Enter your Zendesk email address in the ***Email*** field. -12. Paste the ***API token*** in the ***API Token*** field. -13. Click on the ***Save*** button to save your credentials. - -The following video demonstrates the steps mentioned above. - -
- -
- -## FAQs - -### How do I get my Zendesk subdomain? - -To get your Zendesk subdomain, follow the steps mentioned below. -1. Access your Zendesk dashboard. -2. Copy the string of characters located between `https://` and `.zendesk.com/agent/dashboard` in your Zendesk URL. This string is the subdomain. For example, if your Zendesk URL is `https://example.zendesk.com/agent/dashboard`, the subdomain will be `example`. diff --git a/docs/integrations/builtin/credentials/zoho.md b/docs/integrations/builtin/credentials/zoho.md deleted file mode 100644 index 25dc0e80b..000000000 --- a/docs/integrations/builtin/credentials/zoho.md +++ /dev/null @@ -1,26 +0,0 @@ -# Zoho - -You can use these credentials to authenticate the following nodes with Zoho. - -- [Zoho CRM](/integrations/builtin/app-nodes/n8n-nodes-base.zohoCRM/) - -## Prerequisites - -Create a [Zoho](https://www.zoho.com/) account. - -## Using OAuth - -!!! note "Note for n8n Cloud users" - You'll only need to enter the Credentials Name and click on the circle button in the OAuth section to connect your Zoho account to n8n. - - -1. Access your [Zoho Developer Console](https://api-console.zoho.com/). -2. Click on the 'GET STARTED' button. -3. Click on the 'Server-based Applications' box. -4. Copy the 'OAuth Callback URL' provided in the Zoho OAuth2 API credentials in n8n and paste it in the *Authorized Redirect URIs* field in the Zoho API Console app creation page. -5. Fill in any other necessary information and click on the 'CREATE' button. -6. Use the 'Client ID' and the 'Client Secret' displayed with your Zoho OAuth2 API credentials in n8n. -7. Click on the circle button in the OAuth section to connect a Zoho CRM account to n8n. -8. Click the *Save* button to save your credentials. - -![Getting Zoho credentials](/_images/integrations/builtin/credentials/zoho/getting-oauth-credentials.gif) diff --git a/docs/integrations/builtin/credentials/zoom.md b/docs/integrations/builtin/credentials/zoom.md deleted file mode 100644 index 9c9e9ec0b..000000000 --- a/docs/integrations/builtin/credentials/zoom.md +++ /dev/null @@ -1,41 +0,0 @@ -# Zoom - -You can use these credentials to authenticate the following nodes with Zoom. - -- [Zoom](/integrations/builtin/app-nodes/n8n-nodes-base.zoom/) - -## Prerequisites - -Create a [Zoom](https://zoom.us/) account. - -## Using OAuth - - - -1. Visit the [Zoom App Marketplace](https://marketplace.zoom.us/) and select the 'Build App' option in the *Develop* dropdown on the top-right corner. -2. Create a new OAuth app. -3. Select 'User-managed app'. -4. Set the "Would you like to publish this app on Zoom App Marketplace?" slider to off. -5. Click on the *Create* button. -6. Copy the 'OAuth Callback URL' provided in the Zoom OAuth2 API credentials in n8n and paste it in the 'Redirect URL for OAuth' section in the Zoom app creation page. -7. Copy the Whitelist URL' provided in the Zoom OAuth2 API credentials in n8n and paste it in the 'Redirect URL for OAuth' section in the Zoom app creation page. -8. Copy the Client ID and Client Secret provided in the Zoom app creation page and paste it in the Zoom OAuth2 API credentials in n8n. -9. Enter any necessary information and click continue. -10. In the 'Scopes' section, click *Add Scopes* and choose the scopes that you plan to use. -11. Click on the circle button in the OAuth section to connect your Zoom account to n8n. -12. Click the *Save* button to save your credentials. - -![Getting Zoom OAuth credentials](/_images/integrations/builtin/credentials/zoom/using-oauth.gif) - -## Using Access Token - -1. Visit the [Zoom App Marketplace](https://marketplace.zoom.us/) and select the 'Build App' option in the *Develop* dropdown on the top-right corner. -2. Create a new JWT app and enter any necessary information. -3. Go to the 'App Credentials' tab. -4. Click on *View JWT Token* and copy the given token. -5. Go to the 'Activation' tab and click on the *Activate your app* button. -6. Use the JWT token you copied with your Zoom API credentials in n8n. - -![Getting Zoom JWT credentials](/_images/integrations/builtin/credentials/zoom/using-access-token.gif) diff --git a/docs/integrations/builtin/credentials/zulip.md b/docs/integrations/builtin/credentials/zulip.md deleted file mode 100644 index bfe7b4dcd..000000000 --- a/docs/integrations/builtin/credentials/zulip.md +++ /dev/null @@ -1,19 +0,0 @@ -# Zulip - -You can use these credentials to authenticate the following nodes with Zulip. - -- [Zulip](/integrations/builtin/app-nodes/n8n-nodes-base.zulip/) - -## Prerequisites - -Create a [Zulip](https://zulip.com/) account. - -## Using Access Token - -1. Access your Zulip dashboard. -2. Click on the gear icon on the top right. -3. Click on ***Settings***. -4. Click on the ***Show/change your API key*** button under the ***API Key*** section. -5. Use your Email, URL, and API Key in your Zulip credentials. - -![Getting Zulip credentials](/_images/integrations/builtin/credentials/zulip/using-access-token.gif) diff --git a/docs/integrations/builtin/index.md b/docs/integrations/builtin/index.md deleted file mode 100644 index 2e0fc94c2..000000000 --- a/docs/integrations/builtin/index.md +++ /dev/null @@ -1,29 +0,0 @@ -# Built-in integrations - -This section contains the node library: reference documentation for every built-in node in n8n, and their credentials. - -## Node types - -There are three node types in n8n: app nodes, trigger nodes, and core nodes. - -### App nodes - -These nodes provide integrations with external services. - -### Trigger nodes - -The trigger nodes start a workflow and supply the initial data. A workflow can contain multiple trigger nodes but with each execution, only one of them will execute. This is because the other trigger nodes would not have any input as they're the nodes from which the execution of the workflow starts. - -### Core nodes - -Core nodes provide key functionality, such as describing workflow logic, or manipulating data. Some core nodes are trigger nodes (such as the Webhook Trigger Node). - -## Credentials - -External services need a way to identify and authenticate users. This data can range from an API key over an email/password combination to a long multi-line private key. You can save these in n8n as credentials. - -Nodes in n8n can then request that credential information. As another layer of security, only node types with specific access rights can access the credentials. - -To make sure that the data is secure, it gets saved to the database encrypted. n8n uses a random personal encryption key, which it automatically generates on the first run of n8n and then saved under `~/.n8n/config`. - -To learn more about creating, managing, and sharing credentials, refer to [Manage credentials](/credentials/). diff --git a/docs/integrations/builtin/trigger-nodes/index.md b/docs/integrations/builtin/trigger-nodes/index.md deleted file mode 100644 index 4b6301180..000000000 --- a/docs/integrations/builtin/trigger-nodes/index.md +++ /dev/null @@ -1,3 +0,0 @@ -# Trigger nodes library - -This section provides information about n8n's trigger nodes. diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.activeCampaignTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.activeCampaignTrigger.md deleted file mode 100644 index c8430a7fe..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.activeCampaignTrigger.md +++ /dev/null @@ -1,29 +0,0 @@ -# ActiveCampaign Trigger - -[ActiveCampaign](https://www.activecampaign.com/) is a cloud software platform for small-to-mid-sized business. The company offers software for customer experience automation, which combines the email marketing, marketing automation, sales automation, and CRM categories. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/activeCampaign/). - - - -## Example Usage - -This workflow allows you to receive updates when a new account is added by an admin in ActiveCampaign. You can also find the [workflow](https://n8n.io/workflows/488) on the website. This example usage workflow would use the following node. -- [ActiveCampaign Trigger]() - -The final workflow should look like the following image. - -![A workflow with the ActiveCampaign Trigger node](/_images/integrations/builtin/trigger-nodes/activecampaigntrigger/workflow.png) - - -### 1. ActiveCampaign Trigger node - -1. First of all, you'll have to enter credentials for the ActiveCampaign Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/activeCampaign/). -2. Select 'account_add' from the *Events* dropdown list. -3. Select 'Admin' from the *Source* dropdown list. -4. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the ActiveCampaign Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.acuitySchedulingTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.acuitySchedulingTrigger.md deleted file mode 100644 index 7b0f740fd..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.acuitySchedulingTrigger.md +++ /dev/null @@ -1,29 +0,0 @@ -# Acuity Scheduling Trigger - -[Acuity Scheduling](https://acuityscheduling.com/) is a cloud-based appointment scheduling software solution that enables business owners to manage their appointments online. It has the capability to automatically sync calendars according to users' time zones and can send regular alerts and reminders to users regarding their appointment schedules. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/acuityScheduling/). - - - -## Example Usage - -This workflow allows you to receive updates when a new appointment is scheduled on Acuity Scheduling. You can also find the [workflow](https://n8n.io/workflows/533) on the website. This example usage workflow would use the following node. - -- [Acuity Scheduling Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Acuity Scheduling Trigger node](/_images/integrations/builtin/trigger-nodes/acuityschedulingtrigger/workflow.png) - - -### 1. Acuity Scheduling Trigger node - -1. First of all, you'll have to enter credentials for the Acuity Scheduling Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/acuityScheduling/). -2. Select the `appointment.scheduled` option from the *Event* dropdown list. -3. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Acuity Scheduling Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.affinityTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.affinityTrigger.md deleted file mode 100644 index 762ba9d3d..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.affinityTrigger.md +++ /dev/null @@ -1,27 +0,0 @@ -# Affinity Trigger - -[Affinity](https://www.affinity.co/) is a powerful relationship intelligence platform enabling teams to leverage their network to close the next big deal. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/affinity/). - - -## Example Usage - -This workflow allows you to receive updates when a new list is created in Affinity. You can also find the [workflow](https://n8n.io/workflows/672) on n8n.io. This example usage workflow would use the following node. - -- [Affinity Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Affinity Trigger node](/_images/integrations/builtin/trigger-nodes/affinitytrigger/workflow.png) - -### 1. Affinity Trigger node - -1. First of all, you'll have to enter credentials for the Affinity Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/affinity/). -2. Select 'list.created' from the ***Events*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Affinity Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.airtableTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.airtableTrigger.md deleted file mode 100644 index f2a7cd66e..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.airtableTrigger.md +++ /dev/null @@ -1,56 +0,0 @@ -# Airtable Trigger - -[Airtable](https://airtable.com/) is a spreadsheet-database hybrid, with the features of a database but applied to a spreadsheet. The fields in an Airtable table are similar to cells in a spreadsheet, but have types such as 'checkbox', 'phone number', and 'drop-down list', and can reference file attachments like images. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/airtable/). - - -## Example Usage - -This workflow allows you to receive a Mattermost message when new data gets added to Airtable. You can also find the [workflow](https://n8n.io/workflows/799) on n8n.io. This example usage workflow would use the following nodes. -- [Airtable Trigger]() -- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/) - -The final workflow should look like the following image. - -![A workflow with the Airtable Trigger node](/_images/integrations/builtin/trigger-nodes/airtabletrigger/workflow.png) - -### 1. Airtable Trigger node - -The Airtable Trigger node will trigger the workflow when new data gets added to Airtable. - -1. First of all, you'll have to enter credentials for the Airtable Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/airtable/). -2. Click on ***Add Poll Time*** and select 'Every Minute' from the ***Mode*** dropdown list. This will check Airtable every minute for new data entries. -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 table name in the ***Table*** field. -5. Enter a trigger field name in the ***Trigger Field*** field. If you don't have a 'Created Time' or 'Last modified time' field in your table, please create one. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the new data from Airtable. This output gets passed on to the next node in the workflow. - -![Using the Airtable Trigger node to trigger the workflow](/_images/integrations/builtin/trigger-nodes/airtabletrigger/airtabletrigger_node.png) - -### 2. Mattermost node (post: message) - -This node will send a message about the new data in the channel 'Information Updated' in Mattermost. If you have a different channel, use that instead. - -1. First of all, you'll have to enter credentials for the Mattermost node. You can find out how to do that [here](/integrations/builtin/credentials/mattermost/). - -2. Select a channel from the ***Channel ID*** dropdown list. -3. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. -4. Enter the following message in the ***Expression*** field: -``` -New Data was added to Airtable. -ID:{{$node["Airtable Trigger"].json["fields"]["id"]}} -Name: {{$node["Airtable Trigger"].json["fields"]["name"]}} -``` -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends a message in Mattermost about the new data that got added to Airtable. - -![Using the Mattermost node to send a message of the new data](/_images/integrations/builtin/trigger-nodes/airtabletrigger/mattermost_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Airtable Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.amqpTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.amqpTrigger.md deleted file mode 100644 index c7096a578..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.amqpTrigger.md +++ /dev/null @@ -1,33 +0,0 @@ -# AMQP Trigger - -[AMQP](https://www.amqp.org/) is an open standard application layer protocol for message-oriented middleware. The defining features of AMQP are message orientation, queuing, routing, reliability and security. This node supports AMQP 1.0 compatible message brokers. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/amqp/). - - - -## Example Usage - -This workflow allows you to receive messages for an [ActiveMQ](https://activemq.apache.org/) queue via AMQP Trigger. You can also find the [workflow](https://n8n.io/workflows/513) on the website. This example usage workflow would use the following node. - -- [AMQP Trigger]() - -The final workflow should look like the following image. - -![A workflow with the AMQP Trigger node](/_images/integrations/builtin/trigger-nodes/amqptrigger/workflow.png) - - -### 1. AMQP Trigger node - -1. First of all, you'll have to enter credentials for the AMQP Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/amqp/). -2. Enter the name of the queue or topic in the *Queue / Topic* field. -3. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the AMQP Trigger node. - - - - - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.asanaTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.asanaTrigger.md deleted file mode 100644 index 541d2307f..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.asanaTrigger.md +++ /dev/null @@ -1,28 +0,0 @@ -# Asana Trigger - -[Asana](https://asana.com/) is a web and mobile application designed to help teams organize, track, and manage their work. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/asana/). - - -## Example Usage - -This workflow allows you to receive updates when an event occurs in Asana. You can also find the [workflow](https://n8n.io/workflows/654) on n8n.io. This example usage workflow would use the following node. - -- [Asana Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Asana Trigger node](/_images/integrations/builtin/trigger-nodes/asanatrigger/workflow.png) - -### 1. Asana Trigger node - -1. First of all, you'll have to enter credentials for the Asana Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/asana/). -2. Enter the name of the resource in the ***Resource*** field. -3. Enter the name of the workspace in the ***Workspace*** field. -4. Click on ***Execute Node*** to run the node. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Asana Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.autopilotTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.autopilotTrigger.md deleted file mode 100644 index ffb9bfc7c..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.autopilotTrigger.md +++ /dev/null @@ -1,82 +0,0 @@ -# Autopilot Trigger - -[Autopilot](https://www.autopilothq.com/) is a visual marketing software that allows you to automate and personalize your marketing across the entire customer journey. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/autopilot/). - - -## Events - -- Contact added -- Contact added to a list -- Contact entered to a segment -- Contact left a segment -- Contact removed from a list -- Contact unsubscribed -- Contact updated - -## Example Usage - -This workflow allows you to receive updates when a new contact gets added in Autopilot and add them to a base in Airtable. You can also find the [workflow](https://n8n.io/workflows/991) on n8n.io. This example usage workflow would use the following node. - -- [Autopilot Trigger]() -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Airtable](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/) - -The final workflow should look like the following image. - -![A workflow with the Autopilot Trigger node](/_images/integrations/builtin/trigger-nodes/autopilottrigger/workflow.png) - -### 1. Autopilot Trigger - - The Autopilot Trigger node will trigger the workflow when a new contact gets added in Autopilot. - -1. First of all, you'll have to enter credentials for the Autopilot Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/autopilot/). -2. Select 'Contact Added' from the ***Events*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the information of the new contact that was added to Autopilot. This output gets passed on to the next node in the workflow. - -![Using the Autopilot Trigger node to trigger the workflow](/_images/integrations/builtin/trigger-nodes/autopilottrigger/autopilottrigger_node.png) - -### 2. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `First Name` in the ***Name*** 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: Current Node > Input Data > JSON > contact > FirstName. You can also add the following expression: `{{$json["contact"]["FirstName"]}}`. -5. Enter `First Name` in the ***Name*** field. -6. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -7. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > contact > LastName. You can also add the following expression: `{{$json["contact"]["LastName"]}}`. -8. Click on ***Add Value*** and select 'String' from the dropdown list. -9. Enter `Email` in the ***Name*** field. -10. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -11. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > contact > Email. You can also add the following expression: `{{$json["contact"]["Email"]}}`. -12. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -13. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uses the data from the previous node and returns the data that we set for the workflow. - -![Using the Set node to set the data](/_images/integrations/builtin/trigger-nodes/autopilottrigger/set_node.png) - -### 3. Airtable node - -This node will store the data coming from the previous node in a table in Airtable. - -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 'Append' 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 under the Introduction section. -4. In n8n, paste the ID of the base in the ***Base ID*** field. -5. Enter the table name in the ***Table*** name field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node adds the information of a new contact from the previous node in a table in Airtable. - -![Using the Airtable node to append the information of a subscriber](/_images/integrations/builtin/trigger-nodes/autopilottrigger/airtable_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Autopilot Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.awsSnsTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.awsSnsTrigger.md deleted file mode 100644 index 20d357f3a..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.awsSnsTrigger.md +++ /dev/null @@ -1,29 +0,0 @@ -# AWS SNS Trigger - -[AWS SNS](https://aws.amazon.com/sns/) is a notification service provided as part of Amazon Web Services. It provides a low-cost infrastructure for the mass delivery of messages, predominantly to mobile users. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/aws/). - - - -## Example Usage - -This workflow allows you to receive updates for events in AWS SNS. You can also find the [workflow](https://n8n.io/workflows/509) on the website. This example usage workflow would use the following node. - -- [AWS SNS Trigger]() - -The final workflow should look like the following image. - -![A workflow with the AWS SNS Trigger node](/_images/integrations/builtin/trigger-nodes/awssnstrigger/workflow.png) - - -### 1. AWS SNS Trigger node - -1. First of all, you'll have to enter credentials for the AWS SNS Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/aws/). -2. Select the topic you want to listen for in the *Topic* dropdown list. -3. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the AWS SNS Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.bitbucketTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.bitbucketTrigger.md deleted file mode 100644 index 6a5d998fd..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.bitbucketTrigger.md +++ /dev/null @@ -1,31 +0,0 @@ -# Bitbucket Trigger - -[Bitbucket](https://bitbucket.org/) is a web-based version control repository hosting service owned by Atlassian, for source code and development projects that use either Mercurial or Git revision control systems. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/bitbucket/). - - - -## Example Usage - -This workflow allows you to receive updates when events occur in a Bitbucket repository. You can also find the [workflow](https://n8n.io/workflows/529) on the website. This example usage workflow would use the following node. - -- [Bitbucket Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Bitbucket Trigger node](/_images/integrations/builtin/trigger-nodes/bitbuckettrigger/workflow.png) - - -### 1. Bitbucket Trigger node - -1. First of all, you'll have to enter credentials for the Bitbucket Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/bitbucket/). -2. Select 'Repository' from the *Resource* dropdown list. -3. Select the repository you want to receive updates for from the *Repository* dropdown list. -4. Select the events you want to receive updates for from the *Events* dropdown list. -5. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Bitbucket Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.boxTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.boxTrigger.md deleted file mode 100644 index f27d26376..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.boxTrigger.md +++ /dev/null @@ -1,38 +0,0 @@ -# Box Trigger - -[Box](https://www.box.com/) is a cloud computing company which provides file sharing, collaborating, and other tools for working with files that are uploaded to its servers. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/box/). - - - -## Example Usage - -This workflow allows you to receive updates when events occur in Box. You can also find the [workflow](https://n8n.io/workflows/560) on the website. This example usage workflow would use the following node. - -- [Box Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Box Trigger node](/_images/integrations/builtin/trigger-nodes/boxtrigger/workflow.png) - - -### 1. Box Trigger node - -1. First of all, you'll have to enter credentials for the Box Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/box/). -2. Select the events for which you want to receive updates for from the *Events* dropdown list. -3. Select the type of item that will trigger an update from the *Target Type* dropdown list. -4. Enter the target ID of the file/folder to be monitored for updates in the *Target ID* field. -5. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Box Trigger node. - - -## FAQs - -### How do I find my Target ID in Box? -1. Open the file/folder that you would like to monitor. -2. Copy the string of charatcters after `folder/` in your URL. This is the target ID. For example, if the URL is `https://app.box.com/folder/12345`, then `12345` is the target ID. -3. Paste it in the *Target ID* field in n8n. diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.calTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.calTrigger.md deleted file mode 100644 index 92c8a5c01..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.calTrigger.md +++ /dev/null @@ -1,33 +0,0 @@ -# Cal Trigger - -[Cal](https://cal.com/) is the event-juggling scheduler for everyone. Focus on meeting, not making meetings. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/cal/). - - - -## Example Usage - -This workflow allows you to receive updates for events in Cal. - -- [Cal Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Cal Trigger node](/_images/integrations/builtin/trigger-nodes/caltrigger/workflow.png) - - -### 1. Cal Trigger node - -1. First of all, you'll have to enter credentials for the Cal Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/cal/). -2. Select the events you want to receive updates for from the **Events** dropdown list. -3. Click on **Execute Node** to run the node. - -(Optional Advanced Settings) - -Click on **Add Field** under advanced fields and select the option(s) you wish to add. You can enter an EventType ID, an App ID and a payload template. Note that the eventType ID must be of a team EventType. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Cal Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.calendlyTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.calendlyTrigger.md deleted file mode 100644 index 573835668..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.calendlyTrigger.md +++ /dev/null @@ -1,29 +0,0 @@ -# Calendly Trigger - -[Calendly](https://calendly.com/) is an automated scheduling software that is designed to make the process of finding meeting times easy. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/calendly/). - - - -## Example Usage - -This workflow allows you to receive updates for events in Calendly. You can also find the [workflow](https://n8n.io/workflows/540) on the website. This example usage workflow would use the following node. - -- [Calendly Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Calendly Trigger node](/_images/integrations/builtin/trigger-nodes/calendlytrigger/workflow.png) - - -### 1. Calendly Trigger node - -1. First of all, you'll have to enter credentials for the Calendly Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/calendly/). -2. Select the events you want to receive updates for from the *Events* dropdown list. -3. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Calendly Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.chargebeeTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.chargebeeTrigger.md deleted file mode 100644 index 66efbea2b..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.chargebeeTrigger.md +++ /dev/null @@ -1,40 +0,0 @@ -# Chargebee Trigger - -[Chargebee](https://www.chargebee.com/) is a billing platform for subscription based SaaS and eCommerce businesses. Chargebee integrates with payment gateways to let you automate recurring payment collection along with invoicing, taxes, accounting, email notifications, SaaS Metrics and customer management. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/chargebee/). - - - -## Example Usage - -This workflow allows you to receive updates for events in Chargebee. You can also find the [workflow](https://n8n.io/workflows/486) on the website. This example usage workflow would use the following node. - -- [Chargebee Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Chargebee Trigger node](/_images/integrations/builtin/trigger-nodes/chargebeetrigger/workflow.png) - - -### 1. Chargebee Trigger node - -1. First of all, you'll have to add the webhook URL in Chargebee. You can find instructions on how to do that in the FAQs below. -2. Select the `*` option in the *Events* field to receive updates when any event is triggered. -3. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Chargebee Trigger node. - - -## FAQs - -### How do I add my webhook URL in Chargebee? -1. Open your Chargebee dashboard. -2. Click on "Settings". -3. Click on "Configure Chargebee". -4. Scroll down and click on "Webhooks". -5. Click on the *Add Webhook* button. -6. Enter the Webhook Name and the Webhook URL. -7. Click on the *Create* button. diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.ciscoWebexTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.ciscoWebexTrigger.md deleted file mode 100644 index 8b5ec9d6e..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.ciscoWebexTrigger.md +++ /dev/null @@ -1,28 +0,0 @@ -# Webex by Cisco Trigger - -[Webex by Cisco](https://webex.com/) is a web conferencing and videoconferencing application. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/ciscoWebex/). - - -## Example usage - -This workflow allows you to receive updates when meeting events occur in your Webex account. This example usage workflow uses the following node: - -- [Webex by Cisco Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Webex by Cisco Trigger node](/_images/integrations/builtin/trigger-nodes/ciscowebextrigger/workflow.png) - -### 1. Webex by Cisco Trigger node - -1. First enter your credentials for node. You can find out how to do that [here](/integrations/builtin/credentials/ciscoWebex/). -2. Select 'Meeting' from the *Resource* dropdown list. -3. Select the events you want to receive updates for from the *Events* dropdown list. -4. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Webex by Cisco Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.clickUpTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.clickUpTrigger.md deleted file mode 100644 index 4f9e41f17..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.clickUpTrigger.md +++ /dev/null @@ -1,30 +0,0 @@ -# ClickUp Trigger - -[ClickUp](https://clickup.com/) is a cloud-based collaboration and project management tool suitable for businesses of all sizes and industries. Features include communication and collaboration tools, task assignments and statuses, alerts and a task toolbar. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/clickUp/). - - - -## Example Usage - -This workflow allows you to receive updates for events in ClickUp. You can also find the [workflow](https://n8n.io/workflows/487) on the website. This example usage workflow would use the following node. - -- [ClickUp Trigger]() - -The final workflow should look like the following image. - -![A workflow with the ClickUp Trigger node](/_images/integrations/builtin/trigger-nodes/clickuptrigger/workflow.png) - - -### 1. ClickUp Trigger node - -1. First of all, you'll have to enter credentials for the ClickUp Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/clickUp/). -2. Select your team from the *Team* dropdown list. -3. Select the `*` option in the *Events* field to receive updates for all the events. -4. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the ClickUp Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.clockifyTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.clockifyTrigger.md deleted file mode 100644 index f66f79c09..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.clockifyTrigger.md +++ /dev/null @@ -1,32 +0,0 @@ -# Clockify Trigger - -[Clockify](https://clockify.me/) is a free time tracker and timesheet app for tracking work hours across projects. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/clockify/). - - -**Note:** This node uses the workflow timezone setting to specify the range of time entries starting time. You have to configure the workflow timezone setting if you want this Trigger node to retrieve the right time entries. - -## Example Usage - -This workflow allows you to get new time entries from Clockify. You can also find the [workflow](https://n8n.io/workflows/536) on the website. This example usage workflow would use the following node. - -- [Clockify Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Clockify Trigger node](/_images/integrations/builtin/trigger-nodes/clockifytrigger/workflow.png) - - -### 1. Clockify Trigger node - -1. First enter your credentials for the Clockify Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/clockify/). -2. Select the *Workspace* you want to receive updates for using the dropdown list. -3. Click on *Execute Node* to run the workflow. - -**Note:** This node uses polling to get new time entries. You have to use the *Add Poll Time* button if you want this Trigger node to run and retrieve new time entries regularly. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Clockify Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.convertkitTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.convertkitTrigger.md deleted file mode 100644 index 57e549dbe..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.convertkitTrigger.md +++ /dev/null @@ -1,28 +0,0 @@ -# ConvertKit Trigger - -[ConvertKit](https://www.convertkit.com/) is a fully-featured email marketing platform. ConvertKit can be used to build an email list, send email broadcasts, automate sequences, create segments, and build landing pages. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/convertKit/). - - -## Example Usage - -This workflow allows you to receive updates when a subscriber is added through a form in ConvertKit. You can also find the [workflow](https://n8n.io/workflows/644) on n8n.io. This example usage workflow would use the following node. - -- [ConvertKit Trigger]() - -The final workflow should look like the following image. - -![A workflow with the ConvertKit Trigger node](/_images/integrations/builtin/trigger-nodes/convertkittrigger/workflow.png) - -### 1. ConvertKit Trigger node - -1. First of all, you'll have to enter credentials for the ConvertKit Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/convertKit/). -2. Select 'Form Subscribe' from the ***Event*** dropdown list. -3. Select the form from the ***Form ID*** dropdown list. -4. Click on ***Execute Node*** to run the node. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the ConvertKit Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.copperTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.copperTrigger.md deleted file mode 100644 index 4c1ba43c3..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.copperTrigger.md +++ /dev/null @@ -1,30 +0,0 @@ -# Copper Trigger - -[Copper](https://www.copper.com/) is a CRM that focuses on strong integration with Google's G Suite. It is mainly targeted towards small and medium-sized businesses. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/copper/). - - - -## Example Usage - -This workflow allows you to receive an update when a new project is created in Copper. You can also find the [workflow](https://n8n.io/workflows/537) on the website. This example usage workflow would use the following node. - -- [Copper Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Copper Trigger node](/_images/integrations/builtin/trigger-nodes/coppertrigger/workflow.png) - - -### 1. Copper Trigger node - -1. First of all, you'll have to enter credentials for the Copper Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/copper/). -2. Select 'Project' from the *Resource* dropdown list. -3. Select 'New' from the *Event* dropdown list. -4. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Copper Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.customerIoTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.customerIoTrigger.md deleted file mode 100644 index 9bb4b2b23..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.customerIoTrigger.md +++ /dev/null @@ -1,26 +0,0 @@ -# Customer.io Trigger - -[Customer.io](https://customer.io/) enables users to send newsletters to selected segments of customers using their website data. You can send targeted emails, push notifications, and SMS to lower churn, create stronger relationships, and drive subscriptions. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/customerIo/). - - -## Example Usage - -This workflow allows you to receive updates when a subscriber unsubscribes in Customer.io. You can also find the [workflow](https://n8n.io/workflows/645) on n8n.io. This example usage workflow would use the following node. - -- [Customer.io Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Customer.io Trigger node](/_images/integrations/builtin/trigger-nodes/customeriotrigger/workflow.png) - -### 1. Customer.io Trigger node - -1. First of all, you'll have to enter credentials for the Customer.io Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/customerIo/). -2. Select 'Customer Unsubscribe' from the ***Event*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Customer.io Trigger node. diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.emeliaTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.emeliaTrigger.md deleted file mode 100644 index 0cb5b5a9d..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.emeliaTrigger.md +++ /dev/null @@ -1,59 +0,0 @@ -# Emelia Trigger - -[Emelia](https://emelia.io) is a cold-mailing tool. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/emelia/). - - -## Events - -- Email Bounced -- Email Opened -- Email Replied -- Email Sent -- Link Clicked -- Unsubscribed Contact - -## Example Usage - -This workflow allows you to send a message on Mattermost when a lead replies to your email. You can also find the [workflow](https://n8n.io/workflows/1039) on n8n.io. This example usage workflow would use the following nodes. - -- [Emelia Trigger]() -- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/) - -The final workflow should look like the following image. - -![A workflow with the Emelia Trigger node](/_images/integrations/builtin/trigger-nodes/emeliatrigger/workflow.png) - -### 1. Emelia Trigger - -The Emelia Trigger node will trigger the workflow when a lead sends a reply to the campaign `n8n`. If you have a different campaign, use that instead. - -1. First of all, you'll have to enter credentials for the Emelia Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/emelia/). -2. Select a campaign from the ***Campaign*** dropdown list. -3. Select 'Email Replied' from the ***Events*** dropdown list. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node triggers the workflow when a lead sends a reply. This output is passed on to the next node in the workflow. - -![Using the Emelia Trigger node to trigger the workflow](/_images/integrations/builtin/trigger-nodes/emeliatrigger/emeliatrigger_node.png) - -## 2. Mattermost node (post: message) - -This node will send a message to the `Leads` channel in Mattermost. If you have a different channel, use that instead. - -1. First of all, you'll have to enter credentials for the Mattermost node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/mattermost/). -2. Select a channel from the ***Channel ID*** dropdown list. -3. Click on the gears icon next to the ***Message*** field click on ***Add Expression***. - -4. Enter the following message in the ***Expression*** field. `{{$json["contact"]["firstName"]}} from {{$json["contact"]["company"]}} has replied back to your campaign.` -5. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that the node sends a message with a reply to the `Leads` channel in Mattermost. - -![Using the Mattermost node to send a message](/_images/integrations/builtin/trigger-nodes/emeliatrigger/mattermost_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Emelia Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.eventbriteTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.eventbriteTrigger.md deleted file mode 100644 index dc72a4ded..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.eventbriteTrigger.md +++ /dev/null @@ -1,31 +0,0 @@ -# Eventbrite Trigger - -[Eventbrite](https://www.eventbrite.com/) is an event management and ticketing website. The service allows users to browse, create, and promote local events. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/eventbrite/). - - - -## Example Usage - -This workflow allows you to get updates for an Eventbrite event. You can also find the [workflow](https://n8n.io/workflows/538) on the website. This example usage workflow would use the following node. - -- [Eventbrite Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Eventbrite Trigger node](/_images/integrations/builtin/trigger-nodes/eventbritetrigger/workflow.png) - - -### 1. Eventbrite Trigger node - -1. First of all, you'll have to enter credentials for the Eventbrite Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/eventbrite/). -2. Select the profile that contains your event from the *Organization* dropdown list. -3. Select the event you want to receive updates for from the *Event* dropdown list. -4. Select the actions that you want to receive updates for from the *Actions* dropdown list. -5. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Eventbrite Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.facebookTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.facebookTrigger.md deleted file mode 100644 index 96dd0611d..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.facebookTrigger.md +++ /dev/null @@ -1,63 +0,0 @@ -# Facebook Trigger - -[Facebook](https://www.facebook.com/) is a social networking site that makes it easy to connect and share with family and friends online. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/facebookApp/). - - -## Object - -- Get updates about an Ad Account -- Get updates about the app -- Get updates about Certificate Transparency -- Get updates about activity in groups and events in groups of Workplace -- Get updates about the comments on your media -- Get updates about the links for rich previews by an external provider -- Page updates -- Updates regarding granting or revoking permissions -- User profile updates -- Get updates about Whatsapp business account -- Get updates about Workplace security - -## Example Usage - -This workflow allows you to receive a Mattermost message when a user updates their profile on Facebook. You can also find the [workflow](https://n8n.io/workflows/785) on n8n.io. This example usage workflow would use the following nodes. - -- [Facebook Trigger]() -- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/) - -The final workflow should look like the following image. - -![A workflow with the Facebook Trigger node](/_images/integrations/builtin/trigger-nodes/facebooktrigger/workflow.png) - -### 1. Facebook Trigger node - -The Facebook Trigger node will trigger the workflow when a user updates their profile on Facebook. - -1. First of all, you'll have to enter credentials for the Facebook Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/facebookApp/). -2. Select 'User' from the ***Object*** dropdown list. -3. Enter your app ID in the ***App ID*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the updated information of the user from Facebook. This output is passed on to the next node in the workflow. - -![Using the Facebook Trigger node to trigger the workflow](/_images/integrations/builtin/trigger-nodes/facebooktrigger/facebooktrigger_node.png) - -### 2. Mattermost node (post: message) - -This node will send a message of the updated information in the channel `Information Updated` in Mattermost. If you have a different channel, use that instead. - -1. First of all, you'll have to enter credentials for the Mattermost node. You can find out how to do that [here](/integrations/builtin/credentials/mattermost/). - -2. Select a channel from the ***Channel ID*** dropdown list. -3. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. -4. Enter the following message in the ***Expression*** field: `The user with uid {{$node["Facebook Trigger"].json["uid"]}} changed their {{$node["Facebook Trigger"].json["changes"][0]["field"]}} to {{$node["Facebook Trigger"].json["changes"][0]["value"]["page"]}}.`. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends a message about the updated information to the `Information Updated` channel in Mattermost. - -![Using the Mattermost node to send a message of the updated information](/_images/integrations/builtin/trigger-nodes/facebooktrigger/mattermost_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Facebook Trigger node. diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.figmaTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.figmaTrigger.md deleted file mode 100644 index e86928dfb..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.figmaTrigger.md +++ /dev/null @@ -1,19 +0,0 @@ -# Figma Trigger (Beta) - -[Figma](https://www.figma.com/) is a prototyping tool which is primarily web-based, with additional offline features enabled by desktop applications for macOS and Windows. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/figma/). - - -!!! warning "Supported Figma Plans" - Figma does not support webhooks on the free "Starter" plan. Your team would need to be on the "Professional" plan to use this node. - - -## Trigger Events - -- **File Commented**: Triggers when someone comments on a file. -- **File Deleted**: Triggers when an individual file is deleted, but not when an entire folder with all files is deleted. -- **File Updated**: Triggers when a file is saved or deleted. A save occurs when a file is closed or within 30 seconds after changes have been made. -- **File Version Updated**: Triggers when a named version is created in the version history of a file. -- **Library Publish**: Triggers when a library file is published. diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.flowTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.flowTrigger.md deleted file mode 100644 index 48bd1b99d..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.flowTrigger.md +++ /dev/null @@ -1,30 +0,0 @@ -# Flow Trigger - -[Flow](https://www.getflow.com/) is modern task and project management software for teams. It brings together tasks, projects, timelines, and conversations, and integrates with a lot of tools. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/flow/). - - - -## Example Usage - -This workflow allows you to receive updates for specified tasks in Flow. You can also find the [workflow](https://n8n.io/workflows/508) on the website. This example usage workflow would use the following node. - -- [Flow Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Flow Trigger node](/_images/integrations/builtin/trigger-nodes/flowtrigger/workflow.png) - - -### 1. Flow Trigger node - -1. First of all, you'll have to enter credentials for the Flow Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/flow/). -2. Select 'Task' from the *Resource* dropdown list. -3. Enter one or more task IDs separated by commas in the *Task ID* field. You can find the task ID by clicking on the task in Flow and copying the number after `tasks/` in the URL. -4. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Flow Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.formIoTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.formIoTrigger.md deleted file mode 100644 index 869bbb04d..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.formIoTrigger.md +++ /dev/null @@ -1,29 +0,0 @@ -# Form.io Trigger - -[Form.io](https://www.form.io/) is an enterprise class combined form and API data management platform for building complex form-based business process applications. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/formIoTrigger/). - - -## Example Usage - -This workflow allows you to receive updates for newly created submissions in Form.io. This example workflow uses the following node: - -- [Form.io Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Form.io Trigger node](/_images/integrations/builtin/trigger-nodes/formiotrigger/workflow.png) - - -### 1. Form.io Trigger node - -1. First enter credentials for the Form.io Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/formIoTrigger/). -2. Select the project you want to receive updates for using the *Project Name/ID* dropdown list. -3. Select the form you want to receive updates for using the *Form Name/ID* dropdown list. -4. Select **Submission Created** from the *Trigger Events* dropdown list. -5. Click on **Execute Node** to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Form.io Trigger node. diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.formstackTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.formstackTrigger.md deleted file mode 100644 index f9b4bd8f2..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.formstackTrigger.md +++ /dev/null @@ -1,27 +0,0 @@ -# Formstack Trigger - -[Formstack](https://www.formstack.com/) is a workplace productivity platform that helps organizations streamline digital work through no-code online forms, documents, and signatures. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/formstackTrigger/). - - -## Example Usage - -This workflow allows you to receive updates for newly created submissions in Formstack forms. This example workflow uses the following node: - -- [Formstack Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Formstack Trigger node](/_images/integrations/builtin/trigger-nodes/formstacktrigger/workflow.png) - - -### 1. Formstack Trigger node - -1. First enter credentials for the Formstack Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/formstackTrigger/). -2. Enter the form you want to receive updates for using the *Form Name/ID* field. -3. Click on **Execute Node** to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Form.io Trigger node. diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.getResponseTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.getResponseTrigger.md deleted file mode 100644 index 9edd1d6ae..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.getResponseTrigger.md +++ /dev/null @@ -1,78 +0,0 @@ -# GetResponse Trigger - -[GetResponse](https://www.getresponse.com/) is an online platform that offers email marketing software, landing page creator, webinar hosting, and much more. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/getResponse/). - - -## Events - -- Receive notifications when a customer is subscribed to a list -- Receive notifications when a customer is unsubscribed from a list -- Receive notifications when an email is opened -- Receive notifications when an email is clicked -- Receive notifications when a survey is submitted - -## Example Usage - -This workflow allows you to receive updates when a customer gets subscribed to a list in GetResponse and add them to a base in Airtable. You can also find the [workflow](https://n8n.io/workflows/933) on n8n.io. This example usage workflow would use the following nodes. - -- [GetResponse Trigger]() -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Airtable](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/) - -The final workflow should look like the following image. - -![A workflow with the GetResponse Trigger node](/_images/integrations/builtin/trigger-nodes/getresponsetrigger/workflow.png) - -### 1. GetResponse Trigger - -The GetResponse Trigger node will trigger the workflow when a customer is subscribed to a list in GetResponse. - -1. First of all, you'll have to enter credentials for the GetResponse Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/getResponse/). -2. Select 'Customer Subscribed' from the ***Events*** dropdown list. -3. Select a list from the ***List IDs*** dropdown list. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the information of the customer that gets subscribed to a list in GetResponse. This output is passed on to the next node in the workflow. - -![Using the GetResponse Trigger node to trigger the workflow](/_images/integrations/builtin/trigger-nodes/getresponsetrigger/getresponsetrigger_node.png) - -### 2. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `Name` in the ***Name*** 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: Current Node > Input Data > JSON > contact_name. You can also add the following expression: `{{$json["contact_name"]}}`. -5. Click on ***Add Value*** and select 'String' from the dropdown list. -6. Enter `Email` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > contact_email. You can also add the following expression: `{{$json["contact_email"]}}`. -9. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -10. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uses the data from the previous node and returns the data that we set for the workflow. - -![Using the Set node to set the data](/_images/integrations/builtin/trigger-nodes/getresponsetrigger/set_node.png) - -### 3. Airtable node (Append) - -This node will store the data coming from the previous node in a table in Airtable. Create a table like [this](https://airtable.com/shruNwTykzR3tkr6d) 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 'Append' 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 under the Introduction section. -4. In n8n, paste the ID of the base in the ***Base ID*** field. -5. Enter the table name in the ***Table*** name field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node adds the information of the customer from the previous node in a table in Airtable. - -![Using the Airtable node to append the information of a customer](/_images/integrations/builtin/trigger-nodes/getresponsetrigger/airtable_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the GetResponse Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.githubTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.githubTrigger.md deleted file mode 100644 index c002b5e70..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.githubTrigger.md +++ /dev/null @@ -1,31 +0,0 @@ -# GitHub Trigger - -[GitHub](https://github.com/) provides hosting for software development and version control using Git. It offers the distributed version control and source code management (SCM) functionality of Git, access control and several collaboration features such as bug tracking, feature requests, task management, and wikis for every project. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/github/). - - - -## Example Usage - -This workflow allows you to receive updates for GitHub events. You can also find the [workflow](https://n8n.io/workflows/527) on the website. This example usage workflow would use the following node. - -- [GitHub Trigger]() - -The final workflow should look like the following image. - -![A workflow with the GitHub Trigger node](/_images/integrations/builtin/trigger-nodes/githubtrigger/workflow.png) - - -### 1. GitHub Trigger node - -1. First of all, you'll have to enter credentials for the GitHub Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/github/). -2. Enter the repository owner in the *Repository Owner* field. -3. Enter the repository name in the *Repository Name* field. -4. Select the `*` option in the *Events* field to receive updates when any event is triggered. -5. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the GitHub Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.gitlabTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.gitlabTrigger.md deleted file mode 100644 index b6134e41a..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.gitlabTrigger.md +++ /dev/null @@ -1,31 +0,0 @@ -# GitLab Trigger - -[GitLab](https://gitlab.com/) is a web-based DevOps lifecycle tool that provides a Git-repository manager providing wiki, issue-tracking, and continuous integration/continuous installation pipeline features. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/gitlab/). - - - -## Example Usage - -This workflow allows you to receive updates for GitLab events. You can also find the [workflow](https://n8n.io/workflows/528) on the website. This example usage workflow would use the following node. - -- [GitLab Trigger]() - -The final workflow should look like the following image. - -![A workflow with the GitLab Trigger node](/_images/integrations/builtin/trigger-nodes/gitlabtrigger/workflow.png) - - -### 1. GitLab Trigger node - -1. First of all, you'll have to enter credentials for the GitLab Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/gitlab/). -2. Enter the repository owner in the *Repository Owner* field. -3. Enter the repository name in the *Repository Name* field. -4. Select the `*` option in the *Events* field to receive updates when any event is triggered. -5. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the GitLab Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.gmailTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.gmailTrigger.md deleted file mode 100644 index 226400bb0..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.gmailTrigger.md +++ /dev/null @@ -1,14 +0,0 @@ -# Gmail Trigger - -[Gmail](https://www.gmail.com) is an email service developed by Google. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - -## Events - -* Message Received - -## Related resources - -n8n provides an app node for Gmail. You can find the node docs [here](/integrations/builtin/app-nodes/n8n-nodes-base.gmail/). diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.googleCalendarTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.googleCalendarTrigger.md deleted file mode 100644 index d8b2e01cf..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.googleCalendarTrigger.md +++ /dev/null @@ -1,14 +0,0 @@ -# Google Calendar Trigger - -[Google Calendar](https://www.google.com/calendar/) is a time-management and scheduling calendar service developed by Google. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -## Events - -- Event Created -- Event Ended -- Event Started -- Event Updated diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.googleDriveTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.googleDriveTrigger.md deleted file mode 100644 index a04e69915..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.googleDriveTrigger.md +++ /dev/null @@ -1,44 +0,0 @@ -# Google Drive Trigger - -[Google Drive](https://drive.google.com) is a file storage and synchronization service developed by Google. It allows users to store files on their servers, synchronize files across devices, and share files. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/google/). - - -!!! note "Manual Executions vs. Activation" - On manual executions this node will return the last event matching its search criteria. If no event matches the criteria (for example because you are watching for files to be created but no files have been created so far), an error is thrown. Once saved and activated, the node will regularly check for any matching events and will trigger your workflow for each event found. - - -## Example Usage - -This workflow sends out email notifications when a new file has been uploaded to Google Drive. It uses two nodes: - -- [Google Drive Trigger]() -- [Send Email](/integrations/builtin/core-nodes/n8n-nodes-base.sendEmail/) - -The final workflow should look like the image below. - -![A workflow using the Google Drive Trigger and Send Email node](/_images/integrations/builtin/trigger-nodes/googledrivetrigger/workflow.png) - -### 1. Google Drive Trigger node - -1. Enter valid credentials for the Google Drive Trigger node. You can find out how to do so [here](/integrations/builtin/credentials/google/). -2. Select the `Changes involving a Specific Folder` option in the ***Trigger On*** field. -3. Paste the URL of a Google Drive folder in the ***Folder URL or ID*** field. -4. Select `File Created` in the ***Watch For*** field. -5. Click on *Execute Node* to execute the node. - -In the screenshot below you can see the file returned by the node. - -![GoogleDriveTrigger_node.png](/_images/integrations/builtin/trigger-nodes/googledrivetrigger/googledrivetrigger_node.png) - -### 2. Send Email node - -1. Enter valid credentials for the Send Email node. You can find out how to do so [here](/integrations/builtin/credentials/sendEmail/). -2. Enter valid emails in the ***From Email*** and ***To Email*** fields. -3. Enter `File Created` in the ***Subject*** field. -4. Click on the gear icon next to the ***Text*** field and choose ***Add Expression***. -5. Enter `A file in your Google Drive file folder has been created: {{$json["name"]}}` and close the expression editor. -6. Click on ***Execute Node* to execute the node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.gumroadTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.gumroadTrigger.md deleted file mode 100644 index 1a042cf53..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.gumroadTrigger.md +++ /dev/null @@ -1,27 +0,0 @@ -# Gumroad Trigger - -[Gumroad](https://gumroad.com) is an online platform that enables creators to sell products directly to consumers. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/gumroad/). - - -## Example Usage - -This workflow allows you to receive updates when a sale is made in Gumroad. You can also find the [workflow](https://n8n.io/workflows/650) on n8n.io. This example usage workflow would use the following node. - -- [Gumroad Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Gumroad Trigger node](/_images/integrations/builtin/trigger-nodes/gumroadtrigger/workflow.png) - -### 1. Gumroad Trigger node - -1. First of all, you'll have to enter credentials for the Gumroad Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/gumroad/). -2. Select 'Sale' from the ***Resource*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Gumroad Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.helpScoutTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.helpScoutTrigger.md deleted file mode 100644 index 6673aafa1..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.helpScoutTrigger.md +++ /dev/null @@ -1,27 +0,0 @@ -# Help Scout Trigger - -[Help Scout](https://www.helpscout.com/) is a help desk software that provides an email-based customer support platform, knowledge base tool, and an embeddable search/contact widget for customer service professionals. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/helpScout/). - - -## Example Usage - -This workflow allows you to receive updates when a customer is created in Help Scout. You can also find the [workflow](https://n8n.io/workflows/669) on n8n.io. This example usage workflow would use the following node. - -- [Help Scout Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Help Scout Trigger node](/_images/integrations/builtin/trigger-nodes/helpscouttrigger/workflow.png) - -### 1. Help Scout Trigger node - -1. First of all, you'll have to enter credentials for the Help Scout Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/helpScout/). -2. Select 'Customer - Created' from the ***Events*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Help Scout Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.hubspotTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.hubspotTrigger.md deleted file mode 100644 index fc5f15442..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.hubspotTrigger.md +++ /dev/null @@ -1,36 +0,0 @@ -# HubSpot Trigger - -[HubSpot](https://www.hubspot.com/) provides tools for social media marketing, content management, web analytics, landing pages, customer support, and search engine optimization. - -!!! note "Credentials" - For this node, you will have to retrieve the App ID and Client secret from the 'Using OAuth' section as well as the Developer API Key from the 'Using Developer API Key' section. You can find authentication information for this node [here](/integrations/builtin/credentials/hubspot/). - - -!!! note "Webhooks" - If you activate a second trigger, the previous trigger stops working. This is because the trigger registers a new webhook with HubSpot when activated. HubSpot only allows one webhook at a time. - - -## Example Usage - -This workflow allows you to receive updates when a new contact is created in HubSpot. You can also find the [workflow](https://n8n.io/workflows/628) on the website. This example usage workflow would use the following node. - -- [HubSpot Trigger]() - -The final workflow should look like the following image. - -![A workflow with the HubSpot Trigger node](/_images/integrations/builtin/trigger-nodes/hubspottrigger/workflow.png) - - -### 1. HubSpot Trigger node - -1. First of all, you'll have to enter credentials for the HubSpot Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/hubspot/). -2. Enter the HubSpot App ID in the ***App ID*** field. You can find out how to obtain the ***App ID*** in the link above. -3. Click on ***Execute Node*** to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the HubSpot Trigger node. - - - - - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.invoiceNinjaTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.invoiceNinjaTrigger.md deleted file mode 100644 index 45ac9fc70..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.invoiceNinjaTrigger.md +++ /dev/null @@ -1,29 +0,0 @@ -# Invoice Ninja Trigger - -[Invoice Ninja](https://www.invoiceninja.com/) is a free open-source online invoicing app for freelancers & businesses. It offers invoicing, payments, expense tracking, & time-tasks. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/invoiceNinja/). - - - -## Example Usage - -This workflow allows you to receive updates when new invoices are created in Invoice Ninja. You can also find the [workflow](https://n8n.io/workflows/535) on the website. This example usage workflow would use the following node. - -- [Invoice Ninja Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Invoice Ninja Trigger node](/_images/integrations/builtin/trigger-nodes/invoiceninjatrigger/workflow.png) - - -### 1. Invoice Ninja Trigger node - -1. First of all, you'll have to enter credentials for the Invoice Ninja Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/invoiceNinja/). -2. Select the 'Invoice Created' option from the *Event* dropdown list to receive updates when a new invoice is created. -3. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Invoice Ninja Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.jiraTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.jiraTrigger.md deleted file mode 100644 index 4d07e999c..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.jiraTrigger.md +++ /dev/null @@ -1,29 +0,0 @@ -# Jira Trigger - -[Jira](https://www.atlassian.com/software/jira) is a proprietary issue tracking product developed by Atlassian that allows bug tracking and agile project management. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/jira/). - - - -## Example Usage - -This workflow allows you to receive updates for Jira events. You can also find the [workflow](https://n8n.io/workflows/569) on the website. This example usage workflow would use the following node. - -- [Jira Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Jira Trigger node](/_images/integrations/builtin/trigger-nodes/jiratrigger/workflow.png) - - -### 1. Jira Trigger node - -1. First of all, you'll have to enter credentials for the Jira Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/jira/). -2. Select the `*` option in the *Events* field to receive updates when any event is triggered. -3. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Jira Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.jotFormTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.jotFormTrigger.md deleted file mode 100644 index 9e003de87..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.jotFormTrigger.md +++ /dev/null @@ -1,29 +0,0 @@ -# JotForm Trigger - -[JotForm](https://www.jotform.com/) is an online form building service. JotForm's software creates forms with a drag and drop creation tool and an option to encrypt user data. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/jotForm/). - - - -## Example Usage - -This workflow allows you to receive updates for form events in JotForm. You can also find the [workflow](https://n8n.io/workflows/541) on the website. This example usage workflow would use the following node. - -- [JotForm Trigger]() - -The final workflow should look like the following image. - -![A workflow with the JotForm Trigger node](/_images/integrations/builtin/trigger-nodes/jotformtrigger/workflow.png) - - -### 1. JotForm Trigger node - -1. First of all, you'll have to enter credentials for the JotForm Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/jotForm/). -2. Select the form you want to receive updates for from the *Form* dropdown list. -3. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the JotForm Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.kafkaTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.kafkaTrigger.md deleted file mode 100644 index 2939b8d73..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.kafkaTrigger.md +++ /dev/null @@ -1,87 +0,0 @@ -# Kafka Trigger - -[Kafka](https://kafka.apache.org/) is an open-source distributed event streaming platform that one can use for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/kafka/). - - - -## Example Usage - -This workflow allows you to receive messages from a topic and send an SMS if the value of the temperature is greater than 50. You can also find the [workflow](https://n8n.io/workflows/814) on n8n.io. This example usage workflow would use the following nodes. - -- [Kafka Trigger]() -- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/) -- [Vonage](/integrations/builtin/app-nodes/n8n-nodes-base.vonage/) -- [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 Kafka Trigger node](/_images/integrations/builtin/trigger-nodes/kafkatrigger/workflow.png) - - -### 1. Kafka Trigger node - -This node will trigger the workflow when a new message is sent to the topic `test_topic`. If you're using a different topic, use that instead. We are sending the message `{ "id": 1, "temp": 100 }` to `test_topic`. - -1. First of all, you'll have to enter credentials for the Kafka Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/kafka/). -2. Enter the name of the topic in the ***Topic*** field. -3. Enter the group ID in the ***Group ID*** field. -4. Click on ***Add Option*** and select 'JSON Parse Message'. -5. Toggle ***JSON Parse Message*** to `true`. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node gets triggered when a new message is sent to the `topic_test` topic in Kafka. - -![Using the Kafka Trigger node to get a message from a topic](/_images/integrations/builtin/trigger-nodes/kafkatrigger/kafkatrigger_node.png) - -### 2. IF node - -This node will compare the value of `temp` that we received in the message from the previous node. If the value is greater than 50, it will return true otherwise false. - -1. Click on ***Add Condition*** and select 'Number' from the dropdown list. -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 > Kafka Trigger > Output Data > JSON > message > temp. You can also add the following expression: `{{$node["Kafka Trigger"].json["message"]["temp"]}}`. -4. Select 'Larger' from the ***Operation*** dropdown list. -5. Set ***Value 2*** to 50. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns output for **true** when the temperature is greater than 50. - -![Using the IF node to check if the temp is larger than 50](/_images/integrations/builtin/trigger-nodes/kafkatrigger/if_node.png) - -### 3. Vonage node (send: sms) - -This node sends an SMS to the specified phone number when the value of `temp` is greater than `50`. - -1. Create a Vonage node connected to the 'true' output of the IF node. -2. You'll have to enter credentials for the Vonage node. You can find out how to do that [here](/integrations/builtin/credentials/vonage/). -3. Enter the name of the sender in the ***From*** field. If you're using a number, enter the number instead. -4. Enter the receiver's phone number in the ***To*** field. -5. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. - -6. Enter the following in the ***Expression*** field. -``` -Alert! -The value of temp is {{$node["Kafka Trigger"].json["message"]["temp"]}}. -``` -7. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends an SMS with the value of `temp` that we received from the Kafka Trigger node. - -![Using the Vonage node to send an SMS](/_images/integrations/builtin/trigger-nodes/kafkatrigger/vonage_node.png) - -### 4. 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/trigger-nodes/kafkatrigger/noop_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Kafka Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.keapTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.keapTrigger.md deleted file mode 100644 index c68009385..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.keapTrigger.md +++ /dev/null @@ -1,29 +0,0 @@ -# Keap Trigger - -[Keap](https://keap.com/) is an e-mail marketing and sales platform for small businesses, including products to manage and optimize the customer lifecycle, customer relationship management, marketing automation, lead capture, and e-commerce. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/keap/). - - - -## Example Usage - -This workflow allows you to receive updates when new contacts are created in Keap. You can also find the [workflow](https://n8n.io/workflows/554) on the website. This example usage workflow would use the following node. - -- [Keap Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Keap Trigger node](/_images/integrations/builtin/trigger-nodes/keaptrigger/workflow.png) - - -### 1. Keap Trigger node - -1. First of all, you'll have to enter credentials for the Keap Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/keap/). -2. Select the 'Contact Add' option from the *Event* dropdown list to receive updates when a new contact is created. -3. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Keap Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.koBoToolboxTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.koBoToolboxTrigger.md deleted file mode 100644 index 91ba9d4d3..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.koBoToolboxTrigger.md +++ /dev/null @@ -1,10 +0,0 @@ -# KoBo Toolbox trigger - -[KoBo toolbox](https://www.kobotoolbox.org/) is a field survey and data collection tool that makes it easy to design interactive forms to be completed offline from mobile devices. It is available both as a free cloud solution or as a self-hosted version. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/kobotoolbox/). - -This node starts a workflow upon new submissions of a specified form. The trigger node handles the creation/deletion of the hook, so you don't need to do any setup in KoBo Toolbox. - -It works the same way as the Get Submission operation in the [KoBoToolbox](/integrations/builtin/app-nodes/n8n-nodes-base.koBoToolbox/) node, including supporting the same reformatting options. \ No newline at end of file diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.lemlistTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.lemlistTrigger.md deleted file mode 100644 index 0ced9cfb8..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.lemlistTrigger.md +++ /dev/null @@ -1,65 +0,0 @@ -# Lemlist Trigger - -[Lemlist](https://Lemlist.com) is an email outreach platform that allows you to automatically generate personalized images and videos and send personalized cold emails. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/lemlist/). - - -## Events - -- Email Bounced -- Email Clicked -- Email Opened -- Email Replied -- Email Send Failed -- Email Sent -- Email Unsubscribed - -## Example Usage - -This workflow allows you to send a message on Mattermost when a lead replies to your email. You can also find the [workflow](https://n8n.io/workflows/984) on n8n.io. This example usage workflow would use the following node. - -- [Lemlist Trigger]() -- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/) - -The final workflow should look like the following image. - -![A workflow with the Lemlist Trigger node](/_images/integrations/builtin/trigger-nodes/lemlisttrigger/workflow.png) - -### 1. Lemlist Trigger - -The Lemlist Trigger node will trigger the workflow when a lead sends a reply to the campaign `Docs campaign`. If you have a different campaign, use that instead. - -1. First of all, you'll have to enter credentials for the Lemlist Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/lemlist/). -2. Select 'Email Replied' from the ***Events*** dropdown list. -3. Click on ***Add Field*** and select 'Campaign ID'. -4. Select 'Docs campaign' from the ***Campaign ID*** dropdown list. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the information of the reply that was sent by a lead. This output is passed on to the next node in the workflow. - -![Using the Lemlist Trigger node to trigger the workflow](/_images/integrations/builtin/trigger-nodes/lemlisttrigger/lemlisttrigger_node.png) - -## 2. Mattermost node (post: message) - -This node will send a message to the `Leads` channel in Mattermost. If you have a different channel, use that instead. - -1. First of all, you'll have to enter credentials for the Mattermost node. You can find out how to enter credentials for this node [here](/integrations/builtin/credentials/mattermost/). -2. Select a channel from the ***Channel ID*** dropdown list. -3. Click on the gears icon next to the ***Message*** field click on ***Add Expression***. - -4. Enter the following message in the ***Expression*** field: -``` -{{$json["firstName"]}} has replied back to your {{$json["campaignName"]}}. Below is the reply: -> {{$json["text"]}} -``` -5. Click on ***Execute Node*** to run the workflow. - -In the screenshot below, you will notice that the node sends a message with a reply to the `Leads` channel in Mattermost. - -![Using the Mattermost node to send a message](/_images/integrations/builtin/trigger-nodes/lemlisttrigger/mattermost_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Lemlist Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.linearTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.linearTrigger.md deleted file mode 100644 index 4eb83a93c..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.linearTrigger.md +++ /dev/null @@ -1,16 +0,0 @@ -# Linear Trigger - -[Linear](https://linear.app/) is a SaaS issue tracking tool. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/linear/). - - -## Events - -- Comment Reaction -- Cycle -- Issue -- Issue Comment -- Issue Label -- Project diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mailchimpTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mailchimpTrigger.md deleted file mode 100644 index 4e534b49d..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mailchimpTrigger.md +++ /dev/null @@ -1,31 +0,0 @@ -# Mailchimp Trigger - -[Mailchimp](https://mailchimp.com/) is an integrated marketing platform that allows business owners to automate their email campaigns and track user engagement. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mailchimp/). - - - -## Example Usage - -This workflow allows you to receive updates when Subscribe events occur in a MailChimp list. You can also find the [workflow](https://n8n.io/workflows/516) on the website. This example usage workflow would use the following node. - -- [Mailchimp Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Mailchimp Trigger node](/_images/integrations/builtin/trigger-nodes/mailchimptrigger/workflow.png) - - -### 1. Mailchimp Trigger node - -1. First of all, you'll have to enter credentials for the Mailchimp Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/mailchimp/). -2. Select the list you want to listen to from the *List* dropdown list. -3. Select 'Subscribe' from the *Events* dropdown list. -4. Select 'API', 'Admin', and 'User' from the *Sources* dropdown list. -5. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Mailchimp Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mailerLiteTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mailerLiteTrigger.md deleted file mode 100644 index a803908e3..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mailerLiteTrigger.md +++ /dev/null @@ -1,83 +0,0 @@ -# MailerLite Trigger - -[MailerLite](https://www.mailerlite.com/) is an email marketing solution that provides you with a user-friendly content editor, simplified subscriber management, and campaign reports with the most important statistics. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mailerLite/). - - -## Events - -- Campaign Sent -- Subscriber Added to Group -- Subscriber Added through Webform -- Subscriber Autonomation Completed -- Subscriber Autonomation Triggered -- Subscriber Bounced -- Subscriber Created -- Subscriber Complained -- Subscriber Removed from Group -- Subscriber Unsubscribe -- Subscriber Updated - -## Example Usage - -This workflow allows you to receive updates when a subscriber is added to a group in MailerLite and add them to a base in Airtable. You can also find the [workflow](https://n8n.io/workflows/759) on n8n.io. This example usage workflow would use the following node. - -- [MailerLite Trigger]() -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Airtable](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/) - -The final workflow should look like the following image. - -![A workflow with the Mautic Trigger node](/_images/integrations/builtin/trigger-nodes/mailerlitetrigger/workflow.png) - -### 1. MailerLite Trigger - - The MailerLite Trigger node will trigger the workflow when a subscriber is added to a group in MailerLite. - -1. First of all, you'll have to enter credentials for the MailerLite Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/mailerLite/). -2. Select 'Subscriber Added to Group' from the ***Events*** dropdown list. -3. 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 was added to a group in MailerLite. This output is passed on to the next node in the workflow. - -![Using the MailerLite Trigger node to trigger the workflow](/_images/integrations/builtin/trigger-nodes/mailerlitetrigger/mailerlitetrigger_node.png) - -### 2. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `Name` in the ***Name*** 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 > MailerLite Trigger > Output Data > JSON > data > subscriber > name. You can also add the following expression: `{{$node["MailerLite Trigger"].json["data"]["subscriber"]["name"]}}`. -5. Click on ***Add Value*** and select 'String' from the dropdown list. -6. Enter `Email` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > MailerLite Trigger > Output Data > JSON > data > subscriber > email. You can also add the following expression: `{{$node["MailerLite Trigger"].json["data"]["subscriber"]["email"]}}`. -9. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -10. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node uses the data from the previous node and returns the data that we set for the workflow. - -![Using the Set node to set the data](/_images/integrations/builtin/trigger-nodes/mailerlitetrigger/set_node.png) - -### 3. Airtable node - -This node will store the data coming from the previous node in a table in Airtable. - -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 'Append' 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 under the Introduction section. -4. In n8n, paste the ID of the base in the ***Base ID*** field. -5. Enter the table name in the ***Table*** name field. -6. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node adds the information of the subscriber from the previous node in a table in Airtable. - -![Using the Airtable node to append the information of a subscriber](/_images/integrations/builtin/trigger-nodes/mailerlitetrigger/airtable_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the MailerLite Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mailjetTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mailjetTrigger.md deleted file mode 100644 index 678747e9e..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mailjetTrigger.md +++ /dev/null @@ -1,29 +0,0 @@ -# Mailjet Trigger - -[Mailjet](https://www.mailjet.com/) is a cloud-based email sending and tracking system. The platform allows professionals to send both marketing emails and transactional emails. It includes tools for designing emails, sending massive volumes and tracking these messages. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mailjet/). - - - -## Example Usage - -This workflow allows you to receive updates when emails are sent in Mailjet. You can also find the [workflow](https://n8n.io/workflows/521) on the website. This example usage workflow would use the following node. - -- [Mailjet Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Mailjet Trigger node](/_images/integrations/builtin/trigger-nodes/mailjettrigger/workflow.png) - - -### 1. Mailjet Trigger node - -1. First of all, you'll have to enter credentials for the Mailjet Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/mailjet/). -2. Select the `email.sent` option from the *Event* dropdown list to receive updates when an email is sent. -3. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Mailjet Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mauticTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mauticTrigger.md deleted file mode 100644 index 00373d7ec..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mauticTrigger.md +++ /dev/null @@ -1,57 +0,0 @@ -# Mautic Trigger - -[Mautic](https://www.mautic.org/) is an open-source marketing automation software that helps online businesses automate their repetitive marketing tasks such as lead generation, contact scoring, contact segmentation, and marketing campaigns. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mautic/). - - -## Example Usage - -This workflow allows you to receive updates when a form is submitted in Mautic using the Mautic Trigger node and send an SMS confirmation to the submitter. You can also find the [workflow](https://n8n.io/workflows/721) on n8n.io. This example usage workflow would use the following node. - -- [Mautic Trigger]() -- [Twilio](/integrations/builtin/app-nodes/n8n-nodes-base.twilio/) - -The final workflow should look like the following image. - -![A workflow with the Mautic Trigger node](/_images/integrations/builtin/trigger-nodes/mautictrigger/workflow.png) - -### 1. Mautic Trigger node - -The Mautic Trigger node will trigger the workflow when a Mautic form is submitted. - -1. First of all, you'll have to enter credentials for the Mautic Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/mautic/). -2. Select 'Form Submit Event' from the ***Events*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the data that was submitted to the Mautic form. This output is passed on to the next nodes in the workflow. - -![Using the Mautic Trigger node to trigger the workflow](/_images/integrations/builtin/trigger-nodes/mautictrigger/mautictrigger_node.png) - -### 2. Twilio node (send: sms) - -This node sends a registration confirmation SMS to the users who filled out the Mautic form. We get the phone number of the submitter from the previous node. - -1. First of all, you'll have to enter credentials for the Twilio node. You can find out how to do that [here](/integrations/builtin/credentials/twilio/). - -3. Enter the Twilio phone number in the ***From*** field. -4. Click on the gears icon next to the ***To*** field and click on ***Add Expression***. -5. Select the following in the ***Variable Selector*** section: Nodes > Mautic Trigger > Output Data > JSON > mautic.form_on_submit > [item: 0] > submission > results > phone_number. You can also add the following expression: `{{$node["Mautic Trigger"].json["mautic.form_on_submit"][0]["submission"]["results"]["phone_number"]}}`. -6. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. -7. Enter the following message in the ***Expression*** field. -``` -Hey, {{$node["Mautic Trigger"].json["mautic.form_on_submit"][0]["submission"]["results"]["first_name"]}} 👋 -Thank you for signing up for the Webinar - Getting Started with n8n. The webinar will start at 1800 CEST on 31st October 2020. -See you there! -``` -8. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends an SMS to the submitter whose name and phone number are returned by the Mautic Trigger node. - -![Using the Twilio node to send an SMS](/_images/integrations/builtin/trigger-nodes/mautictrigger/twilio_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Mautic Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mqttTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mqttTrigger.md deleted file mode 100644 index 5ad074061..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.mqttTrigger.md +++ /dev/null @@ -1,29 +0,0 @@ -# MQTT Trigger - -[MQTT](https://mqtt.org) is an open OASIS and ISO standard lightweight, publish-subscribe network protocol that transports messages between devices. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/mqtt/). - - - -## Example Usage - -This workflow allows you to receive messages from a queue using the MQTT Trigger node. You can also find the [workflow](https://n8n.io/workflows/657) on the website. This example usage workflow would use the following node. - -- [MQTT Trigger]() - -The final workflow should look like the following image. - -![A workflow with the MQTT Trigger node](/_images/integrations/builtin/trigger-nodes/mqtttrigger/workflow.png) - - -### 1. MQTT Trigger node - -1. First of all, you'll have to enter credentials for the MQTT Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/mqtt/). -2. Enter the name of the topic in the ***Topics*** field. -3. Click on ***Execute Node*** to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the MQTT Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.netlifyTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.netlifyTrigger.md deleted file mode 100644 index e101197e3..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.netlifyTrigger.md +++ /dev/null @@ -1,6 +0,0 @@ -# Netlify Trigger - -[Netlify](https://netlify.com/) offers hosting and serverless backend services for web applications and static websites. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/netlify/). diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.notionTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.notionTrigger.md deleted file mode 100644 index df39c4d7b..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.notionTrigger.md +++ /dev/null @@ -1,83 +0,0 @@ -# Notion Trigger - -[Notion](https://notion.so) is an all-in-one workspace for your notes, tasks, wikis, and databases. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/notion/). - - -## Example Usage - -This workflow allows you to receive a message on Mattermost when new meeting notes get added to the Notion. You can also find the [workflow](https://n8n.io/workflows/1089) on n8n.io. This example usage workflow would use the following nodes. - -- [Notion Trigger]() -- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/) -- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/) -- [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 Notion Trigger node](/_images/integrations/builtin/trigger-nodes/notiontrigger/workflow.png) - -### 1. Notion Trigger node - -The Notion Trigger node will trigger the workflow when new data gets added to Notion. - -1. First of all, you'll have to enter credentials for the Notion Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/notion/). -2. Click on ***Add Poll Time*** and select 'Every Hour' from the ***Mode*** dropdown list. This will check Notion every hour for new meeting notes. -3. Select 'Page Added to Database' from the ***Event*** dropdown list. -4. Select the database that contains the meeting notes from the ***Database*** dropdown list. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node returns the new data from Notion. This output gets passed on to the next node in the workflow. - -**Note:** Make sure to add a field with the `Created Time` property type in your Notion database. - -![Using the Notion Trigger node to trigger the workflow](/_images/integrations/builtin/trigger-nodes/notiontrigger/notiontrigger_node.png) - -### 2. IF node - -This node will check if the notes belong to the `Marketing` team. If the team is `Marketing` the node will return `true`, otherwise `false`. - -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: Current Node > Input Data > JSON > properties > Team. You can also add the following expression: `{{$json["properties"]["Team"]}}`. -4. Enter `Marketing` in the ***Value 2*** field. -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node checks the team that we received from the previous node and returns `true` if the value equals `Marketing`. - -![Using the IF node to check the team](/_images/integrations/builtin/trigger-nodes/notiontrigger/if_node.png) - -### 3. Mattermost node (post: message) - -This node will send a message about the new data in the channel 'Marketing' in Mattermost. If you have a different channel, use that instead. - -1. First of all, you'll have to enter credentials for the Mattermost node. You can find out how to do that [here](/integrations/builtin/credentials/mattermost/). - -2. Select a channel from the ***Channel ID*** dropdown list. -3. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. -4. Enter the following message in the ***Expression*** field: -``` -New meeting notes got added. -Agenda: {{$json["properties"]["Agenda"]["content"]}} -Date: {{$json["properties"]["created time"]}} -``` -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends a message in Mattermost about the new data that got added to Notion. - -![Using the Mattermost node to send a message](/_images/integrations/builtin/trigger-nodes/notiontrigger/mattermost_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/trigger-nodes/notiontrigger/noop_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Notion Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.onfleetTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.onfleetTrigger.md deleted file mode 100644 index f4973c762..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.onfleetTrigger.md +++ /dev/null @@ -1,28 +0,0 @@ -# Onfleet trigger - -[Onfleet](https://onfleet.com/) is a logistics platform offering a last-mile delivery solution. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/onfleet/). - - -## Operations - -Trigger a workflow on: - -* SMS recipient opt out -* SMS recipient response missed -* Task arrival -* Task assigned -* Task cloned -* Task completed -* Task created -* Task delayed -* Task ETA -* Task failed -* Task started -* Task unassigned -* Task updated -* Worker created -* Worker deleted -* Worker duty diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.payPalTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.payPalTrigger.md deleted file mode 100644 index fb06c2110..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.payPalTrigger.md +++ /dev/null @@ -1,27 +0,0 @@ -# PayPal Trigger - -[PayPal](https://paypal.com) is a digital payment service that supports online fund transfers that customers can use when shopping online. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/payPal/). - - -## Example Usage - -This workflow allows you to receive updates when a billing plan is activated in PayPal. You can also find the [workflow](https://n8n.io/workflows/653) on n8n.io. This example usage workflow would use the following node. - -- [PayPal Trigger]() - -The final workflow should look like the following image. - -![A workflow with the PayPal Trigger node](/_images/integrations/builtin/trigger-nodes/paypaltrigger/workflow.png) - -### 1. PayPal Trigger node - -1. First of all, you'll have to enter credentials for the PayPal Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/payPal/). -2. Select 'Billing Plan Activated' from the ***Events*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the PayPal Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.pipedriveTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.pipedriveTrigger.md deleted file mode 100644 index 10fed5a0c..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.pipedriveTrigger.md +++ /dev/null @@ -1,28 +0,0 @@ -# Pipedrive Trigger - -[Pipedrive](https://www.pipedrive.com/) is a cloud-based sales software company that aims to improve the productivity of businesses through the use of their software. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/pipedrive/). - - - -## Example Usage - -This workflow allows you to receive updates for all changes in Pipedrive. You can also find the [workflow](https://n8n.io/workflows/490) on the website. This example usage workflow would use the following node. - -- [Pipedrive Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Pipedrive Trigger node](/_images/integrations/builtin/trigger-nodes/pipedrivetrigger/workflow.png) - - -### 1. Pipedrive Trigger node - -1. First of all, you'll have to enter credentials for the Pipedrive Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/pipedrive/). -2. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Pipedrive Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postmarkTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postmarkTrigger.md deleted file mode 100644 index 8bdadda35..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.postmarkTrigger.md +++ /dev/null @@ -1,29 +0,0 @@ -# Postmark Trigger - -[Postmark](https://postmarkapp.com) helps deliver and track application email. You can track statistics such as the number of emails sent or processed, opens, bounces and, spam complaints. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/postmark/). - - -## Example Usage - -This workflow allows you to receive updates when an email is bounced or opened using the Postmark Trigger Node. You can also find the [workflow](https://n8n.io/workflows/660) on n8n.io. This example usage workflow would use the following node. - -- [Postmark Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Postmark Trigger node](/_images/integrations/builtin/trigger-nodes/postmarktrigger/workflow.png) - -### 1. Postmark Trigger node - -1. First of all, you'll have to enter credentials for the Postmark Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/postmark/). -2. Select 'Bounce' from the ***Events*** dropdown list. -3. Select 'Open' from the ***Events*** dropdown list. -4. Toggle the ***Include Content*** field to true. -5. Click on ***Execute Node*** to run the node. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Postmark Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.pushcutTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.pushcutTrigger.md deleted file mode 100644 index 461d4ff57..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.pushcutTrigger.md +++ /dev/null @@ -1,69 +0,0 @@ -# Pushcut Trigger - -[Pushcut](https://pushcut.io) is an app for iOS that lets you create smart notifications to kick off shortcuts, URLs, and online automation. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/pushcut/). - - -## Example Usage - -This workflow allows you to send an SMS to a number whenever you go out. You can also find the [workflow](https://n8n.io/workflows/870) on n8n.io. This example usage workflow uses the following nodes. - -- [Pushcut Trigger]() -- [Twilio](/integrations/builtin/app-nodes/n8n-nodes-base.twilio/) - -The final workflow should look like the following image. - -![A workflow with the Pushcut Trigger node](/_images/integrations/builtin/trigger-nodes/pushcuttrigger/workflow.png) - -### 1. Pushcut Trigger node - -Whenever you leave your house, Pushcut will send you a notification with an action `Leaving Home`. The Pushcut Trigger node will trigger the workflow when this action is selected. - -To create an action in the Pushcut app, follow the instructions mentioned in [FAQs](#how-to-configure-a-pushcut-action). - -1. First of all, you'll have to enter credentials for the Pushcut Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/pushcut/). -2. Enter an action name in the ***Action Name*** field. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node triggers the workflow whenever the `Leaving Home` action is selected. - -![Using the Pushcut Trigger node to trigger the workflow](/_images/integrations/builtin/trigger-nodes/pushcuttrigger/pushcuttrigger_node.png) - -### 2. Twilio node (send: sms) - -This node will send an SMS to a specified phone number notifying the recipient that you are going out. - -1. First of all, you'll have to enter credentials for the Twilio node. You can find out how to do that [here](/integrations/builtin/credentials/twilio/). -2. Enter the Twilio phone number in the ***From*** field. -4. Enter the receiver's phone number in the ***To*** field. -5. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. - -6. Enter `I'm {{$node["Pushcut Trigger"].json["input"]}}` in the ***Expression*** field. -7. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends an SMS with the input that we received from the Pushcut Trigger node. - -![Using the Twilio node to send an SMS](/_images/integrations/builtin/trigger-nodes/pushcuttrigger/twilio_node.png) - -## FAQs - -### How to configure a Pushcut action? - -Follow the steps mentioned below to configure your Pushcut Trigger node with your Pushcut app. - -1. In your Puschcut app, select a notification from the ***Notifications*** screen. -2. Click on the ***Add Action*** button. -3. Enter an action name in the ***Label*** field. -4. Select the ***Server*** tab. -5. Select the ***Integration*** tab. -6. Click on ***Integration Trigger***. -7. In n8n, enter a name for the action and click on ***Execute Node***. -8. Select this action under the ***Select Integration Trigger*** screen in your Pushcut app. -9. Click on ***Done*** on the top right to save the action. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Pushcut Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.rabbitmqTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.rabbitmqTrigger.md deleted file mode 100644 index 421bce9ca..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.rabbitmqTrigger.md +++ /dev/null @@ -1,86 +0,0 @@ -# RabbitMQ Trigger - -[RabbitMQ](https://www.rabbitmq.com) is an open-source message broker that accepts and forwards messages. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/rabbitmq/). - - -## Example Usage - -This workflow allows you to receive messages from a queue and send an SMS if the value of the temperature is greater than 50. You can also find the [workflow](https://n8n.io/workflows/845) on n8n.io. This example usage workflow would use the following nodes. - -- [RabbitMQ Trigger]() -- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/) -- [Vonage](/integrations/builtin/app-nodes/n8n-nodes-base.vonage/) -- [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 RabbitMQ Trigger node](/_images/integrations/builtin/trigger-nodes/rabbitmqtrigger/workflow.png) - -### 1. RabbitMQ Trigger node - -This node will trigger the workflow when a new message is sent to the queue `temp`. If you're using a different queue, use that instead. We are sending the message `{ "id": 1, "temp": 100 }` to `temp`. - -1. First of all, you'll have to enter credentials for the RabbitMQ Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/rabbitmq/). -2. Enter the name of the queue or topic in the ***Queue / Topic*** field. -3. Click on ***Add Option*** and select 'JSON Parse Body'. -4. Toggle ***JSON Parse Body*** to `true`. By setting this value to true, the node returns the body as JSON instead of a string. -5. Click on ***Add Option*** and select 'Only Content'. -6. Toggle ***Only Content*** to `true`. By setting this to true, the node only returns the message. -7. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node gets triggered when a new message is sent to the `temp` queue in RabbitMQ. - -![Using the RabbitMQ Trigger node to get a message from a queue](/_images/integrations/builtin/trigger-nodes/rabbitmqtrigger/rabbitmqtrigger_node.png) - -### 2. IF node - -This node will compare the value of `temp` that we received in the message from the previous node. If the value is greater than 50, it will return true otherwise false. - -1. Click on ***Add Condition*** and select 'Number' from the dropdown list. -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 > RabbitMQ > Output Data > JSON > temp. You can also add the following expression: `{{$node["RabbitMQ"].json["temp"]}}`. -4. Select 'Larger' from the ***Operation*** dropdown list. -5. Set ***Value 2*** to 50. -6. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node returns output for **true** when the temperature is greater than 50. - -![Using the IF node to check if the temp is larger than 50](/_images/integrations/builtin/trigger-nodes/rabbitmqtrigger/if_node.png) - -### 3. Vonage node (send: sms) - -This node sends an SMS to the specified phone number when the value of `temp` is greater than `50`. - -1. Create a Vonage node connected to the 'true' output of the IF node. -2. You'll have to enter credentials for the Vonage node. You can find out how to do that [here](/integrations/builtin/credentials/vonage/). -3. Enter the name of the sender in the ***From*** field. If you're using a number, enter the number instead. -4. Enter the receiver's phone number in the ***To*** field. -5. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***. - -6. Enter the following in the ***Expression*** field. -``` -Alert! -The value of temp is {{$node["RabbitMQ"].json["temp"]}}. -``` -7. Click on ***Execute Node*** to run the node. - - -In the screenshot below, you will notice that the node sends an SMS with the value of `temp` that we received from the RabbitMQ Trigger node. - -![Using the Vonage node to send an SMS](/_images/integrations/builtin/trigger-nodes/rabbitmqtrigger/vonage_node.png) - -### 4. 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/trigger-nodes/rabbitmqtrigger/noop_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the RabbitMQ Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.redisTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.redisTrigger.md deleted file mode 100644 index 610ad5d6e..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.redisTrigger.md +++ /dev/null @@ -1,9 +0,0 @@ -# Redis trigger - -[Redis](https://redis.io/) is an open-source, in-memory data structure store, used as a database, cache and message broker. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/redis/). - - -Use the Redis trigger node to subscribe to a Redis channel. The workflow starts whenever the channel receives a new message. diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.seaTableTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.seaTableTrigger.md deleted file mode 100644 index b80edfb53..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.seaTableTrigger.md +++ /dev/null @@ -1,34 +0,0 @@ -# SeaTable Trigger - -[SeaTable](https://seatable.co) is a collaborative database application with a spreadsheet interface. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/seaTable/). - - - -## Example usage - -This workflow allows you to receive updates when new rows are created in a Table. This example usage workflow would use the following node. - -- [SeaTable Trigger]() - -The final workflow should look like the following image. - -![A workflow with the SeaTable Trigger node](/_images/integrations/builtin/trigger-nodes/seatabletrigger/workflow.png) - - -### 1. SeaTable Trigger node - -1. First enter your credentials for the SeaTable Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/seaTable/). -2. Select the **Table** you want to receive updates for. -3. From the ***Events*** dropdown select **Row Created**. -3. Click on **Execute Node** to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the node. - - - - - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.sendInBlueTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.sendInBlueTrigger.md deleted file mode 100644 index 16e6d331a..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.sendInBlueTrigger.md +++ /dev/null @@ -1,7 +0,0 @@ -# Sendinblue Trigger - -Sendinblue is a digital marketing platform to help users grow their business. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/sendInBlue/). - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.shopifyTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.shopifyTrigger.md deleted file mode 100644 index 5eb773d51..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.shopifyTrigger.md +++ /dev/null @@ -1,29 +0,0 @@ -# Shopify Trigger - -[Shopify](https://www.shopify.com/) is an e-commerce platform that allows users to set up an online store and sell their products. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/shopify/). - - - -## Example Usage - -This workflow allows you to receive updates when a new order is created in Shopify. You can also find the [workflow](https://n8n.io/workflows/547) on the website. This example usage workflow would use the following node. - -- [Shopify Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Shopify Trigger node](/_images/integrations/builtin/trigger-nodes/shopifytrigger/workflow.png) - - -### 1. Shopify Trigger node - -1. First of all, you'll have to enter credentials for the Shopify Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/shopify/). -2. Select 'Orders create' from the *Topic* dropdown list. -3. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Shopify Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.stravaTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.stravaTrigger.md deleted file mode 100644 index 1b8ac8c08..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.stravaTrigger.md +++ /dev/null @@ -1,71 +0,0 @@ -# Strava Trigger - -[Strava](https://www.strava.com/) is an internet service for tracking human exercise which incorporates social network features. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/strava/). - - -## Events - -* -- `*` -- Created -- Deleted -- Updated - - -**Activity** -- `*` -- Created -- Deleted -- Updated - - -**Athlete** -- `*` -- Created -- Deleted -- Updated - - -## Example Usage - -This workflow allows you to receive updates when a new activity gets created in Strava using the Strava Trigger node. It also allows you to tweet about the activity that was created in Strava using the Twitter node. You can also find the [workflow](https://n8n.io/workflows/745) on n8n.io. This example usage workflow would use the following node. -- [Strava Trigger]() -- [Twitter](/integrations/builtin/app-nodes/n8n-nodes-base.twitter/) - -The final workflow should look like the following image. - -![A workflow with the Strava Trigger node](/_images/integrations/builtin/trigger-nodes/stravatrigger/workflow.png) - -### 1. Strava Trigger node - -This node will trigger the workflow when a new activity gets created in Strava. - -1. First of all, you'll have to enter credentials for the Strava Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/strava/). -2. Select 'Activity' from the ***Object*** dropdown list. -3. Select 'created' from the ***Event*** dropdown list. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node triggers the workflow when a new activity gets created in Strava. - -![Using the Strava Trigger node to receive updates when a new activity is created](/_images/integrations/builtin/trigger-nodes/stravatrigger/stravatrigger_node.png) - -### 2. Twitter node (create: tweet) - -This node will tweet about the activity that gets created in Strava. - -1. First of all, you'll have to enter credentials for the Twitter node. You can find out how to do that [here](/integrations/builtin/credentials/twitter/). -2. Click on the gears icon next to the ***Text*** field and click on ***Add Expression***. - -3. Enter the following text in the ***Expression*** field: `I ran {{$node["Strava Trigger"].json["object_data"]["distance"]}} meters and completed my {{$node["Strava Trigger"].json["object_data"]["name"]}}!` -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that this node gets the information of the activity in Strava from the previous node and tweets about it. - -![Using the Twitter node to tweet about the activity](/_images/integrations/builtin/trigger-nodes/stravatrigger/twitter_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Strava Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.stripeTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.stripeTrigger.md deleted file mode 100644 index 8aaceed39..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.stripeTrigger.md +++ /dev/null @@ -1,32 +0,0 @@ -# Stripe Trigger - -Stripe is a suite of payment APIs that powers commerce for online businesses. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/stripe/). - - - -## Example Usage - -This workflow allows you to receive updates for Stripe events. You can also find the [workflow](https://n8n.io/workflows/545) on the website. This example usage workflow would use the following node. -- [Stripe Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Stripe Trigger node](/_images/integrations/builtin/trigger-nodes/stripetrigger/workflow.png) - - -### 1. Stripe Trigger node - -1. First of all, you'll have to enter credentials for the Stripe Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/stripe/). -2. Select the `*` option in the *Events* field to receive updates when any event is triggered. -3. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Stripe Trigger node. - - - - - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.surveyMonkeyTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.surveyMonkeyTrigger.md deleted file mode 100644 index af74f04b4..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.surveyMonkeyTrigger.md +++ /dev/null @@ -1,31 +0,0 @@ -# SurveyMonkey Trigger - -[SurveyMonkey](https://www.surveymonkey.com/) is an online cloud-based SaaS survey platform that also provides a suite of paid back-end programs. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/surveyMonkey/). - - - -## Example Usage - -This workflow allows you to receive updates when responses are created for SurveyMonkey surveys. You can also find the [workflow](https://n8n.io/workflows/551) on the website. This example usage workflow would use the following node. - -- [SurveyMonkey Trigger]() - -The final workflow should look like the following image. - -![A workflow with the SurveyMonkey Trigger node](/_images/integrations/builtin/trigger-nodes/surveymonkeytrigger/workflow.png) - - -### 1. SurveyMonkey Trigger node - -1. First of all, you'll have to enter credentials for the SurveyMonkey Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/surveyMonkey/). -2. Select the 'Survey' option from the *Type* dropdown list. -3. Select 'Response Created' from the *Event* dropdown list. -4. Select the surveys you want to receive updates for from the *Survey IDs* dropdown list. -5. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the SurveyMonkey Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.taigaTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.taigaTrigger.md deleted file mode 100644 index bb8006345..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.taigaTrigger.md +++ /dev/null @@ -1,27 +0,0 @@ -# Taiga Trigger - -[Taiga](https://www.taiga.io/) is a free and open-source project management platform for startups, agile developers, and designers. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/taiga/). - - -## Example Usage - -This workflow allows you to receive updates when an event occurs in Taiga. You can also find the [workflow](https://n8n.io/workflows/686) on n8n.io. This example usage workflow would use the following node. - -- [Taiga Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Taiga Trigger node](/_images/integrations/builtin/trigger-nodes/taigatrigger/workflow.png) - -### 1. Taiga Trigger node - -1. First of all, you'll have to enter credentials for the Taiga Trigger 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. -2. Click on ***Execute Node*** to run the node. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Taiga Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.telegramTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.telegramTrigger.md deleted file mode 100644 index 740812a87..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.telegramTrigger.md +++ /dev/null @@ -1,85 +0,0 @@ -# Telegram Trigger - -[Telegram](https://telegram.org/) is a cloud-based instant messaging and voice over IP service. Users can send messages and exchange photos, videos, stickers, audio, and files of any type. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/telegram/). - - -## Updates - -- `*`: All updates -- ***message***: Trigger on a new incoming message of any kind- text, photo, sticker, etc -- ***edited_message***: Trigger on a new version of a channel post that is known to the bot and was edited -- ***channel_post***: Trigger on a new incoming channel post of any kind - text, photo, sticker, etc -- ***edited_channel_post***: Trigger on a new version of a channel post that is known to the bot and was edited -- ***inline_query***: Trigger on a new incoming inline query -- ***callback_query***: Trigger on a new incoming callback query -- ***shipping_query***: Trigger on a new incoming shipping query. Only for invoices with flexible price -- ***pre_checkout_query***: Trigger on a new incoming pre-checkout query. Contains full information about checkout -- ***poll***: Trigger on a new poll state. Bots receive only updates about stopped polls and polls which are sent by the bot - -## Example Usage - -This workflow allows you to receive messages using the Telegram Trigger node and send an image of a cocktail when a message is received. You can also find the [workflow](https://n8n.io/workflows/782) on n8n.io. This example usage workflow would use the following nodes. - -- [Telegram Trigger]() -- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) -- [Telegram](/integrations/builtin/app-nodes/n8n-nodes-base.telegram/) - -The final workflow should look like the following image. - -![A workflow with the Telegram Trigger node](/_images/integrations/builtin/trigger-nodes/telegramtrigger/workflow.png) - -### 1. Telegram Trigger node - -This node will trigger the workflow when a user sends a new message. - -1. First of all, you'll have to enter credentials for the Telegram Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/telegram/). -2. Select 'message' from the ***Updates*** dropdown list. This will trigger the workflow when a user sends a message. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node triggers the workflow when a user sends a new message. - -![Using the Telegram Trigger node to trigger the workflow](/_images/integrations/builtin/trigger-nodes/telegramtrigger/telegramtrigger_node.png) - -### 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/trigger-nodes/telegramtrigger/httprequest_node.png) - -### 3. Telegram node (sendPhoto: message) - -This node will send a reply to the message with the name and image of the cocktail that we got from the previous node. - -1. Select the credentials that you entered in the Telegram Trigger node. -2. Select 'Send Photo' from the ***Operation*** dropdown list. -3. Click on the gears icon next to the ***Chat ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Telegram Trigger > Output Data > JSON > message > chat > id. You can also add the following expression: `{{$node["Telegram Trigger"].json["message"]["chat"]["id"]}}`. -5. Click on the gears icon next to the ***Photo*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > drinks > [item: 0] > strDrinkThumb. You can also add the following expression: `{{$node["HTTP Request"].json["drinks"][0]["strDrinkThumb"]}}`. -7. Click on ***Add Field*** and select 'Caption' from the dropdown list. -8. Click on the gears icon next to the ***Caption*** field and click on ***Add Expression***. -9. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > JSON > drinks > [item: 0] > strDrink. You can also add the following expression: `{{$node["HTTP Request"].json["drinks"][0]["strDrink"]}}`. -10. Click on ***Add Field*** and select 'Reply To Message ID' from the dropdown list. -11. Click on the gears icon next to the ***Reply To Message ID*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Nodes > Telegram Trigger > Output Data > JSON > message > message_id. You can also add the following expression: `{{$node["Telegram Trigger"].json["message"]["message_id"]}}`. -13. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends a reply to the message with the name and image of the cocktail that we got from the previous node. - -![Using the Telegram node to send a message with an image and instruction of a cocktail](/_images/integrations/builtin/trigger-nodes/telegramtrigger/telegram_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Telegram Trigger node. - - - - - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.theHiveTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.theHiveTrigger.md deleted file mode 100644 index f2ca411fc..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.theHiveTrigger.md +++ /dev/null @@ -1,60 +0,0 @@ -# The Hive trigger - -[TheHive](https://thehive-project.org/) is a scalable open-source and free security incident response platform. - -## Example Usage - -This workflow allows you to receive updates when an event occurs in TheHive. You can also find the [workflow](https://n8n.io/workflows/810) on the website. This example usage workflow would use the following node. - -- [TheHive Trigger]() - -The final workflow should look like the following image. - -![A workflow with the TheHive Trigger node](/_images/integrations/builtin/trigger-nodes/thehivetrigger/workflow.png) - -### 1. TheHive Trigger node - -This node will trigger the workflow whenever a new event occurs in TheHive. To trigger the workflow for a specific event, select that event instead. - -1. First of all, you'll have to add the webhook URL in TheHive instance configuration. Refer to the [FAQs](#how-to-configure-a-webhook-in-thehive) to learn how to configure a webhook in TheHive. -2. Select the `*` from the **Events** dropdown list. This will trigger the workflow for all the events. -3. Click on **Execute Node** to run the node. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the TheHive Trigger node. - - -## FAQs - -### How to configure a Webhook in TheHive? - -To configure the webhook for your TheHive instance follow the steps mentioned below. -1. Copy the webhook URL from TheHive Trigger node. -2. Add the following lines to the application.conf file. This is TheHive configuration file. -``` -notification.webhook.endpoints = [ - { - name: WEBHOOK_NAME - url: WEBHOOK_URL - version: 0 - wsConfig: {} - includedTheHiveOrganisations: ["ORGANIZATION_NAME"] - excludedTheHiveOrganisations: [] - } -] -``` -3. Replace `WEBHOOK_URL` with the URL you copied in the previous step. -4. Replace `ORGANIZATION_NAME` with your organization name. -5. Execute the following cURL command to enable notifications. -```sh -curl -XPUT -uTHEHIVE_USERNAME:THEHIVE_PASSWORD -H 'Content-type: application/json' THEHIVE_URL/api/config/organisation/notification -d ' -{ - "value": [ - { - "delegate": false, - "trigger": { "name": "AnyEvent"}, - "notifier": { "name": "webhook", "endpoint": "WEBHOOK_NAME" } - } - ] -}' -``` diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.togglTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.togglTrigger.md deleted file mode 100644 index 520b91471..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.togglTrigger.md +++ /dev/null @@ -1,30 +0,0 @@ -# Toggl Trigger - -[Toggl](https://toggl.com/) is a time tracking app that offers online time tracking and reporting services through their website along with mobile and desktop applications. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/toggl/). - - - -## Example Usage - -This workflow allows you to get new time entries from Toggl. You can also find the [workflow](https://n8n.io/workflows/517) on the website. This example usage workflow would use the following node. - -- [Toggl Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Toggl Trigger node](/_images/integrations/builtin/trigger-nodes/toggltrigger/workflow.png) - - -### 1. Toggl Trigger node - -1. First of all, you'll have to enter credentials for the Toggl Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/toggl/). -2. Click on *Execute Node* to run the workflow. - -**Note:** This node uses polling to get new time entries. You'll have to use the *Add Poll Time* button if you want this Trigger node to run regularly to retrieve new time entries. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Toggl Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.trelloTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.trelloTrigger.md deleted file mode 100644 index 7d683ff7f..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.trelloTrigger.md +++ /dev/null @@ -1,47 +0,0 @@ -# Trello Trigger - -[Trello](https://trello.com/) is a web-based Kanban-style list-making application which is a subsidiary of Atlassian. Users can create their task boards with different columns and move the tasks between them. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/trello/). - - - -## Example Usage - -This workflow allows you to receive updates for changes in the specified list in Trello. You can also find the [workflow](https://n8n.io/workflows/491) on the website. This example usage workflow would use the following node. - -- [Trello Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Trello Trigger node](/_images/integrations/builtin/trigger-nodes/trellotrigger/workflow.png) - - -### 1. Trello Trigger node - -1. First of all, you'll have to enter credentials for the Trello Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/trello/). -2. Enter the ID of the list in the *Model ID* field. You can find instructions on how to do that in the FAQs below. -3. Click on *Execute Node* to run the workflow. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Trello Trigger node. - - - -## FAQs - -### How do I find the Model ID? - -For this specific example, the List ID would be the Model ID. - -1. Open the Trello board that contains the list. -2. If the list doesn't have any cards, add a card to the list. -3. Open the card, add '.json' at the end of the URL, and press enter. -4. In the JSON file, you will see a field called `idList`. -5. Copy `idList`and paste it in the *Model ID* field in n8n. - - -### What is the Model ID? - -It is the ID of any model in Trello. Depending on the use-case, it could be the User ID, List ID, and so on. diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.typeformTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.typeformTrigger.md deleted file mode 100644 index f8279a112..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.typeformTrigger.md +++ /dev/null @@ -1,101 +0,0 @@ -# Typeform Trigger - -[Typeform](https://www.typeform.com/) is an online software as a service company that specializes in online form building and online surveys. Its main software creates dynamic forms based on user needs. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/typeform/). - - - -## Example Usage - -This workflow allows you to store the response of a form submission to Airtable and send a message to a channel on Slack. You can also find the [workflow](https://n8n.io/workflows/916) on the website. This example usage workflow would use the following nodes. - -- [Typeform Trigger]() -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Airtable](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/) -- [Slack](/integrations/builtin/app-nodes/n8n-nodes-base.slack/) - -The final workflow should look like the following image. - -![A workflow with the Typeform Trigger node](/_images/integrations/builtin/trigger-nodes/typeformtrigger/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. Here 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/trigger-nodes/typeformtrigger/typeformtrigger_node.png) - -### 2. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. We will set the value of `Name` and `Email` in this node. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `Name` in the ***Name*** 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: 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."]}}`. -5. Click on ***Add Value*** and select 'String' from the dropdown list. -6. Enter `Email` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. 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?"]}}`. -9. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -10. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sets the values of `Name` and `Email`. These values are passed to the next node in the workflow. - -![Using the Set node to set the values](/_images/integrations/builtin/trigger-nodes/typeformtrigger/set_node.png) - -### 3. Airtable node (Append) - -This node will append the data that we set in the previous node to a table. Create a table like [this](https://airtable.com/shreoj1AmTE6S6Eep) 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 'Append' 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 ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node appends the data that we had set in the previous node. - -![Using the Airtable node to insert data into an Airtable table](/_images/integrations/builtin/trigger-nodes/typeformtrigger/airtable_node.png) - -### 4. Slack node (post: message) - -This node will send a message about the new form submission to a channel in a Slack workspace. - -1. First of all, you'll have to enter credentials for the Slack node. You can find out how to do that [here](/integrations/builtin/credentials/slack/). -2. Enter the name of a channel in the ***Channel*** field. -3. Click on the gears icon next to the ***Text*** field and click on ***Add Expression***. -4. Enter the following text in the ***Expression Editor*** -``` -*New Submission* -Name: {{$node["Set"].json["Name"]}} -Email: {{$node["Set"].json["Email"]}} -``` -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends a message with the new form response on Slack. - -![Using the Slack node to send a message to channel](/_images/integrations/builtin/trigger-nodes/typeformtrigger/slack_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Typeform Trigger node. - - - - - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.venafitlsprotectcloudtrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.venafitlsprotectcloudtrigger.md deleted file mode 100644 index 3e2ad7fed..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.venafitlsprotectcloudtrigger.md +++ /dev/null @@ -1,8 +0,0 @@ -# Venafi TLS Protect Cloud Trigger - -[Venafi](https://www.venafi.com/){:target=_blank .external-link} is a cybersecurity company providing services for machine identity management. They offer solutions to manage and protect identities for a wide range of machine types, delivering global visibility, lifecycle automation, and actionable intelligence. - -The n8n Venafi TLS Protect Cloud trigger node allows you to start a workflow in n8n in response to events in the [cloud-based Venafi TLS Protect](https://vaas.venafi.com/){:target=_blank} service. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/venafiTlsProtectCloud/). diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.webflowTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.webflowTrigger.md deleted file mode 100644 index dca5360a3..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.webflowTrigger.md +++ /dev/null @@ -1,27 +0,0 @@ -# Webflow Trigger - -[Webflow](https://webflow.com) is an application that allows you to build responsive websites with browser-based visual editing software. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/webflow/). - - -## Example Usage - -This workflow allows you to receive updates when a form submission occurs in your Webflow website. You can also find the [workflow](https://n8n.io/workflows/651) on n8n.io. This example usage workflow would use the following node. - -- [Webflow Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Webflow Trigger node](/_images/integrations/builtin/trigger-nodes/webflowtrigger/workflow.png) - -### 1. Webflow Trigger node - -1. First of all, you'll have to enter credentials for the Webflow Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/webflow/). -2. Select your website from the ***Site*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Webflow Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.wiseTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.wiseTrigger.md deleted file mode 100644 index 113a6e67d..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.wiseTrigger.md +++ /dev/null @@ -1,99 +0,0 @@ -# Wise Trigger - -[Wise](https://wise.com) allows you to transfer money abroad with low-cost money transfers, receive money with international account details, and track transactions on your phone. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/wise/). - - -## Events - -- Triggered every time a balance account is credited -- Triggered every time a transfer's list of active cases is updated -- Triggered every time a transfer's status is updated - -## Example Usage - -This workflow allows you to receive updates from Wise and add information of a transfer to a base in Airtable. You can also find the [workflow](https://n8n.io/workflows/993) on n8n.io. This example usage workflow would use the following nodes. - -- [Wise Trigger]() -- [Wise](/integrations/builtin/app-nodes/n8n-nodes-base.wise/) -- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/) -- [Airtable](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/) - -The final workflow should look like the following image. - -![A workflow with the Wise Trigger node](/_images/integrations/builtin/trigger-nodes/wisetrigger/workflow.png) - -### 1. Wise Trigger node (transferStateChange) - -This node will trigger the workflow when the status of your transfer changes. - -1. First of all, you'll have to enter credentials for the Wise Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/wise/). -2. Select 'Personal' from the ***Profile*** dropdown list. -3. Select 'Transfer State Changed' from the ***Event*** dropdown list. -4. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node triggers the workflow when a new order gets created. - -![Using the Wise Trigger node to trigger the workflow](/_images/integrations/builtin/trigger-nodes/wisetrigger/wisetrigger_node.png) - -### 2. Wise node (get: transfer) - -This node will get the information about the transfer. - -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. -5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > data > resource > id. You can also add the following expression: `{{$json["data"]["resource"]["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 transfer. - -![Using the Wise node to retrieve the information of the transfer](/_images/integrations/builtin/trigger-nodes/wisetrigger/wise_node.png) - -### 3. Set node - -We will use the Set node to ensure that only the data that we set in this node gets passed on to the next nodes in the workflow. We will set the value of `Transfer ID`, `Date`, `Reference`, and `Amount` in this node. - -1. Click on ***Add Value*** and select 'String' from the dropdown list. -2. Enter `Transfer ID` in the ***Name*** 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: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`. -5. Click on ***Add Value*** and select 'String' from the dropdown list. -6. Enter `Date` in the ***Name*** field. -7. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > created. You can also add the following expression: `{{$json["created"]}}`. -9. Click on ***Add Value*** and select 'String' from the dropdown list. -10. Enter `Reference` in the ***Name*** field. -11. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > reference. You can also add the following expression: `{{$json["reference"]}}`. -13. Click on ***Add Value*** and select 'String' from the dropdown list. -10. Enter `Amount` in the ***Name*** field. -11. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***. -12. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > sourceValue. You can also add the following expression: `{{$json["sourceValue"]}}`. -13. Toggle ***Keep Only Set*** to `true`. We set this option to true to ensure that only the data that we have set in this node get passed on to the next nodes in the workflow. -14. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sets the values of `Transfer ID`, `Date`, `Reference`, and `Amount`. These values are passed to the next node in the workflow. - -![Using the Set node to set the values](/_images/integrations/builtin/trigger-nodes/wisetrigger/set_node.png) - -### 4. Airtable node (Append) - -This node will append the data that we set in the previous node to a table. Create a table like [this](https://airtable.com/shrZQQCRtQPBYTmUe) 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 'Append' 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 ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node appends the data that we had set in the previous node. - -![Using the Airtable node to insert data into an Airtable table](/_images/integrations/builtin/trigger-nodes/wisetrigger/airtable_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Wise Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.wooCommerceTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.wooCommerceTrigger.md deleted file mode 100644 index fb43a7dbb..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.wooCommerceTrigger.md +++ /dev/null @@ -1,66 +0,0 @@ -# WooCommerce Trigger - -[WooCommerce](https://woocommerce.com/) is a customizable, open-source e-commerce plugin for WordPress. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/wooCommerce/). - - -## Events - -- coupon.created -- coupon.updated -- coupon.deleted -- customer.created -- customer.updated -- customer.deleted -- order.created -- order.updated -- order.deleted -- product.created -- product.updated -- product.deleted - -## Example Usage - -This workflow allows you to send a message on Mattermost when an order is created in WooCommerce. You can also find the [workflow](https://n8n.io/workflows/848) on n8n.io. This example usage workflow would use the following nodes. - -- [WooCommerce Trigger]() -- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/) - -The final workflow should look like the following image. - -![A workflow with the WooCommerce Trigger node](/_images/integrations/builtin/trigger-nodes/woocommercetrigger/workflow.png) - -### 1. WooCommerce Trigger node - -This node will trigger the workflow when an order is created in your WooCommerce store. - -1. First of all, you'll have to enter credentials for the WooCommerce Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/wooCommerce/). -2. Select 'order.created' from the ***Event*** dropdown list. This will trigger the workflow when a user sends a message. -3. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node triggers the workflow when a new order gets created. - -![Using the WooCommerce Trigger node to trigger the workflow](/_images/integrations/builtin/trigger-nodes/woocommercetrigger/woocommercetrigger_node.png) - -### 2. Mattermost (post: message) - -This node will send a message to a Mattermost channel sharing the details of the order that was created in WooCommerce. - -1. First of all, you'll have to enter credentials for the Mattermost node. You can find out how to do that [here](/integrations/builtin/credentials/mattermost/). -2. Select the channel from the ***Channel ID*** dropdown list. -3. Click on the gears icon next to ***Message*** field. -4. Enter the following message in the ***Expression*** editor -``` -{{$node["WooCommerce Trigger"].json["billing"]["first_name"]}} bought {{$node["WooCommerce Trigger"].json["line_items"][0]["name"]}}! -``` -5. Click on ***Execute Node*** to run the node. - -In the screenshot below, you will notice that the node sends a message to the `Sales` channel on Mattermost about the order that was created in WooCommerce. - -![Using the Mattermost node to send the information of the order to a channel](/_images/integrations/builtin/trigger-nodes/woocommercetrigger/mattermost_node.png) - -!!! note "Activate workflow for production" - 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 as specified by the settings in the WooCommerce Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.workableTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.workableTrigger.md deleted file mode 100644 index 405db901c..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.workableTrigger.md +++ /dev/null @@ -1,12 +0,0 @@ -# Workable Trigger - -[Workable](https://www.workable.com/) is a recruiting platform. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/workable/). - - -## Trigger Events - -- **Candidate Created** -- **Candidate Moved** diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.wufooTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.wufooTrigger.md deleted file mode 100644 index d8d951b54..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.wufooTrigger.md +++ /dev/null @@ -1,27 +0,0 @@ -# Wufoo Trigger - -[Wufoo](https://wufoo.com) is an online form builder that helps you create custom HTML forms without writing code. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/wufoo/). - - -## Example Usage - -This workflow allows you to receive updates when a form is submitted in Wufoo. You can also find the [workflow](https://n8n.io/workflows/703) on n8n.io. This example usage workflow would use the following node. - -- [Wufoo Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Wufoo Trigger node](/_images/integrations/builtin/trigger-nodes/wufootrigger/workflow.png) - -### 1. Wufoo Trigger node - -1. First of all, you'll have to enter credentials for the Wufoo Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/wufoo/). -2. Select a form from the ***Forms*** dropdown list. -3. Click on ***Execute Node*** to run the node. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Wufoo Trigger node. - diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.zendeskTrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.zendeskTrigger.md deleted file mode 100644 index 29793e02a..000000000 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.zendeskTrigger.md +++ /dev/null @@ -1,28 +0,0 @@ -# Zendesk Trigger - -[Zendesk](https://www.zendesk.com/) is a support ticketing system, designed to help track, prioritize, and solve customer support interactions. More than just a help desk, Zendesk Support helps nurture customer relationships with personalized, responsive support across any channel. - -!!! note "Credentials" - You can find authentication information for this node [here](/integrations/builtin/credentials/zendesk/). - - -## Example Usage - -This workflow allows you to receive updates for support in Zendesk. You can also find the [workflow](https://n8n.io/workflows/648) on n8n.io. This example usage workflow would use the following node. - -- [Zendesk Trigger]() - -The final workflow should look like the following image. - -![A workflow with the Zendesk Trigger node](/_images/integrations/builtin/trigger-nodes/zendesktrigger/workflow.png) - -### 1. Zendesk Trigger node - -1. First of all, you'll have to enter credentials for the Zendesk Trigger node. You can find out how to do that [here](/integrations/builtin/credentials/zendesk/). -2. Click on the ***Add Condition*** button and select 'All' from the dropdown list. -3. Select 'Open' from the ***Value*** dropdown list. -4. Click on ***Execute Node*** to run the node. - -!!! note "Activate workflow for production" - 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 as specified by the settings in the Zendesk Trigger node. -