Skip to content

Daily work

Create a Flow

The five-step wizard for adding a new pipeline. Pick the use case, paste the URLs, set a cadence, optionally dry-run, save.

Customer-app route
/flows/new
Who uses this
Every authenticated team member.

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. 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.
  • 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. Save. First run fires within a few minutes; click Run now on the Flow detail page if you want immediate feedback.

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.