Use Shopify Flow to route Lantern quiz completions into the rest of your stack—marketing tools, CRMs, helpdesks, and ops apps—without writing code. This guide gives you a reusable base workflow and a set of mini‑recipes you can adapt to any Flow‑compatible app.
Prerequisites
Shopify Flow installed and active.
A published Lantern quiz collecting responses.
Optional (for customer data): add an Opt‑in page and enable Create customer in Shopify in Lantern (Results Page → Order & Customer Tags), then republish. If you turn this on, use the Flow trigger “Quiz Completed — with customers.” Otherwise, use “Quiz Completed.”
Base Workflow
1. Start the workflow
1.1 Open Shopify Flow, click Create workflow, then choose Select a trigger.
1.2 In the editor, select Lantern as the app.
1.3 Choose the trigger that fits your setup: Quiz Completed — with customers (recommended if you enabled customer creation) or Quiz Completed.
2. (Optional) Scope which quizzes run
2.1 Click the plus icon → Condition.
2.2 Click Add a variable, choose quizID, leave Equal to, then enter your Quiz ID (find it in Lantern → More Integrations).
2.3 You can add more conditions later (e.g., check a specific answer) to route different branches.
3. Add a short delay
3.1 Click the plus icon → Action → Flow → Wait.
3.2 Set 30–60 seconds so new customers finish creating/propagating before downstream actions run.
4. Add your destination app action(s)
4.1 Click the plus icon → Action.
4.2 From the app list, select your tool (marketing, CRM, helpdesk, ops), then choose the relevant action.
4.3 Map identifiers/fields using Add variable (see Variables below).
4.4 (Optional) Add additional branches for different quizzes or answers.
5. Turn it on and test
5.1 Give your flow a name.
5.2 Click Turn on workflow to activate.
5.3 Complete a test quiz and verify the action executed (Flow → Runs) and that your destination app received the data.
Variables You Can Use Anywhere
Quiz metadata:
{{quizName}},{{quizID}},{{sessionId}},{{resultsUrlFull}}Customer (only with the — with customers trigger + customer creation enabled):
{{email}},{{customer.id}}Responses loop (for email bodies, notes, or payloads that accept text):
A customer has completed the quiz {{quizName}}.
Session ID: {{sessionId}}
Results page: {{resultsUrlFull}}
The following responses were provided:
{% for responses_item in responses.responses %} {{ forloop.index }}. {{ responses_item.question }} — {{ responses_item.answer }} {% endfor %}Tip: Some app actions only accept short text. In those cases, include a brief summary and the {{resultsUrlFull}} link instead of the full loop.
Applications of Shopify Flow Integrations
A. Marketing: add/update a contact and tag with quiz context
Use Shopify Flow to send Lantern quiz data to your marketing service by adding or updating the contact (email or customer ID) and writing a tag or custom field with {{quizName}}, {{quizID}}, and optionally “Completed via Lantern”; optionally scope the flow to a specific quiz or response.
B. CRM: create/update a person and log the quiz
Use Flow to create or update the person/contact in your CRM (email or customer ID) and log the quiz with a short note plus {{resultsUrlFull}} and any key answers; if there’s no connector, send an internal email to your CRM’s dropbox/forwarding address.
C. Helpdesk: open a ticket when certain answers indicate support needs
Use a condition on keywords/choices to create a ticket/conversation in your helpdesk, setting the subject to “Quiz Completed — {{quizName}}” and including {{resultsUrlFull}} with a brief summary (avoid sensitive details).
D. Fulfillment/Ops: tag customers or kick off internal tasks
Use Shopify actions to add a customer tag (e.g., quiz-skin-dry) or set a customer metafield based on answers, then—if your ops tool has a connector—trigger a task or handoff.
E. Internal notifications: email the team
Use Flow → Send internal email to notify the team with subject “Quiz Completed — {{quizName}}” and either the responses loop or a short summary plus {{resultsUrlFull}}.
Tips
Pick the right trigger: use “— with customers” when downstream actions require Customer ID or email.
Wait helps reliability: keep 30–60s (or 60–120s for brand‑new customers) before app actions.
Route by quiz or answer: add Conditions to branch the flow, and label branches clearly.
Prevent duplicates: add a customer tag after your action (e.g.,
quiz-notify-posted) and check for it at the top on re‑runs.PII hygiene: avoid sending sensitive answers into third‑party systems; link
{{resultsUrlFull}}instead.Testing: after your app action, temporarily add Shopify → Add customer tag as a proof step; if the tag appears, Flow ran to that point.
Troubleshooting
Flow ran, app didn’t update: open Flow → Runs and inspect inputs for your app action; confirm identifiers and that the step shows Completed.
Customer not found: ensure you enabled Create customer in Shopify, republished the quiz, and used the — with customers trigger; consider adding a short Wait.
Wrong quiz firing: add the quizID condition.
No connector? Use Send internal email to the app’s intake address or tag/metafields for downstream syncs.
Plan limits: some app actions require specific plan tiers; if an action is missing, check the app’s plan/integration settings.