sendblue-imessage

Route iMessage/SMS messages through Sendblue for per-client freight broker lines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

iMessage/SMS communication for freight brokers is centralized and scalable across multiple clients, each with its own virtual environment to manage messages, quotes, and confirmations without data bleed.

Core Features & Use Cases

  • Per-client VPS deployment: one OpenClaw instance, one dedicated Sendblue number, one webhook URL per client.
  • Webhook-driven inbound/outbound messaging: automatic posting of messages between broker and clients.
  • Multi-channel readiness: supports Outlook or Gmail inbox connections and per-client credential management.
  • Use Case: A solo freight broker onboarding three clients can operate three isolated lines with independent configurations, logs, and workflows.

Quick Start

Set up a per-client VPS, copy the skills into the server, configure the environment, run the webhook server, and register the client's webhook URL.

Frequently Asked Questions about sendblue-imessage

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

FAQPage Schema
How do I automate iMessage and SMS routing for multiple freight broker clients?

Automating iMessage and SMS routing involves configuring Sendblue with a dedicated webhook URL on a per-client VPS, using Flask and Python scripts to route inbound and outbound messages independently. This isolates client data and scales communication.

What is a per-client VPS deployment for freight broker messaging?

A per-client VPS deployment provides each freight broker client with an isolated OpenClaw instance, a dedicated Sendblue number, and a unique webhook URL. This ensures independent configurations, logs, and workflows without data bleed between clients.

Do I need a dedicated Sendblue number and webhook for each client?

Yes, you need a dedicated Sendblue number and a unique webhook URL for each client. This per-client setup on a VPS ensures that messaging, quotes, and confirmations remain isolated and scalable across multiple accounts.

Can I use Flask and YAML frontmatter to configure broker messaging environments?

Yes, you can use Flask and YAML frontmatter in SKILL.md to drive environment configuration for broker messaging. This setup allows you to manage per-client credentials and webhook routing for Sendblue integration dynamically.

What are the limitations of using Sendblue webhooks for iMessage automation?

The primary limitation is the infrastructure requirement: you must provision a separate VPS for each client to maintain isolated environments. This approach requires dedicated Sendblue numbers and manual webhook URL registration for every client line.

How does webhook-driven messaging handle real-time freight quotes and confirmations?

Webhook-driven messaging automatically posts inbound and outbound messages between the broker and clients by routing Sendblue events to a Flask server. This enables real-time processing of freight inquiries, quotes, and confirmations.