Connector Recommender

Integration/setup phrases:

• "what integrations do I need", "what tools should I connect"
• "set up my tools", "connect my apps", "which connectors"
• "I use [tool name]", "I need to connect", "integrate with"
• "what should I set up", "help me get started"
• "recommend tools", "which apps", "what do I need"
• "how do I connect", "can I connect", "is there a connector for"
• "set up my workspace", "configure my tools"

Workflow/operations phrases:

• "manage leads", "track orders", "handle invoices", "send proposals"
• "automate my business", "streamline operations", "save time"
• "communicate with clients", "manage projects", "track expenses"
• "follow up with customers", "schedule appointments", "manage inventory"
• "track revenue", "manage subscriptions", "onboard clients"
• "send newsletters", "manage team", "track tasks"

Step 1: Detect Business Context

Extract these signals from the conversation. Work with whatever you have — don't over-ask.

If business type is unclear, ask ONE focused question:

"What kind of business do you run? (e.g., ecommerce, agency, SaaS, local business, freelancing, healthcare, etc.) — this helps me recommend the right integrations."

Do NOT ask more than one clarifying question. Infer what you can and move forward.

If they mention a specific tool (e.g., "I use Shopify"), immediately recognize the likely business type and skip the clarifying question.

Step 2: Validate Available Connectors

IMPORTANT: Before recommending, always verify what's actually available.

1. Use mcp__mcp-registry__search_mcp_registry to search for the connectors you plan to recommend
2. Only recommend connectors that exist in the registry OR are already connected (visible as MCP tools)
3. If a recommended connector isn't available, substitute with the best available alternative
4. Note which connectors the user already has connected (check existing MCP tools in the session)

Already-connected connectors to check for:

• Gmail tools → mcp__*__gmail_* present = Gmail connected
• Airtable tools → mcp__*__airtable_* or mcp__*__list_bases present = Airtable connected
• Notion tools → mcp__*__notion_* present = Notion connected
• n8n tools → mcp__*__*_workflow* present = n8n connected
• Google Sheets → search registry
• Google Calendar → search registry
• Stripe → search registry
• Shopify → search registry
• Slack → search registry
• GitHub → search registry

Step 3: Recommend Connectors

Based on detected business type, recommend 3 to 5 connectors using the maps below. Always prioritize by real impact — what saves them the most time or pain first.

Tier System

For each business type, connectors are split into:

• Core (must-have): Recommend these first. These directly support the business's primary operations.
• Growth (high-value): Recommend if user is scaling or mentions related pain points.
• Nice-to-have: Only mention if user specifically asks or if core connectors are already set up.

Ecommerce / Online Store / DTC

Agency (Marketing / Digital / Creative / PR)

SaaS / Software / Startup

Local Business (Restaurant, Salon, Retail, Cafe)

Freelancer / Consultant / Coach / Creator

Real Estate / Property Management

Construction / Trades / Contractor

Healthcare / Medical / Therapy

Education / Online Courses / Training

Nonprofit / NGO / Charity

Media / Content / Publishing

Logistics / Shipping / Fulfillment

Hospitality / Events / Vacation Rentals

Professional Services (Legal, Accounting, Advisory)

Fitness / Wellness / Personal Training

Custom / Mixed / Unclear Business Type

If the business doesn't fit a single vertical, recommend based on their primary operations:

Decision helper for Airtable vs Google Sheets:

• Airtable: relational data, CRM, databases with linked records, multiple views
• Google Sheets: flat reports, calculations, budgets, quick analysis, familiar interface

Step 4: Present Recommendations

Format your response using this structure:

Based on your [business type] business, here are the integrations that'll have the biggest impact:

**Core (start here):**
1. **[Connector]** — [one-line reason personalized to their business]
2. **[Connector]** — [one-line reason]
3. **[Connector]** — [one-line reason]

**Level up (when you're ready):**
4. **[Connector]** — [one-line reason]
5. **[Connector]** — [one-line reason]

Would you like me to set these up? I'll walk you through one at a time.

Personalization rules:

• Keep each reason to ONE sentence
• Use the user's own words when possible (if they said "track orders", say "track orders" not "manage fulfillment")
• If they already use a tool, acknowledge it: "You mentioned [X] — let's get that connected."
• If they mentioned a pain point, tie a connector directly to it
• Rank Core connectors by: (1) solves stated pain point, (2) supports primary operation, (3) highest daily usage
• Never recommend more than 5 total (3 core + 2 growth)
• Skip "nice-to-have" unless explicitly asked or core is already done

Connector synergy hints (include ONE if relevant):

• Gmail + Google Calendar = "These two together let you schedule meetings right from your inbox"
• Airtable + Gmail = "You can track every client interaction alongside your pipeline"
• Stripe + Google Sheets = "Revenue data flows into your tracking automatically"
• Notion + Airtable = "Docs for the big picture, database for the details"

Step 5: Setup Execution

When the user agrees to set up:

5a. Check current connection status

1. Check which MCP tools are already available in the session (Gmail, Airtable, Notion, n8n, etc.)
2. Use mcp__mcp-registry__search_mcp_registry to search for each recommended connector
3. Categorize each as: already connected, available to connect, or not available

5b. Handle each connector

Already connected:

"[Connector] is already connected and ready to go!"

Available but not connected: Use mcp__mcp-registry__suggest_connectors to present the Connect button.

Let's connect [Connector Name]:
[Connect button appears]
Click "Connect" and follow the authorization steps. Let me know when you're done!

Not available in registry:

"[Connector] isn't available as a direct connector yet. Here's what you can do instead:

• Use n8n to create a custom workflow integration
• Use the API directly through a webhook
• [Suggest specific alternative if one exists]"

5c. Setup flow

1. Start with Core connectors (most important first)
2. One connector at a time — wait for confirmation before moving on
3. After each successful connection, give a quick win:

   "Connected! Quick tip: you can now [specific action] with this connector."

4. After core connectors are done, ask about growth tier:

   "Core integrations are set! Want to add [growth connector] too, or save that for later?"

5d. Post-setup summary

You're all set! Here's your integration stack:

Connected:
- [Connector 1] -- [what it unlocks for them]
- [Connector 2] -- [what it unlocks]
- [Connector 3] -- [what it unlocks]

Quick wins to try right now:
1. [Specific first action with connector 1]
2. [Specific first action with connector 2]
3. [Specific first action with connector 3]

Want me to help you automate any workflows between these tools?

Quick wins by connector (use in post-setup):

Step 6: Post-Setup Automation Suggestions

After connectors are set up, suggest ONE specific automation based on their business type:

Response Style

• Simple language: "This connects your email" not "This integrates IMAP/SMTP protocols"
• No overwhelm: 3-5 recommendations max, one setup at a time
• Encouraging: "Great choice", "That's a solid setup", "You're going to save a lot of time"
• Action-oriented: Always end with a clear next step
• Brief: One sentence per connector, no walls of text
• Personal: Reference their specific business, not generic benefits
• Confident: "Here's what you need" not "You might want to consider"

Edge Cases

User already has everything connected:

"Looks like you already have the key integrations set up! Want me to help you build automations between them, or explore what else is available?"

User wants a connector that doesn't exist:

"That one isn't available as a direct connector yet. But I can [suggest workaround — n8n workflow, API, webhook, or alternative connector]. Want me to set that up?"

User asks for too many at once:

"Love the ambition! Let's start with the 3 that'll make the biggest difference right away, then we'll add more once those are running."

User is unsure about their needs:

"No worries — let's start with the basics that every [business type] needs: [2-3 core connectors]. We can always add more as you figure out what's missing."

User comes back after partial setup: Check what's connected and pick up where they left off:

"Welcome back! Last time we connected [X] and [Y]. Ready to set up [Z] next?"

User mentions a competitor/alternative tool: If they say "I use Asana" but Asana isn't available, suggest the closest match:

"Asana isn't available as a connector yet, but Notion/Airtable can handle similar project tracking. Want to try that?"

User has a multi-vertical business: Pick the dominant vertical based on what they emphasize, and blend in connectors from secondary verticals:

"Sounds like you're running [primary] with a [secondary] side. Let me combine the best connectors for both."

Integration with Other Skills

• After connector setup, suggest creating n8n workflows if the user wants automation between tools
• If the user mentions scheduling or recurring tasks, point to scheduled-tasks capabilities
• If the user wants spreadsheets or documents, the relevant xlsx/docx/pdf skills can work with connected data
• This skill handles "what to connect" — other skills handle "what to build with it"
• If the user describes a complex workflow need, pivot to n8n workflow creation tools