Keep contact context current after IP enrichment
Your system can enrich an IP with location details before sending a profile update to Notis. Ask Notis to keep the corresponding Botbaba contact current with the context your team uses.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Contact
Tool to update an existing contact. Use when needing to modify contact details after confirming contact_id.
Why this helps
Contact context can go stale when enrichment and messaging live in separate tools.
- Carries selected, useful Ip2location context into an existing contact update.
- Avoids retyping enrichment details into Botbaba.
- Keeps customer-facing work aligned with the context your backend has already checked.
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 tell Notis what you want conversationally.
- 3Use one instruction to update the matching Botbaba contact when your backend sends a profile update enriched with Ip2location details.
- 4Pick an incoming webhook trigger and a channel for run reports.
- 5Test with one real profile update and confirm the intended contact changed.
Questions about this workflow
Does this workflow perform the IP lookup?
The workflow starts when your backend sends a webhook; have that system perform or obtain the Ip2location enrichment before notifying Notis.
Which contact details should be updated?
State the intended update in the plain-language instruction and keep it to location context your process is appropriate to retain.
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.