feat(library): How Do You Build a WhatsApp AI Agent With Sim?

[icecrasher321]

Summary

• Adds the library post "How Do You Build a WhatsApp AI Agent With Sim?" at apps/sim/content/library/how-to-build-whatsapp-ai-agent-with-sim/.
• Generated by the Library Post PR Maker workflow from a Gauge Action Center brief.

Type of Change

• New content

Testing

The generator normalizes Sim marketing links to https://www.sim.ai and runs check:site-urls. After the PR opens, the workflow's content gate checks changed paths, frontmatter keys, FAQ placement, internal links, and canonical Sim marketing links; CI validates the post with check:library-content.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[icecrasher321]

@cubic review

[icecrasher321]

@greptile

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Oct 15, 2026 4:10pm UTC

[cubic-dev-ai]

@cubic review

@icecrasher321 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}

[greptile-apps]

Confidence Score: 4/5

[Low impact] Adds a tutorial document and cover image to the library.

The marketing wording must meet the repository’s rule before merging; the missing worker example is a non-blocking improvement.

Findings

1.  Worker connection is left unexplained ▶
2.  Comparison breaks the copy rules ▶

Summary

Adds a WhatsApp AI agent guide and cover image.

• The guide explains how WhatsApp messages reach Sim and get replies.
• The guide shows how message IDs prevent duplicate replies and track delivery.
• The guide shows when WhatsApp conversations should move to a person.
• The guide explains what self-hosting Sim does and does not include.
• The guide compares Sim with three other WhatsApp agent platforms.
• The guide gives teams a test checklist and production workflow.

Verification limitation: I could not inspect the cover image visually because image input is unavailable.

_{Reviews (1) · Last reviewed commit: "feat(library): How Do You Build a WhatsA..." · Reviewed by Greptile}

[greptile-apps]

Worker connection is left unexplained

The guide never shows how the worker sends its normalized event into Sim. The linked WhatsApp setup uses a native webhook trigger that expects Meta’s signed payload, not the worker’s normalized object. Readers must work out this connection themselves.

Add an example using the workflow execute API, including authentication and Start inputs, or explain how the native trigger fits this design.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Comparison breaks the copy rules

Calling Sim “the strongest fit” violates the marketing guide’s explicit “No exclamation marks or superlatives” directive. This repository requirement must be met before merging. Replace the absolute claim with a concrete statement about which teams Sim fits.

Suggested change

	Sim is the strongest fit when a team wants a self-hostable, extensible AI workspace for custom WhatsApp reasoning and business-system actions, while Botpress, respond.io, and n8n serve different operational priorities.
	Sim fits teams that want a self-hostable, extensible AI workspace for custom WhatsApp reasoning and business-system actions, while Botpress, respond.io, and n8n serve different operational priorities.

Context Used: CLAUDE.md (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!