textgrid-provider

Configure TextGrid outbound SMS, inbound webhooks, and A2P 10DLC registration.

1|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/MikeyMiami/lovable-web-design --skill textgrid-provider
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: textgrid-provider
Source: https://github.com/MikeyMiami/lovable-web-design/tree/main/skills/textgrid-provider
Command: npx skills add https://github.com/MikeyMiami/lovable-web-design --skill textgrid-provider

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill manages the transition and operational maintenance of the TextGrid messaging provider, handling outbound SMS, inbound webhooks, and the complex per-client A2P 10DLC registration flow.

Core Features & Use Cases

  • Messaging Provider Swap: Configures the TextGrid API as the outbound SMS transport for existing legacy clients.
  • Inbound Webhook Management: Implements signature verification and routing for reply-driven exits and missed-call textback functionality.
  • A2P 10DLC Registration: Orchestrates the subaccount, brand, and campaign registration process required for compliant business messaging.

Quick Start

Use the textgrid-provider skill to configure the messaging webhooks and A2P registration flow for a specific client subaccount.

Frequently Asked Questions about textgrid-provider

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

FAQPage Schema
How do I configure outbound SMS transport using TextGrid for legacy clients?

Configure outbound SMS transport by setting the TextGrid API as the messaging provider within your existing platform architecture. This skill manages the provider swap process specifically for legacy client maintenance and infrastructure transitions.

How does TextGrid webhook signature verification work for inbound SMS?

TextGrid webhook verification uses secure HMAC-SHA1 signature validation to authenticate inbound SMS payloads. This mechanism enables reliable routing for reply-driven exits and missed-call textback functionality without compromising security.

What is the A2P 10DLC registration process for TextGrid messaging?

A2P 10DLC registration orchestrates the creation of subaccounts, brands, and campaigns required for compliant business messaging. This per-client isolation ensures regulatory compliance when sending Application-to-Person messages via TextGrid.

Do I need a separate TextGrid subaccount for each client to ensure messaging isolation?

Yes, subaccount-based messaging isolation is required for compliant A2P 10DLC registration. This architecture separates messaging traffic, webhook routing, and campaign registration securely across individual clients within the platform.

Can I use TextGrid messaging for reply-driven exits and missed-call textback workflows?

Yes, TextGrid supports reply-driven exits and missed-call textback workflows through inbound webhook management. The skill implements signature verification and routing to automate these specific messaging interactions.

What are the limitations of swapping to TextGrid as an SMS provider?

TextGrid provider swaps apply primarily to legacy client maintenance and require subaccount-based architecture. Implementations must satisfy HMAC-SHA1 webhook verification and complete A2P 10DLC campaign registration before compliant messaging activation.