Start your weekly Notion planning with a fresh Hashnode catalogue
Begin the week with the published work already in view.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Fetch Publication Posts
Tool to fetch a paginated list of posts from a publication. Use when you need to list posts page by page for a given publication host.
Why this helps
A weekly planning session can lose time rebuilding context about what shipped recently.
- Start planning with recent publication context.
- Spot gaps and themes before choosing the next task.
- Reduce manual prep across separate tools.
Setup
Build it in a few focused steps.
- 1Connect Notion and Hashnode to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Tell Notis in one instruction to fetch the latest publication posts weekly and summarize themes or follow-ups for your Notion editorial review.
- 4Choose a weekly schedule and select a channel for run reports.
- 5Test once with the next scheduled run or run it with one real publication.
Questions about this workflow
Does it create a Notion report?
The prompt can ask Notis to summarize the fetched posts for your planning session; it does not require a field-mapping setup.
Can I change the day?
Yes. Choose the recurring weekly schedule that fits your planning routine.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Hashnode. A trigger fires from one place; an action lands in another.
Notion triggers
Hashnode actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Hashnode Accept Publication Invite
Tool to accept a publication invitation. Use when you have a valid invite token and want to join the publication.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Hashnode Add Reply
Tool to add a reply to an existing comment. Use after confirming comment ID and reply content.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Hashnode: Check Custom Domain Availability
Tool to check if a custom domain is available for your Hashnode publication. Use when verifying domain mapping before setup.
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.
Hashnode: Fetch Invitations
Tool to fetch pending publication invitations. Use when you need to list current pending invites for a team-managed publication before taking further actions.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Hashnode: Fetch Popular Tags
Tool to fetch a paginated list of popular tags. Use when you need to browse popular tags page by 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.
Fetch Publication Posts
Tool to fetch a paginated list of posts from a publication. Use when you need to list posts page by page for a given publication host.
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.
Fetch Series Posts
Tool to fetch posts from a series within a publication. Use when retrieving and paginating through series posts in a specific publication.
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.
Fetch Single Article
Tool to fetch a single article by slug from a publication. Use when you need the detailed content of a specific post.
Connect any two apps with Notis in the middle.
Notion and Hashnode, 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 Hashnode.