Review engagement after a location-aware message
When a regional message goes out, its engagement can guide the next step. Have your backend send the campaign signal to Notis and retrieve the corresponding Botbaba analytics.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Message Analytics
Tool to retrieve analytics data for a specific message. Use after sending a message to analyze its delivery and engagement statistics.
Why this helps
Engagement details are easy to overlook when they require a separate manual lookup after a campaign.
- Retrieves analytics for a specific Botbaba message tied to a regional signal.
- Makes post-send review easier to fit into the existing workflow.
- Helps your team learn which location-aware messages merit follow-up.
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 it in plain language.
- 3Write one instruction asking Notis to retrieve analytics for the Botbaba message referenced by a backend event related to your Ip2location-informed campaign.
- 4Select an incoming webhook trigger and a channel for run reports.
- 5Test with one real campaign message and check that the analytics refer to the right message.
Questions about this workflow
Does this send or change a campaign?
No. It retrieves analytics for a specific Botbaba message.
What provides the location context?
Your backend can use Ip2location data to identify the relevant campaign event before notifying Notis.
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.