Keep scheduled job monitoring from slipping
Let Notis send a recurring Honeybadger check-in for the scheduled job you document in Notion.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Report Check-In
Tool to report a check-in (ping) to Honeybadger. Use when monitoring scheduled tasks to signal they're running on time.
Why this helps
Remembering to signal that a recurring job is healthy creates a small but persistent mental load.
- Automate a repetitive monitoring ping.
- Use Notion as the reference for the job's purpose and cadence.
- Reduce the chance of forgetting a routine check-in.
Setup
Build it in a few focused steps.
- 1Connect Notion and Honeybadger to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Write one instruction asking Notis to report the Honeybadger check-in for the job documented in Notion on its intended schedule.
- 4Select a Notis recurring schedule trigger and choose a channel for run reports.
- 5Test with one real scheduled job and confirm Honeybadger receives the check-in.
Questions about this workflow
Does this verify that the job actually ran?
A scheduled check-in reports the ping at the configured time. Use it only when that timing is an appropriate signal for your monitoring setup.
Where is the schedule configured?
Select the recurring schedule as the Notis trigger when creating the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Honeybadger. A trigger fires from one place; an action lands in another.
Notion triggers
Honeybadger actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Report Check-In
Tool to report a check-in (ping) to Honeybadger. Use when monitoring scheduled tasks to signal they're running on time.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Report Deployment
Tool to report a new deployment to Honeybadger. Use after a successful release to notify Honeybadger of the deployment.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Report Event
Tool to send custom events to Honeybadger Insights. Use when recording structured NDJSON telemetry.
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.
Report Exception
Tool to report an exception notice to Honeybadger. Use when sending error details (stack trace, context) for diagnostics.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Upload File to S3
Tool to upload a local file to a managed S3 bucket. Use when preparing files for source-map uploads.
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.
Upload Source Map
Tool to upload JavaScript source maps for error de-minification. Use after deploying assets to Honeybadger to attach source maps.
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 Honeybadger, 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 Honeybadger.