Product Introduction: You can create a form on n8n through which you can collect leads from interested user's. You can also verify each user's email address to validate whether it's a valid email to make sure it lands on their inbox(suitable for those who have newletter / want's to send bulk email) The leads with valid email will then get saved as a leads with the relevant field data to gmail, google sheets and discord(through webhook). You can add/remove any integration you feel like. Setup Guide: Create Your Form: Begin by logging into your n8n account and navigating to the workflow editor. You can then customize your form fields to gather relevant information from your prospects, such as name, email address, and any additional data you require. Email Verification: After collecting the lead data, add an Email Verification node to validate each user's email address. This crucial step ensures that only genuine and deliverable email addresses are included in your lead database, maximizing the effectiveness of your outreach efforts. We have used hunter.io service in this, you can change it to any other service you need.
Tags
Discord
Gmail
Google Sheets
HunterRelated workflows
See all Discord→Send Google Sheets data as a message to a Discord channel
This workflow sends a message to a Discord channel when a new row is added or a row is updated in a Google Sheet. The message will send all data rows in the Google Sheet. Prerequisites Discord account and Discord credentials. Google account and Google credentials. How it works Using a code node, we can use the obtained Google Sheet data to create a custom message that will be sent to Discord. The message will be sent to the Discord channel specified in the Discord node. Setup This workflow requires that you set up a Discord webhook and have an existing Google Sheet with data. See how to set up a Discord webhook here.
Get all members of a Discord server with a specific role
Use Case This workflow retrieves all members of a Discord server or guild who have a specific role. Due to limitations in the Discord API, it only returns a limited number of users per call. To overcome this, the workflow uses Google Sheets to track which user we received last to return all Members (of a certain role) from a Discord server in batches of 100 members. Setup Add your Google Sheets and Discord credentials. Create a Google Sheets document that contains ID as a column. We're using this to remember which member we received last. Edit the fields in the setup node Setup: Edit this to get started. You can read up on how to get the Discord IDs via this link. Link to your Discord server in the Discord nodes Activate the workflow Call the production webhook URL in your browser Requirements Admin rights in the Discord server and access to the developer portal of discord Google Sheets Minimum n8n version 1.28.0 Potential Use cases Writing a direct message to all members of a certain role Analysing user growth on Discord regularly Analysing role distributions on Discord regularly Saving new members in a Discord ... Keywords Discord API, Getting all members from Discord via API, Go
Automated Workflow Backup System with Google Drive, Gmail and Discord Alerts'
How it works This workflow automates the backup of all your n8n workflows to a specified Google Drive folder. It operates in two main phases: Orchestration (Scheduled Task): The workflow is initiated by a Schedule Trigger (e.g., daily at 1:30 AM by default). It then uses an n8n API Node to fetch a list of all existing workflows in your n8n instance. A Loop Over Items node processes each fetched workflow individually. For every workflow in the list, an Execute Workflow node calls the "worker" part of this same workflow, passing the individual workflow's data. Individual Workflow Backup (Worker Task): This part is triggered by the When Executed by Another Workflow node (called by the orchestrator part). It first retrieves the passed workflow data. A Parameters node defines the target Google Drive directory. The Get Google Drive File Data node searches the specified Google Drive folder to see if a backup file for the current workflow (named as WorkflowName_WorkflowID.json) already exists. An IF Node (ifDriveEmpty) checks the result: If a backup file exists, the workflow data is converted to a binary JSON file using a Code Node, and then the existing file on Google Drive is updated (Ba