JUST Docs
Tutorials

Create a workflow and send it to Klaviyo

Build a guided workflow, name its answers with Klaviyo keys, and receive a "Workflow Completed" event on each shopper's profile.

At the end of this tutorial, every shopper who completes your workflow sends a Workflow Completed event to Klaviyo, attached to their profile by email and carrying their answers under the keys you chose.

Prerequisites

1. Build the workflow

On the Workflows page, create a workflow: the questions the agent asks one by one before recommending products.

An email step is required

The event is sent only when the run captured a valid email address. Add an Email step to the workflow. Its wording doubles as the consent line, so say what the email will be used for. A run without a usable email sends nothing.

Name each answer with a Klaviyo key

Each step has a Klaviyo key field: it names that answer's property in the outgoing event. Left empty, the step keeps its default key, shown as the field's placeholder. A readable key (skin_type, budget) is what you will select in Klaviyo when building a segment or a flow filter.

The Klaviyo keys panel at the bottom of the builder recaps every key the event will expose.

Renaming a key breaks what was built on it

Klaviyo segments and flow filters reference properties by name. If you rename a key later, everything built on the old name stops matching.

2. Choose the destination

At the bottom of the workflow, the On completion bar selects what fires once a shopper completes the workflow. Pick Klaviyo. The picker is enabled only while the integration is connected.

3. Set the workflow live

Set the workflow live from the workflows list. Shoppers trigger the live workflow from your store: see Expert Mode for the button and the data-workflow attribute.

4. What arrives in Klaviyo

Each completed run sends one Workflow Completed metric event. Klaviyo creates the metric on the first event; no setup is needed on Klaviyo's side. The event upserts the shopper's profile by email and carries:

PropertyContent
your Klaviyo keysEach answer, at the top level under the step's key, in the shop's default language
workflow_nameThe workflow's name
answersEvery answer, keyed by the question's wording, in the shop's default language
answers_by_keyEvery answer, keyed by the step's Klaviyo key, in the shop's default language
answers_as_givenEvery answer as the shopper gave it, keyed by the step's Klaviyo key
recommended_productsThe recommended products: title, url, price…

The Integrations card shows the last event sent and, if any, the last delivery error.

Answers in the shop's default language

On a storefront in another language, the shopper picks translated options. The event carries each option as you wrote it in the shop's default language, so one segment or flow filter matches every shopper, whatever their language. The answer of a step skipped with "Skip" arrives in the default language too. Free-text answers stay as the shopper typed them.

To repeat an answer in an email as the shopper gave it, read answers_as_given in the template: {{ event.answers_as_given.skin_type }}. This property is nested, so segments and flow filters cannot use it.

Next

On this page