communicationapi_key

Heyy

Connect with your customers on Whatsapp, SMS, Messenger and Instagram using automation.

Verdict

Heyy is a multi-channel messaging platform that lets teams manage customer conversations across SMS, WhatsApp, and other channels from one inbox. In Switchy, @mentioning Heyy gives your AI direct access to contact management, labeling, and webhook setup — useful for support teams who want to organize inbound messages, tag contacts on the fly, or automate follow-ups without leaving chat. The MCP uses an API key, so setup is quick. It won't send messages or read conversation history; it focuses on contact data and event plumbing.

Common use cases

  • Tag inbound leads by campaign source
  • Create custom contact fields during discovery calls
  • Set up webhooks for new message alerts
  • Organize contacts into segments for outreach
  • Audit webhook configs before a product launch

Integration

Vendor
Heyy
Category
communication
Auth
API_KEY
Tools
13
Composio slug
heyy

Tools

  • Create Contact

    Tool to create a new contact in Heyy with optional details including first name, last name, email, phone number, labels, and custom attributes. Use when you need to add a new contact to your Heyy account.

  • Create Contact Attribute

    Tool to create a new custom attribute for contacts in Heyy. Use when you need to add custom fields to track additional information about contacts, such as customer segments, preferences, or custom identifiers.

  • Create Label

    Tool to create a new label for categorizing contacts in Heyy. Use when you need to organize contacts into categories or groups.

  • Create Webhook

    Tool to create a new webhook for receiving event notifications across multiple channels. Use when you need to set up real-time event notifications for messages.

  • Delete Attribute
    destructive

    Tool to delete an attribute by its unique identifier. Use when you need to remove an attribute from the system.

  • Delete Label
    destructive

    Tool to delete a label by its unique identifier. Use when you need to remove a label from the system.

  • Delete Webhook
    destructive

    Tool to delete a webhook by its unique identifier. Use when you need to remove a webhook from Heyy.

  • List API Webhooks

    Tool to retrieve all API webhooks configured for the account. Use when you need to inspect or manage webhook configurations.

  • List Attributes

    Tool to retrieve all attributes available in the Heyy system. Use when you need to get a list of all attributes with their properties and visibility settings.

  • List Automations

    Tool to retrieve automation workflows for a specified channel. Use when you need to get all workflows configured for a channel.

  • List Channels

    Tool to retrieve all available channels from the Heyy system. Use when you need to get a complete list of channels with their details including name, type, status, and timestamps.

  • List Message Templates

    Tool to retrieve all message templates available in the Heyy system. Use when you need to view all existing templates for messaging.

  • Update Webhook

    Tool to update a webhook's URL and active status. Use when you need to modify an existing webhook's endpoint or enable/disable it.

Setup

Setup guide

  1. 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Find Heyy in the MCP directory and click Connect. 3. You'll be prompted to paste an API key — generate one in your Heyy account under Settings > API Keys. 4. Copy the key and paste it into Switchy, then click Authorize. 5. Switchy confirms the connection and lists the tools now available. 6. Open any Space, type '@Heyy list contacts' and send — if you see a response listing your contacts, the integration is live. 7. From now on, @mention Heyy in any message to invoke tools like creating labels, adding contacts, or managing webhooks.

What teammates see: by default, memories from Heyy are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

Add Lead from Call

@Heyy create a contact named Jordan Lee with email jordan@example.com and phone +1-555-0199, then apply the label 'Q1 Pipeline'.
Open in a Space →

Build Custom Attribute

@Heyy create a contact attribute called 'Subscription Tier' with type text so we can segment customers by plan.
Open in a Space →

Set Up Event Webhook

@Heyy create a webhook pointing to https://example.com/heyy-events that fires on new message events.
Open in a Space →

Organize by Label

@Heyy create a label called 'EMEA Prospects' so we can filter contacts by geography.
Open in a Space →

Audit Webhooks

@Heyy list all webhooks and show me the URL and event types for each one.
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@Heyy show me all the contacts labeled 'enterprise-trial' who haven't been messaged in the last 30 days

Output

Based on your Heyy account, here are 12 contacts with the 'enterprise-trial' label and no recent message activity: • Sarah Chen (sarah@acmecorp.com) — last contact 45 days ago • Marcus Williams (m.williams@techstart.io) — last contact 38 days ago • Jennifer Park (jpark@innovate.co) — last contact 33 days ago [9 more contacts listed with similar details] All contacts include phone numbers and custom attributes like 'trial_start_date' and 'company_size'. Would you like me to draft a re-engagement message for this segment?

Notes

This example demonstrates Heyy's contact filtering and label system. The MCP requires read access to contacts and labels. Note that 'last message' timing depends on your message history being tracked in Heyy — if you use multiple communication channels outside Heyy, this data may be incomplete.

Prompt

@Heyy create a new contact for Jamie Rodriguez at jamie@newclient.com, phone +1-555-0199, and tag them with 'q1-onboarding' and 'premium-tier'

Output

Contact created successfully in Heyy: **Jamie Rodriguez** • Email: jamie@newclient.com • Phone: +1-555-0199 • Labels: q1-onboarding, premium-tier • Contact ID: cnt_8x7k2m9p The 'q1-onboarding' label already existed in your account. I created the 'premium-tier' label as it wasn't found. This contact is now visible in your Heyy dashboard and will appear in any filtered views using these labels.

Notes

This showcases Heyy's contact creation and auto-labeling workflow. The MCP will create missing labels on-the-fly, which is convenient but can lead to label sprawl if prompts contain typos. Always verify label names match your existing taxonomy. Requires write access to contacts and labels.

Prompt

@Heyy set up a webhook to notify our #customer-alerts Slack channel whenever a contact replies to a message, and show me all currently active webhooks

Output

Webhook created successfully: **New Webhook: Customer Reply Alerts** • Event: message.received • Endpoint: https://hooks.slack.com/services/T00/B00/xxx • Status: Active • Webhook ID: wh_4n8j2k1m **All Active Webhooks (3 total):** 1. Customer Reply Alerts (just created) 2. New Contact Notifications → Zapier endpoint 3. Label Changes → Internal API (created 14 days ago) The new webhook will fire immediately when contacts send inbound messages through any Heyy channel. Test it by sending a message to one of your Heyy numbers.

Notes

This example pairs webhook creation with a list operation to show configuration management. Webhooks require you to provide a valid HTTPS endpoint — the MCP cannot generate Slack webhook URLs for you. Be cautious: webhook events can trigger rapidly during high-volume periods, potentially overwhelming your endpoint or hitting rate limits on the receiving service.

Use-case deep-dives

Onboarding drip campaign setup

When Heyy fits a 2-person team running customer onboarding

A two-person SaaS team sends 40 onboarding emails a week to trial users across SMS and email. Heyy's contact creation and label tools let you tag users by trial stage (day 1, day 3, churned) and trigger sequences without leaving your AI workspace. The custom attribute tool handles edge cases like plan tier or referral source. This works if your onboarding logic is simple and you're under 500 contacts a month. Above that threshold, you'll hit rate limits on contact creation and the lack of bulk import becomes painful. If your sequences branch on more than three conditions, you need a proper marketing automation tool. For small teams running linear drips with light segmentation, Heyy keeps the setup in one place and the API key is the only auth you manage.

Support ticket handoff tagging

Where Heyy wins for 4-person support teams doing triage

A four-person support team handles 80 inbound messages a day across WhatsApp and SMS. During morning triage, they label contacts by urgency (hot, warm, cold) and assign custom attributes for product area or bug type. Heyy's label and attribute tools let the AI assistant apply these tags in real time as the team reviews threads, so handoff context is already in place when someone picks up a follow-up. The webhook tool sends escalations to Slack when a hot label gets added. This setup breaks down if your team needs to search historical messages by content or if you're routing based on skill-based queues. Heyy doesn't expose message search or advanced routing logic. For small teams doing simple triage with tag-based handoff, Heyy keeps the workflow tight and the 13 tools cover the common moves without requiring a CRM.

Event attendee follow-up batching

When Heyy handles post-event outreach for small conferences

A three-person events team runs quarterly meetups with 60 attendees and sends follow-up messages over SMS and email. After each event, they create contacts in Heyy with custom attributes for session attended and interest tags, then batch-send personalized follow-ups. The label tool groups attendees by interest (investor, partner, customer) and the webhook tool notifies the team when someone replies. This works if your attendee list is under 200 per event and you're sending one or two follow-up waves. Beyond that, the lack of bulk contact import and template versioning becomes a bottleneck. If you're running multi-day conferences with complex segmentation, you need a dedicated event platform. For small recurring events where follow-up is manual and personalized, Heyy keeps the contact data and outreach in one workspace without forcing you into a heavyweight CRM.

Frequently asked

What does the Heyy MCP let me do in Switchy?

The Heyy MCP connects your Heyy contact database to Switchy's AI workspace. Your team can create contacts, add custom attributes, apply labels for segmentation, and manage webhooks for real-time notifications—all through natural language. It's useful when you're syncing customer data or automating contact workflows without switching between tools.

Do I need admin access to connect Heyy?

You need an API key from your Heyy account, which typically requires admin or developer permissions to generate. The key grants full access to contact management and webhook configuration, so only connect it if you're comfortable giving Switchy write access to your contact database and notification settings.

Can the Heyy MCP send messages to contacts?

No. The MCP focuses on contact management—creating contacts, adding attributes, applying labels, and configuring webhooks. It doesn't send messages or interact with Heyy's messaging channels. If you need to send messages, use Heyy's interface directly or integrate a dedicated messaging MCP alongside this one.

Why use this instead of Heyy's API directly?

The MCP removes the need to write code or remember API endpoints. Your team can say 'create a contact for John with the label VIP customer' and Switchy handles the API calls. It's faster for ad-hoc tasks and non-technical teammates, but if you're building automated pipelines, Heyy's API gives you more control.

Who on my team should connect the Heyy MCP?

Whoever manages your contact database or customer segmentation—usually a CRM admin, operations lead, or customer success manager. Since the API key has write access, avoid connecting it to shared workspaces where junior team members might accidentally delete labels or attributes. One connection per workspace is enough.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.