Check browser research against existing Salesforce leads
Before you create another lead, check whether Salesforce already has a matching prospect. Notis can review available lead records against your browser research.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List leads
Lists leads from salesforce using soql query, allowing flexible filtering, sorting, and field selection.
Why this helps
A prospect found during research may already exist in Salesforce, and checking manually adds another interruption to the workflow.
- Surface possible existing leads before you decide what to do next.
- Reduce repetitive manual searches across browser research and Salesforce.
- Review findings with the matching context returned from Salesforce.
Setup
Build it in a few focused steps.
- 1Connect Browserbase MCP and Salesforce once in Notis.
- 2Create an automation in the portal or from any channel, then give it a name.
- 3In one instruction, define how to compare supplied prospects with Salesforce leads and how to report possible matches.
- 4Pick a recurring Notis schedule and choose where run reports should go.
- 5Test with one real prospect and review the Salesforce lead results.
Questions about this workflow
Does this workflow create or merge leads?
No. It lists leads for comparison and reports possible matches. You can decide how to handle them.
What if the browser research does not include enough matching information?
Provide additional identifying details in the input. Notis can only compare using information available from the research and Salesforce results.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browserbase MCP to Salesforce. A trigger fires from one place; an action lands in another.
Browserbase MCP triggers
Salesforce actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Salesforce Account
Deprecated: creates a new salesforce account using a json post request, requiring 'name'; specific fields (e.g., custom, dunsnumber) may have org-level prerequisites.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add contact to campaign
Adds a contact to a campaign by creating a campaignmember record, allowing you to track campaign engagement.
Add lead to campaign
Adds a lead to a campaign by creating a campaignmember record, allowing you to track campaign engagement.
Add product to opportunity
Adds a product (line item) to an opportunity. the product must exist in a pricebook entry that's associated with the opportunity's pricebook.
Apply lead assignment rules
Applies configured lead assignment rules to a specific lead, automatically routing it to the appropriate owner based on your organization's rules.
Associate contact to account
Associates a contact with an account by updating the contact's accountid field.
Clone opportunity with products
Clones an opportunity and optionally its products (line items). creates a new opportunity with the same field values and products as the original.
Clone record
Creates a copy of an existing salesforce record by reading its data, removing system fields, and creating a new record. optionally apply field updates to the clone.
Connect any two apps with Notis in the middle.
Browserbase MCP and Salesforce, 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 Salesforce.