Keep important support context attached to the subscriber
When an escalation is captured in Mem0, Notis can apply your existing Kit follow-up tag so the need stays visible during audience work.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Tag Subscriber by Email
Tool to associate a subscriber with a tag using an email address. use when you have a tag id and subscriber email ready. use after confirming both resources exist.
Why this helps
Sensitive or time-critical follow-up can be dropped when support context and subscriber records live in separate places.
- Keep important cases easier to locate in Kit.
- Reduce reliance on remembering a separate follow-up note.
- Make existing follow-up organization more consistent.
Setup
Build it in a few focused steps.
- 1Connect Mem0 and Kit to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to set one up.
- 3Use one prompt asking Notis to apply the existing Kit escalation tag when a Mem0 note clearly marks an escalation and includes the subscriber's email.
- 4Pick an incoming webhook trigger and a channel for run reports.
- 5Test with one real escalation record and verify the matching subscriber was tagged.
Questions about this workflow
Does tagging resolve the support issue?
No. It makes the subscriber easier to identify in Kit; the support follow-up still needs its usual owner and process.
What if the subscriber email is missing?
Tell Notis to skip tagging and report that the note needs an email address.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Mem0 to Kit. A trigger fires from one place; an action lands in another.
Mem0 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.
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."
Create Webhook
Tool to create a new webhook subscription. use when you need subscriber or purchase event notifications.
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"
Delete Custom Field
Tool to delete a specific custom field. use after confirming the custom field id is correct. deletes the field permanently.
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.
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.
Mem0 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.