Bring Whatsapp Api
to CrewAI
Learn how to connect Zenvia Conversion to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Zenvia Conversion MCP Server?
Connect your Zenvia Conversion (formerly Sirena) account to any AI agent to automate your sales and support workflows. Manage leads, send WhatsApp messages, and track interactions through natural conversation.
What you can do
- Lead Management — Create and manage leads from multiple sources and track their conversion into prospects.
- WhatsApp Messaging — Send free-text messages to active conversations or initiate new ones using HSM templates.
- Team Coordination — List agents, groups, and labels to maintain a clear overview of your team's structure and assignments.
- Interaction History — View full interaction logs and histories for any prospect to maintain context across your sales pipeline.
- Workflow Automation — Streamline repetitive tasks like lead creation and follow-ups using natural language commands.
How it works
1. Subscribe to this server
2. Enter your Zenvia Conversion API Key (from API Access app)
3. Start managing your sales conversations from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Sales Teams — manage leads and WhatsApp conversations more efficiently without switching apps.
- Support Agents — quickly respond to customer queries and track interaction history.
- Marketing Managers — monitor lead acquisition and conversion rates across different groups and agents.
Built-in capabilities (10)
You can include contact details and an initial message (comment). Create a new lead in Zenvia Conversion
Get account information
Get detailed information about a specific prospect
List agents in the account
List agent groups
List interactions for a prospect
List labels
List all prospects in Zenvia Conversion
Send a message to a prospect
Send a message template (HSM) to a prospect
Why CrewAI?
When paired with CrewAI, Zenvia Conversion becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Zenvia Conversion tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
Zenvia Conversion in CrewAI
Zenvia Conversion and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Zenvia Conversion to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Zenvia Conversion in CrewAI
The Zenvia Conversion 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Zenvia Conversion for CrewAI
Every tool call from CrewAI to the Zenvia Conversion MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
What is the difference between a Lead and a Prospect?
In Zenvia Conversion, a Lead is an initial contact entry. Once a lead is processed or created via the API, it becomes a Prospect in your CRM pipeline.
Can I start a WhatsApp conversation with a new number?
Yes, but you must use an approved HSM template to initiate a new conversation. Free-text messages can only be sent to active conversations within the 24-hour window.
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.
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.