Keep refund decisions and follow-ups together
Put the refund request, available order context, and next review step in one Notion entry.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Insert row database
Creates a new page (row) in a specified notion database.
Why this helps
Refund requests need timely review, but details and decisions can get separated from the follow-up work.
- Make refund review work visible
- Keep the supplied reason with the follow-up
- Clarify where a decision is still needed
Setup
Build it in a few focused steps.
- 1Connect Baselinker and Notion once in the Notis portal.
- 2Create an automation by telling Notis how to organize refund follow-ups, in the portal or any channel.
- 3Describe in one instruction how submitted refund details should become a Notion review entry.
- 4Choose a webhook trigger and where run reports should go.
- 5Test with one real refund example and confirm any missing decision context is marked.
Questions about this workflow
Will Notis approve or issue refunds?
No. This workflow creates a Notion review entry and does not take action on the refund in Baselinker.
Can it summarize the reason for a refund?
Yes, from the reason and context included in the webhook request. It should identify missing information rather than invent it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Baselinker to Notion. A trigger fires from one place; an action lands in another.
Baselinker triggers
Notion actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add multiple content blocks (bulk, user-friendly)
Efficiently adds multiple standard content blocks to a notion page in a single api call with automatic markdown parsing. the 'content' field in notionrichtext blocks now automatically detects and parses markdown formatting including headers (# ## ###), bold (**text**), italic (*text*), strikethrough (~~text~~), inline code (`code`), links ([text](url)), and more. ideal for bulk content creation, ai agents, and replacing multiple individual add page content calls. supports automatic text formatting, content splitting, and up to 100 blocks per request.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add content to Notion page
Deprecated: appends a single content block to a notion page or a parent block (must be page, toggle, to-do, bulleted/numbered list, callout, or quote); invoke repeatedly to add multiple blocks.
Append complex blocks (advanced, full control)
Appends complex blocks with full notion block structure to a parent block or page. use for advanced scenarios requiring precise control: code blocks, tables, embeds, nested children within blocks, or when working with pre-built notion block objects. requires full notion api block schema - use add multiple page content for simpler content creation.
Archive Notion Page
Archives (moves to trash) or unarchives (restores from trash) a specified notion page.
Create comment
Adds a comment to a notion page (via `parent page id`) or to an existing discussion thread (via `discussion id`); cannot create new discussion threads on specific blocks (inline comments).
Create Notion Database
Creates a new notion database as a subpage under a specified parent page with a defined properties schema; use this action exclusively for creating new databases.
Create Notion page
Creates a new empty page in a notion workspace.
Delete a block
Archives a notion block, page, or database using its id, which sets its 'archived' property to true (like moving to "trash" in the ui) and allows it to be restored later.
Connect any two apps with Notis in the middle.
Baselinker and Notion, 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 Notion.