Start the day with follow-up drafts ready to review
Let a short daily routine prepare relevant content for the prospects whose follow-up is due.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Generate Personalized Content
Tool to generate hyper-personalized sales content. Use after confirming contact and user details.
Why this helps
Remembering which prospects need a follow-up and composing each message can drain focus from the rest of the day.
- Bring due follow-ups into a consistent daily routine.
- Reduce the effort of starting each follow-up message.
- Use prospect context already recorded in Notion.
Setup
Build it in a few focused steps.
- 1Connect Notion and Autobound to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to prepare daily follow-up content for due prospects.
- 3Write one plain-language instruction describing which Notion follow-ups are due and how Autobound should personalize the content.
- 4Choose a daily Notis schedule and select a channel for run reports.
- 5Test the prompt with one real due prospect and review the generated draft.
Questions about this workflow
Does this send messages on the schedule?
No. The Autobound action generates personalized content. Review the result and handle sending through your usual process.
How does Notis know which follow-ups are due?
Explain in the prompt how due follow-ups are represented in your Notion workspace and ask Notis to use that context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Autobound. A trigger fires from one place; an action lands in another.
Notion triggers
Autobound actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Generate Insights
Tool to generate ranked prospect or company insights. Use after resolving identifiers to retrieve the most relevant insights.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Generate Personalized Content
Tool to generate hyper-personalized sales content. Use after confirming contact and user details.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or 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.
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 Autobound, 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 Autobound.