Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Connect your AI SaaS intelligent agent to any messaging channel via OpenClaw (WhatsApp, Telegram, Slack, Discord, iMessage, and more)
Connect your AI SaaS intelligent agent to any messaging channel via OpenClaw (WhatsApp, Telegram, Slack, Discord, iMessage, and more)
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
This skill forwards user messages to an AI SaaS chatbot and returns its response. It maintains conversation context per user by using their channel and user identifier as a session key.
These environment variables must be set in your ~/.openclaw/openclaw.json under skills.entries.amernet-ai-saas.env: VariableDescriptionAI_SAAS_API_KEYYour API key from the portal (Settings → API Keys). Needs all permission.AI_SAAS_CHATBOT_IDThe chatbot ID to route all messages to (copy from the Chatbots page).AI_SAAS_BASE_URLBase URL of your AI SaaS instance. Default: https://saas.salesbay.ai
When the user sends ANY message through any connected channel: Identify the current channel name (e.g. whatsapp, telegram, slack, discord) and the user's identifier on that channel (phone number, user ID, or username). Construct a sender_id combining both: <channel>:<user_identifier> WhatsApp example: whatsapp:+15551234567 Telegram example: telegram:123456789 Slack example: slack:U012AB3CD Discord example: discord:123456789012345678 Send a POST request to the chatbot API: POST ${AI_SAAS_BASE_URL}/api/v1/chatbots/${AI_SAAS_CHATBOT_ID}/chat Authorization: Bearer ${AI_SAAS_API_KEY} Content-Type: application/json { "sender_id": "<constructed sender_id>", "message": "<user message text>" } Parse data.responses from the JSON response. Return each item's text field as a separate message to the user. If multiple responses exist, send them in order. If the API returns an error or is unreachable, reply: "Sorry, the AI assistant is temporarily unavailable. Please try again in a moment."
If the user explicitly says "reset", "start over", "clear chat", or "/reset": DELETE ${AI_SAAS_BASE_URL}/api/v1/chatbots/${AI_SAAS_CHATBOT_ID}/conversations/<sender_id> Authorization: Bearer ${AI_SAAS_API_KEY} Then confirm: "Conversation cleared. How can I help you?"
If the user says "/status" or "/ping": GET ${AI_SAAS_BASE_URL}/api/v1/chatbots/${AI_SAAS_CHATBOT_ID} Authorization: Bearer ${AI_SAAS_API_KEY} Report the chatbot name and whether it is active.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.