Add an eSputnik balance lookup to campaign readiness review
When campaign content signals a readiness check, let Notis retrieve the current eSputnik organization balance.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Get Organization Balance
Tool to retrieve the current organization balance. Use when you need to check the account's available funds before sending campaigns.
Why this helps
A campaign can move forward while a balance check remains an easy-to-miss manual follow-up.
- Puts a balance check near the readiness review.
- Helps reduce forgotten pre-campaign checks.
- Returns current organization balance context.
Setup
Build it in a few focused steps.
- 1Connect Notion and eSputnik to Notis once through the portal.
- 2Create an automation in the portal or tell Notis to retrieve the balance when a campaign page requests a readiness check.
- 3Describe the readiness cue and balance lookup in one plain-language instruction.
- 4Select Page Content Updated for the specified campaign page and choose a run-report channel.
- 5Test with one real readiness update and verify the returned balance.
Questions about this workflow
Can this be limited to a campaign page?
Yes. Page Content Updated supports a specific page scope.
Does this action approve campaign spending?
No. It retrieves the current organization balance.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Esputnik. A trigger fires from one place; an action lands in another.
Notion triggers
Esputnik actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
ADD_DOMAIN
Tool to register a domain for web tracking or widgets. Use after confirming the site ID.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Orders Bulk
Tool to transfer orders in bulk to eSputnik. Use when you need to import up to 1000 orders at once.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Bulk Add or Update Contacts
Tool to bulk add or update up to 3000 contacts asynchronously. Use when you have a batch of contacts to import or update in one request and need a single session ID for tracking.
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.
Change Token Activity
Action to change (activate/deactivate) the activity state of a mobile push token. Endpoint: PUT /api/v1/contact/token/activated/{app_uuid}/{token_id} Body: { "active": boolean } Response: { "active": boolean }
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Contact
Tool to delete a contact by its Yespo ID. Use when you need to remove a contact with no pending interactions.
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.
Delete Contact by External ID
Tool to delete a contact by externalCustomerId.
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.
Delete SMS Message
Tool to delete a base SMS message by ID. Use when you need to remove an SMS template before sending. Example: "Delete SMS message with ID 123"
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 App Inbox Message
Tool to retrieve an App Inbox message by ID. Use when you need to fetch its content, metadata, and translations before sending or editing.
Connect any two apps with Notis in the middle.
Notion and Esputnik, 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 Esputnik.