Skip to content
Notis

Validate return addresses before use

Keep return instructions clearer with an address check at intake.

Trigger

New Page

Triggers when a new page is added to a Notion database.

Action

Validate Address

Tool to validate and standardize addresses. Use when you need detailed parsing, geocode, and deliverability verdict of an address.

Why this helps

Return addresses copied from old documents can be stale or inconsistently formatted.

  • Flag address issues before a return is initiated.
  • Keep return records more consistent.
  • Reduce repeated checks by hand.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Google address validation to Notis once in the portal.
  • 2Create an automation and write one prompt describing validation of new return-address records.
  • 3Select New Page for the returns database and choose where run reports should appear.
  • 4Test with one real return-address record and review the result.

Questions about this workflow

Does this create a return label?

No. The action validates and standardizes the address; label creation is outside this workflow.

Can the prompt ask for an exception report?

Yes. Describe in plain language how Notis should report addresses that need human review.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Google address validation. A trigger fires from one place; an action lands in another.

Notion triggers

Google address validation actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Provide Validation Feedback

Tool to provide feedback on an address validation attempt. Use after completing an address validation sequence.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Validate Address

Tool to validate and standardize addresses. Use when you need detailed parsing, geocode, and deliverability verdict of an address.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

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.

TriggerInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

TriggerInstant

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.

TriggerInstant

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.

TriggerInstant

Connect any two apps with Notis in the middle.

Notion and Google address validation, 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 Google address validation.