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 Complete Step-by-Step Guide 🔐
   
   Meta Description:  
   Learn how to set up and generate TOTP (Time-based One-Time Password) codes with n8n, using a simple workflow. Ideal for adding two-factor authentication to your automation processes.
   
   Keywords:  
   n8n, TOTP, two-factor authentication, 2FA, automation, workflow automation, secure workflows, generate OTP, MFA, n8n tutorial, n8n TOTP node
   
   —
   
   Article:
   
   # How to Generate TOTP Codes in n8n: A Complete Step-by-Step Guide 🔐
   
   In today’s digital world, security is everything—especially when automating repetitive or sensitive tasks. One common way to enhance security for applications and systems is by implementing two-factor authentication (2FA), and n8n, the open-source workflow automation tool, makes it easy to incorporate this into your workflows using Time-based One-Time Passwords (TOTP).
   
   In this article, we’ll walk you through a simple but powerful n8n workflow designed to generate TOTP codes automatically—perfect for scenarios where you need to securely access third-party platforms or APIs. This guide is suitable for both beginners and experienced users looking to boost their automation security.
   
   ---
   
   ## 🧰 What You’ll Need
   
   - An instance of n8n (you can run it locally or use n8n.cloud)
   - Access to a TOTP secret (usually provided by the service you want to authenticate with)
   - n8n credentials configured for TOTP
   - A basic understanding of how workflows work in n8n
   
   ---
   
   ## 🚀 Workflow Overview
   
   The workflow in our example is called:
   
   **Complete Guide to Setting Up and Generating TOTP Codes in n8n 🔐**
   
   It consists of only two nodes, but these are more than enough to generate a functioning TOTP code on demand:
   
   1. Manual Trigger Node  
   2. TOTP Node
   
   Let’s break each component down.
   
   ---
   
   ### 🖱️ Manual Trigger Node
   
   First up is the “Manual Trigger” node. This node, labeled “When clicking ‘Test workflow’,” serves as the entry point for the workflow. It's primarily used for testing and manually executing the workflow from within the n8n editor.
   
   Once you click "Execute Workflow" in the UI, this node activates and passes control to the next node in the sequence.
   
   No additional parameters are needed for this step. Simple, clean, and effective.
   
   ---
   
   ### ⏱️ TOTP Node
   
   The heart of the workflow is the TOTP node. TOTP (Time-based One-Time Password) is an algorithm that generates a new password every 30 seconds. This is the basis for many two-factor authentication systems, like those in Google Authenticator and Authy.
   
   In our workflow, the TOTP node is configured with credentials stored under the name:  
   **TOTP account Mars55**
   
   These credentials contain the TOTP secret necessary to generate authentication codes. Once triggered, the node outputs a valid TOTP code at the moment it's executed.
   
   This TOTP code can then be used as part of an authentication workflow—for example, when calling an API endpoint that requires 2FA.
   
   ---
   
   ## 🛡️ Why Use TOTP in n8n?
   
   TOTP enhances security for any system you interact with. Here are a few practical use cases where this TOTP workflow can be incredibly useful:
   
   - Automating login sequences that require an OTP  
   - Accessing APIs that enforce 2FA measures  
   - Sending TOTP codes as part of a backup alert or monitoring system  
   - Integrating secure gateways into CI/CD pipelines
   
   By integrating TOTP generation directly into an n8n workflow, you eliminate the need for manual code generation—saving you time and increasing the security of your processes.
   
   ---
   
   ## 🌐 3rd-Party APIs Used
   
   Although this workflow doesn't call any external third-party APIs directly, it relies on stored TOTP credentials typically associated with external services or platforms. These could be platforms like:
   
   - Google (for services using 2FA)
   - GitHub Authenticator
   - Amazon AWS (with MFA enabled)
   - Any other platform providing a TOTP authentication secret
   
   So while no external API calls are made in this workflow, the TOTP itself is often used to authenticate API calls to services like these.
   
   ---
   
   ## 🧪 Testing the Workflow
   
   To test the TOTP generation:
   
   1. Open your n8n instance.
   2. Navigate to the workflow editor and create a new workflow.
   3. Add the “Manual Trigger” node.
   4. Add the “TOTP” node and connect it to the trigger node.
   5. Configure the TOTP node with your TOTP credentials (secret key).
   6. Click “Execute Workflow.”
   
   You’ll receive the current TOTP code in the output of the TOTP node.
   
   You can then use this output as input to other nodes—such as an HTTP Request node—to perform authenticated actions automatically.
   
   ---
   
   ## 🧠 Final Thoughts
   
   As automation becomes more integral to modern workflows, secure authentication methods like TOTP are vital. n8n’s TOTP node is a powerful tool that allows you to integrate 2FA directly into your automation pipelines.
   
   Whether you're building admin tools, managing cloud resources, or accessing secure APIs, having the ability to generate TOTP codes directly in your workflows makes n8n a compelling choice for both developers and system admins seeking a low-code solution.
   
   Stay secure, stay automated! 🔐
   
   —
   
   Keywords Recap:  
   n8n, TOTP, two-factor authentication, 2FA, secure workflows, generate OTP, MFA, n8n tutorial, n8n TOTP node
   
   Third-Party APIs Used (Indirectly):  
   - Google services (Authenticator)
   - GitHub
   - AWS
   - Any provider offering TOTP-based 2FA
   
   Happy automating!

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.