by getBible
Overview The Get Bible Query Workflow is a modular and self-standing workflow designed to retrieve scriptures dynamically based on structured input. It serves as an intermediary layer that extracts references, queries the GetBible API, and returns scriptures in a standardized JSON format. This workflow is fully prepared for integration—simply call it from another workflow with the required JSON input, and it will return the requested scripture data. Who Is This For? This workflow is ideal for developers, Bible study apps, research tools, and dynamic scripture-based projects that need seamless access to scriptural content without direct API interaction. ✅ Use Cases: Bible Study Apps** → Embed scripture retrieval functionality. Research & Theology Tools** → Fetch structured verse data. Dynamic Content Generation** → Integrate real-time scripture references. Sermon Preparation** → Automate scripture lookups. How It Works Trigger Workflow → This workflow is designed to be called from another workflow with a structured JSON input. Receive Input → Accepts a JSON object containing references, translation, and API version. Extract References → Parses single verses, comma-separated lists, and ranged passages. Query API → Sends structured requests to the GetBible API. Format Response → Returns structured JSON output, maintaining API response consistency. JSON Input Structure References** → Should include the book name, chapter, and verse(s). Multiple Verses** → Separated by commas (e.g., John 3:16,18). Verse Ranges** → Defined with a dash (e.g., John 3:16-18). Translation** → Choose from the supported translations. API Version** → Currently supports v2. Example JSON Input { "references": [ "1 John 3:16", "Jn 3:16", "James 3:16", "Rom 3:16" ], "translation": "kjv", "version": "v2" } Example API Response { "result": { "kjv_62_3": { "translation": "King James Version", "abbreviation": "kjv", "book_name": "1 John", "chapter": 3, "ref": ["1 John 3:16"], "verses": [ { "chapter": 3, "verse": 16, "name": "1 John 3:16", "text": "Hereby perceive we the love of God, because he laid down his life for us: and we ought to lay down our lives for the brethren." } ] } } } 💡 Fully structured and formatted response – ready for seamless integration. Integration and Usage The GetBible Query Workflow is designed for immediate use. Simply call it from another workflow and pass the appropriate JSON object as input, and it will return the requested scripture passages. ✔️ No additional configuration is required. ✔️ Designed for fast, reliable, and structured scripture retrieval. ✔️ Fully compatible with GetBible API responses. Why Use This Workflow? ✔️ Fast & Reliable → Direct API integration for efficient queries. ✔️ Flexible Queries → Supports single, multi-verse, and ranged requests. ✔️ Agent-Compatible → Easily integrates into automated workflows. ✔️ No Code Needed → Just configure the JSON input and run the workflow. Next Steps 🔗 API Support 📖 API Documentation 💬 Need help? Join the community for support! 🚀
by Preston Zeller
How It Works This workflow automates the real estate lead qualification process by leveraging property data from BatchData. The automation follows these steps: When a new lead is received through your CRM webhook, the workflow captures their address information It then makes an API call to BatchData to retrieve comprehensive property details A sophisticated scoring algorithm evaluates the lead based on property characteristics like: Property value (higher values earn more points) Square footage (larger properties score higher) Property age (newer constructions score higher) Investment status (non-owner occupied properties earn bonus points) Lot size (larger lots receive additional score) Leads are automatically classified into categories (high-value, qualified, potential, or unqualified) The workflow updates your CRM with enriched property data and qualification scores High-value leads trigger immediate follow-up tasks for your team Notifications are sent to your preferred channel (Slack in this example) The entire process happens within seconds of receiving a new lead, ensuring your sales team can prioritize the most valuable opportunities immediately.. Who It's For This workflow is perfect for: Real estate agents and brokers looking to prioritize high-value property leads Mortgage lenders who need to qualify borrowers based on property assets Home service providers (renovators, contractors, solar installers) targeting specific property types Property investors seeking specific investment opportunities Real estate marketers who want to segment audiences by property value Home insurance agents qualifying leads based on property characteristics Any business that bases lead qualification on property details will benefit from this automated qualification system. About BatchData BatchData is a comprehensive property data provider that offers detailed information about residential and commercial properties across the United States. Their API provides: Property valuation and estimates Ownership information Property characteristics (size, age, bedrooms, bathrooms) Tax assessment data Transaction history Occupancy status (owner-occupied vs. investment) Lot details and dimensions By integrating BatchData with your lead management process, you can automatically verify and enrich leads with accurate property information, enabling more intelligent lead scoring and routing based on actual property characteristics rather than just contact information. This workflow demonstrates how to leverage BatchData's property API to transform your lead qualification process from manual research into an automated, data-driven system that ensures high-value leads receive immediate attention.
by Jonathan
This workflow automatically posts a message in Slack when a new invoice is uploaded in Stripe, and it updates the fields in the HubSpot CRM. Prerequisites A Slack account and credentials A HubSpot account and credentials A Stripe account and credentials Nodes Stripe Trigger node triggers the workflow when a new invoice is uploaded. IF nodes filter the invoices that don't have a PO number and if there is no deal for the PO. HubSpot nodes retrieve deals with the specific PO number and update the deal status to 'paid'. Slack nodes post messages about the deals in a Slack channel.
by Maximiliano Rojas-Delgado
Turn Your Ideas into Videos—Right from Google Sheets! This workflow helps you make cool 8-second videos using Fal.AI and Veo 3, just by typing your idea into a Google Sheet. You can even choose if you want your video to have sound or not. It’s super easy—no tech skills needed! Why use this? Just type your idea in a sheet—no fancy tools or uploads. Get a video link back in the same sheet. Works with or without sound—your choice! How does it work? You write your idea, pick the video shape, and say if you want sound (true or false) in the Google Sheet. n8n reads your idea and asks Fal.AI to make your video. When your video is ready, the link shows up in your sheet. What do you need? A Google account and Google Sheets connected with service account (check this link for reference) A copy of the following Google Spreadsheet: Spreadsheet to copy An OpenAI API key A Fal.AI account with some money in it That’s it! Just add your ideas and let the workflow make the videos for you. Have fun creating! if you have any questions, just contact me at max@nervoai.com
by PretenderX
This template automates sending a DingTalk message on new Azure Dev Ops Pull Request Created Events. It uses a MySQL database to store mappings between Azure users and DingTalk users; so the right users get notified. Set up instructions Define the path value of ReceiveTfsPullRequestCreatedMessage Webhook node of your own, copy the webhook url to create a Azure DevOps ServiceHook that call webhook with Pull Request Created event. In order to configure the LoadDingTalkAccountMap node, you need to create a MySQL table as below: |Name|Type|Length|Key| |-|-|-|-| |TfsAccount|varchar|255| |UserName|varchar|255| |DingTalkMobile|varchar|255| You can customize the Ding Talk message content by editing the BuildDingTalkWebHookData node. Define the URL of SendDingTalkMessageViaWebHook Http Request node as your Ding Talk group chat robot webhook URL. Send test of production message from Azure DevOps to test.
by Yaron Been
Description This workflow automatically generates Facebook ad headlines for your product using OpenAI and evaluates their quality using custom AI-generated criteria. It ensures you get high‑quality, scroll‑stopping headlines without needing a copywriter. Overview This workflow captures a product description via a form, generates a Facebook ad headline, invents a scoring rubric, evaluates the headline against it, and optionally loops for revisions — all autonomously. Ideal for marketers and media buyers looking to scale creative testing. Tools Used n8n**: The automation platform that powers and orchestrates the entire workflow. OpenAI**: Used for headline generation, scoring criteria creation, and evaluation logic. (Optional)** Google Sheets / Notion / Email: For logging approved headlines or sharing results. How to Install Import the Workflow: Download the .json file and import it into your n8n instance. Connect OpenAI: Add your OpenAI credentials to the GPT nodes. Customize the Prompt (optional): Tweak the system prompt inside the Set_PromptForHeadline node. Add Output Handling (optional): Connect the “NO” path in the If_NeedMoreIterations node to Google Sheets, Slack, etc. (Optional) Add loop limits or storage logic to manage iterations or save results. Use Cases Media Buyers**: Generate and test hooks at scale with no creative bottlenecks. Solo Marketers**: Get high-converting headlines even without a copywriter. Agencies**: Streamline copy testing and evaluation in client campaigns. Startup Teams**: Automate creative generation during product launches or A/B tests. Connect with Me Website**: https://www.nofluff.online YouTube**: https://www.youtube.com/@YaronBeen/videos LinkedIn**: https://www.linkedin.com/in/yaronbeen/ Hashtags #n8n #openai #automation #copywriting #facebookads #headlines #aicopy #promptengineering #marketingautomation #nocode #llm #creativeautomation #mediabuying #adtesting #adcreative #marketingtools #digitalmarketing #copytesting #scalablecreative #chatgpt #adhooks #growthmarketing #automatedworkflows #aiworkflow #creativeops #marketingops #growthtools
by dataplusminus+-
🎯 Project Purpose This project automates the process of collecting and managing new leads submitted through a web form. It eliminates the need for manual data entry and ensures that each lead is: Properly recorded and time-stamped in a structured format Automatically communicated to the sales or support team Ready for follow-up, with a reminder system in place It’s a lightweight but effective solution suitable for freelancers, small teams, and growing businesses that want to streamline their lead intake process. 🛠️ Tools & Technologies Used Google Forms / Web Form** – Frontend for capturing leads Google Sheets** – Central database for storing lead information n8n** – Automation platform that connects and coordinates all services Gmail** – Handles email notifications for new leads Slack* *(optional) – Provides instant team notifications Date & Time nodes** – Tracks and manages lead response timing Conditional (IF) nodes** – Filters out duplicate and incomplete entries 🔄 Workflow Overview ✨ Key Features ✅ No-code integration using n8n ✅ Instant alerts via Gmail and/or Slack ✅ Google Sheets as an easily accessible backend ✅ Modular design — easy to expand with CRM tools (like HubSpot) ✅ Clean JSON structure and logic, beginner-friendly 📈 Possible Improvements Add email validation via external API (e.g., NeverBounce, Hunter) Integrate with a CRM for deeper automation Add lead scoring based on answers Include automatic follow-up emails after X days Schedule weekly summary reports via email 🧑🏻💻 Creator Information Developed by: Adem Tasin Adem T. 🌐 Website: Dataplusminus+- 📧 Email:dataplusminuss@gmail.com 💼 LinkedIn: Adem Tasin
by Oneclick AI Squad
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. This automated n8n workflow streamlines the process of screening CVs and validating candidate information using AI and email parsing. The system listens for new emails with CV attachments, extracts and processes the data, and either saves valid CVs to a target directory or notifies HR of invalid submissions. Good to Know The workflow improves efficiency by automating CV screening and validation. Ensures only CVs with essential fields (e.g., name, email, skills) are processed further. Email notifications alert HR to incomplete or invalid CVs for timely follow-up. The system pauses until all CV data is fully loaded to avoid processing errors. How It Works Trigger on New CV Email - Detects new emails with CV attachments. Extract Text from PDF CV - Parses content from attached PDF files. Ensure All CV Data Loaded - Waits until all data is ready for processing. Parse & Structure CV Information - Extracts structured details like name, skills, and experience using AI or custom logic. Check CV for Required Fields - Verifies the presence of essential fields (e.g., name, email, skills). Save Valid CV to Folder - Stores successfully validated CVs into a target directory. Notify HR of Invalid CV - Sends an email alert for incomplete or invalid CVs. Data Sources The workflow processes data from email attachments: CV PDF Files** - Contains candidate information in PDF format. How to Use Import the workflow into n8n. Configure email account credentials for monitoring new CV emails. Set up a target directory for storing validated CVs. Test with sample CV PDFs to verify extraction and validation. Adjust AI or custom logic based on specific required fields. Monitor email notifications for invalid CVs and refine the process as needed. Requirements Email account access with IMAP/POP3 support. PDF parsing capabilities (e.g., OCR or text extraction tools). AI or custom logic for data extraction and validation. A target directory for storing validated CVs. Customizing This Workflow Modify the "Check CV for Required Fields" node to include additional required fields (e.g., education, certifications). Adjust the email notification format to include more details about invalid CVs. Integrate with HR software for seamless candidate tracking. Details The workflow ensures efficient CV screening by automating repetitive tasks. Notifications help maintain a high-quality candidate pool by addressing issues early.
by Mutasem
Use case Automatically create todo items in Todoist every morning. This workflow has two flows At 5am, delete any uncompleted tasks every morning At 5:10 am, copy all template tasks into Inbox In each template task, set the due dates and days to add the task. You can do that like this days:mon,tues; due:8pm which will add the task every Monday and Tuesday and make it due at 8pm. How to setup Add Todoist creds Create a template list to copy from in Todoist. Add days and due times on each task as necessary. Set the projects to copy from and to write to in each Todoist node
by Harshil Agrawal
This workflow analyzes the sentiments of the feedback provided by users and sends them to a Mattermost channel. Typeform Trigger node: Whenever a user submits a response to the Typeform, the Typeform Trigger node will trigger the workflow. The node returns the response that the user has submitted in the form. Google Cloud Natural Language node: This node analyses the sentiment of the response the user has provided and gives a score. IF node: The IF node uses the score provided by the Google Cloud Natural Language node and checks if the score is negative (smaller than 0). If the score is negative we get the result as True, otherwise False. Mattermost node: If the score is negative, the IF node returns true and the true branch of the IF node is executed. We connect the Mattermost node with the true branch of the IF node. Whenever the score of the sentiment analysis is negative, the node gets executed and a message is posted on a channel in Mattermost. NoOp: This node here is optional, as the absence of this node won't make a difference to the functioning of the workflow. This workflow can be used by Product Managers to analyze the feedback of the product. The workflow can also be used by HR to analyze employee feedback. You can even use this node for sentiment analysis of Tweets. To perform a sentiment analysis of Tweets, replace the Typeform Trigger node with the Twitter node. Note:* You will need a Trigger node or Start node to start the workflow. Instead of posting a message on Mattermost, you can save the results in a database or a Google Sheet, or Airtable. Replace the Mattermost node with (or add after the Mattermost node) the node of your choice to add the result to your database. You can learn to build this workflow on the documentation page of the Google Cloud Natural Language node.
by Yaron Been
This workflow provides automated access to the Fire Part Crafter AI model through the Replicate API. It saves you time by eliminating the need to manually interact with AI models and provides a seamless integration for image generation tasks within your n8n automation workflows. Overview This workflow automatically handles the complete image generation process using the Fire Part Crafter model. It manages API authentication, parameter configuration, request processing, and result retrieval with built-in error handling and retry logic for reliable automation. Model Description: PartCrafter is a structured 3D mesh generation model that creates multiple parts and objects from a single RGB image. Key Capabilities High-quality image generation from text prompts** Advanced AI-powered visual content creation** Customizable image parameters and styles** Tools Used n8n**: The automation platform that orchestrates the workflow Replicate API**: Access to the Fire/part-crafter AI model Fire Part Crafter**: The core AI model for image generation Built-in Error Handling**: Automatic retry logic and comprehensive error management How to Install Import the Workflow: Download the .json file and import it into your n8n instance Configure Replicate API: Add your Replicate API token to the 'Set API Token' node Customize Parameters: Adjust the model parameters in the 'Set Image Parameters' node Test the Workflow: Run the workflow with your desired inputs Integrate: Connect this workflow to your existing automation pipelines Use Cases Content Creation**: Generate unique images for blogs, social media, and marketing materials Design Prototyping**: Create visual concepts and mockups for design projects Art & Creativity**: Produce artistic images for personal or commercial use Marketing Materials**: Generate eye-catching visuals for campaigns and advertisements Connect with Me Website**: https://www.nofluff.online YouTube**: https://www.youtube.com/@YaronBeen/videos LinkedIn**: https://www.linkedin.com/in/yaronbeen/ Get Replicate API**: https://replicate.com (Sign up to access powerful AI models) #n8n #automation #ai #replicate #aiautomation #workflow #nocode #imagegeneration #aiart #texttoimage #visualcontent #aiimages #generativeart #machinelearning #artificialintelligence #aitools #automation #digitalart #contentcreation #productivity #innovation
by Eduard
Are you a visual thinker working with n8n? 🎨 View and understand workflow structures at a glance with this template! Built with mermaid.js, Bootstrap 5 and AXAJ to create an interactive web page displaying n8n workflows as flowcharts. 🌟 Perfect for documentation, presentations, or just getting a clearer picture of your automation processes. Need customization help? Reach out to Eduard! Benefits 📊 Instant workflow visualization 📱 Responsive design 🔗 Direct links to n8n workflows 🧩 Special shapes for different node types 🚫 Disabled node indication 🔒 No external dependencies – just paste the workflow and call the webhook 🛠️ Easily customizable – enhance the JS script or add custom styling ⚠️ Important note for cloud users ⚠️ Since the cloud version doesn't support environmental variables, please make the following changes in the CONFIG node: Update the instance_url variable: Enter your n8n URL instead of {{$env["N8N_PROTOCOL"]}}://{{$env["N8N_HOST"]}} Change the webhook_path to simply "webhook" instead of {{$env["N8N_ENDPOINT_WEBHOOK"] || "webhook"}} 🌟 Examples Multiple flowcharts on a single page: Several shapes for different nodes: Langchain nodes with special connections styling: