--- title: "How to Build Account-Based Notifications Across CRM and Messaging Platforms" img: https://s3.us-east-2.amazonaws.com/unified-article-images/how_to_build_account_based_notifications_across_crm_and_messaging_platforms-icon.png date: 2026-03-24T00:29:00.000Z tag: Product description: "Account-based notifications are a feature inside a SaaS product that trigger alerts based on changes in customer data—such as deal updates, new activity, or..." url: "https://unified.to/blog/how_to_build_account_based_notifications_across_crm_and_messaging_platforms" --- # How to Build Account-Based Notifications Across CRM and Messaging Platforms ------ _March 24, 2026_ Account-based notifications are a feature inside a SaaS product that trigger alerts based on changes in customer data—such as deal updates, new activity, or engagement signals—and deliver those alerts through messaging platforms like Slack, Gmail, or Microsoft Teams. To build this, your product needs to monitor CRM data in real time and send notifications through messaging systems. CRM platforms like Salesforce and HubSpot store deal and activity data, while messaging platforms handle delivery and collaboration. Each platform exposes different APIs and event models. Unified provides category-specific APIs for CRM and Messaging, allowing your product to retrieve updates and send notifications across platforms using consistent objects and endpoints. ## Why SaaS Products Build Account-Based Notifications Many B2B SaaS products include notification features to help teams stay informed about account activity. Examples include: - Revenue intelligence platforms - Customer success tools - Sales productivity tools - Account management platforms - AI sales assistants These products help users respond quickly to changes in customer accounts. Typical needs include: - **Immediate alerts** when important events occur - **Proactive notifications** for risk or opportunity signals - **Team visibility** across sales and customer success - **Automated workflows** triggered by account changes Without automation, teams must manually monitor CRM systems for updates. ## Common Notification Use Cases Account-based notifications typically support several workflows. **Deal stalled alerts** Notify teams when a deal has not progressed for a defined period. **New activity alerts** Trigger notifications when new calls, meetings, or notes are logged. **Deal stage changes** Alert users when a deal moves to a new stage. **Customer risk signals** Notify teams when support activity spikes or engagement drops. **Internal collaboration alerts** Send messages to Slack or Teams channels for team visibility. ## Unified Categories Used Account-based notifications combine data from CRM and Messaging categories. | Category | Description | Key Objects | | --------- | --------------------------------------------------------------------------- | ----------------------------- | | CRM | Account, deal, and activity data from platforms like Salesforce and HubSpot | contact, company, deal, event | | Messaging | Communication delivery across platforms like Slack, Gmail, and Teams | message, channel | These categories allow your product to detect changes in account data and deliver notifications to users. ## Unified CRM Objects and Key Fields CRM objects provide the signals that trigger notifications. | Object | Key Fields | Purpose | | ------- | ------------------------------------------ | ----------------------- | | Deal | amount, stage_id, probability, closing_at | Track pipeline changes | | Event | type, created_at, contact_ids, company_ids | Detect new activity | | Contact | name, emails, company_ids | Identify affected users | | Company | name, domains | Group account data | Important event types include: - NOTE - EMAIL - CALL - MEETING - TASK These activity types allow your product to trigger notifications based on customer engagement. ## Unified Messaging Objects and Key Fields Messaging objects handle notification delivery. | Object | Key Fields | Purpose | | ------- | ------------------------------------------- | ----------------------------- | | Message | message, subject, author_member, created_at | Notification content | | Channel | id, name, members | Destination for notifications | Messages include: - recipients (`destination_members`, `mentioned_members`) - channels for group notifications - content formatting (plain text, HTML, Markdown) These fields allow notifications to be sent across multiple platforms. ## Connecting Customer CRM and Messaging Platforms Customers connect their CRM and messaging platforms using Unified Connect. Typical flow: 1. Your application launches the authorization flow. 2. The user selects integrations such as Salesforce, HubSpot, Slack, or Gmail. 3. The user authorizes access. 4. Unified returns a **connection_id**. Your application stores: ```plain text user_id → connection_id ``` All API requests reference this identifier. ## Detecting Account Events Notifications are triggered by changes in CRM data. CRM events can be retrieved using: ```plain text GET /crm/{connection_id}/event ``` Common filters include: - `updated_gte` to retrieve recent changes - `deal_id`, `contact_id`, or `company_id` to scope events - `type` to filter activity types Typical trigger conditions include: - no activity for a defined period - new activity logged - deal stage change - deal created or updated ## Sending Notifications Notifications are delivered through the [Messaging API](/messaging). ```plain text POST /messaging/{connection_id}/message ``` To send a notification, provide: - message content - destination channel or recipients - optional thread context using `parent_id` Example notification: ```plain text Deal stalled: No activity on Acme Corp for 14 days ``` Messages can be sent to: - Slack channels - Microsoft Teams channels - email recipients ## Building Notification Logic A typical notification system includes the following steps. **1. Retrieve CRM data** Fetch recent events, deals, and account activity. **2. Evaluate conditions** Apply rules such as inactivity thresholds or stage changes. **3. Generate notification content** Create a message describing the event or alert. **4. Send notification** Use the Messaging API to deliver the message. **5. Track notifications** Optionally store notification history in your application. ## Keeping Notifications Real-Time Unified provides webhook events for CRM and messaging updates. CRM events: - deal created - deal updated - activity created Messaging events: - message created - message updated These events allow your application to trigger notifications immediately when data changes. ## Supported Platforms Unified supports a wide range of integrations across categories. CRM (47+ integrations) - Salesforce - HubSpot - Pipedrive - Zoho CRM Messaging (17 integrations) - Slack - Gmail - Microsoft Teams - Outlook This allows notification systems to work across many customer environments. ## Why This Matters Account-based notifications require monitoring CRM data and delivering alerts through messaging platforms. Without a unified approach, developers must build separate integrations and handle different event models. Unified provides: - consistent CRM and messaging APIs - real-time data access - unified event handling - simplified notification delivery This allows product teams to build notification features that keep users informed without managing integration complexity. Start building account-based notifications across CRM and messaging platforms today. Sign up for a free trial or request a demo to see how Unified can power your product. → [Start your 30-day free trial](https://app.unified.to/login) → [Book a demo](https://calendly.com/d/cph9-g8n-jzg/connect-with-unified)