Something happens on your WordPress site, and a text message goes out through Twilio. The record maps straight across the instant the event fires — a direct, real-time connection built into WordPress itself, no extra plugin required.
What a WordPress Core → Twilio connection can do
When this happens in WordPress Core
What happens in Twilio
The one thing this connection does in Twilio
Everything you need to know about the WordPress Core & Twilio integration
No. Install Integrazo Automator, authorise Twilio once, pick the WordPress event as the trigger, map the post, user and comment fields into the message text and switch the connection on. There is no webhook URL to paste and no JSON to write.
To the number mapped from your form — usually a phone field the visitor filled in. Set the From number once when you build the connection.
Yes. Build the message from any of your post, user and comment fields plus fixed text of your own, in the order you want it to read.
Yes — each run sends a new message; Twilio doesn't dedupe SMS sends. Pair the connection with your form plugin's own duplicate-submission protection if that matters.
Yes. Add a filter condition on any mapped field — contains, equals, starts with, is empty and the rest, combined with AND/OR — and only entries matching it are sent to Twilio. Everything else is skipped and still shows up in your Logs.
The run is logged as failed with the error Twilio returned, and the event is still saved in WordPress — nothing is lost. Once the problem is fixed, the next matching event goes through as normal.
No. The connection runs on your own WordPress site and talks to Twilio directly. The OAuth token is encrypted in your database, and there is no middleman service holding a copy of your data.
The core plugin is free on WordPress.org and covers a single connection. Pro adds unlimited connections, multiple Twilio numbers per connection, and longer message templates, and priority support.