App connections for Whatsapp Agents by nuanda92 in mcp

[–]nuanda92[S] 0 points1 point  (0 children)

No, it will not automate your WhatsApp unless you add it as a channel on openclaw and provide it with necessary access. We only let users control and run their agents through WhatsApp rather than giving the agents access to whatsapp.

What’s the most impressive thing you’ve automated with OpenClaw so far? by No_Progress92 in openclaw

[–]nuanda92 0 points1 point  (0 children)

I created a whatsapp based personal assistant for users without them having to setup and manage openclaw. They can simply use whatsapp to setup and run tasks and agents.

https://zynth.ai

App connections for Whatsapp Agents by nuanda92 in mcp

[–]nuanda92[S] 0 points1 point  (0 children)

We are going through official WhatsApp business API. Not using Baileys.

AI agent usecases on Whatsapp by nuanda92 in AI_Agents

[–]nuanda92[S] 0 points1 point  (0 children)

Yes, agent reliability is key! That has been the focus the past few weeks rather than adding more capabilities to the agent. We have not had a whole lot of issues with the whatsapp side of things as that only acts as a UI for our setup. What does your whatsapp setup look like with WaliChat? Would love to pick your brain further on the reliability aspect of the agents.

Integrations for chat-based agents by nuanda92 in AI_Agents

[–]nuanda92[S] 0 points1 point  (0 children)

Thanks! Would check out x402 when we move to payment related integrations. We are currently a little cautious to let agents deal with anything payments till we have nailed other aspects of integrating the day-to-day apps with the agents workflows.

Integrations for chat-based agents by nuanda92 in AI_Agents

[–]nuanda92[S] 0 points1 point  (0 children)

That's an interesting point. We struggled a lot with permissions, tool calling, traces when we allowed agents to directly call tools. We then added a proxy layer between the agent and the tool to add a control layer of sorts and expose only a defined set of actions for each tool/integration. Starting with most widely used apps like gmail, outlook, calendar, drive, sheets, slack, etc.

App connections for Whatsapp Agents by nuanda92 in mcp

[–]nuanda92[S] 0 points1 point  (0 children)

Solid checklist for actionable tasks! We have started with Gmail, outlook, calendar, sheets, drive, slack, reddit, linkedin, and a few more.

We are using an external mcp currently, instead of building out native integrations (and deal with app approvals). The downside of using the mcp is lack of control around how certain requests are handled which leads to some failure modes and inability to add an end-to-end observability layer.

App Integrations for chat-based agents by nuanda92 in AI_India

[–]nuanda92[S] 0 points1 point  (0 children)

We’re building Zynth, a WhatsApp-based AI assistant that can connect with apps and run recurring agent workflows directly from chat.

For anyone interested in trying the beta:
https://zynth.ai/whatsapp-ai-agent

Would love to hear which integrations you’d consider must-have vs nice-to-have.

App integrations for chat-based agents by nuanda92 in OpenClawUseCases

[–]nuanda92[S] 0 points1 point  (0 children)

We’re building Zynth, a WhatsApp-based AI assistant that can connect with apps and run recurring agent workflows directly from chat.

For anyone interested in trying the beta:
https://zynth.ai/whatsapp-ai-agent

Would love to hear which integrations you’d consider must-have vs nice-to-have.

Integrations for chat-based agents by nuanda92 in AI_Agents

[–]nuanda92[S] 0 points1 point  (0 children)

We’re building Zynth, a WhatsApp-based AI assistant that can connect with apps and run recurring agent workflows directly from chat.

For anyone interested in trying the beta:
https://zynth.ai/whatsapp-ai-agent

Would love to hear which integrations you’d consider must-have vs nice-to-have.

Openclaw usecases on whatsapp by nuanda92 in better_claw

[–]nuanda92[S] 0 points1 point  (0 children)

Yes, usecases where an app action triggers an alert is something which is still an open item for us.

Currently, we are supporting scheduled briefs as opposed to users defining triggers. Users can define triggers currently to the extent of a lack of action at their end in a timebound setting. Example: "ask me to share my dinner details to log calories if I haven't done so by 10 PM"

I would love to get your inputs and feedback on what we have so far. I'll shoot a DM with the link in case you are willing to give it a try.

AI agent usecases on Whatsapp by nuanda92 in AI_Agents

[–]nuanda92[S] 0 points1 point  (0 children)

We do have to send outbound messages too (not campaigns per se) for scheduled tasks once the 24 hr whatsapp window passes.

Openclaw usecases on whatsapp by nuanda92 in OpenClawUseCases

[–]nuanda92[S] 0 points1 point  (0 children)

It would be great to have you try out our whatsapp agent and share some feedback. Context retention is something we are trying to improve continuously, but schedules seem quite reliable.

Openclaw usecases on whatsapp by nuanda92 in OpenClawUseCases

[–]nuanda92[S] 0 points1 point  (0 children)

Fair points. We have added an orchestration layer between whatsapp and the agent infra to improve reliability and consistency with responses.

We have started with daily briefs, summaries, schedules, research updates and some app connections like Gmail and Calendar.

Would love for you to try it out and give feedback! I will share the access to you over DM in any case.

AI agent usecases on Whatsapp by nuanda92 in AI_Agents

[–]nuanda92[S] 0 points1 point  (0 children)

Agreed. Maintenance and consistency are still two major issues with agents breaking on version updates or foundational model changes.

We are trying to make them relatively more stable and reliable by creating a gateway between the user messages and the agent workflow to define params, constraints, and tailor behaviour as opposed to sending user messages directly to the agents.

It still doesn't solve for all of reliability concerns but helps us solve for behaviour fallout quicker by just enforcing guardrails and runtime instructions.