Address Field Schema Verification
Add an address field to your database, Notis confirms Addresszen is ready. Build automations with confidence.
Trigger
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.
Action
Key Availability
Tool to get public information on an api key, including whether it is currently usable. use when you need to verify that a key is valid and available before making further api requests.
Why this helps
Adding address fields without verifying the service is available leads to automations that silently fail.
- Verify API before building on it
- Know immediately if service is unavailable
- Avoid building failed automations
- Smooth schema modification process
Setup
Build it in a few focused steps.
- 1Integrate Notion and Addresszen with Notis.
- 2Tell Notis: 'When I add a new address field to my database schema, verify that Addresszen is available.'
- 3Select 'Data Source Schema Updated' as your trigger.
- 4Set your notification channel.
- 5Add a new address field to your database - Notis verifies Addresszen availability.
Questions about this workflow
Does this check every schema change?
You can scope it to just address-related fields or all schema changes.
What if the API isn't available?
Notis alerts you immediately in your channel so you can investigate before building automations.
Can I still add fields if Addresszen isn't available?
Yes - you can add fields anytime. The check just alerts you to connectivity status.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Addresszen. A trigger fires from one place; an action lands in another.
Notion triggers
Addresszen actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Key Availability
Tool to get public information on an api key, including whether it is currently usable. use when you need to verify that a key is valid and available before making further api requests.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Resolve Address USA
Tool to resolve an address autocompletion by its address id and return the full address in us format. use after obtaining an address suggestion id from the autocomplete endpoint.
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 Addresszen, 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 Addresszen.