Below are clearly defined playbooks, each including a description, conditions (filters), and automated actions.

Finance and Accounting

Cross-System Status Updates

Automatically track overdue invoices in your billing system and notify relevant teams or update fields.

Conditions:

Billing System → Invoice: Status = Overdue
Optional: Due Date older than Today

Actions:

Salesforce → Update Record
- Object: Account or Opportunity
- Field: Invoice_Status__c = Overdue
- Mention: (Billing System → Invoice Number)
- Fallback: No Invoice Ref
Slack → Send Message
- Channel: Accounting
- Title: Overdue Invoice Alert
- Message:
  💸 Invoice [Invoice - Number] for [Account - Account Name] is overdue. Please follow up promptly.

CRM Automation

Playbook: CSV to Salesforce Import

Create Salesforce accounts from CSV file uploads.

Conditions:

CSV → Row: New_Account = Yes

Actions:

Salesforce → Create Record (Account)
- Account Name: Mention (CSV → Account Name)
- Opted Out of Emails: Mention (CSV → OptOut Column), transform 0→No, 1→Yes, Null→No
- Industry: Mention (CSV → Industry Column)

Playbook: Migrate HubSpot Deals into Salesforce Opportunities

Automate Salesforce opportunity creation from HubSpot deals.

Conditions:

HubSpot → Deal: Stage = Closed Won

Actions:

Salesforce → Create Record (Opportunity)
- Opportunity Name: Mention (HubSpot → Deal Name), fallback: No Deal Name
- Close Date: Mention (HubSpot → Close Date), fallback: TBD
- Amount: Mention (HubSpot → Amount), fallback: 0.00

Data Integrity

Playbook: Finding and Fixing Missing Records

Identify and notify about contacts missing critical information.

Conditions:

CRM → Contact: Email = not set

Actions:

Slack → Send Message
- Title: Incomplete Contact Record Alert
- Message:
  ⚠️ Contact [Full Name] has no email. Owner: [Owner Email]. Please update promptly.
Generate CSV
- Fields: Contact Name, Owner, Last Activity Date, Missing Email Field
- CSV manually updated and re-uploaded via a separate Banana playbook.

Customer Health Management

Playbook: Prioritize Tickets from Accounts with Low NPS

Detect and alert about open tickets from low NPS customers.

Conditions:

Salesforce → Account: NPS__c < 50
Salesforce → Case: Status = Open

Actions:

Slack → Send Message
- Title: Low NPS Alert: Prioritize Tickets
- Message:
  🔴 Account [Account Name] with low NPS ([NPS Score]) has open case ([Case Number]). Immediate attention required.
Generate CSV (optional):
- All low NPS accounts and case details for weekly reviews.

Playbook: Too Many Support Tickets for High-Touch Accounts

Identify high-touch customers with excessive open tickets.

Conditions:

Salesforce → Account: AccountType__c = High Touch
Intercom → Ticket: Status = Open
Count(Open Tickets) > 5

Actions:

Salesforce → Update Record
- Field: Open_High_Priority_Tickets__c
- Mention: Count of Open Tickets
- Fallback: 0

Category: Bug & Ticket Management

Playbook: Bug Resolution Completed → Ready for QA Testing

Automatically notify QA team when Jira bugs are resolved.

Conditions:

Jira → Issue: Type = Bug
Jira → Issue: Status changed = Resolved

Actions:

Slack → Send Message
- Title: Bug Ready for QA
- Message:
  ✅ Bug [Issue - Key] resolved, ready for QA testing. Assigned: [Assignee].

Playbook: Critical Ticket SLA Exceeded

Alert and escalate when critical tickets exceed SLA.

Conditions:

Salesforce → Case: Priority = Critical, Status = Open
CreatedDate older than 1 day

Actions:

Slack → Send Message
- Title: Critical SLA Breach
- Message:
  🔴 Case [Case Number] open >1 day. Customer [Account Name] awaiting resolution.
Salesforce → Create Escalation Record
- Subject: Critical SLA Exceeded
- Assigned: Escalation Team
- Description: Mention (Case Number)

Category: Sales and Growth Opportunities

Playbook: Identify a Potential Growth Opportunity

Spot and notify sales about upsell opportunities.

Conditions:

Salesforce → Account: Customer_Satisfaction__c >= 80
Salesforce → Account: UsageScore__c >= 75
Salesforce → Account: Is_Existing_Opportunity__c = False

Actions:

Salesforce → Create Record (Opportunity)
- Opportunity Name: Mention (Account Name) + " Upsell"
- Close Date: Today + 30 Days
- Stage: Prospecting
- Source: BonData
Slack → Send Message
- Title: Upsell Opportunity Created
- Message:
  🚀 Potential upsell: Opportunity [Opportunity Name] created for [Account Name]. Satisfaction: [Satisfaction Score], Usage: [Usage Score].