TOTP VALIDATION (WITHOUT CREATING CREDENTIAL)
Configured with Code, If, Manual Trigger, Edit Fields. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Code
- Routing
- Transform
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.
| Node | Category | Type | Operation |
|---|---|---|---|
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| TOTP VALIDATION | Code | Code | See node parameters |
| IF CODE IS VALID | Routing | If | See node parameters |
| EXAMPLE FIELDS | Transform | Edit Fields | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- 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
TOTP Validation with Function Node
TOTP Validation with Function Node
This template allows you to verify if a 6-digit TOTP code is valid using the corresponding TOTP secret. It can be used in an authentication system.
Example usage:
- You retrieve the user's TOTP secret from a database, then you want to verify if the 2FA code provided by the user is valid.
Setup Guidelines
You only need the "TOTP VALIDATION" node. You will need to modify lines 39 and 40 of the "TOTP VALIDATION" node with the correct values for your specific context.
Testing the Template
You can define a sample secret and code in the "EXAMPLE FIELDS" node below, then click "Test Workflow". If the code is valid for the provided secret, the flow will proceed to the "true" branch of the "IF CODE IS VALID" node. Otherwise, it will go to the "false" branch.
TOTP VALIDATION (WITHOUT CREATING CREDENTIAL)
TOTP VALIDATION (WITHOUT CREATING CREDENTIAL)
Purpose and structure
This folder contains the TOTP VALIDATION (WITHOUT CREATING CREDENTIAL) workflow. Its executable nodes use code, if, manualTrigger, 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
When clicking ‘Test workflow’
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/Manual/0558_Manual_Stickynote_Automation_Triggered.json MIT; preserve source notices.