by System Admin
Tagged with: , , , ,
by Louis Chan
How it works This workflow creates an MCP server that allows coding agents (e.g. Claude, ChatGPT with MCP support, Clawed Code) to interact with Google Docs programmatically. Many agents today can find files in Google Drive, but cannot open, edit, or format documents. This workflow fills that gap. What users can do Search for files in Google Drive Create new Google Docs Get document content Update docs with: Find & Replace Insert text Add page breaks Bullet and numbered lists Checkbox lists Insert tables Why it’s useful This expands agent capabilities from read-only to full *read/write and content manipulation* within Google Docs, enabling workflows such as auto-writing reports, generating checklists, cleaning content, and formatting structured output via AI.
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by ZeroBounce
ZeroBounce Bulk Email Validation and Scoring This template uses the ZeroBounce node to validate and score email addresses. It is designed to first check if an email is deliverable and then uses A.I. Scoring to assess the sender's deliverability confidence. This is an example template to demonstrate ways to use the ZeroBounce node and how to manipulate the data with core n8n nodes. A ZeroBounce API key is needed to use this template. Generate one here. 1. Email Validation The Validate email node sends the email address to the ZeroBounce API to determine its status (e.g., 'valid', 'invalid', 'spam trap'). Function:** Checks the email address against ZeroBounce's Email Validation API 2. A.I. Scoring For emails confirmed as valid, the workflow proceeds to the Score email node. Function:* Applies ZeroBounce's proprietary A.I. model to assess the quality of the email, returning a numerical score (0 to 10*). 3. Output The workflow concludes with the Filter by score Switch Node, which uses the ZeroBounce score to categorize the email into three confidence tiers: High Score:** Indicates high confidence in deliverability and is ready for immediate campaigns. Medium Score:** Suggests moderate risk; these might be suitable for re-engagement or specialized campaigns. Low Score:** Indicates high risk, even if the status was technically valid. These should be suppressed to protect sender reputation.
by System Admin
No description available
by Artem Boiko
Convert a Revit model to Excel and parse it into structured items ready for downstream ETL. This minimal template runs a local RvtExporter.exe, checks success, derives the expected *_rvt.xlsx filename, reads it from disk, and parses it to data items in n8n. What it does Setup: define path_to_revit_converter and revit_file. Run converter: execute RvtExporter.exe "<converter>" "<revit_file>" (writes *_rvt.xlsx next to the RVT). Check success: branch on converter error output. Read Excel: compute <revit_file> → *_rvt.xlsx and read it from disk. Parse: convert the workbook into structured items (rows → items). Prerequisites Windows** host (local executable and filesystem paths). DDC Revit toolkit installed: C:\\DDC_Converter_Revit\\datadrivenlibs\\RvtExporter.exe. A local .rvt you can read; the converter will write *_rvt.xlsx next to it. How to use Import this JSON into n8n. Open “Setup – Define file paths” and set: path_to_revit_converter: C:\\DDC_Converter_Revit\\datadrivenlibs\\RvtExporter.exe revit_file: e.g., C:\\Sample_Projects\\your_project.rvt Run Manual Trigger. On success, the flow will read *_rvt.xlsx and emit parsed items. Outputs On disk: <YourProject>_rvt.xlsx (created by the converter). In n8n: parsed rows as items, ready for Transform/Load phases. Notes & tips If your converter writes the Excel to a different folder/file name, update the “Success – Create Excel filename” node to point to the actual path. Ensure write permissions in the project folder and avoid non-ASCII characters in paths when possible. This template is purposefully minimal (Extract-only). Chain it with your own Transform/Load steps. Categories Data Extraction · Files & Storage · ETL · CAD/BIM Tags cad-bim, revit, ifc, dwg, extract, xlsx, etl Author DataDrivenConstruction.io info@datadrivenconstruction.io Consulting and Training We work with leading construction, engineering, consulting agencies and technology firms around the world to help them implement open data principles, automate CAD/BIM processing and build robust ETL pipelines. If you would like to test this solution with your own data, or are interested in adapting the workflow to real project tasks, feel free to contact us. Docs & Issues: Full Readme on GitHub
by KlickTipp
Community Node Disclaimer: This workflow uses KlickTipp community nodes. Introduction This template listens for new events in Google Calendar and automatically creates or updates participant profiles in KlickTipp. Every attendee’s email address (and other available details) is mapped directly into your KlickTipp account without manual steps. This ensures your contact list always reflects the latest event registrations in real time. Perfect for coaches, consultants, and event organizers who want to capture RSVP information instantly and keep their marketing lists up to date. With each new attendee synced, you can launch reminder emails, follow-up campaigns, or trigger automated onboarding sequences. How it works This template keeps your KlickTipp list in sync with Google Calendar across the full event lifecycle. For each attendee, the workflow optionally filters out internal domains, then writes event details into KlickTipp custom fields. It watches your calendar for: Event Created* → creates/updates each attendee as a KlickTipp contact and adds the *event created/updated tag. Event Cancelled* → tags attendees with *event canceled. Event Updated* → routes attendees by *responseStatus** and tags them: accepted → event confirmed declined → event declined tentative → event considered Setup Instructions KlickTipp Preparation Prepare custom fields Google Calendar | event summary, data type: "Single line" Google Calendar | event description, data type: "Single line" Google Calendar | event location, data type: "Single line" Google Calendar | event start datetime, data type: "Datetime" Google Calendar | event end datetime, data type: "Datetime" Prepare tags: Google Calendar | event created/updated Google Calendar | event canceled Google Calendar | event declined Google Calendar | event confirmed Google Calendar | event considered Credential Configuration Connect your Google Calendar account using Client ID and Client Secret from the Google Cloud. Authenticate your KlickTipp connection with username/password credentials (API access required). Customization Recommended poll frequency: every 1–5 minutes for near real-time updates. Adjust to your local timezone if necessary. Each trigger works independently, allowing partial deployments if only certain event types are needed.
by KlickTipp
Community Node Disclaimer This workflow uses KlickTipp community nodes, available for self-hosted n8n instances only. Introduction This workflow receives an array of tag names, checks which tags already exist in KlickTipp, creates the missing ones, and returns a unified array of tag IDs — so you can reuse the same "get or create tags" logic across multiple automations. How it works Accepts input tagNames[] (array of tag names). Splits the array into individual items and maps each name into a value field for matching. Loads your full KlickTipp tag list and matches by tag name. Creates tags that don’t exist yet. Combines existing + newly created tags and returns a single aggregated array of IDs. Setup Instructions Credentials Configure your KlickTipp credentials in the KlickTipp nodes. How to call this sub-workflow From a parent workflow, use an Execute Sub-workflow node and pass: { "tagNames": ["Tag A", "Tag B", "Tag C"] } Output Returns aggregated tag IDs: { "tagIds": [123456789, 98765431, 999999999] } Testing Test with a mix of existing and new tag names. Confirm new tags appear in KlickTipp and the output contains all expected IDs. Use tagIds[] in your parent workflow (for example, when updating or tagging contacts).
by ZeroBounce
ZeroBounce Email Validation and Scoring This template uses the ZeroBounce node to validate and score email addresses. It is designed to first check if an email is deliverable and then uses A.I. Scoring to assess the sender's deliverability confidence. This is an example template to demonstrate ways to use the ZeroBounce node and how to manipulate the data with core n8n nodes. A ZeroBounce API key is needed to use this template. Generate one here. 1. Email Validation The Validate email node sends the email address to the ZeroBounce API to determine its status (e.g., 'valid', 'invalid', 'spam trap'). Function:** Checks the email address against ZeroBounce's Email Validation API 2. A.I. Scoring For emails confirmed as valid, the workflow proceeds to the Score email node. Function:* Applies ZeroBounce's proprietary A.I. model to assess the quality of the email, returning a numerical score (0 to 10*). 3. Output The workflow concludes with the Filter by score Switch Node, which uses the ZeroBounce score to categorize the email into three confidence tiers: High Score:** Indicates high confidence in deliverability and is ready for immediate campaigns. Medium Score:** Suggests moderate risk; these might be suitable for re-engagement or specialized campaigns. Low Score:** Indicates high risk, even if the status was technically valid. These should be suppressed to protect sender reputation.