Systeme.io is great for selling, sending emails and running your funnels. For looking at your list, not so much.
You want to count how many people came in through last month's lead magnet. Share the list of sign-ups with the person who helps you, without giving them access to your account. Cross your quiz answers with your sales to see which profile actually buys. For all of that, a Google Sheet is hard to beat: columns, filters, a chart in two clicks.
Most tutorials you'll find are about Pabbly, Make or Zapier, and they skip the fact that Systeme.io now has its own integration. Here are the five ways to do it, what each one really sends to your sheet, and the quiz case nobody covers.
Before you choose: a snapshot or a tap?
Two very different needs hide behind the same question.
- The snapshot. You want your list at a given moment, to clean it up, prepare a review or send it to someone. An export is enough, and it's free.
- The tap. You want every new contact to land in the sheet on its own, the moment they sign up. That takes automation: a Systeme.io workflow, or a middleman like Make.
A snapshot is taken by hand. A tap runs without you.
Way 1: the Systeme.io CSV export
This is the simplest option. According to Systeme.io's help center:
- Go to the CRM tab, then Contacts.
- Select the contacts you want to export.
- Click More actions, then Export.
- Systeme.io generates a CSV file and sends it by email to your account address.
The catch: the file can only be downloaded for 3 days. After that it's deleted, and you have to run the export again.
Then, in Google Sheets: File, then Import, and pick your CSV. The Append to current sheet option adds the new contacts below the old ones, handy if you export every month.
Good for: a monthly review, a list cleanup, a backup. Not for: following sign-ups live.
Way 2: the native Google Sheets integration, in a workflow
This is the one tutorials forget: Systeme.io has its own Google Sheets integration, with no Zapier or Make involved.
1. Connect your Google account. Click your profile picture, then Settings, and Integrations in the left menu. Pick Google Sheets, click Connect, choose your Google account and allow access to the files you use with Systeme.io. You can connect several Google accounts.
2. Build the workflow. Under Automations, then Workflows, create a workflow and pick its trigger: tag added, form subscribed, new sale, course enrollment, page visited... Then add the action Add a new row to a Google Sheet. You choose the file, the worksheet, and map each piece of data to a column. A Test button lets you check before you activate it.
Four things to know before you rely on it:
- It lives in workflows, not in automation rules. The help center says it plainly: a simple rule can't do it.
- Your sheet must already exist, with its column headers. The integration doesn't create sheets from scratch. Type Date, First name, Email... on the first row first.
- It adds rows, it doesn't update them. A contact who triggers the workflow twice shows up twice.
- A workflow only counts what happens after it's activated. Your existing contacts won't go through it: for them, use way 1.
Systeme.io's pricing page lists Google Sheets in its integrations table, plan by plan. Check your plan's line before building everything on it.
Way 3: Make, with the Systeme.io webhook
Make has a Systeme.io app, but it can only act: create a contact, add a tag, enroll someone in a course. It has no trigger. For Make to know a contact just arrived, Systeme.io has to tell it, with its send webhook action.
- In Make, create a scenario that starts with the Webhooks module, "Custom webhook", and copy its address.
- In Systeme.io, add a webhook action to an automation rule (on your opt-in page's form, for example) or to a workflow (on a tag added), and paste the address.
- Run a test sign-up. Systeme.io sends the event as JSON, and Make learns its structure.
- Add the Google Sheets "Add a Row" module and map each field to its column.
What comes through is richer than a plain row: the event type, the contact with its fields, and depending on the trigger, the order, the tag, the course or the webinar. You keep what you need.
Make's free plan gives you 1,000 credits a month, plenty to test. On the Systeme.io side, the pricing page lists a single automation rule on the free plan: if it's already in use, go through a workflow.
Way 4: Zapier
Zapier also has a Systeme.io app, and this one has triggers: New Optin, New Sale, New Tag Added to Contact, New Webinar Registration, New Completed Campaign. A two-step Zap is enough: the Systeme.io trigger, then a row in Google Sheets. No need to touch your Systeme.io rules.
Zapier's free plan allows two-step Zaps and 100 tasks a month, with an advertised update time of 15 minutes. Beyond that, you need a paid plan. It's the right pick if you already have a Zapier account.
Way 5: Pabbly Connect
Pabbly works like Make: Systeme.io sends a webhook, Pabbly catches it and adds the row. Its official tutorial starts from an automation rule on an opt-in form, with the "Send Webhook" action, then uses the Google Sheets "Add New Row" action.
Its selling point is price: a free plan with 100 tasks a month, one-time payment plans, and internal steps (filters, routers, text formatting) that don't count as tasks.
The 5 ways side by side
| Price | Difficulty | Real time | What lands in the sheet | |
|---|---|---|---|---|
| Systeme.io CSV export | Free | Very easy | No, redo it by hand | The selected contacts, in one go |
| Native integration (workflow) | Included in Systeme.io, depending on your plan | Easy | Yes | One row per trigger, with the fields you map |
| Make | Free up to 1,000 credits a month | Medium | Yes | The whole webhook event: contact, fields, tag, order |
| Zapier | Free up to 100 tasks a month | Easy | Depends on the plan (15 min advertised on free) | The data from the Systeme.io trigger |
| Pabbly Connect | Free up to 100 tasks a month | Medium | Yes | The webhook data |
My advice if you're starting from scratch: the native integration for the tap, the CSV export for the snapshot. Bring in Make only on the day the workflow isn't enough.
The quiz case: answers in Google Sheets, the contact in Systeme.io
A quiz is a goldmine for a spreadsheet. Each row tells you who the person is, what they answered and which profile they got. After fifty responses, you see which roadblocks keep coming back, in which words, and that's often where your next offer is born.
But you also want that contact in Systeme.io, with the right tag, so your email sequence starts. There's one rule to know on the Tiquiz side: a quiz sends its leads to a single destination, Systeme.io, GoHighLevel or a webhook. To get both, there are two setups.
Setup A: all native, Tiquiz then a Systeme.io workflow
Tiquiz sends the lead to Systeme.io with its profile tag, the custom fields from your capture form and, if you set them up, the tags for their answers. In Systeme.io, a workflow starts on tag added (a profile's tag) and adds a row to your sheet.
The small trick that changes everything: one workflow per profile, one worksheet per profile. Your "Busy Strategist" tab fills up on one side, "Stuck Perfectionist" on the other. You see at a glance which profile grows fastest.
The limit: the sheet only gets what Systeme.io knows about the contact. Detailed answers, question by question, aren't on the contact record. On the Tiquiz side, this setup uses a single connection, so it works on the free plan.
For profile tags, the Systeme.io tags guide explains how to name them, and the Systeme.io automation rules article what you can trigger with them.
Setup B: the Tiquiz webhook and Make, to keep every answer
Here, the quiz sends its leads to the Tiquiz webhook. The webhook reaches Make within a second with a complete lead: the contact, the profile, the score, every answer in order, custom fields and tags. In the same Make scenario, one after the other:
- Google Sheets "Add a Row": a row with the date, first name, email, profile, score and one column per question;
- Systeme.io "Create a Contact", then "Add a Tag to a Contact" with the profile tag: your sequence starts as usual.
This is the most complete setup: your sheet becomes a research notebook, and Systeme.io stays your email engine. The trade-off: you rebuild in Make what the native connection does on its own (course enrollment, answer tags, score ranges). You only get what you add to the scenario.
On the Tiquiz side, the webhook counts as one connection. Your Systeme.io key lives in Make, not in Tiquiz, so this setup also fits the free plan. The step by step to create and test the webhook is in the webhook explained simply, and the exact data format on the webhook help page.
And with no automation at all?
Tiquiz has its own export: in My leads, the Export CSV button gives you a file with one column per question, the date, phone, country, scores on a scored quiz and the tag applied. Accents come through cleanly, and it imports into Google Sheets exactly like the Systeme.io file. It's the snapshot, quiz edition.
Take action: your quiz sheet in 20 minutes
Don't look for the perfect setup. Start simple, and add detail only when you need it.
- Create the sheet. One tab per profile, and on the first row: Date, First name, Email. Add the columns you want to fill.
- Connect Google Sheets to Systeme.io: Settings, Integrations, Google Sheets.
- Connect your Tiquiz quiz to Systeme.io and give each profile a tag.
- Create one workflow per profile: trigger tag added, action Add a new row to a Google Sheet, the right tab. Test, then activate.
- Take the quiz yourself, with a test address. The row should appear in the right tab, and the contact in Systeme.io.
In a month, open your sheet and count. The biggest profile is the audience waiting for you. The profile that buys the most is the one you talk to first. A sheet and five minutes are enough to see it.
FAQ · Systeme.io and Google Sheets
Does Systeme.io have a native Google Sheets integration?
Yes. According to Systeme.io's help center, you connect your Google account under Settings, Integrations, then use the "Add a new row to a Google Sheet" action in a workflow. It isn't available in simple automation rules, and it adds rows without updating existing ones.
Can I export Systeme.io contacts to Google Sheets without Zapier?
Yes, two ways. The CSV export (CRM, Contacts, select, More actions, Export), which you then import into Google Sheets. Or the native Google Sheets integration in a workflow, for new contacts as they come in.
Can a Tiquiz quiz send its leads to both Systeme.io and a webhook?
No, a quiz has a single destination. To get both, send the quiz to Systeme.io and let a workflow write the row to your sheet, or send it to the webhook and let Make create the contact in Systeme.io on top of the row.
How many connections does each Tiquiz plan include?
A connection is a Systeme.io key, a GoHighLevel sub-account or a webhook. The free plan has 1, the subscription ($17/month or $170/year) has 2, PLUS has as many as you want. On the free plan, the 10 visible leads per 30-day window are sent.
Do quiz answers end up in Google Sheets?
With the Tiquiz webhook, yes: every answer travels with the lead, and Make can turn them into one column per question. Going through Systeme.io, the sheet only gets what the contact record holds. And the CSV export in My leads always has one column per question.
Make, Zapier or Pabbly: which one for Systeme.io?
Zapier if you already have an account: it has ready-made Systeme.io triggers. Make or Pabbly if you want more free operations: both catch the Systeme.io webhook. And if one row per new contact is all you need, the native integration skips all three.
Sources (checked November 2, 2026)
- Systeme.io, how to import or export a contact list (export sent by email, file available for 3 days): help.systeme.io/article/238
- Systeme.io, how to integrate Google Sheets (Settings, Integrations; workflows only; column headers required; updated March 27, 2026): help.systeme.io/article/3739
- Systeme.io, how to create workflows (triggers and actions, including "Send webhook" and "Add a new row to a Google Sheet"; updated October 12, 2026): help.systeme.io/article/1542
- Systeme.io, how to trigger a webhook after an opt-in or a sale (automation rule or workflow, JSON data): help.systeme.io/article/144
- Systeme.io, pricing (1 automation rule on the free plan, Google Sheets in the integrations table): systeme.io/pricing
- Make, Systeme.io app (actions only, no trigger): apps.make.com/systeme-io
- Make, Systeme.io and Google Sheets: make.com
- Make, pricing (1,000 credits a month on the free plan): make.com/en/pricing
- Zapier, Systeme.io and Google Sheets (Systeme.io triggers): zapier.com
- Zapier, pricing (100 tasks a month, two-step Zaps, 15-minute update time on free): zapier.com/pricing
- Pabbly, save Systeme.io leads to Google Sheets: pabbly.com
- Pabbly Connect, pricing (100 tasks a month free, one-time payment plans): pabbly.com/connect/pricing
- Google, import a CSV file into Google Sheets: support.google.com




