Turn rail disruption alerts into customer follow-ups
A service disruption can quickly become a customer issue. Start a Salesforce task from the Bart alert and keep the next step visible.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create task
Creates a new task in salesforce to track activities, to-dos, and follow-ups related to contacts, leads, or other records.
Why this helps
When a rail disruption arrives in one tool and customer work lives in another, follow-up can slip through the cracks.
- Capture an alert as a concrete customer follow-up
- Reduce manual copying between Bart and Salesforce
- Keep disruption response work in the CRM
Setup
Build it in a few focused steps.
- 1Connect Bart and Salesforce once in the Notis portal.
- 2Create an automation in the portal, or tell Notis in plain language from any channel.
- 3Describe the outcome: create a Salesforce task when a Bart service alert may affect a customer trip, and include the alert details in the task.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real Bart alert and review the created task.
Questions about this workflow
Does Bart provide an event trigger for service alerts?
Bart exposes no trigger events in this setup. A Notis webhook can start the automation when an HTTP request is sent.
Can the automation know which Salesforce customer is affected?
Only if the request or other information available to Notis identifies the customer or related Salesforce record. The task action needs enough context to associate the follow-up appropriately.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bart to Salesforce. A trigger fires from one place; an action lands in another.
Bart 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.
Bart 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.