Review incident context for Salesforce leads on a schedule
Bring incident and lead context together during a recurring review when the available records give you a reliable link.
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 lead's reported technical issue can be overlooked when incident monitoring and lead tracking are reviewed separately.
- Surface lead follow-up context during recurring incident reviews.
- Use a supplied identifier to link a lead and incident reliably.
- Avoid creating or changing lead records based on an ambiguous match.
Setup
Build it in a few focused steps.
- 1Connect Bugsnag and Salesforce once in the Notis portal.
- 2Create an automation in Automations and name it for lead incident review.
- 3Tell Notis to review open Bugsnag incidents and Salesforce leads, report only reliable matches using supplied identifiers, and summarize the needed follow-up.
- 4Choose a Notis schedule as the trigger and set the review cadence.
- 5Choose a report channel, then test with one incident and a known Salesforce lead.
Questions about this workflow
Does this workflow change Salesforce leads?
No. It uses the Salesforce lead listing action to review available records and report relevant context; it does not update the lead.
How does Notis know which lead relates to an incident?
Provide a reliable shared identifier or other explicit matching context. Similar names alone may not establish that a lead is affected.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bugsnag to Salesforce. A trigger fires from one place; an action lands in another.
Bugsnag 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.
Bugsnag 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.