Connect Bug Recorder to Salesforce

When something happens in Bug Recorder, Notis takes the next step in Salesforce. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Bug Recorder to Salesforce

View example

Attach Bug Context to a Salesforce Record

Turn an incoming Bug Recorder error into a concise Salesforce note on the related account, lead, contact, or opportunity when its record can be identified.

View example

Create Salesforce Follow-Up for a New Error

Create a Salesforce task from a Bug Recorder error that needs human investigation, with a short summary and useful diagnostic context.

View example

Record Customer Impact from Error Reports

Add a concise Salesforce note summarizing a Bug Recorder error's known customer impact, while clearly marking impact details that are missing.

View example

Track Error Reports That Need Release Investigation

Create a Salesforce task when a Bug Recorder error includes release or version context that your team wants to investigate.

View example

Review Recent Salesforce Error Notes

On a recurring schedule, list recent Salesforce notes related to Bug Recorder errors and summarize them in the run report for review.

View example

Find Error Notes Missing a Salesforce Link

On a recurring schedule, review Salesforce notes for Bug Recorder error summaries that lack a clear related customer record and report them for cleanup.

View example

Review Leads Mentioned in Error Notes

On a schedule, list Salesforce leads and compare them with available Bug Recorder error notes to report only clear, supported relationships for human review.

View example

Review Open Opportunities for Error Context

On a schedule, list Salesforce opportunities and relevant Bug Recorder notes, then report explicit opportunity references that may need human follow-up.

View example

Create Tasks for Error Notes Still Needing Review

On a schedule, inspect Salesforce error notes and create follow-up tasks only for items that match your explicit review criteria and lack a recorded resolution.

Supported Triggers and Actions

Notis builds workflows that link Bug Recorder to Salesforce. A trigger fires from one place; an action lands in another.

Bug Recorder triggers

Salesforce actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add contact to campaign

Adds a contact to a campaign by creating a campaignmember record, allowing you to track campaign engagement.

ActionInstant

Add lead to campaign

Adds a lead to a campaign by creating a campaignmember record, allowing you to track campaign engagement.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Associate contact to account

Associates a contact with an account by updating the contact's accountid field.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.