Skip to content
CommunicationLive

Flivara × Slack

Get real-time Slack alerts the moment a client views or signs a proposal.

What this integration does

Connect Slack to Flivara and keep your whole team instantly informed at every stage of the proposal lifecycle — from first view to signed deal. No more checking the Flivara dashboard — the deal comes to you.

Key benefits

  • Instant Slack notifications on proposal events
  • Choose specific channels per event type
  • Rich message formatting with proposal details
  • Team mentions when high-value deals close
  • Daily digest of proposal activity

Step-by-step setup

  1. 1

    Add Flivara to your Slack workspace

    Navigate to Settings → Integrations → Slack in your Flivara dashboard and click "Add to Slack". You will be directed to Slack's OAuth page. Select your workspace from the dropdown, review the requested permissions, and click "Allow".

    You need to be a Slack Workspace Admin or have permission to install apps to complete this step.

  2. 2

    Select notification channels

    After authorizing, choose which Slack channels receive each type of notification. Recommended setup: #proposals-sent → when a proposal is shared; #deals-won → when a proposal is signed; #proposals-viewed → when a client first opens a proposal.

  3. 3

    Configure notification content

    Customize what information appears in each Slack message. You can include: proposal title, client name, deal value, the direct Flivara link, and a @mention of the proposal owner. Toggle each field on or off per notification type.

  4. 4

    Set value thresholds for team mentions

    Configure a deal-value threshold above which Flivara sends a @channel mention in your #deals-won channel. For example: proposals over $10,000 trigger a @channel shout-out so the whole team celebrates the win.

  5. 5

    Enable the daily digest

    Turn on the Daily Proposal Digest to receive a 9 AM summary in a chosen channel. The digest shows proposals sent, viewed, signed, and expired in the past 24 hours — a lightweight way to stay on top of pipeline health without individual pings.

Use case examples

Instant win notification

Scenario

A £15,000 website redesign proposal is accepted at 11:47 PM.

What happens

Within seconds, a Slack message appears in #deals-won: "🎉 Deal closed! [Client] signed the Website Redesign proposal for £15,000. Owner: @sarah. View in Flivara →" The whole team sees it first thing the next morning.

Sales team follow-up trigger

Scenario

A client opens a proposal for the third time in two days without signing.

What happens

Flivara sends a Slack message to the proposal owner: "👀 [Client] just viewed your Brand Identity proposal for the 3rd time — this might be a good moment to follow up." The rep sends a timely nudge and closes the deal.

Pipeline morning briefing

Scenario

An agency director wants a daily summary without logging into Flivara.

What happens

At 9 AM, a digest lands in #proposals-daily: "Yesterday: 4 sent, 3 viewed, 1 signed ($4,200), 0 expired. 7 proposals currently open. Oldest open: 12 days." Full pipeline visibility in 10 seconds.

Troubleshooting

Slack notifications stopped arriving.

The most common cause is the Flivara Slack app being uninstalled or the bot being removed from the target channel. Re-check in Settings → Integrations → Slack. If status shows "Disconnected", re-authorize. Also verify the Flivara bot is still a member of the target channels.

I am receiving duplicate notifications.

This happens when the same Slack workspace is connected twice (e.g. by two different Flivara users). Go to Settings → Integrations → Slack, disconnect any duplicate connections, and re-configure with a single authorized account.

The @channel mention is not sending even for high-value deals.

Check the value threshold setting in Settings → Integrations → Slack → Advanced. The threshold is in your account's primary currency. Also verify the selected channel allows @channel mentions for the Flivara bot role.

Daily digest is not arriving.

Confirm the digest is toggled "On" and the scheduled time is set correctly. The digest uses UTC time — adjust for your local timezone offset. Also check that the digest channel has not been archived.