Keep a reported Bugsnag impact with the Salesforce contact
Record a customer impact report next to the contact so the people following up can find the same incident context.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create contact
Creates a new contact in salesforce with the specified information.
Why this helps
Customer impact details can stay buried in error reports instead of the contact record used for outreach.
- Keep a reported impact visible on the identified Salesforce contact.
- Include the incident reference in the contact's account context.
- Avoid losing customer reports in monitoring-only workflows.
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 contact impact tracking.
- 3Tell Notis to add a Salesforce note to the contact identified in the incoming request, summarizing the reported impact and linking the Bugsnag incident.
- 4Choose the Notis webhook trigger and configure the request to include the Salesforce contact reference and impact details.
- 5Choose a report channel, then test with one real report and a known contact.
Questions about this workflow
Does Bugsnag automatically provide Salesforce contact IDs?
That is not specified here. Include a reliable contact reference in the webhook request if the workflow should attach a note to a specific contact.
What if there is no customer impact information?
The workflow should not create a contact note unless the incoming request includes a reported impact and identifies the contact.
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.