Open merged documents in an isolated browser session
When an ActiveMerge workflow is ready for a browser-based check, start an isolated session so the next review can begin without extra setup.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Browser Session
Deprecated action for creating a browser session.
Why this helps
Switching from document generation to a separate browser task can interrupt review and leave the next step waiting.
- Start a browser session from an ActiveMerge completion webhook.
- Keep the browser work isolated from other sessions.
- Give your agent a defined session to use for the requested review.
Setup
Build it in a few focused steps.
- 1Connect ActiveMerge and Browserbase tool once in the Notis portal.
- 2Create an automation and name it for the document review.
- 3Tell Notis to start a Browserbase session when the ActiveMerge webhook says a document is ready, then pass along the document URL and review instructions included in the request.
- 4Choose notis_webhook as the trigger and select where run reports should go.
- 5Test with one real document completion request and confirm the session starts.
Questions about this workflow
Does ActiveMerge provide a native trigger for this workflow?
No. ActiveMerge has no trigger events in this package, so an HTTP request to a Notis webhook starts the automation.
Will this workflow inspect the document automatically?
It starts a Browserbase session. Include the URL and desired review instructions in the webhook request if you want Notis to direct the next browser task.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link ActiveMerge to Browserbase tool. A trigger fires from one place; an action lands in another.
ActiveMerge triggers
Browserbase tool actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Contexts create
Deprecated compatibility action for creating a browser context.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Contexts get
Deprecated compatibility action for retrieving a browser context.
Update Browser Context
Updates a browser context to provide fresh upload and encryption details.
Create Browser Session
Deprecated action for creating a browser session.
Create Browser Context
Creates a reusable browser context.
Create Browser Session
Creates an isolated browser session and returns its connection details.
Download Session Artifacts
Downloads a completed session’s generated files as a ZIP archive.
Delete a browser context
Permanently deletes a browser context and all its stored data.
Connect any two apps with Notis in the middle.
ActiveMerge and Browserbase tool, 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 Browserbase tool.