Event Venue Address Resolution
Add a venue to your event, get the complete address automatically. No hunting for venue details.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
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.
Why this helps
Event locations are incomplete or hard to find, making it difficult to share venue info with attendees or organizers.
- Complete venue addresses from venue name
- Fewer incomplete event details
- Attendees have full location info
- Less research work required
Setup
Build it in a few focused steps.
- 1Connect Notion and Addresszen to Notis.
- 2Ask Notis: 'When a new event page is created, resolve the venue address using Addresszen.'
- 3Select 'Page Created' and scope to your events database.
- 4Choose your notification channel.
- 5Create a test event - the venue address completes automatically.
Questions about this workflow
How does Notis know which venue I mean?
You provide the venue name or partial address in Notion. Addresszen matches it to the correct location.
What if the venue isn't recognized?
Notis flags it in your channel so you can add the address manually or search for the correct venue.
Can this add venue coordinates?
Addresszen provides the full address. Additional details like coordinates may require separate steps.
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.