mirror of
https://github.com/n8n-io/n8n-docs.git
synced 2025-11-20 17:48:34 +00:00
redirect and temp remove
This commit is contained in:
Deborah Barnard
parent
1468d45e6c
commit
4cf4358fbf
792
docs/_redirects
792
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/
|
||||
|
||||
@ -1,3 +0,0 @@
|
||||
# App nodes library
|
||||
|
||||
This section provides information about n8n's app nodes.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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`.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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`.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
## 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.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
!!! 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.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
!!! 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.
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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`.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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`.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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`.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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`.
|
||||
|
||||
|
||||
@ -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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
!!! 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.
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
!!! 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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:
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
!!! 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.
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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`.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
## 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`.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
!!! 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.
|
||||
|
||||
@ -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
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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`.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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/)
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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`.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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 `/<page-id>/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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
## 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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`.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
!!! 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.
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
### 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`.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
!!! 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.
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
!!! 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.
|
||||
|
||||
@ -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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
## 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.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
!!! 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.
|
||||
|
||||
@ -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
|
||||
@ -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:
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
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:
|
||||
|
||||
|
||||
|
||||
And here's the result of adding the record to the Grist table:
|
||||
|
||||
|
||||
|
||||
### 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':
|
||||
|
||||
|
||||
|
||||
### 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:
|
||||
|
||||
|
||||
|
||||
The result is that the Name in the first record changed from 'Grist' to 'Grist Labs':
|
||||
|
||||
|
||||
|
||||
## 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.
|
||||
@ -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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
|
||||
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user