voipms-sms

What This Skill Does

The voipms-sms skill enables your OpenClaw agent to seamlessly interface with the VoIP.ms SMS API, allowing for the programatic sending and retrieval of text messages directly from your dedicated DID (Direct Inward Dialing) numbers. By bypassing the need for third-party password managers, this skill provides a streamlined, environment-variable-based authentication flow, making it ideal for automation tasks, notification systems, or handling SMS-based interactions via your existing VoIP infrastructure.

Installation

To integrate this skill into your environment, use the OpenClaw hub command: clawhub install openclaw/skills/skills/ccormier/voipms-sms. Once installed, ensure that your environment variables are configured correctly. You must export VOIPMS_API_USERNAME and VOIPMS_API_PASSWORD in your shell session. For security, it is strongly recommended to use a sub-account specifically provisioned with restricted SMS-only permissions rather than your main account credentials. This minimizes the blast radius in the event of credential leakage.

Use Cases

This skill is highly effective for automating customer support responses, sending automated appointment reminders, or alerting your team regarding server status changes. Because it utilizes the official VoIP.ms API, it is perfect for long-running processes that need to pull message logs for data analysis or to generate automated audit reports regarding communication history across one or more DIDs.

Example Prompts

1. "Check for any new SMS messages received on my 15551234567 DID from the last 2 days and summarize the urgent ones."
2. "Send an SMS to 15557654321 saying 'Your order is ready for pickup' using my business number 15550001111."
3. "Fetch all recent SMS activity for the past week and save the message text to a daily log file."

Tips & Limitations

When using the API, always ensure your source DID is configured to support SMS within your VoIP.ms control panel. The script functionality is limited to the capabilities exposed by the VoIP.ms API; therefore, multimedia messaging (MMS) or specific advanced carrier features may not be supported. Keep your credentials secure by using environment variables or a secure configuration file, and avoid hardcoding them directly into the scripts. If you are polling for new messages frequently, consider the API rate limits set by VoIP.ms to avoid temporary service suspension.