Keep customer-impacting regressions with the Salesforce account
Put a regression's customer context beside the account record your team uses to coordinate the response.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create note
Creates a new note attached to a salesforce record with the specified title and content.
Why this helps
The engineering alert and the customer account history often live in separate places, making impact harder to track.
- Keep the regression summary with the account context.
- Give customer-facing teammates a place to find the incident details.
- Use a supplied Salesforce record reference to avoid guessing which account is affected.
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 regression tracking.
- 3Tell Notis to create a Salesforce note on the account identified in each incoming regression alert, using the supplied error summary and incident link.
- 4Choose the Notis webhook trigger and configure Bugsnag to send the alert with the account reference.
- 5Choose a report channel, then test with one real regression alert and a known account.
Questions about this workflow
Can Notis identify the customer account from an error alone?
Only when the request includes a reliable account identifier or enough supplied context to identify it. Do not assume Bugsnag provides Salesforce account data.
What if the alert does not identify an account?
Have the automation avoid creating an account note when the record cannot be identified, and report that the alert needs account context.
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.