Find the Salesforce account context for recurring incidents
Make account context easier to find by checking incident identifiers against Salesforce during a regular review.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List accounts
Lists accounts from salesforce using soql query, allowing flexible filtering, sorting, and field selection.
Why this helps
An incident may affect a known customer, but responders still have to switch tools and search for the matching account.
- Surface Salesforce account details for incidents with a reliable account identifier.
- Reduce manual searching across monitoring and CRM tools.
- Keep the review grounded in account data Salesforce can return.
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 incident account lookup.
- 3Tell Notis to review incidents and look up Salesforce accounts only when a reliable account identifier is present, then summarize the incident alongside returned account details.
- 4Choose a Notis schedule as the trigger and set the review cadence.
- 5Choose a report channel, then test with one incident linked to a known Salesforce account.
Questions about this workflow
Can the workflow find accounts from a company name alone?
It can only use the available Salesforce listing and incident data. Provide a reliable identifier when possible, and have Notis report ambiguous matches rather than assume.
Does this update account records?
No. It lists matching accounts and summarizes returned details; it does not modify them.
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.