Workflow Templates

Tagged with: , , , ,

Tagged with: , , , ,

Video Introduction Want to automate your inbox or need a custom workflow? 📞 Book a Call | 💬 DM me on Linkedin What This Workflow Does This workflow creates an MCP (Model-Client-Protocol) server that exposes your Airtable data as AI-powered tools, enabling external applications like ChatGPT, custom GPTs, or voice agents to query your Airtable base using natural language. Instead of manually searching through your Airtable records, you can simply ask ChatGPT questions like "list all contacts from Microsoft" and receive instant answers pulled directly from your database. Key Features Natural Language Queries**: Ask questions about your Airtable data in plain English from ChatGPT or other AI applications Multi-Table Support**: Includes tools for both Contacts and Companies tables (easily customizable for your own tables) Real-Time Data Access**: External applications query live data directly from your Airtable base No-Code Integration**: Connect ChatGPT to your Airtable without writing any code Setup & Configuration 1. Airtable Connection First, create an Airtable Personal Access Token at airtable.com/create/tokens with these required scopes: data.records:read data.records:write schema.bases:read Then add this token to n8n by creating a new Airtable Personal Access Token API credential. 2. Configure Your Tables Update both Airtable Tool nodes to point to your own Airtable base and tables. The default setup includes Search Contacts and Search Companies tools, but you can customize these or add additional tools for other tables in your base. 3. Connect to ChatGPT After publishing the workflow, copy the Production URL from the MCP Server Trigger node. In ChatGPT, enable Developer Mode in settings, navigate to Apps, and create a new app using this MCP Server URL. Common Use Cases Query customer or contact databases from ChatGPT Research companies in your CRM without opening Airtable Build custom AI assistants with access to your organizational data Enable team members to access data through conversational interfaces

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.

No description available

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).

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, optionally applies a prefix to all tags, checks which tags already exist in KlickTipp, creates the missing ones, and returns a unified array of resolved tag names. This allows you to reuse the same get or create tags logic across multiple automations without duplicating tag-handling logic. It’s especially useful when tags are namespaced by a tool or source (for example, Zoho | Webinar) and you want to enforce consistent tagging conventions across different workflows. How it works Accepts input: tagNames[] — array of base tag names prefix — optional string applied to all tag names Splits tagNames[] into individual items and builds the final tag name: If prefix is provided → prefix tagName (e.g. Zoho | Webinar) If prefix is empty → tagName (e.g. Webinar) Loads the existing KlickTipp tags and matches them by name. Creates tags that do not yet exist. Combines existing and newly created tags. Returns a single aggregated array of resolved tag names, without duplicates. Setup Instructions 1) Credentials Configure your KlickTipp credentials in the KlickTipp nodes. 2) How to call this sub-workflow From a parent workflow, use an Execute Sub-workflow node and pass: Without prefix { "tagNames": ["Webinar", "Newsletter] } With prefix { "prefix": "Zoho | ", "tagNames": ["Webinar", "Newsletter"] } Resulting tag names resolved or created in KlickTipp: Zoho | Webinar Zoho | Newsletter Output Returns a unified array of tag names: { "tags": ["Zoho | Webinar", "Zoho | Newsletter"] } Testing Test with a mix of existing and new tag names. Confirm new tags appear in KlickTipp when missing. Verify that the output contains all expected tag names, without duplicates. If a prefix is used, ensure tags are resolved or created under the correct namespace (for example, Zoho | …). Reuse the returned tags[] in downstream workflows (for example, for filtering, comparison, or further tagging logic).

No description available

No description available

No description available

Tagged with: , , , ,

Tagged with: , , , ,