By the numbers
- $19.99a month for Zapier Professional with 750 tasks, billed annually ($29.99 month to month)Zapier pricing
- 750requests a minute allowed on Klaviyo's subscribe endpoint, with up to 1,000 profiles per callKlaviyo API, Bulk Subscribe Profiles
- 20,000URL Fetch calls a day for Apps Script on a consumer Google account, 100,000 on WorkspaceGoogle Apps Script quotas
- 3%Klaviyo's benchmark submit rate for signup formsKlaviyo sign-up form best practices
Vendor figures are averages across many stores, not controlled tests. Use them to decide what to test first.
There is no native connection
Google Forms has no Klaviyo setting, and Klaviyo has no Google Forms integration to switch on. Every working setup puts something in between: an automation tool such as Zapier or Make that watches for new responses, a short Apps Script that calls Klaviyo's API, or a manual export and import. Choose by volume and by who will look after it. A handful of responses a month suits Zapier's free plan or a CSV. Hundreds a week suit a paid automation plan or a script someone on the team owns. Whichever you pick, the step that matters most is the Klaviyo action at the end, because only one kind of call records marketing consent.
Zapier: a form trigger and a subscribe action
Zapier has ready-made Zaps for Google Forms and Klaviyo. Use the Google Forms trigger New Form Response, which Zapier lists as instant, and the Klaviyo action Subscribe Profile, which subscribes a profile to email marketing, SMS marketing or both. It asks for a consent-to-subscribe field and, optionally, a list. Map the email question to the email field and pick the list your welcome flow starts from. Zapier's Klaviyo app also has Add Profile to List, Create Profile and Create Or Update Profile. Those are useful for writing a survey answer to a profile, but none of them is the subscribe step. Send a test response before you turn the Zap on.
What Zapier costs for this
Zapier bills in tasks, and a task is a successful action: the trigger is free, and each Klaviyo action that runs uses one. The Free plan includes 100 tasks a month and two-step Zaps, which is exactly one form trigger plus one subscribe action. Professional starts at $19.99 a month billed annually, or $29.99 month to month, for 750 tasks. The 1,500-task tier is $39.00 a month billed annually or $58.50 monthly. If you also want survey answers written to the profile in a second Klaviyo step, each response uses two tasks, and multi-step Zaps need a paid plan.
Make: the same idea, priced in credits
Make has both apps. Its Google Forms module can watch responses directly or through the linked Google Sheet, and its Klaviyo app includes Add or Subscribe Profiles to a List, which can subscribe profiles with marketing consent, plus Create and Add a Profile to a List. Choose the subscribe behaviour, not a plain add. Make's Free plan includes 1,000 credits a month; paid tiers change often, so check its pricing page for the current figures. Make suits teams that already run other scenarios there. For a single form feeding a single list, the Zapier free plan is usually simpler to set up and read.
Apps Script: call Klaviyo's API yourself
If you would rather not pay a subscription, a script can do the job. Link the form to a Google Sheet, open its script editor and add an installable form-submit trigger: Google's documentation notes that form-submit triggers for Forms and for Sheets are installable only. The Sheets event passes the script namedValues, the question names with their answers. The script then sends a POST to Klaviyo's Bulk Subscribe Profiles endpoint, /api/profile-subscription-bulk-create-jobs, with a private API key in an Authorization: Klaviyo-API-Key header, a revision header and a JSON:API body holding the email, email marketing consent set to SUBSCRIBED and the list as a relationship. The key needs the lists:write, profiles:write and subscriptions:write scopes. Keep it in the script's properties, never in the form or the sheet.
The limits of the script route
Apps Script is free within quotas. A consumer Gmail account gets 20,000 URL Fetch calls a day and 90 minutes of trigger runtime a day; a Google Workspace account gets 100,000 calls and 6 hours. Each run can last 6 minutes. On Klaviyo's side, the subscribe endpoint allows a burst of 75 requests a second, 750 a minute and up to 1,000 profiles per call, so one call per response sits far inside every limit. What a script does not give you is monitoring. If the key is revoked or Klaviyo rejects a request, nobody hears about it unless the script emails someone, so log each response status and check it after any change.
CSV import for a one-off list
For an event or a giveaway that has closed, export the responses from the linked sheet as a CSV and import it into a Klaviyo list. Map each column to a Klaviyo property, including any consent column. Klaviyo's import offers Apply bulk consent, and its own guidance is to choose that only if everyone in the file explicitly consented to email marketing from you; otherwise choose to import only the consent in your file. Delete anyone who did not tick the consent question before you upload. A CSV is the cheapest route and the slowest: nobody gets a welcome email until you import, so it is the wrong choice for a form that promised a code.
Adding a profile is not subscribing it
This is where most Google Forms setups go wrong. Klaviyo's Add Profile to List endpoint adds a profile to a list, and its reference recommends the Subscribe Profiles endpoint instead if you are trying to give a profile consent to receive email marketing, SMS marketing or both. Treat a profile that was only added as not subscribed. The subscribe call has a sharp edge of its own: Klaviyo says it removes any UNSUBSCRIBE, SPAM_REPORT or USER_SUPPRESSED suppressions from the profiles it receives. So send only the people who opted in on this form, never every respondent, or someone who unsubscribed last year and then filled in a feedback form starts getting your emails again.
Double opt-in and historical imports
A subscribe call follows the list's own opt-in setting. On a double opt-in list, Klaviyo sends a confirmation message and subscribes the person only once they confirm; on a single opt-in list they are subscribed straight away. If you are moving responses collected weeks ago, Klaviyo lets you set historical_import to true with a consented_at time in the past. That skips the double opt-in message and any Added to list flows. Use it only for consent you can show you collected, with each response's timestamp as consented_at. For live responses leave it off, so new subscribers get the same confirmation and welcome as everyone else.
Put the consent on the form
A Google Form does not ask for marketing consent unless you add the question. Add an optional checkbox under the email field that names the brand and says what people will get, for example: Email me news and offers from [brand]. I can unsubscribe at any time. Then send only the responses that ticked it to Klaviyo, and keep a copy of the wording with the dates you used it. If you collect phone numbers for texts, follow Klaviyo's sample US disclosure: who is sending, Message frequency varies, Message and data rates may apply, Consent is not a condition of purchase, and Reply HELP for help or STOP to cancel, with links to your privacy policy and terms.
Test it end to end
Submit the form with an address you control that Klaviyo has never seen. Open the profile in Klaviyo and check three things: it is on the right list, its email consent shows as subscribed, and the welcome flow started. On a double opt-in list, confirm the email first. Then submit once without ticking the consent box and check that nothing reached Klaviyo. Repeat the test whenever someone edits the form's questions, because a renamed question can quietly break the field mapping in a Zap or a script.
When a signup form does it better
Google Forms suits jobs that are not storefront signups: a wholesale application, an event RSVP, a survey sent to existing customers. For shoppers on your store, a signup form on the site is the shorter path, with no connector to break and consent written at the moment of signup. Klaviyo's own sign-up forms come with every Klaviyo account, against a benchmark submit rate of 3%. Wisepops measured popups on Shopify stores converting at 6.97%, against 4.73% on other platforms. If the survey questions are the point, ask them inside the popup instead of sending shoppers to a separate form.
Where Veya fits
Veya builds signup popups for Shopify stores: Claude builds each design from your brief, and signups go to Klaviyo. Veya connects to Klaviyo by OAuth, so there is no API key to paste, and subscribes each signup through the same Bulk Subscribe Profiles call described above, for each channel only when the visitor gave consent for it. The list's own single or double opt-in setting still applies. Quiz and survey answers from the popup become Klaviyo profile properties, and a Veya Signup event is sent once Klaviyo accepts the subscription, for flows to start from. Each signup keeps the consent wording shown, the time and the page it came from, so you can show what someone agreed to.
Questions
Can I connect Google Forms to Klaviyo directly?
No. Neither product has a built-in integration with the other. You need something in between: Zapier or Make watching for new responses, an Apps Script that calls Klaviyo's API when the form is submitted, or a CSV exported from the linked sheet and imported into a Klaviyo list.
How do I add Google Forms responses to a Klaviyo list?
The quickest route is a Zap with the Google Forms trigger New Form Response and Klaviyo's Subscribe Profile action, with your list selected and the email question mapped to the email field. Only send respondents who ticked a marketing consent question, then test with a fresh address and check the profile's consent status in Klaviyo.
Is there a free way to send Google Forms to Klaviyo?
Yes. Zapier's Free plan includes 100 tasks a month with two-step Zaps, enough for one subscribe action per response at low volume. Make's Free plan includes 1,000 credits a month. An Apps Script has no fee within Google's quotas, and a CSV import is free but manual.
Why are my Google Forms signups not subscribed in Klaviyo?
Usually because the connector adds or creates the profile instead of subscribing it. Klaviyo's Add Profile to List endpoint points you to Subscribe Profiles for marketing consent, so switch the action to Subscribe Profile in Zapier or Add or Subscribe Profiles to a List in Make. On a double opt-in list, the person is also not subscribed until they click the confirmation email.
Will Google Forms signups trigger my Klaviyo welcome flow?
A flow triggered by joining the list starts when the profile is subscribed to it, so on a double opt-in list it waits for the confirmation. Profiles sent as a historical import skip Added to list flows on purpose, so use that flag only for old responses, never for new ones.
Can I send Google Forms survey answers to Klaviyo profiles?
Yes. In Zapier, add a Klaviyo Update Profile or Create Or Update Profile step after the subscribe step and map each answer to a custom profile property. That makes the Zap multi-step, which needs a paid Zapier plan and uses two tasks per response.
Sources
- Zapier, Google Forms and Klaviyo integrations (triggers and actions)
- Zapier, subscribe new Google Forms responses to profiles in Klaviyo
- Zapier pricing (plans, tasks and two-step Zaps)
- Zapier Help Center, tasks in Zapier
- Make, Google Forms and Klaviyo integration (modules)
- Make pricing (Free plan credits)
- Google Apps Script, event objects (form-submit triggers)
- Google Apps Script, quotas for Google services
- Klaviyo API reference, Bulk Subscribe Profiles
- Klaviyo API reference, Add Profiles to List
- Klaviyo Help Center, how to migrate existing email subscribers into Klaviyo
- Klaviyo Help Center, how to set up your SMS disclosure language
- Klaviyo, sign-up form best practices (3% benchmark submit rate)
- Wisepops, 20+ popup statistics 2026 (email signup popups, about 1 billion displays)
Figures checked November 10, 2026.