Set up bidirectional Clay + n8n integrations for data enrichment and automation. Use when the user asks about connecting Clay to n8n, Clay webhooks in n8n, sending data from n8n to Clay, Clay HTTP API with n8n, or building Clay automation pipelines. Triggers on "Clay n8n", "n8n Clay", "Clay webhook n8n", "Clay automation", "Clay HTTP API n8n". Do NOT use for Clay-only workflows without n8n.
Build CRM automations with n8n for HubSpot, Salesforce, lead routing, and Slack notifications. Use when the user asks about n8n CRM integration, n8n HubSpot workflows, n8n Salesforce sync, lead routing in n8n, Slack notifications from n8n, or pipeline reporting. Triggers on "n8n HubSpot", "n8n Salesforce", "n8n CRM", "lead routing n8n", "n8n Slack", "pipeline report n8n", "deal stage n8n". Do NOT use for Clay integration (use clay-integration).
Configure n8n triggers and webhooks for real-time and scheduled automations. Use when the user asks about n8n webhook setup, cron triggers, schedule triggers, app event triggers, webhook URLs, webhook authentication, or how to start n8n workflows. Triggers on "n8n webhook", "n8n trigger", "cron trigger", "schedule trigger", "webhook URL", "webhook auth", "test vs production URL". Do NOT use for workflow design beyond the trigger node.
Design n8n workflow architectures for B2B GTM automations. Use when the user asks about building n8n workflows, choosing nodes, designing data flows, sub-workflows, or structuring multi-step automations. Triggers on "design workflow", "n8n workflow", "node sequence", "data flow", "sub-workflow", "workflow architecture". Do NOT use for trigger/webhook setup (use triggers-webhooks) or error handling (use error-handling).
Find and enrich contacts at target companies in Clay. Use when the user asks about finding decision makers, people enrichment, LinkedIn enrichment, title or seniority filtering, buying committee mapping, contact discovery at companies, or Sales Navigator imports. Triggers on "find contacts", "find people", "people enrichment", "decision makers", "LinkedIn enrichment", "title filtering", "seniority", "buying committee", "Sales Navigator". Do NOT use for email-specific waterfall setup, phone number finding, or company-only enrichment.
Create and configure Clay tables, choose column types, import data, and set up auto-update. Use when the user asks about creating a Clay table, choosing column types, importing data (CSV, CRM, LinkedIn), setting up views and filters, configuring auto-update, using the Chrome extension, or organizing workbooks. Triggers on "create table", "table setup", "column types", "data import", "auto-update", "Clay table", "workbook", "views", "filters", "CSV import", "Chrome extension", "Clip to Clay". Do NOT use for enrichment-specific questions, scoring, or formula writing.
Send transactional emails and enroll recipients in drip sequences through a deployed saasmail instance's HTTP API. Use this skill whenever the user wants to programmatically send mail, fire off a template, kick off an onboarding/drip sequence, manage recipient enrollment, or integrate their app with their self-hosted saasmail server — even if they don't name the product (e.g. "send a welcome email from my Worker", "enroll this signup in my onboarding drip", "POST to /api/send", "use my mail API").
Use this skill when the user wants to install, configure, run, or troubleshoot BitRouter — an LLM proxy that runs two ways: a local Rust daemon at http://localhost:4356 (BYOK) or BitRouter Cloud at https://api.bitrouter.ai/v1 (managed, brk_* keys, Stripe credits or x402 wallet). Unifies OpenAI, Anthropic, Google, OpenRouter, GitHub Copilot, and OpenCode Zen/Go behind one endpoint. Also covers signup on bitrouter.ai, minting brk_ API keys, migrating off LiteLLM / OpenRouter / any OpenAI- or Anthropic-compatible gateway, editing bitrouter.yaml, and wiring coding-agent harnesses (Claude Code, Codex, Hermes Agent, OpenClaw). Trigger on "set up a local LLM proxy", "managed AI gateway", "replace litellm", "point claude code at a proxy", "bitrouter cloud", "brk_ key", anything naming bitrouter.yaml, port 4356, or api.bitrouter.ai — even when the user does not name BitRouter directly.
Databricks AI Runtime (`air`) CLI — the command-line tool for submitting and managing GPU training workloads on Databricks serverless compute. Use for: running `air` workloads, custom Docker image setup, environment configuration, and troubleshooting `air` jobs.