Carry ActiveMerge status updates into Botbaba user actions
When a document status changes, let Notis trigger the relevant Botbaba action for the users named in the request.
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
Following up with the right people after document status changes can turn into a chain of repetitive checks and messages.
- Trigger a Botbaba action for one or more specified bot users.
- Use an incoming request to carry the document status and user context into the workflow.
- Avoid manually restarting the same follow-up after each status update.
Setup
Build it in a few focused steps.
- 1Connect ActiveMerge and Botbaba once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3In one instruction, describe which ActiveMerge status request should trigger the Botbaba action and identify the users and action context it needs.
- 4Choose the webhook trigger and where run reports should go.
- 5Send one real status request with the needed user details to test the automation.
Questions about this workflow
Can this action target multiple users?
Yes. Botbaba's Execute Bot Action By User action supports specific users. Provide the user details the action requires.
Does Notis monitor ActiveMerge status changes directly?
No native ActiveMerge triggers are available in this package. An HTTP request from your document workflow must start the automation.
Can the workflow choose users using a field mapping screen?
No. Notis automations are prompt-based. Describe the outcome in plain language and include the necessary user context in the incoming request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link ActiveMerge to Botbaba. A trigger fires from one place; an action lands in another.
ActiveMerge 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.
ActiveMerge 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.