Generate Personalized Customer Responses Instantly
Customer message arrives? Get a personalized response draft in seconds. Edit or send as-is.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Text Chat Completion
Tool to generate text completions or chat responses using a specified llm model. use after assembling the conversation history to produce the next response.
Why this helps
Customer messages require immediate response. Composition is cognitively taxing and delays create frustration.
- Response drafts appear within seconds with no composition delay
- Maintains personalization while saving time
- Faster response times improve customer satisfaction
- Reduces cognitive load of constant customer communication
Setup
Build it in a few focused steps.
- 1Connect Ai ml api to Notis via the portal.
- 2Ask Notis 'Generate customer response drafts when messages arrive' or configure via Automations.
- 3Set up a webhook or integration to route incoming customer messages to Notis.
- 4Define your response tone and guardrails (never promise timelines, mention core offer).
- 5Send a test customer message and verify a personalized draft appears within seconds.
Questions about this workflow
Will the response sound generic?
Not if you provide personality guidelines. Tell Notis your tone, values, and unique selling points, and it weaves those in.
Can I edit before sending or must I send as-is?
Always edit. Every draft is a suggestion you can refine, personalize, or reject. No automated sending.
What if the customer is asking something complex?
Notis generates a first draft to get you started, but you add expertise and nuance for complex questions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ai ml api. A trigger fires from one place; an action lands in another.
Notion triggers
Ai ml api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Moderation Completion
Tool to classify input text or image for safety using a moderation model. use after receiving user-generated content to filter out unsafe material.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Text Chat Completion
Tool to generate text completions or chat responses using a specified llm model. use after assembling the conversation history to produce the next response.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion and Ai ml api, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Ai ml api.