Respond to new-region logins with a user-specific action
A first login from an unexpected region can call for a simple check-in. Send that context to Notis and have Botbaba run the appropriate action for the identified user.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Execute Bot Action By User
Tool to execute a bot action for specific users. Use when you need to trigger actions for one or multiple bot users.
Why this helps
Finding the right user and deciding what to do after an unexpected login can interrupt focused work.
- Passes a new-region signal to a Botbaba action for a specific user.
- Makes a defined login follow-up easier to repeat.
- Cuts the manual steps between an IP check and a user conversation.
Setup
Build it in a few focused steps.
- 1Connect Ip2location and Botbaba to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Write one plain-language instruction asking Notis to run the chosen Botbaba action for the user identified by a backend new-region login alert using Ip2location.
- 4Select an incoming webhook trigger and choose a channel for run reports.
- 5Test using one real example that your team is authorized to process.
Questions about this workflow
Can Notis decide what counts as a new region?
Your backend should apply your chosen location rule using Ip2location and send the resulting signal to the Notis webhook.
Can the action address a specific Botbaba user?
The available event executes a Botbaba action for specific users; the prompt should explain how the incoming alert identifies the intended user.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ip2location to Botbaba. A trigger fires from one place; an action lands in another.
Ip2location triggers
Botbaba actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Shopify Cart Creation Simulator
Tool to simulate a Shopify cart creation webhook payload. Use when generating test payloads for BOTBABA_CART_CREATION_SHOPIFY_WEBHOOK.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Cart Creation Shopify Webhook
Tool to receive Shopify Cart Creation webhooks. Use when configuring Shopify webhook for Cart Creation events and forwarding the payload to Botbaba. Must be called upon receiving Shopify payload.
Cart Update Shopify Webhook
Tool to forward Shopify cart update events to BotBaba. Use when processing Shopify Cart Update webhook after configuring the webhook in your store.
Shopify Checkout Creation Webhook Receiver
Tool to receive Shopify checkout creation webhook events. Use when configuring your Shopify store to notify BotBaba of checkout creation events.
Checkout Update Shopify Webhook
Tool to forward Shopify checkout/update events to Botbaba. Use when handling Shopify checkout update notifications.
Delete a broadcast campaign
Tool to delete a broadcast campaign. Use when you need to permanently remove a Botbaba broadcast by its ID after confirming it exists.
Delete Contact
Tool to delete a contact. Use when you have the contact ID and want to remove it from Botbaba.
Delete a conversation flow
Tool to delete a conversation flow. Use when you need to permanently remove a Botbaba flow by its ID after confirming it exists.
Connect any two apps with Notis in the middle.
Ip2location and Botbaba, 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 Botbaba.