Set up separate Salesforce account records for new divisions
Give a newly launched division its own record when your team decides it needs separate account tracking.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
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.
Why this helps
New divisions can be hard to track when their conversations remain mixed into the parent account's history.
- Create a separate account record from a known Salesforce source.
- Support distinct tracking when a division has its own relationship context.
- Avoid cloning based on speculative organizational changes.
Setup
Build it in a few focused steps.
- 1Connect Botbaba and Salesforce once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3In one instruction, ask Notis to clone the supplied Salesforce account only when accessible Botbaba conversation data confirms the division should be tracked separately, and report any required updates for review.
- 4Choose the recurring schedule trigger and select where run reports should go.
- 5Test with one real division launch and verify the clone before using it for ongoing records.
Questions about this workflow
Does this action create a fully configured new division account?
It clones an existing record. Review the clone and apply any division-specific details using supported Salesforce actions.
What if the team has not decided to track the division separately?
The instruction should require an explicit decision or confirmation and skip tentative discussion.
Can it avoid creating multiple clones on later runs?
The clone action does not promise duplicate detection. Use a reliable tracking method or ensure the workflow only receives each confirmed launch once.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botbaba to Salesforce. A trigger fires from one place; an action lands in another.
Botbaba 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.
Botbaba 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.