Documentation
Start, Connect, and Operate with Confidence
This guide is for new teams using OK | Flows for the first time. It covers the product model, the builder, logic, secure prefill, Salesforce delivery, and the operational habits that matter once a flow is live.
What OK | Flows actually is
Before you start configuring anything, it helps to understand the product model. OK | Flows is not just a form builder. It is a governed capture, logic, prefill, and delivery layer for Salesforce-oriented campaign experiences.
Flows
A published respondent experience with branding, steps, success states, and optional gamification.
Logic
Branching, conditional visibility, simulator tooling, and publish-time routing checks.
Delivery
CloudPage or Marketing Cloud data delivery, mappings, upsert control, and operational sync behavior.
Prefill
Signed or opaque context resolution so the flow can know who the respondent is before the first step.
How the system works
This is the end-to-end flow a new team should keep in mind. The product is strongest when you think about it as a governed journey from context resolution through downstream delivery.
Prefill resolves
JWT, opaque token, or audience-run context resolves before the first step where required.
Journey runs
The respondent moves through branded steps, block logic, and conditional visibility.
Response is captured
The platform stores a completed response or preserves a partial draft if the flow is abandoned.
Delivery executes
CloudPage or Marketing Cloud delivery writes mapped output using insert or upsert rules.
Operators review
Teams review responses, runs, sync state, and downstream campaign behavior from the dashboard.
Quickstart
This is the fastest sane path for a new team. It prioritizes a successful first launch over exploring every possible feature on day one.
Create or template a flow
Start blank or use a seeded template when you want default blocks, success copy, and SFMC-ready scaffolding.
Shape the respondent experience
Add blocks, tune copy, set theme overrides, configure success actions, and make the flow feel on-brand.
Add logic only where it matters
Use branching, display conditions, and the simulator to control pathing without making the flow hard to maintain.
Connect delivery
Enable CloudPage or SFMC delivery, choose insert or upsert behavior, and map your fields to target attributes.
Publish and verify
Run through the publish preflight, open the public URL, submit test data, and confirm the target system receives what you expect.
Operate and improve
Review responses, monitor drafts and partial sync, and refine theme, logic, and mappings from real campaign feedback.
Builder basics
The builder is where you shape the respondent experience. New users should focus first on content structure, theme fit, and success-state clarity before adding advanced logic.
Content and blocks
Build the step sequence with text, choice, image, structured contact, rating, hidden, and logic-aware blocks.
Theme and branding
Use preset themes or override colors, typography, spacing, shell elements, media, and max-width behavior.
Success and completion
Configure completion messaging, follow-up CTAs, reward presentation, and next-step guidance after submit.
Responses and analytics
Track outcomes, review submissions, and inspect form-level signals after the flow is live.
Logic and workflow
Add logic where it improves the journey, not everywhere by default. The platform already supports path simulation, condition testing, and risk visibility, so use those tools before publishing any complex branch model.
OK | Flows supports both answer-driven and context-driven paths. That means the same flow can react to what a respondent chooses and to what SFMC or prefill already knows about them.
Answer-based and context-based branching
Conditional visibility with show or hide behavior
Path simulator with sample answers and prefill context
Cycle and hidden-target warnings in preflight
Path-aware back navigation during the live journey
Per-block logic and display-condition testing
Good practice
Start with the simple path first, then layer in logic. Before publishing, run the simulator with realistic answers and prefill context so your team can verify the journey instead of guessing how it will behave live.
Salesforce Marketing Cloud setup
This is the minimum path to get a governed flow writing to your downstream destination without relying on ad-hoc landing page glue.
- 1
Configure global SFMC or CloudPage credentials in Dashboard Settings.
- 2
Open a flow and enable CloudPage or SFMC delivery in the form-level integration settings.
- 3
Choose insert or upsert depending on whether you are creating new rows or updating existing audience members.
- 4
Map block outputs and system fields to the correct target Data Extension attributes.
- 5
Publish the flow, submit a controlled test, and verify the target Data Extension receives the expected shape.
Insert mode
Use when each submission should create a new row and you want a record of every send or response event.
Upsert mode
Use when submissions should update an existing contact or audience row using a stable key such as ContactID or EmailAddress.
Important: connection success is not enough. You still need the right Data Extension key, exact field names, and the right insert or upsert behavior for the delivery model you are implementing.
Prefill models
Prefill determines how the flow learns who the respondent is before they begin. This is a core part of the product, especially for personalized or Salesforce-driven journeys.
JWT prefill
Good for signed links when you control the secret on both sides and want lightweight contextual access.
Opaque token prefill
Good when you want the form to resolve context from a stored token rather than embedding the payload directly in the URL.
Audience prefill runs
Good for campaign-scale generation when you need many prefill URLs prepared and written back into SFMC in batches.
Operations, drafts, and campaign-scale workflows
New users often focus on the form itself and forget the operational layer. OK | Flows includes draft capture, deferred sync, and managed audience workflows because production campaigns rarely stop at the submit button.
Partial-response capture
Flows can store unfinished drafts so you can preserve signal from respondents who do not complete the full journey.
Deferred sync
Drafts can be synced later to CloudPage or SFMC through cron or the manual sync control in the dashboard.
Managed runs
Audience prefill runs expose creation state, processing state, and operational visibility for large campaign sends.
Gamification
Prize pools, reveal mechanics, inventory controls, and reward metadata can be returned as part of the same governed flow model.
API reference
These are the core routes that matter most when integrating the platform, testing flows, or operating automation around them.
POST/api/forms/:formId/submit// Submit a completed response.POST/api/forms/:formId/draft// Save or update a partial response draft.POST/api/forms/:formId/prefill// Resolve signed or opaque prefill context for the form.POST/api/forms/:formId/prefill-tokens// Mint opaque prefill links one at a time.POST/api/forms/:formId/prefill-tokens/bulk// Mint opaque prefill links in bulk.POST/api/forms/:formId/sfmc-prefill-sync// Generate and push prefill URLs back into SFMC.POST/api/forms/:formId/sfmc-partials-sync// Manually sync partial drafts for one form from the dashboard context.POST/api/cron/sfmc-partials-sync// Process stale drafts globally and write them to the configured target.POST/api/cron/sfmc-prefill-runs// Process managed audience prefill runs.
For environment-level deployment details, the repository README, runbooks, and feature logs should still be treated as the deeper technical source of truth.
Security and production notes
These are the habits worth following before you put real traffic or real audience data through the platform.
Use signed transport and verify webhook signatures whenever CloudPage delivery is enabled.
Treat prefill secrets, cron secrets, and CloudPage shared secrets as separate credentials.
Do not publish a flow until the preflight warnings and critical issues are understood.
For larger SFMC sends, prefer managed prefill runs or opaque prefill rather than hand-built links.
Troubleshooting
These are the most common first-week issues teams run into when they move from simple form publishing into real Salesforce-connected campaign workflows.
SFMC connection test passes but no data arrives
Check the target Data Extension key, verify exact attribute names, and confirm whether insert or upsert is the right mode for your target row model.
Prefill links open the flow but show token or context errors
Verify the prefill secret matches the deployed environment and confirm the form ID or token mode matches the flow you are opening.
Partial drafts exist but nothing is written back
Confirm partial capture is enabled on the form, CloudPage delivery is active, and the cron or manual sync route is being triggered successfully.
Conditional paths behave unexpectedly
Use the logic simulator with representative answers and prefill context, then inspect any hidden-target or cycle warnings before publishing again.
Gamification visuals work but rewards or metadata feel inconsistent
Validate the prize configuration, reveal mechanic settings, and mapped output fields so the visual effect and allocated outcome stay aligned.
Need implementation help?
If you are planning a live SFMC rollout, onboarding a new team, or validating prefill and delivery behavior before a campaign, we can help you structure the implementation correctly.