Catch Mailsoftly connection problems early
Let Notis check that Mailsoftly credentials still work on a schedule and tell you when the firm lookup fails.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Authenticate Firm
Tool to validate the api key and retrieve firm details. use when confirming credentials before making other mailsoftly api calls.
Why this helps
A broken connection can go unnoticed until you need Mailsoftly, adding a surprise troubleshooting task to an already busy day.
- Surface authentication issues before a time-sensitive task depends on Mailsoftly.
- Get a concise run report without remembering to check the connection manually.
- Keep a recurring maintenance check in the background.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mailsoftly to Notis once through the portal.
- 2In Automations, create a new automation and name it Mailsoftly connection check.
- 3Write one plain-language prompt asking Notis to validate the Mailsoftly API key, retrieve firm details, and report whether the check succeeded.
- 4Choose a recurring schedule, select a channel for run reports, and test with one real example.
Questions about this workflow
What does this automation check?
It uses Mailsoftly's Authenticate Firm action to validate the API key and retrieve firm details. It does not send campaigns or manage subscribers.
Why use a recurring trigger?
A schedule can check the connection without depending on an unrelated Notion page or comment event.
Do I need to configure field mappings?
No. Describe the check in the automation prompt; Notis interprets the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mailsoftly. A trigger fires from one place; an action lands in another.
Notion triggers
Mailsoftly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Authenticate Firm
Tool to validate the api key and retrieve firm details. use when confirming credentials before making other mailsoftly api calls.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 Mailsoftly, 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 Mailsoftly.