Keep scheduled Bolt incident summaries on Salesforce records
Give customer teams a clear record of recurring device issues without rereading every log entry.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List notes
Lists notes from salesforce using soql query, allowing flexible filtering, sorting, and field selection.
Why this helps
Repeated sensor incidents are hard to spot when history is spread across logs and CRM notes.
- Review available incident history for recurring patterns.
- Keep a concise summary with the relevant Salesforce record.
- Help customer conversations start with the existing incident context.
Setup
Build it in a few focused steps.
- 1Connect Bolt IoT and Salesforce once in the Notis portal.
- 2Create an automation and describe the incident summary you want.
- 3Tell Notis what history to review, how to identify the Salesforce record, and what counts as a useful summary.
- 4Choose the recurring schedule trigger and where run reports should go.
- 5Test with one real history review and verify the note is attached to the correct record.
Questions about this workflow
Will Notis see all historical Bolt logs?
It can review history available through the connected Bolt MCP or API. State the time range or limits in your instruction if relevant.
Can it create duplicate notes every run?
The note action creates a note. Instruct Notis to check for an existing equivalent summary where possible and report uncertainty rather than repeatedly creating duplicates.
What happens if a record match is uncertain?
Have Notis skip note creation and report the incident summary for manual matching.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bolt iot to Salesforce. A trigger fires from one place; an action lands in another.
Bolt iot 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.
Bolt iot 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.