n8n Teller Credential

Custom credential for n8n that encapsulates Teller's mutual TLS authentication scheme. It lets any n8n node that relies on HTTP requests (for example the built-in HTTP Request node) connect to the Teller Banking API using an Application ID, auth code, and the Teller-issued client certificate pair.

Features

• Credential stores the Teller Application ID, access token, and mutual-TLS certificates securely, with environment selection (Production, Sandbox, or custom URL).
• Node exposes a simple List Accounts operation that calls Teller’s /accounts endpoint using the credential.
• Optional CA bundle field for custom trust chains.
• Automatically injects mutual TLS options and HTTP basic authentication into every outgoing request that uses the credential or node.
• Built-in credential test against /accounts.

Installation

1. Copy this repository into your n8n community nodes directory (for example ~/.n8n/custom/).

2. Install dependencies and build the project:

   npm install
   npm run build

3. Restart n8n so it can load the new credential package.

Usage

1. In the n8n UI open Credentials → Create Credential and choose Teller API.
2. Pick the Teller environment (Production, Sandbox, or Custom) and paste the following values obtained from the Teller developer dashboard:
   • Application ID
   • Access Token (value begins with token_)
   • Certificate (PEM) – raw contents of certificate.pem
   • Private Key (PEM) – raw contents of private-key.pem
   • CA Bundle (Optional) – only required if Teller supplied a custom CA chain
3. Save the credential and run the built-in test to verify connectivity.
4. Use it from the bundled Teller API node or any HTTP Request node that supports credential selection.
   • Sandbox users can leave the default credentials test in place; the credential will automatically call https://api-sandbox.teller.io when the sandbox environment is selected.

Development

• npm run dev watches and rebuilds on change.
• npm run build produces the compiled output in dist/ for n8n to consume.

Notes

• Teller requires mutually authenticated TLS on every API request. Ensure the certificate and private key stay in PEM format when pasted into the credential fields.
• Requests default to https://api.teller.io. Override the base URL in individual nodes if you need to target Teller's sandbox endpoints.