Build production-ready user authentication with Airtable and JWT
This n8n workflow provides a comprehensive solution for user authentication and management, leveraging Airtable as the backend database. It includes flows for user sign-up and login, aswell as the sample crud operations retrieving user details, and updating user information.
Youtube Video of me explaining the flow: https://www.youtube.com/watch?v=gKcGfyq3dPM
How it Works
User Sign-Up Flow
- Receives POST request: A webhook listens for POST requests containing new user details (email, first name, last name, password).
- Checks for existing email: The workflow queries Airtable to see if the submitted email already exists.
- Handles email in use: If the email is found, it responds with
{"response": "email in use"}. - Creates new user: If the email is unique, the password is SHA256 hashed (Base64 encoded), and the user's information (including the hashed password) is stored in Airtable. A successful response of
{"response": "success"}is then sent.
User Login Flow
- Receives POST request: A webhook listens for POST requests with user email and password for login.
- Verifies user existence: It checks Airtable for a user with the provided email. If no user is found, it responds with a failure message (
"wrong email"). - Compares passwords: If a user is found, the submitted password is hashed (SHA256, Base64 encoded) and compared with the stored hashed password in Airtable.
- Responds with JWT or error: If passwords match, a JWT token containing the user's ID and email is issued. If they don't match, a
"wrong password"response is sent.
Flows for a Logged-In User
These flows require a JWT-authenticated request.
-
Get User Details:
- Webhook (GET): Receives a JWT-authenticated request.
- Airtable (Read): Fetches the current user’s record using the
jwtPayload.id. - Set Node ("Specify Current Details"): Maps fields like "First Name," "Last Name," "Email," and "Date" from Airtable to a standard output format.
-
Update User Details:
- Webhook (POST): Receives updated user data (email, name, password).
- Airtable (Upsert): Updates the record matching
jwtPayload.idusing the submitted fields. - Set Node ("Specify New Details"): Outputs the updated data in a standard format.
Set Up Steps (Approx. 5 Minutes)
Step 1: Set up your Airtable Base and Table
You'll need an Airtable Base and a table to store your user data. Ensure your table has at least the following columns:
- Email (Single Line Text)
- First Name (Single Line Text)
- Last Name (Single Line Text)
- Password (Single Line Text - this will store the hashed password)
- Date (Date - optional, for user sign-up date)
Step 2: Obtain an Airtable Personal Access Token
- Go to the Airtable website and log in to your account.
- Navigate to your personal access token page (usually found under your developer settings or by searching for "personal access tokens").
- Click "Create new token."
- Give your token a name (e.g., "n8n User Management").
- Grant necessary permissions:
- Scope:
data.records:read,data.records:writefor the specific base you will be using. - Base: Select the Airtable base where your user management table resides.
- Scope:
- Generate the token and copy it immediately. You won't be able to see it again. Store it securely.
Step 3: Create a JWT Auth Credential in n8n
- In your n8n instance, go to "Credentials" (usually found in the left-hand sidebar).
- Click "New Credential" and search for "JWT Auth".
- Give the credential a name (e.g., "UserAuthJWT").
- For the "Signing Secret," enter a strong, random string of characters. This secret will be used to sign and verify your JWT tokens. Keep this secret highly confidential.
- Save the credential.
Customization Options
This workflow is designed to be highly adaptable:
- Database Integration: Easily switch from Airtable to other databases like PostgreSQL, MySQL, MongoDB, or even Google Sheets by replacing the Airtable nodes with the appropriate database nodes in n8n.
- Authentication Methods: Extend the authentication to include multi-factor authentication (MFA), social logins (Google, Facebook), or integrate with existing identity providers (IdP) by adding additional nodes.
- User Profile Fields: Add or remove user profile fields (e.g., phone number, address, user roles) by adjusting the Airtable table columns and the Set nodes in the workflow.
- Notification System: Integrate notification systems (e.g., email, SMS) for events like new user sign-ups, password resets, or account changes.
- Admin Panel: Build an admin panel using n8n to manage users directly, including functionalities for adding, deleting, or updating user records, and resetting passwords.
This workflow provides a solid foundation for building robust user management systems, adaptable to a wide range of applications and security requirements.
Need Assistance or Customization?
Do you have specific integrations in mind, or are you looking to add more user management features to this workflow?
If you need help setting this up, or want to adapt it for a unique use case, don't hesitate to reach out! You can contact me directly at nanabrownsnr@gmail.com. I'd be glad to assist you.
Build Production-Ready User Authentication with Airtable and JWT
This n8n workflow provides a robust and scalable solution for user authentication, leveraging Airtable as a user database and JSON Web Tokens (JWT) for secure session management. It simplifies the process of verifying user credentials and issuing JWTs, making it ideal for building secure backend services or APIs.
What it does
This workflow automates the following steps:
- Listens for Authentication Requests: A Webhook triggers the workflow, expecting user credentials (e.g., email and password) in the incoming request.
- Fetches User Data from Airtable: It queries an Airtable base to retrieve user information based on the provided credentials.
- Validates User Credentials: An If node checks if a user with the given credentials exists in Airtable.
- Generates JWT (if valid): If the credentials are valid, a JSON Web Token (JWT) is generated using the Crypto node, containing relevant user information.
- Responds to Webhook:
- Success: If authentication is successful, the workflow responds to the webhook with the generated JWT.
- Failure: If authentication fails (e.g., invalid credentials), it responds with an appropriate error message and status code.
- Prepares Response: An "Edit Fields" (Set) node is used to format the output data before responding to the webhook, ensuring a consistent API response.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Airtable Account: An Airtable account with a base configured to store user data (e.g.,
userstable withemailandpasswordfields). - Airtable API Key: An Airtable API key configured as a credential in n8n.
- JWT Secret: A secret key for signing and verifying JWTs, configured within the Crypto node.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Airtable Credentials:
- Click on the "Airtable" node.
- Select or create an Airtable credential. You'll need your Airtable API Key.
- Specify the Base ID and Table Name where your user data is stored.
- Configure Webhook:
- The "Webhook" node will automatically generate a unique URL. This is the endpoint you will send authentication requests to.
- Ensure the Webhook method is set to
POSTand the response mode isRespond to Webhook.
- Configure Crypto Node (JWT Generation):
- Click on the "Crypto" node.
- Set the "Operation" to
Sign. - Choose
HS256as the algorithm (or another suitable algorithm). - Provide a strong, secret key for signing the JWT. This key should be stored securely (e.g., using n8n environment variables).
- Define the payload for your JWT (e.g., user ID, email).
- Configure If Node:
- The "If" node is responsible for checking if the user exists and the password matches. You will need to configure its conditions to compare the incoming password with the one retrieved from Airtable.
- Activate the Workflow: Once configured, activate the workflow in n8n.
You can now send POST requests to the Webhook URL with user credentials to authenticate users and receive a JWT in response.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte