Carry campaign creative context into Botbaba user actions
Keep campaign context attached as it moves from an Abyssale creative request to Botbaba users.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Execute Bot Action By User
Run a bot action for one or more users.
Why this helps
Campaign details and audience instructions are easy to lose when a creative handoff requires manual copying into chatbot operations.
- Reduce copy and paste between creative requests and Botbaba.
- Run an existing action for the specified Botbaba users.
- Preserve campaign context provided by the incoming request.
Setup
Build it in a few focused steps.
- 1Connect Abyssale and Botbaba once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a campaign-focused name.
- 3In one instruction, tell Notis to use the incoming creative and campaign context to run the chosen existing Botbaba action for the users specified in the request.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real request containing the intended user details and review the run report.
Questions about this workflow
Can Notis determine the intended audience from the creative alone?
No. The webhook request must provide the Botbaba user details. Notis can use the provided context but cannot invent an audience.
What does this Botbaba action do?
It triggers an existing Botbaba action for one or more specified bot users.
Does the workflow create or edit a campaign in Abyssale?
No. The trigger is a Notis webhook request carrying campaign and creative context; the listed Botbaba action runs for the specified users.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abyssale to Botbaba. A trigger fires from one place; an action lands in another.
Abyssale triggers
Botbaba actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Shopify Cart Creation Simulator
Generate a sample payload to test a cart creation webhook.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Cart Creation Shopify Webhook
Receive a cart creation webhook payload for forwarding.
Cart Update Shopify Webhook
Forward a cart update event.
Shopify Checkout Creation Webhook Receiver
Receive a checkout creation webhook event.
Checkout Update Shopify Webhook
Forward a checkout update event.
Delete a broadcast campaign
Permanently delete a broadcast campaign.
Delete Contact
Delete a contact.
Delete a conversation flow
Permanently delete a conversation flow.
Connect any two apps with Notis in the middle.
Abyssale 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.