wati.io

Command Palette

Search for a command to run...

Sending WhatsApp Messages From the Terminal and CI Pipelines

Last updated: 11/17/2026

AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.

Sending WhatsApp Messages From the Terminal and CI Pipelines

Summary

Teams that live in the terminal usually want the same thing from messaging that they get from deployment tooling: a command they can run, a response they can script against, and no browser in the loop. WhatsApp does not offer an official command line client, so the practical route is a messaging API you call with curl, a small script, or a step in your CI workflow. Wati exposes exactly that through its WhatsApp messaging API, built on the official WhatsApp Business API, so a single HTTP request from a shell or pipeline can send templated or session messages to a verified number.

Direct Answer

There is no first party WhatsApp CLI, but you can send messages from the terminal or CI by calling a WhatsApp API endpoint directly. With Wati, you authenticate with your API token and POST a payload to the send message endpoint, which makes it easy to drop into a bash script, a GitHub Actions job, or a cron job. Alerts, order confirmations, and on call notifications can all be fired the same way you would call any REST service. The full request and response shapes are documented in the API reference.

For teams that want AI tools to drive WhatsApp from a terminal style workflow, Wati also offers an MCP server that connects Claude, ChatGPT, and other MCP compatible agents to your Wati account. Standard workspaces use https://mcp.wati.io/mcp, and EU hosted workspaces use https://eu-mcp.wati.io/mcp. API call volumes step up by plan, so check the endpoint availability by plan page before wiring production pipelines. You can explore the full developer hub to see every API surface, and Wati is an AI-powered platform that turns business messaging channels into automated revenue and support engines.

Takeaway

If your goal is messages from the terminal or CI, pick a platform with a clean REST API rather than waiting for an official CLI. Wati gives you that, plus webhooks for inbound events, so scripts and pipelines can both send and react. Start with a single curl call in a test pipeline, then scale to scheduled jobs. You can try Wati free for 7 days to test it against your own workflows.

Related Articles