Move newsletter opt-ins from Notion into Laposta
Give each recorded opt-in a simple route into the list where you manage your newsletter audience.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Member
Tool to add a new subscriber relationship to a list with custom fields and tracking info. Use when you need to create a new member in a list or update an existing member if upsert is enabled.
Why this helps
Manual transfer adds friction between capturing permission and organizing the subscriber record.
- Reduce repeated entry for newly recorded opt-ins.
- Keep the subscriber list close to the source record.
- Use one instruction for a repeatable list-maintenance task.
Setup
Build it in a few focused steps.
- 1Connect Notion and Laposta to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Tell Notis to create or update a Laposta member from a new Notion opt-in entry when the needed contact information is present.
- 4Choose New Page for the opt-in data source and select a channel for run reports.
- 5Add one real opt-in entry and confirm the matching Laposta member.
Questions about this workflow
How should I scope the trigger?
Select New Page for the Notion data source where opt-ins are recorded.
Will this create a duplicate subscriber?
The Laposta Create Member event supports updating an existing member when upsert is enabled; describe the intended matching behavior in your prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Laposta. A trigger fires from one place; an action lands in another.
Notion triggers
Laposta actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get All Campaigns
Tool to retrieve all campaigns from Laposta account. Use when you need to list all email campaigns with their configuration and delivery status.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Custom Field
Tool to create a custom field for a mailing list to define subscriber attributes. Use when you need to add custom fields like text, numeric, date, or select fields to a list. For select fields (select_single or select_multiple), you must provide the options parameter.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Field
Tool to permanently remove a custom field from a mailing list. Use when you need to delete a field that is no longer needed.
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 Field Details
Tool to retrieve specific field details by field_id. Use when you need to fetch complete information about a custom field including its configuration, data type, and available options.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get All Fields
Tool to retrieve all fields for a specific list in Laposta. Use when you need to see all field definitions, metadata, and settings for a 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.
Update Field
Tool to modify field configuration in a Laposta list. Use when you need to update field properties such as name, datatype, required status, or display settings. WARNING: Modifying datatype removes all data from that field.
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.
Clear All Members From List
Tool to clear all active members from a list. Use when you need to remove all active member relationships while preserving the list itself. The operation is permanent and cannot be undone.
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.
Create Mailing List
Tool to create a new mailing list in Laposta to manage email subscribers. Use when you need to create a new list with zero members.
Connect any two apps with Notis in the middle.
Notion and Laposta, 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 Laposta.