Add Alicia Meta Ads v2 workflow with client management and reporting

[gabrjacinto]

📋 Description

This PR introduces a complete n8n workflow for "Alicia - Meta Ads v2", a WhatsApp-based assistant that provides Meta Ads insights and reporting for multiple client accounts.

Key Features:

• WhatsApp Integration: Receives messages via Evolution API webhook and processes requests mentioning "Alicia"
• Client Management: Maps 13 client names/aliases to their Meta Ads account IDs (Antonio Neto, Gabriel Jacinto, Dani Escudero, Agro, Escola de Música, Panmalhas, GFiX Store, Arte em Gelo, ITAG Tecnologia, Hi Dogz, Batata Bistrô, Caribbean Bronze, Larissa Kelleter)
• Flexible Date Handling: Supports multiple date presets (today, yesterday, this week, last 7/14/30 days, last month) with intelligent parsing from natural language
• Dual Reporting Modes:
  • Leads campaigns: Reports impressions, clicks, leads, and cost-per-lead
  • E-commerce campaigns (Hi Dogz, Batata Bistrô): Reports impressions, clicks, sales, and cost-per-sale
• AI-Powered Agent: Claude Opus-based agent with four specialized tools:
  • buscar_insights: Query Meta Ads metrics for specific accounts/campaigns
  • listar_campanhas: List all campaigns in an account
  • listar_conjuntos: List ad sets for accounts or campaigns
  • buscar_insights_multiplas_contas: Aggregate insights across multiple accounts when no specific client is mentioned
• Formatted Output: Portuguese (Brazil) formatted responses with proper currency formatting (R$), thousand separators, and emojis for visual clarity

Workflow Architecture:

1. Parse incoming WhatsApp messages
2. Filter for "Alicia" mentions and valid content
3. Calculate date ranges and detect client/report requests
4. Route to either:
   • Quick Report Path: Direct Meta Ads API call → formatted response (for specific client + report request)
   • AI Agent Path: Intelligent processing via Claude with tool access (for general queries or multi-account requests)
5. Send formatted response back via WhatsApp

🔗 Related Issue

N/A

🧪 Type of Change

• ✨ New feature (non-breaking change which adds functionality)

🧪 Testing

• Manual testing completed
• Functionality verified in development environment
• Tested with different connection types (if applicable)

The workflow has been tested with:

• WhatsApp message parsing from Evolution API
• Client name detection and aliasing
• Date range calculations for various presets
• Meta Ads API integration with proper token handling
• Both leads and e-commerce reporting formats
• AI agent tool invocation and response formatting

✅ Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have manually tested my changes thoroughly
• I have verified the changes work with different scenarios

📝 Additional Notes

The workflow uses a hardcoded Meta Ads access token embedded in the code nodes. For production deployment, this should be moved to n8n credentials management for better security.

The client mapping is implemented as an array to support multiple aliases per client and avoid key duplication issues. Aliases are sorted by length (longest first) to ensure more specific matches take precedence.

Date calculations properly handle timezone considerations by using UTC operations and the last_7d preset ends 2 days before today to account for incomplete data in Meta Ads reporting.

https://claude.ai/code/session_01TSV3FcRdbPFXKZUAftjEoQ

Summary by Sourcery

Add a new n8n workflow that powers the WhatsApp-based Alicia Meta Ads v2 assistant for multi-client Meta Ads insights and reporting.

New Features:

• Introduce a WhatsApp-triggered Meta Ads reporting assistant that supports multiple client accounts and aliases.
• Add intelligent date range handling with common reporting presets and natural language parsing for Meta Ads queries.
• Provide dual reporting flows for leads and e-commerce campaigns, including account-level and multi-account summaries via an AI agent with Meta Ads tooling.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds a new n8n workflow implementing the “Alicia - Meta Ads v2” WhatsApp assistant that parses Evolution API webhooks, maps client aliases to Meta Ads accounts, computes date ranges, routes between a quick-report path and an AI-agent path with Claude tools, calls the Meta Ads API for leads/e-commerce reports, and returns formatted Portuguese responses over WhatsApp.

File-Level Changes

Change	Details	Files
Introduce complete n8n workflow JSON for the Alicia Meta Ads v2 assistant	Define trigger node for Evolution API WhatsApp webhooks and initial parsing/validation logic for messages mentioning Alicia Implement client alias mapping for 13 Meta Ads accounts using an array structure and longest-alias matching to resolve the target account Add date-handling nodes that parse natural language presets into Meta Ads-compatible ranges with UTC handling and special logic for last_7d cutoffs Configure two reporting modes (leads vs e-commerce) with different metric selections and cost-per-lead/cost-per-sale calculations against Meta Ads APIs Set up branching between a quick-report path (direct API-to-response) and an AI-agent path powered by Claude Opus with four tools for insights, campaigns, ad sets, and multi-account aggregation Format responses in Brazilian Portuguese, including R$ currency formatting, thousand separators, emojis, and send them back via WhatsApp through Evolution API	n8n-alicia-meta-ads.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Since the Meta Ads access token is currently hardcoded in the workflow, please move it into n8n credentials or environment variables before merging to avoid leaking sensitive data and to simplify rotation.
• The client name/alias mapping sounds fairly complex; consider centralizing it into a single dedicated node or configuration structure and normalizing input (case, accents, whitespace) in one place to reduce the chance of mismatches and make future client additions simpler.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Since the Meta Ads access token is currently hardcoded in the workflow, please move it into n8n credentials or environment variables before merging to avoid leaking sensitive data and to simplify rotation.
- The client name/alias mapping sounds fairly complex; consider centralizing it into a single dedicated node or configuration structure and normalizing input (case, accents, whitespace) in one place to reduce the chance of mismatches and make future client additions simpler.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}