Create a Flow

What it is

The wizard for adding a new Flow. Walks you through use case → Slate Query — In Progress → Slate Query — Positive Outcomes → Slate Source Format — Writeback → cadence → dry-run toggle → optional Fraud Protection toggle (Enterprise). Saves on the last step and schedules the first run within a few minutes.

What you'll need before you start

• A Slate Query — In Progress URL with service-access enabled (applications Celia will analyze on each run).
• A Slate Source Format — Writeback URL where Celia writes the scores back into your Slate records (ss_celia_* fields).
• A Slate Query — Positive Outcomes URL (last year's converters + this cycle's enrollees — Celia learns from them).
• A populated Data Dictionary so Celia knows your field names — and specifically, all nine required fields must already be in the dictionary before you can activate the Flow: student_type, program_interest, entry_term, campus_visit_count, last_activity_date, application_status, home_state, docs_missing, residency_country. Add these fields to both Slate queries and click Refresh fields on the Flow detail to discover them.
• An active Slate connection — see Slate connection.

Step by step

1. Pick the use case. Risk scoring is the default. Each use case dictates the columns the In Progress query must return.
2. Paste the Slate Query — In Progress URL. The wizard makes a test request and rejects URLs that don't return rows.
3. Paste the Slate Query — Positive Outcomes URL. Celia uses the rows here to calibrate what "good" looks like for your funnel.
4. Paste the Slate Source Format — Writeback URL. The wizard checks it's reachable.
5. Choose cadence. Daily is most common. Weekly for slow-moving cohorts.
6. Toggle dry-run on. Recommended for the first 24 hours — Celia analyzes but does not write back. Verify the output, then flip dry-run off.
7. Optional: enable Fraud Protection. Enterprise plan only — see the section below.
8. Save. First run fires within a few minutes; click Run now on the Flow detail page if you want immediate feedback.

Optional: Fraud Protection (Enterprise)

The form's Fraud Protection Analysis section carries a single checkbox — Enable Fraud Protection Analysis. Checking it adds a fourth parallel Celia analysis to every run of this Flow, looking at the same anonymized rows for patterns worth a human second look (application integrity, financial aid patterns, data consistency, cohort anomalies). It surfaces a signal for human review, never a fraud determination.

• Enterprise only. On other plans the toggle is visible but locked with an "Enterprise feature" note.
• Four more writeback fields. Enabling it adds the four ss_celia_fraud_* fields to the writeback (34 fields instead of 30) — your Slate Source Format must declare them or Slate silently drops them. See the starter kit field tables.
• One more echo field. Add ss_celia_fraud_level to your In Progress query's echo set so Celia's run-over-run stability safeguard covers the fraud verdict.

Full walkthrough — categories, confidence interpretation, and the review workflow — in the Fraud Protection guide.

Common gotchas

In Progress query URL test fails

Service-access usually isn't on. In Slate: Database → Queries → your query → Service → enable, then re-copy the URL.

Writeback URL test fails

The Slate Source Format may not exist yet, or its endpoint is misconfigured. Open the Source Format in Slate and confirm it accepts POSTs from your CeliaConnect IP allowlist.

I'm not sure which use case to pick

Start with risk scoring. It produces all three dimensions plus a Recommendation. You can add more focused Flows later.