Keep reusable replies aligned with current processes
Publish the new process in Notion and refresh the matching Helpwise template with its approved guidance.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Update Helpwise Template
Tool to update an existing email template. Use when you need to modify template name, subject, or content after confirming the template ID.
Why this helps
A new process can be ready in Notion while a saved reply still tells customers to follow the previous steps.
- Reduce outdated customer instructions.
- Make one approved process change easier to carry through.
- Keep reusable replies aligned with team practice.
Setup
Build it in a few focused steps.
- 1Connect Notion and Helpwise to Notis once through the portal.
- 2Create an automation that tells Notis in plain language to update the intended existing Helpwise template from an explicitly approved process page.
- 3Select Page Created and scope it to the process library data source.
- 4Choose a report channel and test with a low-risk template and approved process update.
Questions about this workflow
Can the workflow create a template?
The selected action updates an existing template. Have Notis report when the intended template is not clear.
How can I avoid publishing an unapproved process?
Include an explicit approval requirement in the prompt before any template update.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Helpwise. A trigger fires from one place; an action lands in another.
Notion triggers
Helpwise actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create attachment
Tool to upload a new attachment. Use when you need to send a file to Helpwise and receive its attachment metadata.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add note to conversation
Tool to add a note to a conversation. Use after obtaining the conversation_id to provide context.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Helpwise Team
Tool to create a new team. Use when you need to group users under a team. Use after confirming unique team name.
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.
Create Helpwise Webhook
Tool to create a new webhook in Helpwise. Use when you need to receive event notifications for conversations, messages, or other triggers.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Contact
Tool to delete a contact. Use when you need to remove an existing contact by its unique identifier. Implements robust endpoint probing similar to DeleteWebhook: tries multiple paths and HTTP methods to accommodate dev-apis variations, with user-scoped fallbacks.
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.
Delete Helpwise Conversation
Tool to delete a conversation. Use when you need to permanently remove a conversation by its ID after confirming the ID is correct.
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.
Delete Mailbox
Tool to delete a mailbox. Use when you need to remove an existing mailbox by its unique identifier.
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.
Delete Helpwise Message
Tool to delete a message. Use when you need to permanently remove a message by its ID after confirming the ID is correct.
Connect any two apps with Notis in the middle.
Notion and Helpwise, 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 Helpwise.