Search near-Earth objects from a Notion date range
Write a date window into a plan and get a NASA search for near-Earth objects approaching during it.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Search Near Earth Objects
Tool to search near-earth objects by closest approach date range. use when identifying asteroids in a date window (max 7 days).
Why this helps
Checking objects against a planned time window can be missed when date details live only in project notes.
- Turns a date-specific plan into an object search.
- Keeps the search tied to the planning context.
- Makes it easier to check approaching objects before a date-sensitive activity.
Setup
Build it in a few focused steps.
- 1Connect Notion and Nasa to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally for one.
- 3Write one plain-language instruction asking Notis to search NASA near-Earth objects for the closest-approach date range stated in each new plan and report relevant findings with the page context.
- 4Select the Notion New Page trigger for date-based plans and choose a channel for run reports.
- 5Test with one real plan containing a date window no longer than seven days.
Questions about this workflow
How wide can the date window be?
The listed action supports a maximum date range of seven days. Keep the dates in the page within that limit.
Does it return a general asteroid catalog?
No. It searches near-Earth objects by their closest-approach date range.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Nasa. A trigger fires from one place; an action lands in another.
Notion triggers
Nasa actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get CMR Collections
Tool to retrieve collections from the common metadata repository (cmr). use when you need to search nasa science data collections by spatial, temporal, or metadata filters. call after confirming search criteria.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get CMR Granules
Tool to retrieve granules from the common metadata repository (cmr). use when you need granule metadata filtered by collection ids, spatial, or temporal criteria. call after confirming your filters.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get EONET Categories
Tool to retrieve a list of all event categories from eonet. use when you need current category ids, titles, descriptions, and info links.
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 EONET Events (ATOM)
Tool to retrieve a list of natural events in atom format. use when you need a machine-readable xml feed of recent natural events from eonet.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get EONET Events RSS
Tool to retrieve a list of natural events in rss format. use when you need the latest eonet events as an rss feed.
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 EONET Layers
Tool to retrieve available data layers for event visualization. use after confirming category id if filtering.
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.
GET EONET Magnitudes
Tool to retrieve a list of available event magnitudes and their descriptions. use after determining you need valid magnitude filters before querying events data.
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.
GET EONET Source by ID
Tool to retrieve details for a specific eonet event source by id. use when you need to fetch source metadata (id, title, homepage) before querying events.
Connect any two apps with Notis in the middle.
Notion and Nasa, 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 Nasa.