Skill

Automate WhatsApp Business Communications

Automates WhatsApp Business messaging, templates, and media via Composio's Rube MCP toolkit, with the 24-hour rule.

Works with whatsapprube

78
Spark score
out of 100
Updated last month
Version 13.1.0
Models
universal

Add to Favorites

Why it matters

Streamline your customer interactions on WhatsApp Business by automating message sending, replies, and media sharing. This skill leverages Rube MCP to manage your WhatsApp Business API connection and execute core communication workflows efficiently.

Outcomes

What it gets done

01

Send text, template, and media messages to contacts.

02

Automate replies to incoming customer messages.

03

Manage WhatsApp Business profile and message templates.

04

Share contact information directly via WhatsApp.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-whatsapp-automation | bash

Overview

WhatsApp Business Automation via Rube MCP

Automates WhatsApp Business messaging, templates, media, and profile management through Composio's toolkit via Rube MCP, centered on Meta's 24-hour conversation window and template approval rules. Use for WhatsApp Business automation once Rube MCP is connected with an ACTIVE whatsapp toolkit connection and a WhatsApp Business API account; template messages are required outside the 24-hour window.

What it does

This skill automates WhatsApp Business operations through Composio's WhatsApp toolkit accessed via Rube MCP (no API keys, just the https://rube.app/mcp endpoint plus OAuth), and explicitly requires a WhatsApp Business API account rather than regular WhatsApp. It covers six workflows: sending free-form text messages (requires E.164-formatted phone numbers and resolving a phone_number_id first); sending Meta-approved template messages (checking template approval status, matching variable count/format, and getting the language code right against the specific approved translation); sending media (images/documents/audio/video via an upload-then-send-by-ID flow, or directly by public HTTPS URL, with size limits varying by type - images 5MB, videos 16MB, documents 100MB); replying to a specific incoming message (quoting it, which requires the original message to still exist and be within the 24-hour window); managing the business profile and creating new templates (subject to Meta review, lowercase-with-underscores naming, category affecting pricing/approval); and sharing contact cards.

Its central operating constraint is the 24-hour messaging window: a conversation opens only when the customer messages first, free-form replies are allowed within 24 hours of their last message, and after that only approved template messages (which can themselves re-open the window) are permitted - business-initiated outreach outside this window always requires a template. Other documented pitfalls: uploaded media IDs are temporary and expire, so they should be used promptly after upload; stickers specifically require WebP format at 512x512 pixels; template review can take up to 24 hours and rejected templates must be fixed and resubmitted; template variables use {{1}}, {{2}} double-curly-brace placeholders; and template messages cost money per conversation, on top of per-number/per-account rate limits.

When to use - and when NOT to

Use this skill for any WhatsApp Business automation task - sending messages or templates, uploading/sending media, replying within a conversation, managing templates/profile, or sharing contacts - once Rube MCP is connected and the whatsapp toolkit shows an ACTIVE connection via RUBE_MANAGE_CONNECTIONS. Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.

It is not usable with a regular consumer WhatsApp account - a WhatsApp Business API account is a hard prerequisite - and business-initiated messaging outside the 24-hour window is impossible without an already-approved template, regardless of message content.

Inputs and outputs

Input is a WhatsApp Business action request - a message or template to send, media to upload/send, a reply to a specific message, or a template/profile management task. Output is the tool call result - a sent message/template, an uploaded media ID, a reply confirmation, or template approval status - following the phone-number-resolution and 24-hour-window conventions documented for each workflow.

# Setup: add Rube MCP endpoint
https://rube.app/mcp

Integrations

Built on Composio's WhatsApp toolkit surfaced through Rube MCP tools (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS) and the full WHATSAPP_* tool family for messages, templates, media, and business profile management, ultimately backed by Meta's WhatsApp Business API and its template-approval process.

Who it's for

Developers or agents automating WhatsApp Business communication - customer messaging, templated outreach, media sharing, or contact sharing - through an MCP-connected toolkit rather than direct WhatsApp Business API integration.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.