evolution-v2.4-upgrade-meta-integration

Upgrade Evolution API to 2.4.0-rc2 and configure Meta Cloud API webhooks.

5|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill evolution-v2-4-upgrade-meta-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolution-v2.4-upgrade-meta-integration
Source: https://github.com/rafael-fae/agent-ops-worflow/tree/main/archive/skills/devops/evolution-v2.4-upgrade-meta-integration
Command: npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill evolution-v2-4-upgrade-meta-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps operators safely upgrade Evolution API to the Meta Cloud API-compatible release, activate licensing, and avoid common deployment failures such as broken tunnels, stale nginx cache, and invalid instance IDs.

Core Features & Use Cases

  • Version Upgrade Guidance: Move from Evolution API v2.3.7 to 2.4.0-rc2 with the correct image tag and required database reset.
  • Meta Cloud API Integration: Configure WhatsApp Business webhooks, verify tokens, and dashboard settings for official Meta connectivity.
  • Infrastructure Pitfall Avoidance: Handle Cloudflare Tunnel routing, nginx reloads, licensing constraints, and known broken builds like homolog.
  • Use Case: A DevOps operator needs to restore a WhatsApp integration after upgrading containers and wants a reliable checklist for deployment, webhook validation, and post-upgrade verification.

Quick Start

Ask the Skill to guide you through upgrading Evolution API to 2.4.0-rc2, configuring the Meta Cloud API webhook, and validating the deployment end to end.

Frequently Asked Questions about evolution-v2.4-upgrade-meta-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade Evolution API to version 2.4.0-rc2 for Meta Cloud API integration?

To upgrade Evolution API to 2.4.0-rc2, update your container image tag and perform the required database reset to avoid stale instance states. This ensures compatibility with Meta Cloud API integration and prepares the system for licensing activation.

Why does my Meta Cloud API WhatsApp webhook fail after an Evolution API container upgrade?

Meta Cloud API WhatsApp webhooks often fail after an upgrade due to broken Cloudflare Tunnel routing or stale nginx cache. Reload nginx and verify your webhook token configuration in the Meta dashboard to restore proper instance connectivity.

What is the process for configuring WhatsApp Business webhooks with the Meta Cloud API?

Configuring WhatsApp Business webhooks involves setting the correct verify token and dashboard settings for official Meta connectivity. You must ensure your nginx and Cloudflare Tunnel routing properly expose the endpoint to receive Meta Cloud API callbacks.

Do I need to reset the database when upgrading Evolution API to 2.4.0-rc2?

Yes, a database reset is required when upgrading Evolution API to 2.4.0-rc2 to prevent invalid instance IDs and connection state errors. This clears stale data that could conflict with the new Meta Cloud API compatible release.

What are the common deployment pitfalls when wiring Meta WhatsApp through Cloudflare Tunnel and nginx?

Common deployment pitfalls include broken Cloudflare Tunnel routing, stale nginx cache requiring restarts, and using known broken builds like the homolog image. You must also handle licensing constraints and perform post-upgrade verification for instance state.