Where do I find my Phone Number ID and Access Token?

Log in to the [**Meta Developer Portal**](https://developers.facebook.com/), select your App, and navigate to the WhatsApp > Getting Started section for the ID, and the App Settings for the System User Access Token.

What is the 24-hour window policy?

WhatsApp restricts business-initiated free-text messages. You can only send free-form text if the user has messaged you in the last 24 hours. Outside this window, you must use a pre-approved Template.

INSTANT PLUG AND PLAY

WSLA (WhatsApp) MCP Server for CrewAIGive CrewAI instant access to 5 tools to Get Whatsapp Media Details, List Whatsapp Templates, Send Whatsapp Reaction, and more

Name: WSLA (WhatsApp)
Availability: InStock
Author: Vinkius

Built by Vinkius GDPR 5 Tools Framework

Connect your CrewAI agents to WSLA (WhatsApp) through Vinkius, pass the Edge URL in the `mcps` parameter and every WSLA (WhatsApp) tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Use with Your AI Agent

Ask AI about this App Connector for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The WSLA (WhatsApp) app connector for CrewAI is a standout in the Industry Titans category — giving your AI agent 5 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="WSLA (WhatsApp) Specialist",
    goal="Help users interact with WSLA (WhatsApp) effectively",
    backstory=(
        "You are an expert at leveraging WSLA (WhatsApp) tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in WSLA (WhatsApp) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 5 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About WSLA (WhatsApp) MCP Server

Connect your WhatsApp Business Platform (via Meta Cloud API) to any AI agent to automate your customer communications. WSLA provides a direct bridge to Meta's infrastructure for reliable, scalable messaging.

When paired with CrewAI, WSLA (WhatsApp) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call WSLA (WhatsApp) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Conversational AI — Send instant text messages to any WhatsApp number during active customer support windows.
Business Notifications — Use pre-approved message templates for proactive alerts, appointment reminders, and shipping updates.
Interactive Reactions — Allow your AI agent to react to incoming customer messages with emojis for more natural engagement.
Template Management — List and search all approved templates associated with your WhatsApp Business Account.
Media Intelligence — Retrieve details for incoming media to enable multi-modal interactions through your AI agent.

The WSLA (WhatsApp) MCP Server exposes 5 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 5 WSLA (WhatsApp) tools available for CrewAI

When CrewAI connects to WSLA (WhatsApp) through Vinkius, your AI agent gets direct access to every tool listed below — spanning whatsapp-api, conversational-ai, business-messaging, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

get_whatsapp_media_details

Get media details

list_whatsapp_templates

List message templates

send_whatsapp_reaction

React to a WhatsApp message

send_whatsapp_template

Send a WhatsApp template message

send_whatsapp_text

Send a text message via WhatsApp

Connect WSLA (WhatsApp) to CrewAI via MCP

Follow these steps to wire WSLA (WhatsApp) into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 5 tools from WSLA (WhatsApp)

Why Use CrewAI with the WSLA (WhatsApp) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with WSLA (WhatsApp) through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

WSLA (WhatsApp) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the WSLA (WhatsApp) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries WSLA (WhatsApp) for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries WSLA (WhatsApp), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain WSLA (WhatsApp) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries WSLA (WhatsApp) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for WSLA (WhatsApp) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with WSLA (WhatsApp) immediately.

"Send a WhatsApp message 'Welcome to our service!' to +1234567890."

"List all approved templates for my business account."

Troubleshooting WSLA (WhatsApp) MCP Server with CrewAI

Common issues when connecting WSLA (WhatsApp) to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

WSLA (WhatsApp) + CrewAI FAQ

Common questions about integrating WSLA (WhatsApp) MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.