freight-twilio-webhook

Route freight broker messages across Twilio SMS and LoopMessage iMessage.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/wasay1200/freight-broker-ai --skill freight-twilio-webhook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freight-twilio-webhook
Source: https://github.com/wasay1200/freight-broker-ai/tree/main/skills/freight-twilio-webhook
Command: npx skills add https://github.com/wasay1200/freight-broker-ai --skill freight-twilio-webhook

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, twilio, and includes scripts (resource) components.

What problem does it solve?

Handling broker communications across multiple messaging channels is complex and error-prone. This skill provides a single webhook-based gateway that can receive and route messages via Twilio SMS or LoopMessage iMessage, with automatic channel selection and fallback for non-iMessage users.

Core Features & Use Cases

  • Multi-channel messaging: Twilio SMS and LoopMessage iMessage with automatic fallback.
  • Per-client routing and quick responses via templates and training support for improved accuracy.
  • Lightweight deployment: a single Python webhook server that handles inbound messages, training prompts, and per-client routing.

Quick Start

Run the webhook server and point your Twilio and LoopMessage webhooks to it to start routing messages.

Frequently Asked Questions about freight-twilio-webhook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route inbound freight broker messages across Twilio SMS and iMessage using a webhook?

Routing inbound freight broker messages requires a Python webhook server that processes real-time texts and applies automatic channel selection, using Twilio for SMS and LoopMessage for iMessage with fallback logic for non-iMessage users.

What credentials do I need to set up a unified messaging webhook for Twilio and iMessage?

Setting up a unified messaging webhook requires a running Python server, Twilio credentials including account SID, auth token, and from number, plus an optional LoopMessage API key to enable iMessage routing capabilities.

Can I use a single webhook to handle both Twilio SMS and LoopMessage iMessage for broker communications?

Yes, a single Python webhook server can receive and route broker communications across both Twilio SMS and LoopMessage iMessage, featuring automatic channel selection and fallback for non-iMessage users.

How does multi-channel messaging handle fallback for freight brokers when iMessage is unavailable?

Multi-channel messaging handles fallback by automatically detecting non-iMessage users and routing their communications through Twilio SMS, ensuring freight brokers maintain real-time contact without channel-specific configuration.

What are the limitations of using a Python webhook server for Twilio and iMessage message routing?

Limitations include the requirement for a continuously running Python webhook server to process inbound messages, and the dependency on valid Twilio credentials and an active LoopMessage API key to maintain multi-channel routing.