In September Clubhouse is changing our name. OurnewnameisShortcut.

Twelve Days of Integrations: Rollbar

Richard Huffaker

It’s that time of year again, though it may not quite feel it. The leaves have taken their time falling from the trees, department stores are playing Michael Buble songs on a loop to almost entirely empty rooms, and I put a little hat on my cat because it makes not leaving the house feel slightly more festive. 

To celebrate, Clubhouse is highlighting twelve of our integrations with a detailed write up alongside their own little digital snow globes. We hope you return every day to enjoy these posts alongside your tinglers and fuzzles, your dafflers and wuzzles, and your delicious pot (or Beyond meat) roasts. 

Our tenth featured integration is Rollbar.

On the Tenth Day of Integrations Clubhouse gives to you: ten bugs a'making your customers really upset on twitter and a Rollbar to help fix them.

Bugs are an accepted and unavoidable part of the software development process. And that's because very few individual software bugs are as destructive as flaws in other engineering processes. A mistake in planning the construction of a skyscraper can result in a sinking, leaning tower full of angry rich people (as actually happened with San Francisco's 650 foot tall Millennium Tower), requiring both epic engineering solutions and lawsuits to resolve. A mistake in shipping a piece of software can often be resolved by fixing a typo and without involving even a single attorney. Not quite so serious.

But all the many small bugs that every engineer ships add up to a ton of wasted time and annoyance for those engineers and their customers. Ideally bugs would be easy to spot and are surfaced well before more than a few customers ever find out about them, alongside contextual information that makes the bug easy to fix.

Our integration with Rollbar (and similar tools) helps bring this ideal scenario closer to reality.

How does it work? 

Our Rollbar integration enables you to generate Clubhouse Stories from Rollbar Issues and then to resolve / update those Stories (and vice-versa) based on the current progress on fixing the Issue.

This particular integration takes a couple of extra steps to setup, but those steps are very much worth it.

In Clubhouse

Go to Settings → API Tokens, generate a new API token named "Rollbar" (or anything you want to name it), and copy it to your clipboard.

API Tokens

API token generated in Clubhouse

In Rollbar

Go to User Settings → Connected Account → Clubhouse and save your Clubhouse API token.

Connected Accounts

Integrations within Rollbar

In your Rollbar project, go to Settings → Notifications and select Clubhouse from the list of options.

Clubhouse Setup

Clubhouse setup in Rollbar

In the Clubhouse configuration screen enter the following:

  • API Token: Just make sure the token you generated above is the one you select.
  • Organization: Name of your organization. 
  • Clubhouse project: The project where you want new Stories to be created.
  • Clubhouse epic: The Epic you want new Stories to be part of. (Optional)
  • Initial state: The Workflow state you want Rollbar generated Stories to start in.
  • Reactivated state: The Workflow state Stories will start in if a resolved Rollbar Issue crops back up.
  • Resolved state: The Workflow state for
  • Labels: Labels to apply to stories when created. (Optional)

Click Save Settings, then click Send Test Notification to verify that stories can be created with the correct configuration.

Configure your automated rules, as described in Rollbar's Issue Tracking guide.

Click the toggle to set the integration to Enabled.

All done! Now with Clubhouse and Rollbar you'll be fixing so many bugs that your tech debt will become a tech surplus.

Give us a whirl
Because you shouldn't have to project manage your project management.