Make supplier checks part of outreach preparation
A weekly eligibility pass helps you spot targeting issues while you are already planning the next outreach batch.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Dripcel Post Compliance Send
Tool to check a list of cell numbers against campaign targeting criteria. use when ensuring suppliers comply with your campaign rules before sending messages.
Why this helps
Checking numbers one by one at send time breaks focus and can delay the whole batch.
- Bring eligibility checks forward in the planning process.
- Surface numbers that need attention before outreach.
- Use a Notion list as the source for supplier context.
Setup
Build it in a few focused steps.
- 1Connect Notion and Dripcel to Notis once through the portal.
- 2Ask Notis to review the specified supplier numbers in your Notion outreach list against the named Dripcel targeting criteria once a week.
- 3Select a weekly schedule and choose where run reports should go.
- 4Review the first result with one known eligible and one known ineligible number.
Questions about this workflow
Will it contact the suppliers?
No. The compliance action checks numbers against targeting criteria without sending messages.
What if the Notion list has many records?
Specify a manageable scope in the prompt and check the first run's coverage before relying on the summary.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Dripcel. A trigger fires from one place; an action lands in another.
Notion triggers
Dripcel actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Contact
Tool to delete a contact by their cell number. use when you need to remove a contact from dripcel after confirming the msisdn.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Dripcel Campaigns
Tool to retrieve a list of all campaigns. use after authenticating when you need to paginate or filter campaigns.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get current credit balance
Tool to get current credit balance. use after authenticating and when you need to verify account balance before credit-consuming operations.
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 Deliveries
Tool to retrieve a list of deliveries. use when you need to fetch delivered messages optionally filtered by cell or customerid.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get email templates
Tool to list all available email templates. use when you need to retrieve available templates before sending email campaigns.
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 sales
Tool to retrieve a list of all sales. use when you need comprehensive sales data for reporting or analytics.
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.
Dripcel Post Compliance Send
Tool to check a list of cell numbers against campaign targeting criteria. use when ensuring suppliers comply with your campaign rules before sending messages.
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.
Search replies based on filters
Tool to search replies based on filters. use when you need to find replies by id, campaign, date range, or content.
Connect any two apps with Notis in the middle.
Notion and Dripcel, 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 Dripcel.