Close Salesforce follow-up tasks when chats confirm resolution
When a customer confirms the issue is handled in chat, let Notis record that outcome on the related Salesforce task.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Complete task
Marks a task as completed with optional completion notes. this is a convenience action that updates the task status to 'completed'.
Why this helps
Tasks linger open after a customer has already confirmed a resolution in a later conversation.
- Keep task status aligned with explicit customer confirmations.
- Reduce manual cleanup after a resolved Botbaba conversation.
- Retain a short completion note describing the confirmed outcome.
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 find the related Salesforce task from supplied identifiers and complete it only when available Botbaba conversation data explicitly confirms resolution; include a concise completion note grounded in that data.
- 4Choose the recurring schedule trigger and select where run reports should go.
- 5Test with one real resolved conversation and confirm the correct task is completed.
Questions about this workflow
How does Notis find the task to complete?
The workflow needs a task identifier or enough supplied context to locate the correct task through available Salesforce data. If it cannot confidently identify one, it should report the missing reference.
Does a Botbaba message trigger this immediately?
No Botbaba trigger events are listed. The schedule reviews data available to Notis when the scheduled run begins.
Will Notis close a task based on an implied resolution?
The instruction should require an explicit confirmation in available conversation data. Ambiguous cases should be left open and reported.
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.