Skip to main content
Twilio is a cloud communications platform that lets your app reach users by phone. It works well for apps that need to send real-time text updates, add phone verification, trigger voice calls, or support messaging-based workflows. Twilio is available as an app + chat connector: one shared connection that works in the chat while you build and in your published apps. With Twilio, your app can:
  • Send and receive SMS and MMS messages
  • Make and manage voice calls
  • Support WhatsApp messaging flows
  • Validate and look up phone numbers
Twilio is a good fit when your app needs to communicate with users by phone or text, rather than only through in-app notifications or email.

Common use cases and example apps

How to connect Twilio

Workspace admins and owners can connect Twilio. You can create multiple Twilio connections using different API keys, for example, to separate development and production environments or to manage different Twilio accounts. When a connection is created, Twilio becomes available across all projects in the workspace.

Prerequisites

Before connecting Twilio, make sure you have:
  • A Twilio account
  • A Twilio phone number if your use case requires sending SMS, MMS, or making calls
  • A Standard Twilio API key
  • Lovable workspace owner or admin role
All SMS, MMS, voice, WhatsApp, and other Twilio usage through this connector is billed directly by Twilio based on your Twilio account and plan. Billing is handled by Twilio, not Lovable.

Step 1: Create a Twilio API key

Twilio uses an API Key SID and Secret instead of a single token. This is more secure than using your main Auth Token because API keys can be revoked independently. To create a Twilio Standard API Key:
  1. Go to the Twilio Console and sign in.
  2. Navigate to Account → API keys & tokens.
  3. Click Create API key.
  4. Enter a Friendly name, for example Lovable integration.
  5. Choose the Region for the key:
    • United States (US1): default for most accounts
    • Ireland (IE1)
    • Australia (AU1)
  6. Leave Key type set to Standard.
  7. Click Create API key.
  8. Copy both the API Key SID (starts with SK) and the Secret. The Secret is shown only once, so store it securely before leaving the page.
Your API Key Secret works like a password. Keep it secure and never share it publicly. You’ll need it in the next step.
Before sending production traffic, treat this as an unmanaged connector and secure your Twilio credentials. Keep your API Key Secret private, enable Twilio SMS Pumping Protection, and review SMS Geo Permissions so only intended destination countries are enabled.
You will also need your Account SID (starts with AC), which is available in the Twilio Console. Twilio API credentials are region-specific, so the region you select when creating the key should match the region you use when setting up the Lovable connection. See Twilio documentation for detailed instructions: Create API keys in Twilio console

Step 2: Connect Twilio to Lovable

  1. Open Connectors and select Twilio.
  2. Click Add connection.
  3. In Display name, enter a name for the connection, for example Twilio Prod.
  4. In Region, select the same Twilio region used for the API key:
    • United States (US1)
    • Ireland (IE1)
    • Australia (AU1)
  5. In Account SID, enter your Twilio Account SID (starts with AC).
  6. In Standard API Key SID, enter the API Key SID you created (starts with SK).
  7. In API Key Secret, enter the Secret shown when you created the key.
  8. Click Create.
When connected, your Lovable apps can use Twilio to send messages and power phone-based communication flows.

Manage your connection

Connections are managed from Connectors: select , then open the connection.
  • Unlink projects to remove access from specific projects while keeping the connection available for others. See Unlink projects from a connection for the steps.
  • Delete the connection to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use stop working until a new connection is added. See Delete a connection for the steps and who can delete.