Send DealJourney updates to Slack

Slack is where most teams already are, so DealJourney can announce the things worth announcing there rather than making people check the CRM for them.

Connect the workspace

An administrator does this once, and it covers everyone.

1. 1Open Markedsplass from the sidebar and find Slack.
2. 2Start the connection and approve DealJourney in your Slack workspace.
3. 3Choose the channel updates should land in.
4. 4Send a test message to prove it works before you switch anything on.

DealJourney can post to any public channel on its own. For a private one, invite the DealJourney app to that channel first, otherwise it will not appear in the list.

Choose what gets announced

Each kind of event — a deal won, a document signed, a new support ticket, an invoice paid — has its own switch, and its own choice of channel. That second part is what keeps one channel from carrying everything: deals can go to your sales channel and tickets to your support one.

The owner or assignee of the record is tagged in the message when their DealJourney email address matches a Slack account, so the person who needs to act gets a real notification rather than hoping someone reads the channel.

Stop the channel filling up

Switching an event off to escape the noise also throws away the alerts you wanted. So the noisy events can be narrowed instead:

• Deals and invoices take a minimum value. Only the ones worth at least that figure are posted. The figure is in your own currency, so it means the same thing even when you sell in several. DealJourney offers your own typical deal size from the last three months as a starting point, because a number taken from your own history is a better guess than one we invented.
• New support tickets take a set of priorities. This is the one that arrives already narrowed: new tickets are posted at urgent and high only. Most tickets are medium or low, and posting every one of them is what makes a channel unreadable within a week. Widen it whenever you want.

Nothing is ever hidden because we could not measure it. A deal with no value on it, or a ticket with no priority set, is posted either way. A message that quietly never arrives is worse than one arriving too often, because you would have no way of knowing.

Let an automation post its own message

The built-in list above covers the common moments. For anything else, build a workflow rule and give it a Post to Slack step: "when a deal over 500 000 moves to negotiation, tell the sales channel".

Open Arbeidsflytautomatisering, build the rule as normal, and add Post to Slack as its action. You write the message, and merge fields fill in the record's details. You can also choose a channel, tag the record's owner, and add a button that opens the record in DealJourney.

Use this rather than the webhook step. A webhook pointed at Slack knows nothing about the workspace you connected, so it cannot pick a channel, cannot tag anybody, and makes you look after a second Slack credential DealJourney never issued and cannot help you with.

Send a report to Slack

Any scheduled report can be delivered to a Slack channel instead of, or as well as, an inbox. Build the report as usual, press Planlegg e-post, and choose a channel alongside Mottakere. Leave the address list empty to send it only to Slack.

The channel gets the headline figures and the first few rows, with a button to open the full report. Spreadsheet and PDF attachments stay an email idea — a few thousand rows pasted into a channel helps nobody.

This is also how you change the old daily summary. It is an ordinary scheduled report now, so you choose its day, its time, its time zone and what is in it, the same as every other report. If you had the summary switched on before, it was carried over for you and now sends at 08:00 in your own time zone.

When something is not right

Nothing arrives at all. Check a channel is chosen and send a test message. A workspace that is connected but has no channel cannot post anything.

Nothing arrives in a private channel. The DealJourney app has to be a member of it. Invite it and try again.

A person is never tagged. Their DealJourney email address does not match any account in that Slack workspace. Matching is by email and nothing else.

Fewer messages than you expected. Check the conditions under the event before assuming something is broken — new tickets in particular start filtered to urgent and high.

Someone left and their reports stopped. A scheduled report belongs to the person who created it. If they lose access to the data, the report pauses itself rather than sending figures they were no longer allowed to see.

Turning it off

Disconnecting removes DealJourney's access to the workspace immediately, and nothing further is posted. Messages already in Slack stay there. To stop one kind of update rather than all of them, switch that event off instead.