Speed up your processes with good Slack Notifications

This is one obvious application for working with applications like Hubspot and Pipedrive.

Most companies need certain things to happen with for onboarding new clients. Slack can be a very helpful tool in prompting people towards key actions in your process.

See Automated Crash Reporting to see how we use Slack to give real time notifications anytime a crash happens with Iguana anywhere in the world.

See our Build system. In our company if you push a commit which breaks the build of IguanaX, within minutes you are going to be notified by Slack that there is a problem.

See Boy that cried wolf - false positive. It’s easy to get carried away with notifications and make them too noisy and chatty. If something is everyone’s responsibility then it is no one’s responsibility.

Staff will swiftly ignore notifications which are always bleeping for no good reason.

This is really big - you only do it there is a specific action required by someone. If it’s just a general up date then it’s better for it to go into a general slack channel. This is how we do it with our Build system:

Open

If a developer gets tagged (see Tagging individuals with Slack notifications) if and only if they broke the build - i.e. there is a real action for them to perform.

In the case of the Build system we have links for the following systems:

• Our Git source code commits (in Bitbucket)

• The logs from the build

• At one point we also had links to Jira our project management system (should do that again!)

One can do the same with most web applications with products like Hubspot, Pipedrive and Xero etc.