Stéphane Heckel

Workflows

Workflows by Stéphane Heckel

Sort by:

Automate LinkedIn invitations with Browserflow & Google Sheets tracking

# Manage LinkedIn Invitations with Browserflow **Automate personalized LinkedIn outreach while maintaining human-like behavior** ## Overview This workflow helps you send targeted LinkedIn invitations with customized messages, automatically checking existing connections to avoid duplicate requests. Perfect for recruiters, sales professionals, and anyone building their professional network systematically. ## How It Works 1. **Contact Management**: Store your prospects in a Google Sheet with their LinkedIn profile URLs 2. **Connection Verification**: Automatically check if you're already connected to avoid duplicate invitations 3. **Smart Invitations**: Send personalized invitations to new contacts 4. **Progress Tracking**: Update the Google Sheet with invitation status ## Setup Instructions ### Prerequisites - **Google account** with Sheets access - **Browserflow account** with available credits ([sign up here](https://browserflow.io/)) - **n8n instance** (tested on version 1.109.1) ### Step-by-Step Setup 1. **Prepare Your Contact List** - Download the [Google Sheet Template](https://docs.google.com/spreadsheets/d/1mFKp3wmbV9qp2tpGGsN72zdiC32y8H1nhjdgP885y-U/edit?usp=sharing) - Make a copy to your Google Drive - Extract the Sheet ID from your URL (the string between `/d/` and `/edit`) 2. **Configure Workflow Settings** - Open the `settings` node and enter your Google Sheet ID - Customize your invitation message in the `message` node - Set up your Google Sheets credentials - Configure your Browserflow credentials 3. **Populate Your Data** - Add contacts to your Google Sheet with their LinkedIn profile URLs 4. **Test & Deploy** - Run a test with 1-2 contacts first (update the `Limit` node) - Monitor execution and adjust `Wait` if needed ## Important Considerations - **Responsible Usage**: This tool mimics human behavior and respects LinkedIn's natural usage patterns. It's designed for quality networking, not mass spamming. - **Rate Limits**: Stay within LinkedIn's acceptable limits. - **Account Safety**: Excessive automation can result in LinkedIn restrictions. Always prioritize authentic, valuable connections. ## Support & Community Need assistance? Here's how to get help: - **LinkedIn Discussion**: Comment on this [workflow post](https://www.linkedin.com/posts/n8n-about_n8n-browserflow-activity-7368758690025320448-zupZ/) - **Direct Contact**: Connect with me on [LinkedIn](https://www.linkedin.com/in/stephaneheckel/) - **Community Forum**: Ask questions in the [n8n Community](https://community.n8n.io/)

Sync Google Sheets contacts to SeaTable with update/insert logic

# Keep your Google Sheets contacts in sync with SeaTable Update or Insert records in SeaTable ## How it works - Use a Google Sheet as your central contact list. - For each contact in the sheet: - Check if the record already exists in **SeaTable** (based on email). - If it exists → update the record. - If it doesn’t → insert the new contact. ## How to use 1. Copy the Google Sheet [Template Link](https://docs.google.com/spreadsheets/d/1mFKp3wmbV9qp2tpGGsN72zdiC32y8H1nhjdgP885y-U/edit?usp=sharing). - Get the **Google Sheet ID** (the string between `d/` and `/edit`). 2. In the workflow, set the Sheet ID in the `settings` node. 3. In SeaTable, create or update a base with a **Table1** containing these fields: - `email` - `firstname` - `lastname` - `company` 4. Configure your **Google Sheets** and **SeaTable credentials** in n8n. 5. Add your own contacts to the Google Sheet & run the workflow ## Requirements - Google credentials (for Sheets access) - SeaTable account (Cloud) - n8n (tested on version **1.105.2**, Ubuntu) ## Example use cases - Maintain a **central CRM-like database** in SeaTable. - Ensure consistent contact data when collecting leads in Google Sheets. - Automate **record deduplication** (prevent duplicate entries). ## Need Help? - Join the discussion [here](https://www.linkedin.com/posts/n8n-about_n8n-seatable-airtable-activity-7363129613465571332-Scun/) or contact me directly on [LinkedIn](https://www.linkedin.com/in/stephaneheckel/). - Ask the community in the [n8n Forum](https://community.n8n.io/).

Flag bounced emails in Google Sheets from Gmail delivery error messages

# Scanning Email Inbox for Delivery Errors **Prerequisite:** [Automate Personalized Email Campaigns with Google Docs, Sheets, and SMTP](https://n8n.io/workflows/7065-automate-personalized-email-campaigns-with-google-docs-sheets-and-smtp/). ## How It Works After running your email campaign, some messages may fail to deliver. This workflow scans your email inbox for delivery errors (e.g., bounced messages), flags problematic email addresses in the Google Sheet and ensures future campaigns skip them. ## How to Use 1. **Ensure Prerequisite Workflow:** - You should have the [Email Campaign Workflow](https://n8n.io/workflows/7065-automate-personalized-email-campaigns-with-google-docs-sheets-and-smtp/) configured and running. 2. **Google Sheet Setup:** - Use the [Google Sheet Template](https://docs.google.com/spreadsheets/d/1mFKp3wmbV9qp2tpGGsN72zdiC32y8H1nhjdgP885y-U/edit?usp=sharing). - Identify your document’s ID (the string after `/d/` and before `/edit` in the URL). 3. **Configure Workflow:** - Enter your Google Sheet ID in the `settings` node. - Connect your Google credentials to n8n. 4. **Email Inbox:** - Set up the `readspamfolder` node to search for bounce/error messages in your mail (e.g., in the Spam or Inbox folders—adjust label/folder if emails land elsewhere). 5. **Google Sheet Update:** - Configure the `lookupemail` and `update_err` nodes ## Requirements - **Google Credentials** to access Gmail and sheets. - **Gmail Account** (bounce/error messages must be accessible here). - **n8n Version:** Tested with 1.105.2 (Ubuntu). ## Need Help? - Comment this [post](https://www.linkedin.com/posts/n8n-about_n8n-emailing-smtp-activity-7358928869015310336-G_9n/) or contact me on [LinkedIn](https://www.linkedin.com/in/stephaneheckel/) - Ask in the [n8n Community Forum](https://community.n8n.io/)!

Automate personalized email campaigns with Google Docs, Sheets and SMTP

# Emailing Using Google Sheet, Google Docs, and SMTP Automate personalized email campaigns using a Google Sheets contact list, a Google Docs template, and SMTP delivery. ## How It Works - **Google Docs** is used as the email template with variables: `{{firstname}}`, `{{lastname}}`, `{{company}}`, `{{email}}`. - **Google Sheet** contains your list of recipients (one per row). - For each contact, the workflow merges personal data into the Google Docs template. - Email is sent to each recipient via SMTP (batch size: 1). Use the `Wait` node to respect provider quotas. - After sending, the workflow updates the "process" column of the Google Sheet with the date/time. ## How to Use 1. **Copy Templates:** - [Google Docs Template](https://docs.google.com/document/d/1sR1Mjee0heur6CgEV_ssYzOUbFNaDnyEnPSt1CFEMWI/edit?usp=sharing) - [Google Sheet Template](https://docs.google.com/spreadsheets/d/1mFKp3wmbV9qp2tpGGsN72zdiC32y8H1nhjdgP885y-U/edit?usp=sharing) - Find each document’s ID (the text after `/d/` and before `/edit` in the URL). 2. **Configure Workflow:** - Enter your Google Docs and Google Sheets IDs in the `settings` node. - Set your email subject in the appropriate parameter. 3. **Set Up Credentials:** - Connect your Google account. - Configure the SMTP node with your mail server details. 4. **Update Data:** - Edit the Google Docs template with your message and variables. - Prepare your Google Sheet with these columns: **email**, **firstname**, **lastname**, **company**. 5. **Deploy and Test:** - Connect all nodes. - Test with a small contact batch. - Troubleshoot any node errors (indicated in red in n8n). ## Requirements - **Google Credentials & permissions**: For Sheets and Docs access. - **SMTP Server**: For email delivery (adjust Wait node for rate limits). - **n8n Version**: Tested on 1.105.2 (Ubuntu). ## Need Help? - Comment this [post](https://www.linkedin.com/posts/n8n-about_n8n-emailing-smtp-activity-7358928869015310336-G_9n/) or contact me on [LinkedIn](https://www.linkedin.com/in/stephaneheckel/) - Ask in the [n8n Community Forum](https://community.n8n.io/)! ## See Also After running your email campaign, some messages may fail to deliver. This [workflow](https://n8n.io/workflows/7251-flag-bounced-emails-in-google-sheets-from-gmail-delivery-error-messages/) scans your email inbox for delivery errors (e.g., bounced messages), flags problematic email addresses in the Google Sheet and ensures future campaigns skip them.

Backup n8n workflows with versioning and Notion tracking

## Copy n8n workflows to a slave n8n repository Inspired by [Alex Kim's workflow](https://n8n.io/workflows/3048-clone-n8n-workflows-between-instances-using-n8n-api/), this version adds the ability to keep multiple versions of the same workflow on the destination instance. Each copied workflow’s name is prefixed with the date (`YYYY_MM_DD_`), enabling simple version tracking. Process details and workflow counts are recorded centrally in Notion. ## How it works - Workflows from the **source n8n instance** are copied to the **destination** using the n8n API node. - On the destination, each workflow name is prefixed with the current date (e.g., `2025_08_03_PDF Summarizer`), so you can keep multiple daily versions. - The workflow tracks and saves: - The date of execution. - Number of workflows processed. - Both details are recorded in Notion. ### Rolling retention policy example: - **Day 1:** Workflows are saved with `2025_08_03_` prefix. - **Day 2:** New set saved with `2025_08_04_`. - **Day 3:** Day 1’s set is deleted, new set saved as `2025_08_05_`. - To keep more days, adjust the “Subtract From Date” node. ## How to use 1. **Create a Notion database** with one page and three fields: - `sequence`: Should contain `"prefix"`. - `Value`: Today's date as `YYYY_MM_DD_`. - `Comment`: Number of saved workflows. 2. **Configure the Notion node**: - Enter your Notion credentials. - Link to the created database/page. 3. **Update the "Subtract From Date" node**: - Set how many days’ versions you want to keep (default: 2 days). - Set the limit to 1 in the "Limit" node for testing. 4. **Input credentials** for both source and destination n8n instances. ## Requirements - **Notion** for tracking execution date and workflow count. - **n8n API Keys** for both source and destination instances. Ensure you have the necessary **API permissions** (read, create, delete workflows) - **n8n version** this workflow was tested on 1.103.2 (Ubuntu) ## Need Help? - Comment this [post](https://www.linkedin.com/posts/n8n-about_n8n-activity-7357850874024456192-c0eL/) or contact me on [LinkedIn](https://www.linkedin.com/in/stephaneheckel/) - Ask in the [Forum](https://community.n8n.io/)!