FeaturedHealthcare#Supabase#Healthcare#Intake#Operations#Database

Care Coordination Intake Registry

Summarize a non-clinical care coordination request and save the structured intake record to Supabase.

Workflow at a glance

The full canvas, before you import it

Click any node to see its config.

#Supabase#Healthcare#Intake#Operations#Database

Click a node to select it โ€” same as the Heym editor; the panel shows its settings.

5 nodes ยท Free & source-available

Care Coordination Intake Registry

Capture administrative care-coordination requests in a searchable Supabase table. The workflow summarizes the request, builds a simple record, and inserts it into your own database for staff follow-up.

What this workflow does

  1. CareRequest accepts an administrative coordination request
  2. SummarizeRequest creates a factual short summary for staff
  3. BuildIntakeRecord maps the request into database-ready fields
  4. SaveIntake inserts the record into Supabase
  5. IntakeSaved returns the write result

Use cases

  • Referral or appointment coordination queues
  • Non-clinical service requests
  • Internal follow-up registries for operations teams

Setup

Create a Supabase credential and choose it on SaveIntake. Create a care_intakes table with fields such as request_text, staff_summary, and intake_status, or update the table name and Set mappings for your schema.

Notes

This template is for administrative coordination, not clinical triage or medical advice. Apply your organisation's privacy, retention, and access-control policies before sending any sensitive data to an LLM or database.

How to import this template

  1. 1Click Import โ†’ Copy JSON on this page.
  2. 2Open your Heym and navigate to a workflow canvas.
  3. 3PressCmd+V/Ctrl+Vโ€” nodes appear instantly.
  4. 4Add your API keys in the node config panels and click Run.
More workflow templates
View all templates
Heym
incident analysis ยท production AI
Observed across 100s of AI rollouts

AI workflows don't fail because of prompts.
They fail because of orchestration.

symptom ยท glue code01
5 tools
Scripts, vector DB, approval bot, tracing, browser runner โ€” none of them talk.
symptom ยท visibility02
~0%
Observable behavior across the stack. Debugging is guesswork.
with heym ยท one runtimeโ–ฒ
1 canvas
Agents, RAG, HITL, MCP, traces & evals. Self-hosted. Observable.
AI-Native RuntimeProduction-Grade
github.com/heymrun/heym