← All N8N workflows
Automation & utilitiesCodeExecute CommandExtract From FileFormForm Trigger

Credentials Transfer

Configured with Execute Command, Extract From File, Form, Form Trigger, and additional nodes. Review the connections and setup before adapting this template.

Workflow preview
IntegrationSuccessFormIntegrationErrorFormWeb / APICreate CredentialHTTP RequestCodeGet Instance NamesCodeTransformSettingsEdit FieldsCodeExport CredentialsExecute CommandFiles / mediaGet Credentials DataRead Write FileTransformBinary to JSONExtract From FileCodeGet Credential NamesCodeIntegrationChoose InstanceFormIntegrationChoose CredentialFormCodePrepare Request DataCodeTriggerOn form submissionForm Trigger

Node categories in this workflow

  • Integration
  • Web / API
  • Code
  • Transform
  • Files / media
  • Trigger

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
SuccessIntegrationFormcompletion
ErrorIntegrationFormcompletion
Create CredentialWeb / APIHTTP RequestPOST
Get Instance NamesCodeCodeSee node parameters
SettingsTransformEdit FieldsSee node parameters
Export CredentialsCodeExecute CommandSee node parameters
Get Credentials DataFiles / mediaRead Write FileSee node parameters
Binary to JSONTransformExtract From FilefromJson
Get Credential NamesCodeCodeSee node parameters
Choose InstanceIntegrationFormSee node parameters
Choose CredentialIntegrationFormSee node parameters
Prepare Request DataCodeCodeSee node parameters
On form submissionTriggerForm TriggerSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

None declared. HTTP requests and Code nodes may still need configuration.

Workflow notes

Setup instances

Setup instances

Each instnce requires a name, apiKey and baseURL

Instances config example

Instances config example

[
  {
    "name": "n8n-test",
    "apiKey": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
    "baseUrl": "https://n8n-test.example.com/api/v1"
  },
  {
    ...
  }
]
Sticky Note7

A form with no input fields initiates the process. Consider securing the form using Basic Auth.

Sticky Note8

Credentials are being fetched using the cmd tools, since there is no API endpoint available for this. The data is then converted into a JSON object.

Sticky Note9

A list of the instance names is being extracted from the settings and used as dynamic options for the dropdown in a new form page.

Sticky Note10

A list of the credential names is being extracted from the settings and used as dynamic options for the dropdown in a new form page.

Sticky Note11

Based on the selections made by the user, the necessary data is being provided.

Sticky Note12

The credential data is being transferred to the selected instance based using dynamic authentication

Sticky Note13

Display a confirmation/error message to the user

Credentials Transfer

Credentials Transfer

Purpose and structure

This folder contains the Credentials Transfer workflow. Its executable nodes use code, executeCommand, extractFromFile, form, formTrigger, httpRequest, readWriteFile, set. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

On form submission

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/1984_Code_Executecommand_Automation_Webhook.json MIT; preserve source notices.

More in Automation & utilities