Check existing subscriber fields first
Before planning a new Kit subscriber attribute, bring the current custom field list into view from the Linear issue.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
List Custom Fields
Tool to retrieve a paginated list of custom fields. use after confirming you need to enumerate or inspect all custom fields with cursor-based pagination.
Why this helps
Teams may create duplicate or overlapping subscriber fields when the existing Kit schema is not easy to recall.
- Check the current field inventory before proposing a change.
- Reduce duplicate schema work.
- Keep data decisions linked to the originating request.
Setup
Build it in a few focused steps.
- 1Connect Linear and Kit to Notis once in the portal.
- 2Ask Notis to list Kit custom fields when a Linear issue requests subscriber data changes and identify existing fields relevant to the request.
- 3Select the Linear Issue Created trigger and choose a channel for run reports.
- 4Test with one real data request and confirm the inventory informs the discussion.
Questions about this workflow
Will it create a custom field automatically?
No. It lists existing fields so the team can decide whether a new one is needed.
Can this prevent every duplicate?
It provides context for review; a person should confirm whether an existing field meets the request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Kit. A trigger fires from one place; an action lands in another.
Linear triggers
Kit actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Subscriber to Form
Tool to add a subscriber to a specific form by id. use after confirming form and subscriber ids.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Custom Field
Tool to create a new custom field for subscriber data. use when you need to store extra attributes for subscribers.
Comment Received Trigger
Triggered when a comment is received.
Create Tag
Tool to create a new tag in the account. use when you need a custom label to segment subscribers. use after confirming tag uniqueness to avoid duplicates. example: "create a tag called 'vip' for premium customers."
Issue Created Trigger
Triggered when a new issue is created.
Create Webhook
Tool to create a new webhook subscription. use when you need subscriber or purchase event notifications.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Delete Broadcast
Tool to delete a specific broadcast. use when you need to permanently remove a broadcast by id (after confirming the id). example prompt: "delete broadcast with id 123"
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Delete Custom Field
Tool to delete a specific custom field. use after confirming the custom field id is correct. deletes the field permanently.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Delete Subscriber
Tool to delete (unsubscribe) a subscriber by id. use when you need to remove a subscriber from all sequences and forms after confirming the subscriber exists.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Delete Tag
Tool to delete a tag by id. use when you need to remove obsolete or incorrect tags after confirming the tag exists.
Connect any two apps with Notis in the middle.
Linear and Kit, 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 Kit.