From 435e314c91564cd2ab1ef3ca7f27cd59345b2aed Mon Sep 17 00:00:00 2001 From: Deborah Barnard Date: Wed, 18 May 2022 09:32:03 +0100 Subject: [PATCH] rename [skip ci] --- docs/integrations/custom-operations/index.md | 9 --------- .../app-specific-http-credentials.md | 0 docs/integrations/http-credentials/index.md | 9 +++++++++ mkdocs.yml | 6 +++--- 4 files changed, 12 insertions(+), 12 deletions(-) delete mode 100644 docs/integrations/custom-operations/index.md rename docs/integrations/{custom-operations => http-credentials}/app-specific-http-credentials.md (100%) create mode 100644 docs/integrations/http-credentials/index.md diff --git a/docs/integrations/custom-operations/index.md b/docs/integrations/custom-operations/index.md deleted file mode 100644 index 19157cdf3..000000000 --- a/docs/integrations/custom-operations/index.md +++ /dev/null @@ -1,9 +0,0 @@ -# Overview - -n8n supplies hundreds of nodes, allowing you to create workflows that link multiple products. However, some nodes don't include all the possible operations supported by a product's API. You can work around this using the core [HTTP Request](/integrations/core-nodes/n8n-nodes-base.httpRequest/) and [Webhook](/integrations/core-nodes/n8n-nodes-base.webhook/) nodes. - -To support this, n8n provides custom operations: a way to use the HTTP Request node with an existing credential. This avoids complex credentials setups. Creating an HTTP request can require knowledge of different authentication types, and work to set up the appropriate option (such as basic auth, header, or OAuth2.). n8n's custom operations feature avoids this complexity, using [App-specific HTTP credentials](/integrations/custom-operations/app-specific-http-credentials/). - - - - diff --git a/docs/integrations/custom-operations/app-specific-http-credentials.md b/docs/integrations/http-credentials/app-specific-http-credentials.md similarity index 100% rename from docs/integrations/custom-operations/app-specific-http-credentials.md rename to docs/integrations/http-credentials/app-specific-http-credentials.md diff --git a/docs/integrations/http-credentials/index.md b/docs/integrations/http-credentials/index.md new file mode 100644 index 000000000..35b5da5cf --- /dev/null +++ b/docs/integrations/http-credentials/index.md @@ -0,0 +1,9 @@ +# Overview + +n8n supplies hundreds of nodes, allowing you to create workflows that link multiple products. However, some nodes don't include all the possible operations supported by a product's API. You can work around this using the core [HTTP Request](/integrations/core-nodes/n8n-nodes-base.httpRequest/) and [Webhook](/integrations/core-nodes/n8n-nodes-base.webhook/) nodes. + +To support this, n8n provides a way to use the HTTP Request node with either an existing credential, or using n8n's credential creation process. This avoids complex credentials setups. Creating an HTTP request can require knowledge of different authentication types, and work to set up the appropriate option (such as basic auth, header, or OAuth2.). n8n avoids this complexity using [App-specific HTTP credentials](/integrations/custom-operations/app-specific-http-credentials/). + + + + diff --git a/mkdocs.yml b/mkdocs.yml index 4bc1db3bd..3d177bc41 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -114,9 +114,9 @@ nav: - Nodes: integrations/nodes/ - Trigger nodes: integrations/trigger-nodes/ - Credentials: integrations/credentials/ - - Custom operations: - - Overview: integrations/custom-operations/index.md - - App-specific HTTP credentials: integrations/custom-operations/app-specific-http-credentials.md + - HTTP node credentials: + - Overview: integrations/http-credentials/index.md + - App-specific HTTP credentials: integrations/http-credential/app-specific-http-credentials.md - Creating nodes: - Overview: integrations/creating-nodes/index.md - Code-based node building: