Survey Insights to Segments

What it does

Each Typeform survey response sorted into your interests and an intent, saved on the person's Klaviyo profile, with a weekly theme summary in Slack.

• Starts for each new completed response to your survey in Typeform.
• AI picks the interests the person chose (from your list), their intent (ready to buy, comparing options, just learning, unhappy or other), a one-line summary and a word-for-word quote.
• With a valid email, saves survey_interests, survey_intent and survey_date on the person's Klaviyo profile for your segments and flows.
• Logs every response to your Google Sheet.
• Once every 7 days, counts the week's responses by intent in code (never by the AI) and posts them to Slack with AI's themes and one suggestion.

What it needs

• A paid plan (agents run live on paid plans).
• An AI provider key (Settings → AI Providers).
• Typeform, Klaviyo, Google Sheets and Slack, connected in Settings → Integrations.
• A survey-log tab with the columns Date | Email | Intent | Interests | Summary | Quote.

What it doesn't do

• It doesn't subscribe anyone or change email consent in Klaviyo: it only adds profile properties.
• It doesn't create the Klaviyo segments: build them on the survey properties once.
• The weekly summary goes out with the first response after 7 days, not at a fixed time.
• Typeform only as the survey tool.

Availability and plans

Included free on the Enterprise plan; on other paid plans it's a one-time purchase per workspace (the price is on the Agents page). The Agents page in the app always shows its current status.

Before you start

• A paid plan: agents run live, and the Free plan only runs Dry Runs.
• An AI provider key (OpenAI, Anthropic, Google and more) in Settings → AI Providers. AI usage is billed by your provider.
• These apps, connected in Settings → Integrations: Typeform, Klaviyo, Google Sheets and Slack.
• The app it watches, connected in Settings → Integrations (the agent starts from an app event).
• About 20 minutes.

• Bring your own AI key
• Typeform (live)
• Klaviyo (live)
• Google Sheets (live)
• Slack (live)

Set it up step by step

Get the agent first (buy it, or it's already yours when your plan includes it), then in Agents → My agents press “Set up this agent”. That creates the agent's workflow in your workspace (it counts towards your plan's workflow limit) and opens the canvas with a setup checklist above it. Each item links to the exact place to go and ticks itself off when it's done.

1. Connect your AI provider

The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.

• Connect your AI provider

2. Connect Typeform

Connect Typeform with a personal token that has forms:read and responses:read (Settings → Integrations → Typeform).

• Connecting Typeform

3. Connect Klaviyo

Connect Klaviyo with a private key that has profiles:write (Settings → Integrations → Klaviyo).

• Connecting Klaviyo

4. Connect Google Sheets

Connect the Google account that can open your survey log (Settings → Integrations → Google Sheets).

• Connecting Google Sheets

5. Connect Slack

Connect the Slack workspace for the summary (Settings → Integrations → Slack).

• Connecting Slack

6. Pick your survey

Open the trigger and pick the Typeform account and the survey.

7. Describe your survey

Open “Sort the answers” and “Find the themes” and replace the placeholders with your survey and interests.

8. Pick the Klaviyo account

Open “Update the Klaviyo profile” and pick the account.

9. Pick the survey log

Open “Log the response” and “Read the survey log” and pick the same spreadsheet and tab (columns Date | Email | Intent | Interests | Summary | Quote).

10. Pick the Slack channel

Open “Post the weekly summary” and pick the workspace and channel.

11. Test it with Dry Run

Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.

• Dry Run vs Run

12. Switch the trigger on

Open the trigger and click “Activate app trigger”: new responses are checked every few minutes.

How it works

The agent is a normal workflow with 20 steps (2 AI steps). You can open, edit and monitor it like any other workflow.

• New Typeform response — Starts on “New response” in Typeform (an app event). Starts a run for each new completed response to your survey (checked every few minutes).
• Sort the answers — AI step (runs on your AI provider key). AI reads the answers and picks the person's interests (from your list), their intent, a one-line summary and a word-for-word quote.
• Today's date — Step. In code: today's date in your time zone, for the log and the weekly summary.
• Has an email? — Step. In code: exactly one valid email address, so the profile can be found in Klaviyo.
• Update Klaviyo? — Decision: picks the branch to follow. With a valid email the Klaviyo profile gets the segments; without one the response is only logged.
• Update the Klaviyo profile — Klaviyo: Create or update a profile. Branch: Valid email. Creates or updates the person's Klaviyo profile with survey_interests, survey_intent and survey_date, for segments and flows. It doesn't change their email consent.
• Log the response — Google Sheets: Add a row. Branch: Log only. Adds a row to your survey log (Date | Email | Intent | Interests | Summary | Quote).
• When was the last summary? — Recalls what it remembered earlier (memory “survey-insights-to-segments”). Reads the date of the last weekly summary.
• Summary due? — Step. In code: the summary goes out once every 7 days, with the first response after that.
• Send the summary? — Decision: picks the branch to follow. Once every 7 days; otherwise this run ends here.
• No summary this run — Kept in the run history. Branch: Not yet. The last summary went out less than 7 days ago.
• Read the survey log — Google Sheets: Read rows. Branch: Weekly. Reads your survey log.
• Keep the last 7 days — Step. In code: keeps the responses logged in the last 7 days.
• Each response this week — Repeats the steps below for each item (up to 300 per run). Goes through this week's responses so they can be counted (up to 300).
• [For each item — “Each response this week”] Counted — Kept in the run history. Nothing is changed in the log.
• Count by intent — Step. In code, not AI: this week's responses grouped and counted by intent.
• Find the themes — AI step (runs on your AI provider key). AI reads this week's counted responses and writes the main themes and one suggestion, without restating the counts.
• Post the weekly summary — Slack: Post a message. Posts the counts (from code) and the themes to your Slack channel.
• Remember this summary — Remembers it for later runs (memory “survey-insights-to-segments”, kept 60 days). Stores today's date so the summary goes out once a week.
• Summary posted — Kept in the run history. The run history keeps the summary.

Test it with Dry Run

Press Dry Run in the canvas. The agent runs on the sample data stored on its trigger (the “Sample data for Dry Run” box), so you can check every step's output before anything is live. The sample has the same shape as a real event from the app.

Sample data fields

response_id, token, submitted_at, landed_at, answers (a list), hidden, score, variables (a list), metadata.platform, metadata.referer.

• Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.
• For-each loops repeat only the first 3 items.
• Memory steps don't read or write stored memory: a recall finds nothing, and a save only shows what it would store.

Go live

• Open the trigger and click “Activate app trigger”: new responses are checked every few minutes.
• Activating the app trigger needs the trigger's connected account. The first check only remembers what's already there, so older items don't start runs; the same item never starts two runs.
• The setup checklist adds a “paid plan” item before activation: live runs need a paid plan (the Free plan only runs Dry Runs).
• When every checklist item is done and the trigger is on, the checklist says “Live — this agent is running”. Follow its runs in the workflow's History tab and in Analytics → Agents.

• App event triggers
• Switching a trigger on (Activation)

Questions

What changes in Klaviyo?

The person's profile gets three properties: survey_interests, survey_intent and survey_date. Build segments or flows on them. Their email consent isn't changed: someone who isn't subscribed stays unsubscribed.

When does the weekly summary arrive?

With the first survey response at least 7 days after the last summary. A week without responses has no summary.

Are the counts right?

Yes: they're counted in code from the log, by intent. The AI only writes the themes and the suggestion, without numbers.

Troubleshooting

• “No AI provider connected” or a rejected key: connect or fix the key in Settings → AI Providers, then press Test there.
• A checklist item stays unticked: the setting is still empty or still contains its placeholder text. Open the step from the checklist and fill it in.
• An app step fails with “Needs reconnect”: the account's access was revoked or expired. Reconnect it in Settings → Integrations.
• Slack says the app isn't in the channel: in Slack, type /invite @Fluxo Flow in that channel (always needed for private channels).
• No runs start: activate the app trigger with a connected account. Only items created after activation start runs.
• A step failed: open the run in History and check that step in the Trace tab for the error and what it received.

• Debugging failed runs
• Error messages
• Get help