Automate weekly marketing reports with GoMarble MCP, Claude AI & Gmail
Automated Marketing Analytics Report with AI Agent How it works Transform your marketing data into actionable insights with this intelligent automation workflow. The system combines scheduled triggers with AI-powered analysis to deliver comprehensive marketing reports directly to your inbox. Key Features: Scheduled automated reporting (daily, weekly, or monthly) AI-powered data analysis using advanced language models Multi-platform marketing data integration via GoMarble MCP Intelligent report generation with actionable recommendations Direct email delivery of formatted reports Set up steps Prerequisites: GoMarble MCP account and API access Gmail account for report delivery n8n instance (cloud or self-hosted) Configuration Time: ~15-20 minutes Step-by-step setup: Connect GoMarble MCP to n8n Follow the integration guide: GoMarble n8n Setup Configure your marketing platform credentials (Google Ads, Facebook Ads, Analytics) Configure the Schedule Trigger Set your preferred reporting frequency Choose optimal timing for data availability Customize the Report Prompt Define specific metrics and KPIs to track Set analysis parameters and report format preferences Set up AI Agent Configuration Choose between Anthropic Claude or OpenAI models Configure the GoMarble MCP tools for your marketing platforms Configure Gmail Integration Set recipient email addresses Customize email template and subject line Advanced Configuration: Add conditional logic for performance thresholds Include custom data visualization requests Set up alert triggers for significant metric changes What you'll get Automated Intelligence: Regular marketing performance analysis without manual effort Cross-Platform Insights: Unified view of Google Ads, Facebook Ads, and Analytics data AI-Powered Recommendations: Strategic insights and optimization suggestions Professional Reports: Well-formatted, executive-ready marketing summaries Scalable Solution: Easy to extend with additional marketing platforms or custom metrics Perfect for marketing teams, agencies, and business owners who want to stay on top of their marketing performance with minimal manual work.
By Sankalp DevAutomatic jest test generation for GitHub PRs with dual AI review
Workflow: Automatic Unit Test Creator from GitHub 🏗️ Architecture Overview This workflow listens for GitHub pull-request events, analyzes changed React/TypeScript files, auto-generates Jest tests via AI, has them reviewed by a second AI pass, and posts suggestions back as PR comments: GitHub Webhook → PR opened or updated Fetch & Diff → Retrieve raw diff of changed files Filter & Split → Isolate .tsx files & their diffs Fetch File Contents → Provide full context for tests Test Maker Agent → Generate Jest tests for diff hunks Code Reviewer Agent → Refine tests for style & edge-cases Post PR Comment → Sends suggested tests back to GitHub 📦 Node-by-Node Breakdown mermaid flowchart LR A[Webhook: /github/pr-events] --> B[GitHub: Get PR] B --> C[Function: Parse diff_url + owner/repo] C --> D[HTTP Request: GET diff_url] D --> E[Function: Split on "diff --git"] E --> F[Filter: /\.tsx$/] F --> G[GitHub: Get File Contents] G --> H[Test Maker Agent] H --> I[Code Reviewer Agent] I --> J[Function: Build Comment Payload] J --> K[HTTP Request: POST to PR Comments] Webhook: GitHub PR Events Type: HTTP Webhook (/webhook/github/pr-events) Subscribed Events: pullrequest.opened, pullrequest.synchronize GitHub: Get PR Node: GitHub Action: "Get Pull Request" Inputs: owner, repo, pull_number Function: Parse diff_url + owner/repo Extracts: diff_url (e.g. …/pulls/123.diff) owner, repo, mergecommitsha HTTP Request: GET diff_url Fetches unified-diff text for the PR. Function: Split on "diff --git" Splits the diff into file-specific segments. Filter: /.tsx$/ Keeps only segments where the file path ends with .tsx. GitHub: Get File Contents For each .tsx file, fetches the latest blob via GitHub API. Test Maker Agent Prompt: "Generate Jest unit tests covering only the behaviors changed in these diff hunks." Output: Raw Jest test code. Code Reviewer Agent Reads file + generated tests Prompt: "Review and improve these tests for readability, edge-cases, and naming conventions." Output: Polished test suite. Function: Build Comment Payload Wraps tests in TypeScript fences: ts // generated tests… Constructs JSON: json { "body": "<tests>" } HTTP Request: POST to PR Comments URL: https://api.github.com/repos/{owner}/{repo}/issues/{pull_number}/comments Body: Contains the suggested tests. 🔍 Design Rationale & Best Practices Focused Diff Analysis Targets only .tsx files to cover UI logic. Two-Stage AI Separate "generate" + "review" steps mimic TDD + code review. Stateless Functions Pure JS for parsing & transformation, easy to test. Non-Blocking PR Comments Asynchronous suggestions—developers aren't blocked. Scoped Permissions GitHub token limited to reading PRs & posting comments.
By VarritechVerify email deliverability with Hunter
Companion workflow for Hunter node docs
By amudhan