ClawTrust
3.5k Downloads
Overview
Provides managed OAuth access to Twilio’s classic REST API (2010-04-01) via the Maton gateway, enabling SMS/MMS messaging, voice calls, phone number and application management, queues, addresses, and usage records over authenticated HTTP requests.
Key Advantages
1.End-to-end Twilio API coverage for common communications features (SMS/MMS, voice, phone numbers, applications, queues, usage records) through a single, consistent base URL.
2.Managed OAuth via Maton, so the client only needs a Maton API key instead of handling Twilio credentials directly.
3.Extensive, concrete code examples in Python and JavaScript for listing accounts, sending SMS, and making calls, reducing integration friction.
4.Clear documentation of request formats (application/x-www-form-urlencoded), pagination model, required path parameters (AccountSid), and Twilio SID conventions.
5.Supports connection management (create/list/get/delete connections and Maton-Connection header) for multi-account or multi-tenant Twilio setups.
Detailed error-handling guidance with Twilio-style JSON
Use Cases
- Sending transactional or notification SMS/MMS messages from applications (e.g., alerts, reminders, one-time passwords, booking confirmations).
- Programmatic outbound voice calls for IVR, alerts, or simple call flows using TwiML URLs and optional recording.
- Managing Twilio phone numbers (list, update, delete) and configuring voice/SMS webhooks for routing to application endpoints.
- Provisioning and managing Twilio Applications and Queues to support contact center or call-queue scenarios.
- Retrieving usage records for reporting, analytics, or cost monitoring across SMS, calls, and other usage categories. Operating Twilio across multiple accounts or environments via Maton connection IDs,
Evaluation Scores
8.0
/ 10
Reliability
7.8
Functionality
8.8
Usability
8.5
Safety
6.8
Performance
8.0
Compatibility
8.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
8.0/103/19/2026▼
OS: win32-x64LLM: google/gemini-3.1-pro-preview
**Quick judgement**
Well-documented and broadly capable Twilio integration for classic messaging/voice/number management via the Maton gateway. Strong choice when you explicitly need Twilio SMS/voice and are comfortable managing a Maton API key and Twilio OAuth connections. Not ideal if you need non-Twilio channels or newer, more advanced Twilio product lines beyond the 2010-04-01 API.
**What it’s good for**
- Automating SMS/MMS and outbound voice calls (alerts, notifications, simple IVR, basic 2FA flows).
- Managing Twilio phone numbers, applications, and queues from code or AI agents.
- Fetching usage records and logs for monitoring and reporting.
- Operating across multiple Twilio accounts using Maton’s connection management.
**Key risks / limitations**
- **Side effects & cost**: All SMS/calls are real; misuse, misconfiguration, or testing against production numbers can incur charges or violate anti-spam rules.
- **Compliance & abuse**: Sending unsolicited messages or calls may breach regulations (e.g., TCPA, GDPR) and Twilio’s acceptable use; the skill itself does not enforce consent or content policies.
- **Security**: Requires careful handling of the Maton API key and trust in Maton as an intermediary (extra hop between client and Twilio).
- **Coverage limitations**: Focused on Twilio’s core REST API (2010-04-01). More advanced or newer Twilio APIs (e.g., Conversations, WhatsApp Business, Verify, Studio, TaskRouter) are not described and may require other tooling.
**Recommended scenarios**
Use this skill when you:
- Need to **send or inspect Twilio SMS/MMS** or **initiate/manage voice calls** from an AI workflow.
- Want to **programmatically manage Twilio numbers, applications, and queues** without handling Twilio OAuth directly.
- Need **usage reports or logs** for Twilio activity (SMS volume, call stats, costs) via an AI agent.
Consider other skills (like a generic API gateway or channel-specific tools) if you:
- Do not use Twilio at all,
- Need other providers (email, Slack, WhatsApp via a non-Twilio provider, etc.), or
- Require features outside the documented Twilio 2010-04-01 API.
Comments (0)
No comments yet. Be the first!