See whether security signals are leading to contact activity
A location-based alert process is easier to trust when you review whether people are being reached. Schedule a brief Botbaba activity summary after your Ip2location security checks run.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Contact Analytics
Tool to retrieve analytics data for contacts. Use when you need summary metrics (e.g., new or active contacts) over a date range. Note: BotBaba API does not have a dedicated contact analytics endpoint. This action aggregates data from messages and tags to provide contact interaction metrics.
Why this helps
Without a regular pulse, it is hard to notice when security follow-up is being skipped or going quiet.
- Creates a predictable cadence for checking Botbaba contact activity.
- Helps surface follow-up gaps without daily dashboard visits.
- Keeps operational review separate from individual alert handling.
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 for a weekly review conversationally.
- 3In one instruction, ask Notis to retrieve Botbaba contact analytics for a defined period and summarize activity relevant to your Ip2location security follow-up.
- 4Select a recurring schedule trigger and choose where run reports should arrive.
- 5Run one scheduled example and confirm the summary covers the period you intended.
Questions about this workflow
Does this action analyze Ip2location records?
No. The Botbaba event aggregates contact interaction metrics; the prompt can frame why you are reviewing it after your location-based security process.
How often does it run?
Set the recurring cadence as the Notis cron trigger when creating the automation.
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.