Articles

How to integrate Slack with Confluence

A guide we wrote to run you through how to hook up Confluence and Slack using the Slack for Confluence Pro plugin.

Moving off Hipchat onto Slack and still using Confluence as your internal wiki? Then you might be worried about not having access to your team’s internal knowledge on Confluence from your internal chat tool.

Luckily, there’s a way to integrate Slack with Confluence thanks to Atlassian’s add-ons marketplace. Using the Slack for Confluence Pro plugin, you can send notifications from Confluence right to Slack for $5/month after a free trial.

Below I’m going show you how to set up the Slack for Confluence Pro add-on in just a few minutes.

How to connect Slack to Confluence

Log into your Confluence Cloud account

Click the gear icon in the upper right and select the Add-ons menu option

confluence-add-ons

Click “Find new add-ons” in the right side menu

confluence-manage-add-ons

Search for “slack for confluence” then click “Free trial” in the Slack for Confluence Pro row.

You’ll need to accept terms and conditions of the add-on author, which asks for ask for read permissions to read your Confluence install. That means the plugin author will be able to read and access your Confluences pages.

Important Caveat: Use this plugin at your own risk. Slack for Confluence is built by Made in 49. I tried to visit their website which is using an expired SSL certificate and the website is a placeholder that just displays the company’s name. I couldn’t find much information on the plugin author and this plugin isn’t Atlassian Verified, so use it at your own risk.

After you’ve verified click the Go to Settings.

Now you need to setup a webhook, which are basically a way to send data into Slack in real time. All you need to do is** **go to your webhook manage**r and choose a channel you want to send your Confluence notifications to inside of Slack. Copy the webhook url for the next step.

copy-webhook

Now you’re going to need to paste your copied webhook into the Webhook URL field in your Slack for Confluence settings page. You can leave all the other settings as the defaults or change them if you want.

paste-webhook

You’ll also need to choose a Slack channel to tell the connector where to push your notifications. The channel needs to start with a # symbol, or if you’re pushing to an individual user you need to start with an @ symbol. You can push your notifications to multiple channels by separating each entry with a comma.

choose-channel

Hit Save, and you should be all set. You can check to see if your webhook was properly set up by loading the Slack channel you connected to and check to see if a notification confirming the integration setup came through.

webhook-setup-good

When you publish a page or a comment, a Slack notification should come through linking directly to your Confluence page. Go ahead and check it out.

slack-notification

Alternatives to Sharepoint

A quick run-through of the different tools you can use instead of Sharepoint for internal knowledge sharing.

There’s no denying that some teams really love using Microsoft Sharepoint and Office 365 to share internal knowledge. If you’re not one of those teams though then you’ve come to the right place. We’ve outlined a few viable alternatives to Sharepoint for you below in case your team’s looking for a new internal knowledge base.

Why you may want a SharePoint alternative

Before we jump into the alternatives tools you can use in place of Sharepoint, it’s probably useful to take a step back and think about why you might want to switch off Sharepoint. It’s a big decisions and not one to be lightly made, so we’ve discussed some of the reasons you might want to switch belong.

Not on the Microsoft stack anymore

For years Microsoft dominated the business software market. It seemed like everyone used Windows, Microsoft Office, Outlook and all Microsoft’s other tools including Sharepoint, to do their work. Recently though with the advent of cloud based software, there’s been a shift. There’s more options for software to solve your every business need then you could possibly evaluate. The rise of APIs also makes it easier to connect them all together, meaning you don’t need to feel constrained to one ecosystem. If you find your team has ditched Skype, Office, and Outlook and instead use Slack, Google Docs and GMail, it might be time to ditch Sharepoint for another wiki product too.

Less Management

Sharepoint’s a great product that has almost every feature you’d want. But it can also feel a bit bloated too. If you’re team’s on the smaller side, you might find that it has too many features and you’re spending more time managing the product than actually using it to solve your business needs. Luckily, there’s simpler tools out there now that do most of what Sharepoint does without all the bloat, so you get what you need but aren’t distracted by features you don’t want.

Easier to use

Chances are your team would love to use tools at work that are as simple as the ones they use at home, like Facebook, GMail and Dropbox. Besides making your team happier, easy-to-use tools are better for your company because it means that people will actually use them and not have to ask too many question about how to use them. If it seems like people on your team just aren’t engaging on Sharepoint like they used to because their bar for usability and design has gone up, it might be time to switch to something lighter that looks more like a consumer app and less like a clunky enterprise tool.

We’ve taken the time to research some of the most popular sharepoint alternatives so you can save yourself some time. If you have any questions please reach out in the comments.

Huddle

Huddle’s an all-in-one collaboration hub for your team. It has basically every tool your company might need to stay in sync, including file storage, project management and collaboration tools. It’s geared towards bigger companies that need a secure place to collaborate as an enterprise. The big downside to Huddle is that it’s made for big companies, and carries hefty price tag with it starting at $20 per month per user. That means if you have a company with 50 employees and you’re adding more every month, then you’re looking at thousands of dollars a year for a suite of products where other similar ones exist at a much lower price point.

G Suite

G Suite, the product formerly known as Google Apps for Work, is used by over 5M businesses, and it’s no surprise. Although the name is new, you’ve probably heard of a few of the products included in G Suite already, including GMail, Google Hangouts, Google Chat, Google Docs, Google Drive, Google Calendar and all the other Google-named products it includes. G Suite basically gives you everything you need to collaborate seamlessly with your team.

The one area Google Apps tends to break down is organizing all the content that gets created by your team as they collaborate in one centralized place. For the world’s best search company, finding a Google Doc from a team member to collaborate on a project or to quickly get at a piece of information you need can be pretty challenging. G Suite seems to not work that great when you’re trying to organize all of those documents and emails into one centralized repository of easy to access knowledge for the entire team.

Dropbox

Dropbox is most well known for their easy-to-use cloud file-storage systems, but what you may not know is they are getting into the same company collaboration space as Sharepoint with the recent launch of Dropbox Paper. Dropbox and Paper work well together, seamlessly allowing you to store your files on Dropbox’s servers and write updates to your team in their innovative Dropbox Paper editor.

The caveat is that Dropbox and Paper might not match the feature set that you’re using Sharepoint for since there isn’t a clear organizational between included in either product from Dropbox. Also, neither tool has features that allows you easily access your from your messaging tool or make sure the content store in there is updated regularly be team members.

Confluence

Confluence is a team collaboration tool built by the company Atlassian. It’s over 15 years old now and is a serious contender in the team collaboration space. Up until recently, Confluence and it’s other add-on products like HipChat, Jira, and Bitbucket were focused mostly on software departments, but lately other teams in a company’s organization like the marketing, sales, support and legal have started adopting it too.

Confluence is great because it has every feature you need for team collaboration and hooks up to all the other products in Atlassian’s portfolio, like their chat tool, Hipchat. That strength is also its weakness though because the tool can feel bloated at times and it doesn’t hook up with other non-Atlassian-owned chat tools like Slack easily. If you’re a team using Slack and want a simple, easy to use internal wiki for your team, Confluence probably isn’t your best choice.

Tettra + Slack

Slack’s taking the business world by storm. It’s one of the fastest growing business apps of all time with over 3M daily active users, 800,000 of which are paying to use the product. What makes Slack shine is that it doesn’t take much effort to get your team started using it and does a great job of making it easy to add for your team to message into the system. In December Slack opened up their platform, allowing third party developers to create apps. There’s hundreds of integrations you can add to Slack now, which makes it all the easier to add more content into your messaging tool.

Slack’s greatest strength is how easy it is to add a message into a channel (aka chat room) whether it be an actual message from a human or a notification from a bot. Since it’s so easy to load up on messages, the channels tend to get crowded, and it’s hard to save the content that might be useful later on to your team in a centralized place separated from all the other messages. There’s lot of good content that’s created and useful as your team talks, but really no central place to put it.

That’s what we built Tettra to solve. It’s an internal wiki, connected directly to Slack. With Tettra, you can curate your team’s knowledge in one centralized repository, and then search it right from Slack. With Tettra and Slack, you should be able to recreate most of the functionality you’ve come to expect from Sharepoint, and give your team a simple, beautifully designed way to communicate, collaborate and share knowledge.

If you’re using Slack and interested in trying out Tettra, you can sign up for a free trial on our site. If you have any questions please reach out to us too. We love talking to people who are interested in using our product.

Why every company needs a workplace wiki

Learn what a workplace wiki is and why your team needs one to succeed.

Imagine this… On your first day of a new job a cord is plugged into your head then all the knowledge about how to do your new job is seamlessly transferred to you, just like how Neo learns kung fu in the Matrix. You’d save weeks learning the ins-and-outs of your new role, save time for for your team by not having to ask questions and you’d immediately be productive from day one.

i know kung fu

It might sound unrealistic, but at some companies, that type of knowledge transfer actually exists (without the cord going into your brain, of course). What I’m talking about is a workplace wiki.

What’s a workplace wiki?

A workplace wiki is a central place where all your coworkers can store internal documentation about processes, projects or products their building. You can think of as Wikipedia or Google for your company. Don’t know how to do something? Just look it up on the internal wiki.

Why does your company need a workplace wiki?

What do Apple, Google, Microsoft, Facebook and Amazon all have in common? If you guessed the are five of the largest companies by market cap in the world, you’d be right. If you guessed the all used internal wikis, you’d also be right.

Companies that don’t have a workplace wiki are at a disadvantage versus their competitors who do. Here are a few reasons why having an internal wiki is important.

Onboard new team members faster

Growing companies spend thousands of dollars a year recruiting teammates, but don’t invest nearly as much money making sure new hires are onboarded quickly and efficiently. Every week someone takes to ramp up to full speed is money gone from company’s bank account in lost productivity.

For the people you’re hiring, starting a new job can be stressful. Having no clue what to do, how to do it, or who to ask for help can make your new teammates feel inept. The reality is, none of that is their fault either since there’s no training course for working a company you’ve never worked at before.

With an internal wiki, new team members can look up what they need to do their job with a simple search, so it makes them feel smarter and saves you money on ramp up cost.

19% of your team’s time is spent searching for information

According to a study by consulting firm McKinsey, knowledge workers spent 19% of their time searching and gathering information to do their jobs. Put another way, for every 5 people you hire, you basically only get productive work out of 4.

Having a centralized internal wiki that contains internal document for how to perform processes, links to important documents and allows your team to collaborate on a specific topic is a huge time saver. In fact, that same study found that by setting us systems that make it easier to search and gather information, you not only recoup that lost 19% but also could increase productivity by as much as 35%.

Knowledge doesn’t leave with people

When one of your teammates inevitably leaves, she’ll take all the institutional knowledge on how to do their job with her. Sure, there’s the “brain dump” approach where you ask your teammate to write down everything she knows before leaving, but that rarely works since it’s hard to document everything in such a short time period and important pieces of information are inevitably forgotten.

With an internal wiki, you can systematically capture your team’s knowledge as it’s happening in real time, so you already have it when you need it later. Over time, the accruement of institutional knowledge becomes a huge competitive advantage for your company that you may otherwise have missed out on creating.

Don’t have a workplace wiki yet?

At Tettra, we’re big believers in empowering your team, so we’re building the easiest to use internal wiki that will help your team share and access your team’s knowledge. We even let you search your wiki right from Slack.

If you’re using Slack and need a wiki, you can sign up for Tettra for free on our site.

If Slack’s not your thing, then there’s plenty of open-source wikis you can setup on your own servers for free, including MediaWiki, DokuWiki and Foswiki.