Run any Skill in Manus with one click

freight-imessage-setup

Stars0

Forks0

UpdatedMarch 6, 2026 at 01:10

Configure iMessage relay servers for client SMS integration. Supports BlueBubbles or custom relay implementations to enable two-way SMS communication between freight brokers and the AI. Use when setting up iMessage for a new client, testing SMS connectivity, or checking relay status. Triggered by "setup iMessage", "configure SMS", "test iMessage", "iMessage status", or "SMS relay".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

wasay1200

wasay1200/freight-broker-ai

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	freight-imessage-setup
description	Configure iMessage relay servers for client SMS integration. Supports BlueBubbles or custom relay implementations to enable two-way SMS communication between freight brokers and the AI. Use when setting up iMessage for a new client, testing SMS connectivity, or checking relay status. Triggered by "setup iMessage", "configure SMS", "test iMessage", "iMessage status", or "SMS relay".

Freight iMessage Setup

Configures iMessage relay for client SMS integration. Brokers communicate with AI via text message.

How It Works

macOS Server: Runs Messages.app with client's Apple ID
Relay Software: BlueBubbles or custom server forwards messages
OpenClaw Integration: Receives webhooks, sends responses
Broker Experience: Texts commands, receives AI responses

Requirements

macOS device (Mac Mini, MacBook, or cloud Mac)
Apple ID logged into Messages.app
Static IP or domain name
BlueBubbles server installed

Setup

Option 1: BlueBubbles (Recommended)

Install BlueBubbles on macOS: https://bluebubbles.app
Configure server password and port

Set env vars:

export IMESSAGE_SERVER_HOST=your-server-ip
export IMESSAGE_SERVER_PORT=12345
export IMESSAGE_SERVER_PASSWORD=your-password

Option 2: Custom Relay

Build your own relay using:

python-imessage library
Webhook forwarding to OpenClaw
HTTP API for sending messages

Usage

Configure iMessage for client

cd skills/freight-imessage-setup/scripts
python3 imessage_setup.py --setup --client-id CLIENT-001 --phone "+1-555-123-4567" --relay-type bluebubbles

Send test message

python3 imessage_setup.py --client-id CLIENT-001 --test-message "+1-555-123-4567"

Check status

python3 imessage_setup.py --client-id CLIENT-001 --status

Broker Text Commands (Once Configured)

Once iMessage is active, brokers can text:

Text	Action
`find loads LA to NYC`	Scan load board
`vet MC#123456`	Check carrier
`check emails`	Email summary
`status`	Current workload
`help`	Command list

SMS Output Example

✅ IMESSAGE CONFIGURED
Client: CLIENT-001
Phone: +1-555-123-4567
Relay: BlueBubbles @ 192.0.2.50:12345
Status: Active

Test message sent successfully.
Ready for broker SMS commands.

Integrations

This skill uses the following external services. See INTEGRATIONS.md for detailed setup instructions, API documentation links, and implementation guidance.

Service	Purpose	Section in INTEGRATIONS.md
Twilio	SMS fallback	Shared Infrastructure: Twilio
BlueBubbles	iMessage relay	Refer to this SKILL.md
LoopMessage	Hosted iMessage bridge	Refer to freight-twilio-webhook SKILL.md

See INTEGRATIONS.md for complete integration architecture

Troubleshooting

"Could not connect" → Check firewall, verify server is running
Messages not sending → Verify Apple ID is signed in on Mac
No webhook received → Check OpenClaw gateway configuration

More from this repository

same repository

freight-email-parser

wasay1200/freight-broker-ai

Monitor freight broker's email inbox via IMAP or Outlook, classify incoming emails using HuggingFace zero-shot or regex, parse quote requests from shippers, extract carrier communications, send/draft replies, and alert broker via SMS with actionable summaries. Supports exception handling workflows like driver ETA drift alerts when telematics or GPS data indicates delays and the AI should notify the shipper or customer by email. Use when a broker wants email monitoring, gets a quote request, needs to process carrier emails, or wants inbox summaries. Triggered by phrases like "check emails", "pending quotes", "carrier emails", "email inbox", "new emails", "email summary", or driver ETA / delay alerts.

2026-03-120

freight-doc-processor

wasay1200/freight-broker-ai

Automatically detect, OCR-parse, and verify POD (Proof of Delivery) and BOL (Bill of Lading) documents received as email attachments. Matches documents to load records, flags discrepancies, and triggers invoicing. Use when a broker receives delivery documents, needs POD confirmation, wants to verify delivery details, or needs to process BOLs. Triggered by phrases like "missing PODs", "check documents", "verify delivery", "resend POD", "process BOL", or automatically when email with PDF/image arrives.

2026-03-090

sendblue-imessage

wasay1200/freight-broker-ai

iMessage/SMS interface for freight brokers via Sendblue. Production setup is one VPS per client, one dedicated Sendblue number per client, and one webhook URL per VPS. Use when setting up broker texting, dedicated lines, or webhook deployment.

2026-03-090

freight-client-onboard

wasay1200/freight-broker-ai

Orchestrate complete client onboarding workflow for freight broker AI service. Automates VPS creation, OpenClaw installation, Twilio SMS webhook setup, skill deployment, and testing. Provides dashboard API for managing multiple clients. Use when onboarding a new freight broker client, checking onboarding status, or managing the client fleet. Triggered by "onboard client", "new client", "client setup", "onboarding status", "create client", or "provision new broker".

2026-03-060

freight-compliance-docs

wasay1200/freight-broker-ai

Generate freight documents (Bill of Lading, Rate Confirmation) and check carrier/broker compliance via FMCSA. Track insurance expiries and authority status. Use when a broker needs to generate a BOL or Rate Con, wants to verify carrier compliance, needs to check upcoming document expiries, or when booking a load. Triggered by phrases like "generate BOL", "generate rate con", "compliance check MC#", "upcoming expiries", or "document for load".

2026-03-060

freight-invoice-tracker

wasay1200/freight-broker-ai

Auto-generate freight invoices after POD confirmation, track accounts receivable aging, send payment reminders, and monitor carrier payments. Use when a load is delivered and needs invoicing, broker wants AR status, an invoice is overdue, or payment reminders are needed. Triggered by phrases like "invoice load", "AR report", "paid invoice", "overdue invoices", "remind shipper", or automatically after POD confirmation.

2026-03-060

name	freight-imessage-setup
description	Configure iMessage relay servers for client SMS integration. Supports BlueBubbles or custom relay implementations to enable two-way SMS communication between freight brokers and the AI. Use when setting up iMessage for a new client, testing SMS connectivity, or checking relay status. Triggered by "setup iMessage", "configure SMS", "test iMessage", "iMessage status", or "SMS relay".

Freight iMessage Setup

Configures iMessage relay for client SMS integration. Brokers communicate with AI via text message.

How It Works

macOS Server: Runs Messages.app with client's Apple ID
Relay Software: BlueBubbles or custom server forwards messages
OpenClaw Integration: Receives webhooks, sends responses
Broker Experience: Texts commands, receives AI responses

Requirements

macOS device (Mac Mini, MacBook, or cloud Mac)
Apple ID logged into Messages.app
Static IP or domain name
BlueBubbles server installed

Setup

Option 1: BlueBubbles (Recommended)

Install BlueBubbles on macOS: https://bluebubbles.app
Configure server password and port

Set env vars:

export IMESSAGE_SERVER_HOST=your-server-ip
export IMESSAGE_SERVER_PORT=12345
export IMESSAGE_SERVER_PASSWORD=your-password

Option 2: Custom Relay

Build your own relay using:

python-imessage library
Webhook forwarding to OpenClaw
HTTP API for sending messages

Usage

Configure iMessage for client

cd skills/freight-imessage-setup/scripts
python3 imessage_setup.py --setup --client-id CLIENT-001 --phone "+1-555-123-4567" --relay-type bluebubbles

Send test message

python3 imessage_setup.py --client-id CLIENT-001 --test-message "+1-555-123-4567"

Check status

python3 imessage_setup.py --client-id CLIENT-001 --status

Broker Text Commands (Once Configured)

Once iMessage is active, brokers can text:

Text	Action
`find loads LA to NYC`	Scan load board
`vet MC#123456`	Check carrier
`check emails`	Email summary
`status`	Current workload
`help`	Command list

SMS Output Example

✅ IMESSAGE CONFIGURED
Client: CLIENT-001
Phone: +1-555-123-4567
Relay: BlueBubbles @ 192.0.2.50:12345
Status: Active

Test message sent successfully.
Ready for broker SMS commands.

Integrations

This skill uses the following external services. See INTEGRATIONS.md for detailed setup instructions, API documentation links, and implementation guidance.

Service	Purpose	Section in INTEGRATIONS.md
Twilio	SMS fallback	Shared Infrastructure: Twilio
BlueBubbles	iMessage relay	Refer to this SKILL.md
LoopMessage	Hosted iMessage bridge	Refer to freight-twilio-webhook SKILL.md

See INTEGRATIONS.md for complete integration architecture

Troubleshooting

"Could not connect" → Check firewall, verify server is running
Messages not sending → Verify Apple ID is signed in on Mac
No webhook received → Check OpenClaw gateway configuration