by Oneclick AI Squad
Description Automates weekly checks for broken links on a website. Scans the site using HTTP requests and filters broken links. Sends Slack alerts for detected broken URLs and creates a list for tracking. Essential Information Runs weekly to monitor website link integrity. Identifies broken links and notifies the team via Slack. Generates a list of broken links for further action. System Architecture Link Checking Pipeline**: Weekly Cron Trigger: Schedules the workflow to run weekly. Scan Blog with HTTP: Performs HTTP GET requests to check website links. Alert and Tracking Flow**: Filter Broken Links: Identifies and separates broken links. Send Slack Alert: Notifies the team via Slack about broken URLs. Create Broken Links List: Compiles a list of broken links. Non-Critical Handling**: No Action for Valid Links: Skips valid links with no further action. Implementation Guide Import the workflow JSON into n8n. Configure the HTTP node with the target website URL (e.g., https://yourblog.com). Set up Slack credentials for alerts. Test the workflow with a sample website scan. Monitor link checking accuracy and adjust HTTP settings if needed. Technical Dependencies HTTP request capability for link scanning. Slack API for team notifications. n8n for workflow automation and scheduling. Database & Sheet Structure No specific database or sheet required; relies on HTTP response data. Example payload: {"url": "https://yourblog.com/broken", "status": 404, "time": "2025-07-29T20:21:00Z"} Customization Possibilities Adjust the Cron trigger to run at a different frequency (e.g., daily). Customize HTTP node to scan specific pages or domains. Modify Slack alert messages in the Send Slack Alert node. Enhance the Create Broken Links List node to save results to a Google Sheet or Notion. Add email notifications for additional alert channels.
by curseduca.com
š Curseduca ā User Creation & Access Group Assignment How it works This workflow automates the process of creating a new user in Curseduca and granting them access to a specific access group. It works in two main steps: Webhook ā Captures user details (name, email, and group information). HTTP Request ā Sends the data to the Curseduca API, creating the user, assigning them to the correct access group, and sending an email notification. Setup steps Deploy the workflow Copy the webhook URL generated by n8n. Send a POST request with the required fields: name email groupId Configure API access Add your API Key and Bearer token in the HTTP Request node headers (replaCurseducace placeholders). Replace <GroupId> in the body with the correct group ID. Notifications By default, the workflow will trigger an email notification to the user once their account is created. Example use cases Landing pages**: Automatically register leads who sign up on a product landing page and grant them immediate access to a course, training, or bundle. Product bundles**: Offer multiple products or services together and instantly give access to the correct group after purchase. Chatbot integration: Connect tools like **Manychat to capture name and email via chatbot conversations and create the user directly in Curseduca. š Curseduca ā Criação de UsuĆ”rio e Liberação de Grupo de Acesso Como funciona Este fluxo de trabalho automatiza o processo de criação de um novo usuĆ”rio no Curseduca e a liberação de acesso a um grupo especĆfico. Ele funciona em duas etapas principais: Webhook ā Captura os dados do usuĆ”rio (nome, e-mail e informaƧƵes de grupo). HTTP Request ā Envia os dados para a API do Curseduca, criando o usuĆ”rio, atribuindo-o ao grupo correto e disparando uma notificação por e-mail. Passos de configuração Publicar o workflow Copie a URL do webhook gerada pelo n8n. Envie uma requisição POST com os campos obrigatórios: name email groupId Configurar o acesso Ć API Adicione sua API Key e Bearer token nos headers do nó HTTP Request (substitua os placeholders). Substitua <GroupId> no corpo da requisição pelo ID correto do grupo. NotificaƧƵes Por padrĆ£o, o fluxo dispara uma notificação por e-mail para o usuĆ”rio assim que a conta Ć© criada. Casos de uso Landing pages**: Registre automaticamente leads que se inscrevem em uma landing page de produto e libere acesso imediato a um curso, treinamento ou pacote. Pacotes de produtos**: OfereƧa mĆŗltiplos produtos ou serviƧos em conjunto e conceda acesso instantĆ¢neo ao grupo correto após a compra. Integração com chatbots: Conecte ferramentas como o **Manychat para capturar nome e e-mail em conversas e criar o usuĆ”rio diretamente no Curseduca.
by Fahmi Fahreza
Auto-clip long videos into viral short clips using Vizard AI This workflow turns long-form YouTube or video URLs into short, high-viral-potential clips, then automatically publishes them to social platforms and logs results in Google Sheets. Whoās it for? Content creators, social media managers, and marketers who want to scale short-form video production automatically. How it works Collect a video URL and viral score via form or schedule. Create a clipping project in Vizard AI. Poll project status until processing is complete. Filter clips by viral score and limit quantity. Publish selected clips and log results to Google Sheets. How to set up Connect Vizard AI, Google Sheets, and social credentials. Configure thresholds and limits in the Set Configuration node, then activate the workflow.
by StƩphane Heckel
Copy n8n workflows to a slave n8n repository Inspired by Alex Kim's workflow, 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 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. Configure the Notion node: Enter your Notion credentials. Link to the created database/page. 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. 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 or contact me on LinkedIn Ask in the Forum!
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
No description available
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,