Keep dividend-history reviews on your calendar automatically
Use a recurring check to bring the dividend history for active ideas back into view.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Dividend History
Retrieves dividend history for a specific symbol.
Why this helps
Keeping up with a list of income ideas can require repetitive checks that are easy to postpone.
- Make historical checks part of a repeatable review routine.
- Gather context for multiple ideas in one pass.
- Keep the research list active without relying on memory alone.
Setup
Build it in a few focused steps.
- 1Connect Notion and Nasdaq to Notis once through the portal.
- 2Create a plain-language prompt asking Notis to review active income ideas and retrieve Nasdaq dividend history for their symbols.
- 3Select a recurring schedule, set the cadence, and choose a report channel.
- 4Run a first check against the current list and confirm that each intended symbol is covered.
Questions about this workflow
Does a recurring history check indicate future dividend safety?
No. The action retrieves historical dividend information only.
Can I change the schedule later?
Yes. Update the automation cadence to match your review routine.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Nasdaq. A trigger fires from one place; an action lands in another.
Notion triggers
Nasdaq actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Datatable Metadata (All Symbols)
Retrieves metadata for a specified datatable, which includes column definitions and potentially example data containing symbols.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Analyst Ratings and Target Prices
Retrieves analyst ratings and target prices for a specific symbol using zacks datatables (zacks/ar for ratings, zacks/tp for target prices).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Dividend History
Retrieves dividend history for a specific symbol.
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 Real-Time Quote
Retrieves real-time quote data for a specific symbol.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Specific Table Row
Retrieves a specific row from a table by filtering on a specified column and value.
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 Tables by Update Date
Retrieves all tables updated on a specific date by fetching all tables and filtering them.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Nasdaq, 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 Nasdaq.