Text new form leads instantly via iMessage and SMS with iBlueText

Quick overview

This workflow collects new leads via an n8n form, formats and validates their phone numbers, sends an iMessage or SMS via iBlueText, and checks delivery status after a short delay to surface send or delivery failures.

How it works

1. Receives a new lead submission from an n8n Form with the lead’s name, mobile number, and request details.
2. Builds the outbound message and normalizes the submitted phone number into international E.164 format.
3. Skips the lead if the phone number does not pass validation.
4. Sends the text message through the iBlueText API using an HTTP request with header-based authentication.
5. Waits one minute and then queries iBlueText for the send status using the returned message ID.
6. Stops with an error if iBlueText reports a failed delivery, otherwise finishes successfully.

Setup

1. Create an iBlueText account and generate an API key (or use a sandbox test key for testing).
2. In n8n, add an HTTP Header Auth credential with Authorization: Bearer <YOUR_KEY> and select it for both iBlueText HTTP requests.
3. Customize the default country code and message text in the workflow settings, and ensure your trigger provides a first name and phone number if you replace the built-in form.
4. Activate the workflow and share the n8n Form URL (or configure your external lead source to send data to the trigger you use).

Requirements

• An iBlueText account (free to start) and an API key from Integrations → API keys. Sandbox test keys (sk-ibt-test-) let you test without texting anyone.
• An iBlueText sending line (a hosted number or your own Mac with the iBlueText Bridge) to send real texts.

Customization

• Replace the form with any trigger that provides a first name and phone number, such as a CRM, Typeform or a webhook.
• Add "voice": true to the request body to send the message as an AI voice note instead of text.
• Connect an error workflow to get an email or Slack alert when a text fails.