Q: Does Co-pilot actually work
I recently started testing Mazaal AI, specifically the Co-Pilot feature, as I was excited about its ability to generate workflows based on prompts. However, after attempting to create an automation to categorize my Gmail inbox at 5 PM daily, I’ve encountered issues where the Co-Pilot simply does not function as expected.
Despite providing a detailed and specific prompt (which your AI Writing Assistant confirmed as "great" and detailed), the workflow was not generated at all. Since this was the main feature I intended to use Mazaal for, I find the current experience disappointing.
I’d appreciate any insights into why this might be happening and whether there are known bugs or limitations affecting the Co-Pilot's ability to execute email-based automations.
Enod_MazaalAI
Apr 11, 2025A: Hi bourbonblackstudios,
Sorry for the inconvenience and wasting your time there! It turns out OpenAI/Anthropic API were down for a moment causing the issue of co-pilot not working. Thanks for flagging this btw, another opportunity to make copilot feature more robust.
Please try again and if issue persist, chat directly to us on our discord https://discord.gg/jM7nzyVF
bourbonblackstudiosI communicate here to help other summolings learn from my process. The co-pilot feature is now active but not working as expected. I prompted it to have an agent read and categorize emails based on subject body and certain parameters (more detailed than I can paste here) and the flow it crated was a new gmail trigger, custom gmail api, and send email trigger) Also creating an agent feature is down
My prompt was "At 5 PM daily, an AI agent should:
Access my Gmail inbox and scan all emails that are marked as read without deleting or marking them as unread. Categorize emails into the following sections based on sender, subject, and content: Client Communications (Past & Present):....(the rest cant fit in this chat) I had your co-pilot proof the prompt before creating it. Got the green light.
In short, there are limits to what you described - even today's latest MCP technologies will have hard time to do that.
I think copilot did it's best for your workflow. Currently all actions will be limited by the API actions and triggers we support - take a look into gmail for example https://mazaal.ai/en/apps/gmail - it's possible to send email and receive one and everything else will be [1/2]
custom gmail api call - which is expected.
Creating agent was disrupted due to LLM APIs behind the scenes and apologies for that. We just improved it by making it dynamic - so now if one LLM is down, we switch to another provider - resulting more robust agent and copilot workflow creation endpoints.
[2/2]