See the right contact context when a location alert arrives
When an Ip2location-enriched alert needs human attention, bring the relevant Botbaba contact into the run report so you do not have to search for it separately.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get BotBaba Contact
Tool to fetch a BotBaba contact by its ID. Use when you need to retrieve the full details of a contact after creation or update.
Why this helps
Switching between an alert and a contact record adds friction at the moment follow-up matters.
- Retrieves a Botbaba contact record associated with an incoming location alert.
- Gives the responder context for deciding the next appropriate step.
- Avoids a separate contact search during 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 to set it up conversationally.
- 3Write one instruction asking Notis to retrieve the Botbaba contact associated with a backend alert enriched using Ip2location data.
- 4Select an incoming webhook trigger and choose a channel for run reports.
- 5Test using one real alert and confirm the intended contact is returned.
Questions about this workflow
Does this change the contact?
No. The selected Botbaba event fetches contact details by ID.
Does this identify a person directly from an IP address?
The event retrieves a Botbaba contact; your backend should apply its own appropriate identity and IP enrichment logic 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.