Bring customer-signal definitions into Faraday traits
Capture a useful customer fact in Notion, then let Notis carry it forward into a Faraday trait definition.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Trait
Tool to create a new trait in Faraday. Use when you need to define a new fact about a person or geographic entity that can be used in modeling, analysis, and reporting.
Why this helps
Important customer signals can be described in planning notes without ever becoming usable analytics traits.
- Turns documented customer facts into an analytics setup action.
- Reduces copy-and-recreate work.
- Keeps data definitions moving toward modeling use.
Setup
Build it in a few focused steps.
- 1Connect Notion and Faraday to Notis once through the portal.
- 2Start an automation in Automations or ask Notis conversationally.
- 3Use one instruction asking Notis to create a Faraday trait when a new customer-signal definition is added.
- 4Choose New Page for the signal-definition database and set a channel for run reports.
- 5Test with one real definition and verify the resulting trait.
Questions about this workflow
What kind of Notion entry fits this workflow?
Use it for a documented fact about a person or geographic entity that should be represented as a Faraday trait.
Do I select trait fields manually?
No. Notis uses the plain-language instruction to interpret the requested result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Faraday. A trigger fires from one place; an action lands in another.
Notion triggers
Faraday actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive Cohort
Tool to archive a cohort in Faraday. Use when you need to stop updates to a cohort while keeping it visible.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Archive Connection
Tool to archive a connection in Faraday. Use when you need to stop updates to a connection while keeping it visible.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Archive Dataset
Tool to archive a dataset in Faraday. Use when you need to archive a dataset and optionally its downstream resources. Archiving stops updates to the resource but keeps it visible.
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.
Archive Outcome
Tool to archive an outcome in Faraday. Use when you need to stop updates to an outcome while keeping it visible.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Archive Persona Set
Tool to archive a persona set in Faraday. Use when you need to stop updates to a persona set while keeping it visible.
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.
Archive Place
Tool to archive a place in Faraday. Use when you need to stop updates to a geospatial area or address set while keeping it visible.
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.
Archive Scope
Tool to archive a scope in Faraday. Use when you need to stop updates to a scope while keeping it visible.
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.
Archive Stream
Tool to archive a stream in Faraday. Use when you need to archive a stream and optionally its downstream resources. Archiving stops updates to the resource but keeps it visible.
Connect any two apps with Notis in the middle.
Notion and Faraday, 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 Faraday.