This article provides a complete, practical walkthrough of the Manual Totp Automation Triggered n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:  
   How to Generate TOTP Codes in n8n: A Step-by-Step Guide 🔐  
   
   Meta Description:  
   Learn how to securely generate Time-Based One-Time Passwords (TOTP) using n8n’s built-in functionality. This guide walks you through a simple two-node workflow setup for TOTP code generation, ideal for 2FA and secure automation.
   
   Keywords:  
   n8n TOTP, TOTP automation, two-factor authentication n8n, n8n security, generate OTP n8n, automation with TOTP, n8n tutorial, n8n workflow example, TOTP generator n8n, create secure workflows n8n  
   
   Third-Party APIs Used:  
   - TOTP account (secured via n8n credential manager; specific implementation detail not provided)
   
   Article:
   
   Complete Guide to Setting Up and Generating TOTP Codes in n8n 🔐
   
   In today's cybersecurity-conscious landscape, Time-Based One-Time Passwords (TOTP) are more important than ever before. Whether you’re implementing two-factor authentication (2FA) or securing an automation step with an expiring access code, integrating TOTP into your automation workflows is a smart and secure decision.
   
   In this article, we’ll cover how to generate TOTP codes in n8n using a simple but powerful two-node workflow. By the end, you'll be able to securely generate TOTP tokens on demand using an interactive test or execution trigger. This is especially beneficial when automating secure API calls, logins, or any operation that requires time-sensitive validation.
   
   What is TOTP?
   
   TOTP stands for Time-Based One-Time Password. It's a type of two-factor authentication method in which a code is generated that is valid for a short interval – usually 30 seconds. Because these codes expire quickly and change constantly, TOTP is a popular method for securing systems.
   
   TOTP is based on a shared secret between client and server and the current time. Popular authenticator apps like Google Authenticator and Authy use this method to secure logins.
   
   Overview of the Workflow
   
   This n8n workflow is composed of two core nodes:
   
   1. Manual Trigger
   2. TOTP Node
   
   Let’s break down each component.
   
   Step 1: Manual Trigger Node
   
   The workflow starts with the "Manual Trigger" node, which activates the workflow when you click “Execute Workflow” in the n8n editor. This node is ideal for testing and development purposes because it allows you to manually run your workflow and immediately see results.
   
   Node Details:
   - Name: "When clicking ‘Test workflow’"
   - Type: Manual Trigger
   - ID: 0fe95b9a-be2b-4022-829e-8b6c801e5baf
   
   Why Use Manual Trigger?  
   This allows you to interactively test TOTP code generation without having to wait for scheduled events or external triggers. It serves as a temporary proxy for whatever event might initiate the real workflow in production (e.g., webhook, cron job, or user interaction).
   
   Step 2: TOTP Node
   
   Connected directly to the Manual Trigger is the TOTP (Time-Based One-Time Password) node. This node generates a valid TOTP code based on secure credentials stored within your n8n credentials store. These credentials include a shared secret required to calculate the code.
   
   Node Details:
   - Name: "TOTP"
   - Type: TOTP
   - Credential Used: TOTP account Mars55 (the shared secret is configured here)
   
   When executed, this node fetches the current timestamp, applies the algorithm using the shared secret stored in the credential, and produces a valid TOTP code.
   
   Security Note:  
   The TOTP shared secret is never exposed in the workflow directly. Instead, it is secured using n8n’s encrypted credential system. Always use n8n’s credential manager to securely store any sensitive keys or tokens.
   
   Use Case Scenarios for TOTP in n8n
   
   1. API Authentication  
   Some third-party services require a valid TOTP code for API access. With this workflow, you can automatically generate and inject the latest code into your API requests as part of a larger n8n flow.
   
   2. Platform Login Automation  
   If you’re automating routine logins or health checks that require 2FA, TOTP in n8n can programmatically generate and supply the verification code, enabling full automation of what would normally require manual input.
   
   3. Scheduled Secure Actions  
   You can combine the TOTP node with a Cron node to perform scheduled actions only when a valid TOTP code is available — such as running a secure backup, accessing privileged data, or sending sensitive information.
   
   Customizing Your Workflow
   
   - Replace the Manual Trigger node with other trigger nodes like Webhook or Cron to automate the TOTP code generation.
   - Add follow-up nodes like HTTP Request to use the generated TOTP code in an API call.
   - Combine with condition nodes to perform logic checks based on time, attempts, or workflows’ context.
   
   Best Practices
   
   - Keep your TOTP secret secure — always use n8n’s credential manager.
   - Regularly rotate your shared secrets, and ensure your workflows account for refresh intervals.
   - Ensure your execution environment’s system clock is synchronized — TOTP is time-sensitive.
   
   Final Thoughts
   
   In just two steps, you’ve built a secure, reusable method for generating TOTP codes inside n8n. Although simple, this workflow opens up many powerful security-enhancing use cases: from automating access to privileged APIs, to building web apps that require intermittent authentication.
   
   n8n’s support for TOTP generation combined with its flexible node architecture enables developers and automation engineers to create secure, robust, and scalable authentication-aware workflows — with zero coding required.
   
   If you’re exploring the idea of adding some security spice 🌶️ to your automations, TOTP in n8n is the ingredient you're missing.
   
   Happy automating — securely! 🔐
   
   —  
   Author:  
   Your AI Assistant for Automation & Integration Enthusiasts  
   

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.