Turn tone feedback into a clear writing style review
A comment about customer-facing tone can prompt a quick look at Cardly writing styles for the next card review.
Trigger
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.
Action
List Writing Styles
Tool to list available writing styles. use when you need to retrieve writing styles available for handwriting personalization.
Why this helps
Tone feedback can be hard to translate into a concrete style choice, especially when it is buried in discussion.
- Connect tone discussions to the available Cardly writing styles.
- Make feedback easier to act on later.
- Keep style exploration in the context of the conversation.
Setup
Build it in a few focused steps.
- 1Connect Notion and Cardly to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to check Cardly styles after tone feedback.
- 3Use one instruction asking Notis to retrieve available Cardly writing styles when a relevant Notion comment is added.
- 4Choose the Notion Comment Created trigger and select a channel for run reports.
- 5Test by adding one real tone feedback comment and review the style list.
Questions about this workflow
Does Cardly apply the style automatically?
No. The action lists available writing styles for you to review.
What access does the comment trigger need?
The Notion integration needs the Read comments capability, and may need reauthorization if that capability was enabled later.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cardly. A trigger fires from one place; an action lands in another.
Notion triggers
Cardly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Contact List
Tool to add a new contact list. use after defining name and optional custom fields, before populating the list with contacts.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Webhook
Tool to create a new webhook subscription. use when you need cardly to notify your application via http post for specific events.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Invitation by Email
Tool to delete an invitation by email address. use when you need to invalidate an outstanding invitation immediately.
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 Webhook
Tool to delete a webhook. use after confirming the webhook id to immediately cease all activity and event subscriptions for that webhook.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Generate Preview
Tool to generate a low-quality, watermarked preview document for a card. use after confirming artwork and template details to estimate costs and delivery.
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.
List Artwork
Tool to retrieve the currently available artwork for your organisation. use when you need to list and paginate artwork items, optionally filtering to only your own artwork.
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.
List Credit History
Tool to list credit history records. use after checking account balance to review recent credits/debits.
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.
List Fonts
Tool to list your currently available fonts. use after confirming authentication to explore font options in cardly.
Connect any two apps with Notis in the middle.
Notion and Cardly, 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 Cardly.