whatsapp-automation

sickn33/antigravity-awesome-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill whatsapp-automation
0 commentsdiscussion
summary

Automate WhatsApp Business operations through Composio's WhatsApp toolkit via Rube MCP.

skill.md

WhatsApp Business Automation via Rube MCP

Automate WhatsApp Business operations through Composio's WhatsApp toolkit via Rube MCP.

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active WhatsApp connection via RUBE_MANAGE_CONNECTIONS with toolkit whatsapp
  • Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  • WhatsApp Business API account required (not regular WhatsApp)

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit whatsapp
  3. If connection is not ACTIVE, follow the returned auth link to complete WhatsApp Business setup
  4. Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. Send a Text Message

When to use: User wants to send a text message to a WhatsApp contact

Tool sequence:

  1. WHATSAPP_GET_PHONE_NUMBERS - List available business phone numbers [Prerequisite]
  2. WHATSAPP_SEND_MESSAGE - Send a text message [Required]

Key parameters:

  • to: Recipient phone number in international format (e.g., '+14155551234')
  • body: Message text content
  • phone_number_id: Business phone number ID to send from

Pitfalls:

  • Phone numbers must be in international E.164 format with country code
  • Messages outside the 24-hour window require approved templates
  • The 24-hour window starts when the customer last messaged you
  • Business-initiated conversations require template messages first

2. Send Template Messages

When to use: User wants to send pre-approved template messages for outbound communication

Tool sequence:

  1. WHATSAPP_GET_MESSAGE_TEMPLATES - List available templates [Prerequisite]
  2. WHATSAPP_GET_TEMPLATE_STATUS - Check template approval status [Optional]
  3. WHATSAPP_SEND_TEMPLATE_MESSAGE - Send the template message [Required]

Key parameters:

  • template_name: Name of the approved template
  • language_code: Template language (e.g., 'en_US')
  • to: Recipient phone number
  • components: Template variable values and parameters

Pitfalls:

  • Templates must be approved by Meta before use
  • Template variables must match the expected count and format
  • Sending unapproved or rejected templates returns errors
  • Language code must match an approved translation of the template

3. Send Media Messages

When to use: User wants to send images, documents, or other media

Tool sequence:

  1. WHATSAPP_UPLOAD_MEDIA - Upload media to WhatsApp servers [Required]
  2. WHATSAPP_SEND_MEDIA_BY_ID - Send media using the uploaded media ID [Required] OR
  3. WHATSAPP_SEND_MEDIA - Send media using a public URL [Alternative]

Key parameters:

  • media_url: Public URL of the media (for SEND_MEDIA)
  • media_id: ID from upload response (for SEND_MEDIA_BY_ID)
  • type: Media type ('image', 'document', 'audio', 'video', 'sticker')
  • caption: Optional caption for the media

Pitfalls:

  • Uploaded media IDs are temporary and expire after a period
  • Media size limits vary by type (images: 5MB, videos: 16MB, documents: 100MB)
  • Supported formats: images (JPEG, PNG), videos (MP4, 3GPP), documents (PDF, etc.)
  • SEND_MEDIA requires a publicly accessible HTTPS URL

4. Reply to Messages

When to use: User wants to reply to an incoming WhatsApp message

Tool sequence:

  1. WHATSAPP_SEND_REPLY - Send a reply to a specific message [Required]

Key parameters:

  • message_id: ID of the message being replied to
  • to: Recipient phone number
  • body: Reply text content

Pitfalls:

  • message_id must be from a message received within the 24-hour window
  • Replies appear as quoted messages in the conversation
  • The original message must still exist (not deleted) for the quote to display

5. Manage Business Profile and Templates

When to use: User wants to view or manage their WhatsApp Business profile

Tool sequence:

  1. WHATSAPP_GET_BUSINESS_PROFILE - Get business profile details [Optional]
  2. WHATSAPP_GET_PHONE_NUMBERS - List registered phone numbers [Optional]
  3. WHATSAPP_GET_PHONE_NUMBER - Get details for a specific number [Optional]
  4. WHATSAPP_CREATE_MESSAGE_TEMPLATE - Create a new template [Optional]
  5. WHATSAPP_GET_MESSAGE_TEMPLATES - List all templates [Optional]

Key parameters:

  • phone_number_id: Business phone number ID
  • template_name: Name for the new template
  • category: Template category (MARKETING, UTILITY, AUTHENTICATION)
  • language: Template language code

Pitfalls:

  • New templates require Meta review before they can be used
  • Template names must be lowercase with underscores (no spaces)
  • Category affects pricing and approval criteria
  • Templates have specific formatting requirements for headers, body, and buttons

6. Share Contacts

When to use: User wants to send contact information via WhatsApp

Tool sequence:

  1. WHATSAPP_SEND_CONTACTS - Send contact cards [Required]

Key parameters:

  • to: Recipient phone number
  • contacts: Array of contact objects with name, phone, email details

Pitfalls:

  • Contact objects must follow the WhatsApp Business API contact schema
  • At least a name field is required for each contact
  • Phone numbers in contacts should include country codes

Common Patterns

24-Hour Messaging Window

  • Customers must message you first to open a conversation window
  • Within 24 hours of their last message, you can send free-form messages
  • After 24 hours, only approved template messages can be sent
  • Template messages can re-open the conversation window

Phone Number Resolution

1. Call WHATSAPP_GET_PHONE_NUMBERS
2. Extract phone_number_id for your business number
3. Use phone_number_id in all send operations

Media Upload Flow

1. Call WHATSAPP_UPLOAD_MEDIA with the file
2. Extract media_id from response
3. Call WHATSAPP_SEND_MEDIA_BY_ID with media_id
4. OR use WHATSAPP_SEND_MEDIA with a public URL directly

Known Pitfalls

Phone Number Format:

  • Always use E.164 format: +[country code][number] (e.g., '+14155551234')
  • Do not include dashes, spaces, or parentheses
  • Country code is required; local numbers without it will fail

Messaging Restrictions:

  • Business-initiated messages require templates outside the 24-hour window
  • Template messages cost money per conversation
  • Rate limits apply per phone number and per account

Media Handling:

  • Uploaded media expires; use promptly after upload
  • Media URLs must be publicly accessible HTTPS
  • Stickers have specific requirements (WebP format, 512x512 pixels)

Template Management:

  • Template review can take up to 24 hours
  • Rejected templates need to be fixed and resubmitted
  • Template variables use double curly braces: {{1}}, {{2}}, etc.

Quick Reference

Task Tool Slug Key Params
Send message WHATSAPP_SEND_MESSAGE to, body
Send template WHATSAPP_SEND_TEMPLATE_MESSAGE template_name, to, language_code
Upload media WHATSAPP_UPLOAD_MEDIA (file params)
Send media by ID WHATSAPP_SEND_MEDIA_BY_ID media_id, to, type
Send media by URL WHATSAPP_SEND_MEDIA media_url, to, type
Reply to message WHATSAPP_SEND_REPLY message_id, to, body
Send contacts WHATSAPP_SEND_CONTACTS to, contacts
Get media WHATSAPP_GET_MEDIA media_id
List phone numbers WHATSAPP_GET_PHONE_NUMBERS (none)
Get phone number WHATSAPP_GET_PHONE_NUMBER phone_number_id
Get business profile WHATSAPP_GET_BUSINESS_PROFILE phone_number_id
Create template WHATSAPP_CREATE_MESSAGE_TEMPLATE template_name, category, language
List templates WHATSAPP_GET_MESSAGE_TEMPLATES (none)
Check template status WHATSAPP_GET_TEMPLATE_STATUS template_id

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

how to use whatsapp-automation

How to use whatsapp-automation on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add whatsapp-automation
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill whatsapp-automation

The skills CLI fetches whatsapp-automation from GitHub repository sickn33/antigravity-awesome-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/whatsapp-automation

Reload or restart Cursor to activate whatsapp-automation. Access the skill through slash commands (e.g., /whatsapp-automation) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.439 reviews
  • Kofi Lopez· Dec 12, 2024

    Solid pick for teams standardizing on skills: whatsapp-automation is focused, and the summary matches what you get after install.

  • Chaitanya Patil· Dec 8, 2024

    Solid pick for teams standardizing on skills: whatsapp-automation is focused, and the summary matches what you get after install.

  • Tariq Chawla· Dec 4, 2024

    whatsapp-automation has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Piyush G· Nov 27, 2024

    We added whatsapp-automation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ishan Chen· Nov 27, 2024

    Useful defaults in whatsapp-automation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Maya Kim· Nov 23, 2024

    whatsapp-automation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Naina Johnson· Nov 3, 2024

    We added whatsapp-automation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Layla Mensah· Oct 22, 2024

    whatsapp-automation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Shikha Mishra· Oct 18, 2024

    whatsapp-automation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Arjun Patel· Oct 18, 2024

    I recommend whatsapp-automation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 39

1 / 4