Surface external feedback on your Mural board instantly
Feedback arrives from your website form, email, or another tool via webhook. Notis instantly adds a sticky to your Mural board. All feedback is visible and actionable in one place.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create sticky note
Tool to create one or more sticky note widgets on a mural. use when you need to add notes to a mural layout.
Why this helps
Feedback arrives through multiple channels but you don't see it until later, so you can't respond quickly or iterate based on input.
- Feedback surfaces immediately as visual items
- All external input in one centralized board
- Respond faster to customer or team feedback
- No missed feedback from various channels
Setup
Build it in a few focused steps.
- 1Connect Mural to Notis.
- 2Create an automation named 'External feedback collection'.
- 3Write the prompt: 'When a webhook arrives with feedback, create a sticky note on my Mural board with the feedback summary and source.'
- 4Select 'Webhook' as the trigger kind.
- 5Notis will provide you a webhook URL to share with your form service or API.
- 6Test by sending a test webhook payload and checking Mural for the sticky.
Questions about this workflow
How do I send data to Notis via webhook?
Notis provides a unique webhook URL after you create the automation. Send POST requests with JSON to that URL and Notis will process them.
Can I format the webhook data into the sticky automatically?
Your prompt tells Notis how to interpret the incoming JSON, so you can extract specific fields like email, message, or category.
What if the webhook payload is different each time?
Describe the data structure in your prompt and Notis will adapt to variations in the incoming data.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mural. A trigger fires from one place; an action lands in another.
Notion triggers
Mural actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create sticky note
Tool to create one or more sticky note widgets on a mural. use when you need to add notes to a mural layout.
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.
Get current user
Tool to retrieve information about the currently authenticated user. use when you need current user details after authentication.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get files for a mural
Tool to retrieve a list of file widgets in a mural. use after confirming the mural id when listing file attachments.
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.
Get Mural Widgets
Tool to retrieve all widgets within a specified mural. use after confirming the mural 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.
MURAL Authorization Request
Tool to initiate the oauth 2.0 authorization process. use when you need to redirect a user to mural to obtain an authorization code.
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.
New Page
Triggers when a new page is added to a Notion database.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Connect any two apps with Notis in the middle.
Not just Notion and Mural. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Mural.