Keep mobile push token changes tied to a clear signal
A confirmed token change can travel from your product process to eSputnik through Notis, with the run report showing that the request was handled.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Change Token Activity
Action to change (activate/deactivate) the activity state of a mobile push token. Endpoint: PUT /api/v1/contact/token/activated/{app_uuid}/{token_id} Body: { "active": boolean } Response: { "active": boolean }
Why this helps
Token maintenance can be easy to overlook when it depends on a separate manual check.
- Apply a token activity change from a specific incoming signal.
- Make the token maintenance step easier to repeat consistently.
- Keep a report of the action in the channel you choose.
Setup
Build it in a few focused steps.
- 1Connect Chameleon and eSputnik to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally for token deactivation.
- 3Use one plain-language instruction telling Notis to deactivate the specified eSputnik mobile push token when a trusted signal arrives.
- 4Choose an incoming webhook trigger and the channel for run reports.
- 5Test with one real token that is approved for deactivation.
Questions about this workflow
Can the action also activate a token?
Yes. The eSputnik action changes the token's active state, so the instruction can specify activation or deactivation.
What starts the workflow?
A Notis webhook starts it when an external tool or custom backend sends the request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Chameleon to Esputnik. A trigger fires from one place; an action lands in another.
Chameleon triggers
Esputnik actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
ADD_DOMAIN
Tool to register a domain for web tracking or widgets. Use after confirming the site ID.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Orders Bulk
Tool to transfer orders in bulk to eSputnik. Use when you need to import up to 1000 orders at once.
Bulk Add or Update Contacts
Tool to bulk add or update up to 3000 contacts asynchronously. Use when you have a batch of contacts to import or update in one request and need a single session ID for tracking.
Change Token Activity
Action to change (activate/deactivate) the activity state of a mobile push token. Endpoint: PUT /api/v1/contact/token/activated/{app_uuid}/{token_id} Body: { "active": boolean } Response: { "active": boolean }
Delete Contact
Tool to delete a contact by its Yespo ID. Use when you need to remove a contact with no pending interactions.
Delete Contact by External ID
Tool to delete a contact by externalCustomerId.
Delete SMS Message
Tool to delete a base SMS message by ID. Use when you need to remove an SMS template before sending. Example: "Delete SMS message with ID 123"
Get App Inbox Message
Tool to retrieve an App Inbox message by ID. Use when you need to fetch its content, metadata, and translations before sending or editing.
Connect any two apps with Notis in the middle.
Chameleon and Esputnik, 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 Esputnik.