Move brand intake details into Fidel api
Capture the brand once in Notion and let Notis register it in Fidel api when its database page is created.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Brand
Tool to create a new brand on fidel. use when you have brand details and need to register it. this tool sends a post request to /v1/brands with the provided brand data.
Why this helps
Brand details can sit in an intake page while someone remembers to re-enter them in Fidel api.
- Reduce duplicate entry during brand onboarding.
- Start Fidel setup from the intake information already gathered.
- Keep a clear run report for each new intake.
Setup
Build it in a few focused steps.
- 1Connect Notion and Fidel api to Notis once in the portal.
- 2Create an automation in the portal and describe creating a Fidel brand from each new completed brand intake page.
- 3Select the Notion New Page trigger for the intake database and choose a channel for run reports.
- 4Test with one real intake page and review the Fidel result.
Questions about this workflow
Does this create a brand for every new page?
The plain-language instruction should specify the brand intake pages to process; test it with one real page before relying on it.
Do I need to map brand fields?
No. Describe the desired outcome in the automation prompt, and Notis interprets the page content.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Fidel api. A trigger fires from one place; an action lands in another.
Notion triggers
Fidel api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Brand
Tool to create a new brand on fidel. use when you have brand details and need to register it. this tool sends a post request to /v1/brands with the provided brand data.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Program
Tool to create a new program. use when registering an offline or online store. use after confirming program name and any optional metadata.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Program Webhook
Tool to register a new webhook for program-related events. use when you need to receive real-time notifications for specific program events in your application.
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.
Delete Offer
Tool to delete a specified offer by its id. use after confirming the correct offer id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Program Webhook
Tool to delete a specified webhook for a program. use when you need to remove a program webhook after confirming programid and hookid.
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.
Delete Webhook
Tool to delete a specified webhook. use when you need to remove a webhook by its 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.
Get Brand
Tool to retrieve information about a specific brand. use when you have a brand id and need its details.
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.
Get Offer
Tool to fetch details of a specific offer. use when you have an offer id and need its full details.
Connect any two apps with Notis in the middle.
Notion and Fidel api, 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 Fidel api.