Customer communication Starts from form submission
Request intake to Notion
Classify incoming requests with a governed decision and create a typed row in a Notion database.
How it runs
3 steps, from form submission to outcome
See how “Request intake to Notion” runs inside a governed flow.
- Trigger: On form submission. An incoming request starts the flow.
- Decision: Classify the request. A governed decision classifies the request.
- Action: Create page. A typed row is created in a Notion database.
Step by step
- 1 Trigger On form submission
An incoming request starts the flow.
- 2 Decision Classify the request
A governed decision classifies the request.
- 3 Action Create page
A typed row is created in a Notion database.
Governed by design
The decision step is a DMN model: rules your team can read, test and version, instead of logic hidden in code. Runs record the model or flow version that produced the outcome, so answers stay explainable.
Related use cases
Browse all →- Customer communication Policy renewal notices Decide renewal terms per policy event and e-mail each customer from a verified domain.
- Finance ops Expense report review Check claims against policy limits, route exceptions to a reviewer and log the result to a sheet.
- Approvals Employee onboarding Approve the new hire, create and share a Drive folder and send the welcome mail.