Keep a regular view of your GetProspect lists
Let Notis bring your current contact list inventory into a weekly review without a manual lookup.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get All Contact Lists
Tool to retrieve all prospect contact lists. Use when you need to list all existing contact lists for an account.
Why this helps
It is easy to lose track of existing lists and create duplicates when organization is spread across tools.
- See available lists as part of a regular review.
- Reduce unnecessary tool switching when planning outreach.
- Spot naming or organization gaps before creating more lists.
Setup
Build it in a few focused steps.
- 1Connect GetProspect to Notis once through the portal.
- 2Create an automation with a prompt to retrieve the contact lists and summarize them.
- 3Select a recurring weekly schedule for the review.
- 4Choose a channel for run reports and test the first inventory.
Questions about this workflow
Does this create or rename any lists?
No. It retrieves and reports the current lists.
Can I receive this before a planning meeting?
Choose a schedule that delivers the report ahead of your usual planning time.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Getprospect. A trigger fires from one place; an action lands in another.
Notion triggers
Getprospect actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Apply Coupon Code
Tool to apply a coupon code to the user's account. Use after you need to activate a coupon before using it.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Company
Tool to create a new company. Use when you need to add a company record via GetProspect API.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Contact
Tool to create a new contact. Use when you need a fresh contact record before associating it to lists.
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.
Create Export
Tool to create a new export job. Use when you need to export contacts or companies based on filters or specific record IDs. Returns HTTP 201 on success.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Contact List
Tool to create a new contact list. Use when you need to organize contacts into a named list.
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 Company
Tool to delete a company record by its ID. Use when you have confirmed this company should be permanently removed.
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 Contact
Tool to delete a contact record by its ID. Use when you need to remove a contact; ensure the contact ID exists before calling.
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.
Delete Multiple Contact Lists
Tool to delete multiple contact lists. Use when you have a set of list IDs and want to remove them in bulk. Use after confirming the lists to delete.
Connect any two apps with Notis in the middle.
Notion and Getprospect, 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 Getprospect.