Back to Catalog

Automate JotForm submissions via HTTP without API keys

moosamoosa
305 views
2/3/2026
Official Page

This guide explains how to send form data from n8n to a JotForm form submission endpoint using the HTTP Request node. It avoids the need for API keys and works with standard multipart/form-data.


πŸ“Œ Overview

With this workflow, you can automatically submit data from any source (Google Sheets, databases, webhooks, etc.) directly into JotForm.

βœ… Useful for:

  • Pushing information into a form without manual entry.
  • Avoiding API authentication.
  • Syncing external data into JotForm.

πŸ›  Requirements

  • A JotForm account.
  • An existing JotForm form.
  • Access to the form’s direct link.
  • Basic understanding of JotForm’s field naming convention.

βš™οΈ Setup Instructions

1. Get the JotForm Submission URL

  1. Open your form in JotForm.
  2. Go to Publish β†’ Quick Share β†’ Copy Link. Example form URL: sample form
  3. Convert it into a submission endpoint by replacing form with submit: Example: submit url

2. Identify Field Names

Each JotForm field has a unique identifier like q3_name[first] or q4_email.

Steps to find them:

  • Right-click a field in your published form β†’ choose Inspect.
  • Locate the name attribute in the <input> tag.
  • Copy those values into the HTTP Request node in n8n.

Example mappings:

  • First Name β†’ q3_name[first]
  • Last Name β†’ q3_name[last]
  • Email β†’ q4_email

3. Configure HTTP Request Node in n8n

  • Method: POST
  • URL: Your JotForm submission URL (from Step 1).
  • Content Type: multipart/form-data
  • Body Parameters: Add field names and values.

Example Body Parameters:

{
  "q3_name[first]": "John",
  "q3_name[last]": "Doe",
  "q4_email": "john.doe@example.com"
}

4. Test the Workflow

  1. Trigger the workflow (manually or with a trigger node).
  2. Submit test data.
  3. Check JotForm β†’ Submissions to confirm the entry appears.

πŸš€ Use Cases

  • Automating lead capture from CRMs or websites into JotForm.
  • Syncing data from Google Sheets, Airtable, or databases.
  • Eliminating manual data entry when collecting responses.

πŸŽ› Customization Tips

  • Replace placeholder values (John, Doe, john.doe@example.com) with dynamic values.
  • Add more fields by following the same naming convention.
  • Use n8n expressions ({{$json.fieldName}}) to pass values dynamically.

HTTP Request Workflow

This n8n workflow demonstrates a basic usage of the HTTP Request node, a versatile tool for interacting with almost any web service or API. It serves as a foundational example for making external HTTP calls within your n8n automations.

What it does

This workflow contains:

  1. An HTTP Request Node: This node is pre-configured to make an HTTP request. While its specific target URL and method are not defined in this JSON, it represents the core functionality of sending data to or retrieving data from an external endpoint.
  2. A Sticky Note: A simple note to provide context or instructions within the workflow.

Prerequisites/Requirements

  • An n8n instance (cloud or self-hosted).
  • No external API keys or accounts are strictly required for this specific workflow as presented, but you would need to configure the HTTP Request node with a target URL and any necessary authentication or data for a functional use case.

Setup/Usage

  1. Import the workflow: Copy the JSON code and import it into your n8n instance.
  2. Configure the HTTP Request node:
    • Double-click the "HTTP Request" node.
    • In the node settings, specify the URL you wish to send a request to.
    • Select the appropriate HTTP Method (e.g., GET, POST, PUT, DELETE).
    • Add any necessary Headers, Query Parameters, or Body Content depending on the API you are interacting with.
    • If the API requires authentication, configure it under the Authentication section.
  3. Activate the workflow: Once configured, activate the workflow to enable it to run.
  4. Execute the workflow: You can manually execute the workflow by clicking "Execute Workflow" in the n8n editor, or it can be triggered by other nodes (e.g., a Webhook, Cron, or another application's trigger) if integrated into a larger automation.

Related Templates

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use β€” Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➀ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

πŸ“Š Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. πŸš€πŸ“šπŸ’¬ What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. πŸ“¦ Step 3: Logs release data into Google Sheets for record-keeping and analysis. πŸ“Š Step 4: Retrieves FAQ or documentation data from Notion. πŸ“š Step 5: Merges GitHub and Notion data to calculate documentation drift. πŸ” Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. πŸ”” Key Benefits βœ… Keeps SDK documentation aligned with product releases βœ… Prevents outdated information from reaching users βœ… Provides centralized release tracking in Google Sheets βœ… Sends real-time Slack alerts for overdue updates βœ… Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31

Automate Gmail responses with GPT and human-in-the-loop verification

Try It Out! This n8n template uses AI to automatically respond to your Gmail inbox by drafting response for your approval via email. How it works Gmail Trigger monitors your inbox for new emails AI Analysis determines if a response is needed based on your criteria Draft Generation creates contextually appropriate replies using your business information Human Approval sends you the draft for review before sending Auto-Send replies automatically once approved Setup Connect your Gmail account to the Gmail Trigger node Update the "Your Information" node with: Entity name and description Approval email address Resource guide (FAQs, policies, key info) Response guidelines (tone, style, formatting preferences) Configure your LLM provider (OpenAI, Claude, Gemini, etc.) with API credentials Test with a sample email Requirements n8n instance (self-hosted or cloud) Gmail account with API access LLM provider API key Need Help? Email Nick @ nick@tropicflare.com

Nick CanfieldBy Nick Canfield
88