[PR #1007] [MERGED] fix(evolutionapi): enable integration env flags (n8n/openai/evoai) and update #16315

New Issue

GiteaMirror · 2026-07-14T23:19:00-05:00

GiteaMirror commented

2026-07-14 23:19:00 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/1007
Author: @Siumauricio
Created: 7/14/2026
Status: ✅ Merged
Merged: 7/14/2026
Merged by: @Siumauricio

Base: canary ← Head: fix/evolutionapi

📝 Commits (1)

fb64197 fix(evolutionapi): enable integration flags and update version

📊 Changes

3 files changed (+16 additions, -2 deletions)

View changed files

📝 blueprints/evolutionapi/docker-compose.yml (+8 -1)
📝 blueprints/evolutionapi/meta.json (+1 -1)
📝 blueprints/evolutionapi/template.toml (+7 -0)

📄 Description

Problem

After Evolution API v2.3.x, integrations (n8n, OpenAI, EvoAI, Dify) must be explicitly enabled via environment variables. The template did not set any of these flags, so every attempt to configure an integration failed with errors like `Error: N8n is disabled` (#430).

The template was also pulling `evoapicloud/evolution-api:latest` (unpinned) while `meta.json` still claimed `v2.1.2`.

Changes

template.toml / docker-compose.yml: add the integration enable flags introduced in Evolution API v2.3.x, defaulting to `true` and exposed as template env vars so users can toggle them:
- `N8N_ENABLED`, `OPENAI_ENABLED`, `EVOAI_ENABLED`, `DIFY_ENABLED`, `TYPEBOT_ENABLED` (+ `TYPEBOT_API_VERSION`), `CHATWOOT_ENABLED`
docker-compose.yml: pin image to `evoapicloud/evolution-api:v2.3.7` (latest stable release of the now-canonical `evolution-foundation/evolution-api` repo; 2.4.0 is still RC)
meta.json: bump version `v2.1.2` → `v2.3.7`

Verification (deployed on demo instance)

`GET /` → `{"status":200,"message":"Welcome to the Evolution API, it is working!","version":"2.3.7",...}`
Created a test instance, then `GET /n8n/find/:instance`, `/openai/find`, `/evoai/find`, `/dify/find` → all return `200 []` instead of the "disabled" error
`POST /n8n/create/:instance` (the exact flow from the issue screenshot) → 201, bot created successfully
`node build-scripts/generate-meta.js --check` → 476 templates validated

Closes #430

🤖 Generated with Claude Code

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Dokploy/templates/pull/1007 **Author:** [@Siumauricio](https://github.com/Siumauricio) **Created:** 7/14/2026 **Status:** ✅ Merged **Merged:** 7/14/2026 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `canary` ← **Head:** `fix/evolutionapi` --- ### 📝 Commits (1) - [`fb64197`](https://github.com/Dokploy/templates/commit/fb64197738a529e83e4fe4e384b95be4208a6aad) fix(evolutionapi): enable integration flags and update version ### 📊 Changes **3 files changed** (+16 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/evolutionapi/docker-compose.yml` (+8 -1) 📝 `blueprints/evolutionapi/meta.json` (+1 -1) 📝 `blueprints/evolutionapi/template.toml` (+7 -0) </details> ### 📄 Description ## Problem After Evolution API v2.3.x, integrations (n8n, OpenAI, EvoAI, Dify) must be explicitly enabled via environment variables. The template did not set any of these flags, so every attempt to configure an integration failed with errors like **\`Error: N8n is disabled\`** (#430). The template was also pulling \`evoapicloud/evolution-api:latest\` (unpinned) while \`meta.json\` still claimed \`v2.1.2\`. ## Changes - **template.toml / docker-compose.yml**: add the integration enable flags introduced in Evolution API v2.3.x, defaulting to \`true\` and exposed as template env vars so users can toggle them: - \`N8N_ENABLED\`, \`OPENAI_ENABLED\`, \`EVOAI_ENABLED\`, \`DIFY_ENABLED\`, \`TYPEBOT_ENABLED\` (+ \`TYPEBOT_API_VERSION\`), \`CHATWOOT_ENABLED\` - **docker-compose.yml**: pin image to \`evoapicloud/evolution-api:v2.3.7\` (latest stable release of the now-canonical \`evolution-foundation/evolution-api\` repo; 2.4.0 is still RC) - **meta.json**: bump version \`v2.1.2\` → \`v2.3.7\` ## Verification (deployed on demo instance) - \`GET /\` → \`{"status":200,"message":"Welcome to the Evolution API, it is working!","version":"2.3.7",...}\` - Created a test instance, then \`GET /n8n/find/:instance\`, \`/openai/find\`, \`/evoai/find\`, \`/dify/find\` → all return \`200 []\` instead of the "disabled" error - \`POST /n8n/create/:instance\` (the exact flow from the issue screenshot) → **201, bot created successfully** - \`node build-scripts/generate-meta.js --check\` → 476 templates validated Closes #430 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-07-14 23:19:00 -05:00

GiteaMirror closed this issue

2026-07-14 23:19:02 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#16315