Keep model repository files in step with approved notes
Reduce copying between Notion and Hugging Face when model documentation is ready to update.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Create Models Commit
Tool to create a commit to a Hugging Face model repository. Use when you need to add, update, or delete files in a model repository. Supports both standard JSON and JSON-lines (NDJSON) formats. JSON-lines format is recommended for better performance.
Why this helps
Approved documentation gets delayed when it must be copied by hand into a model repository.
- Reduce repetitive documentation transfer.
- Keep a known Notion source connected to repository updates.
- Make changes visible as repository history.
Setup
Build it in a few focused steps.
- 1Connect Notion and Hugging Face to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to update a model repository from approved notes.
- 3In one instruction, specify the page and repository, and ask Notis to create a commit only when the page clearly indicates that content is approved.
- 4Choose the Notion Page Content Updated trigger scoped to the model notes page and a channel for run reports.
- 5Test with a non-production file change and review the commit contents.
Questions about this workflow
Can this update any file in the repository?
Describe the specific documentation or configuration file and repository in the prompt.
How can I prevent draft notes from being committed?
Set a clear approval condition in the instruction and test it with both draft and approved content.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Hugging Face. A trigger fires from one place; an action lands in another.
Notion triggers
Hugging Face actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Change Discussion Status
Tool to change the status of a Hugging Face repository discussion. Use when you need to open or close discussions on models, datasets, or spaces.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check Dataset Validity
Tool to check whether a specific dataset is valid on Hugging Face Hub. Use when you need to determine what features (preview, viewer, search, filter, statistics) are available for a dataset.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Check Models Upload Method
Tool to check if files should be uploaded through the Large File mechanism or directly. Use when preparing to upload files to a Hugging Face model repository to determine the appropriate upload method for each file.
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.
Check Spaces Upload Method
Tool to check if files should be uploaded through the Large File mechanism or directly to Hugging Face Spaces. Use when preparing to upload files to a Hugging Face Space repository to determine the appropriate upload method for each file.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Claim Paper Authorship
Tool to claim authorship of a paper on Hugging Face. Use when you need to associate yourself or another user with an ArXiv paper.
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.
Request Repository Access
Tool to request access to a gated repository on Hugging Face Hub. Use when you need to submit an access request for models, datasets, or Spaces that require approval. The fields required vary by repository.
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.
Create Collection
Tool to create a new collection on Hugging Face. Use when you need to organize and curate models, datasets, spaces, papers, or other collections into a named collection.
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.
Create Datasets Branch
Tool to create a new branch in a Hugging Face dataset repository. Use when you need to create a branch for versioning or experimentation with dataset changes.
Connect any two apps with Notis in the middle.
Notion and Hugging Face, 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 Hugging Face.