Lovable: Klaviyo Connector for Email and SMS Apps
LovableLovable added a Klaviyo connector that lets apps read and update a Klaviyo account through one shared connection. Apps can look up and update profiles, subscribe contacts with consent, track events, read campaigns and flows, and receive webhooks. It works as an app + chat connector, usable both while building in chat and in published apps.
Key Takeaways
- Lovable apps can now read and update a Klaviyo account through one shared connection, in both chat and published apps.
- Creating a profile does not subscribe anyone: the subscribe call is where email or SMS consent is recorded.
- Apps can track events, read campaigns and flows, and receive webhooks from Klaviyo flows.
- Authentication uses a private API key (
pk_), and its scopes are fixed at creation, so scope changes mean a new key. - Connections are private by default and can be shared with members or the workspace, with multiple keys allowed for dev and production.
- Lovable points users to its built-in Lovable Emails for transactional messages rather than Klaviyo.
Klaviyo inside Lovable apps
Lovable introduced a Klaviyo connector for apps that need email and SMS marketing data. A single shared connection to a Klaviyo account works in project chat during building and in published apps, which suits signup forms, profile lookups and campaign views. For standard transactional emails such as signup confirmations, password resets and receipts, Lovable recommends its built-in Lovable Emails feature instead.
What apps can do
Through the connector, an app can look up a profile, and create or update one without subscribing the person to marketing. Subscribing a profile to a list is a separate call, and that is where email or SMS consent is recorded. Apps can also track events such as a signup or purchase on a profile, read campaigns and flows, and receive webhooks from a Klaviyo flow.
Setup
Setup needs a Klaviyo account where the user is an Owner or Admin, and a Klaviyo private API key that starts with pk_. The public site ID does not work. Every key needs the accounts:read scope so Lovable can verify the connection. Subscribing people needs lists:write, profiles:write and subscriptions:write, listing profiles needs profiles:read, and reading campaigns and flows needs campaigns:read and flows:read. Klaviyo shows the key only once and scopes cannot be changed later, so changing scopes means creating a new key and updating the Lovable connection.
In Lovable, the user opens Connectors, selects Klaviyo, adds an App + chat connector connection, names it, pastes the key and sets sharing. Connections are private by default and can be shared with specific members or the whole workspace. Lovable verifies the key before saving. Multiple connections with different keys are allowed, for example to separate development from production.
Availability and limits
App + chat connectors are available by default on Free, Pro and Business plans. On Enterprise, an admin must first change the "Who can create connections and clients" setting. Each connection represents one Klaviyo account, there is no per-end-user Klaviyo login, and billing and rate limits are handled by Klaviyo. If the key is revoked, requests fail until a new key is added to the connection.