We plan to cut over from app.clubhouse.io to app.shortcut.com on Monday, Sep 13 at 5pm Pacific Time. We’ll permanently redirect the old URL to the new one, so none of your bookmarks will break (though we recommend you do update them to the new URL at some point).

The first time you access the app at the new address you’ll be asked to log in with your usual credentials. After that, your browser should remember you per traditional browser behavior.

It’s a fun name, it’s memorable, and it fits. We cut through the chaos, noise, and confusion around ongoing work to help people get that work done faster and without wanting to throw their computer out the window. Essentially, we provide a shortcut to getting work done.

The Clubhouse Audio App became so big so fast that we couldn’t possibly hope to forever maintain our own brand standing in the face of their explosive popularity. But our product strategy remains the same.

Our core values remain the same. Our brand identity remains the same (well, other than our name). We believe we’ll only be stronger going forward for this change. Read our blog post about the change.

The following integrations are fully controlled by Shortcut, and we
can provide fairly definitive instructions for them.

Bitbucket

Customers will need to delete the integration from the Bitbucket
side then re-add it from the Shortcut side sometime between September 13 -
November 13.

Note: Linking commits to stories is now via [sc-XXX]. However, we will support [chXXX] forever as well.

Box

No customer action is needed.

Dropbox

No customer action is needed.

GitHub

No customer action is needed.

Note: Linking commits to stories is now via [sc-XXX]. However, we will support [chXXX] forever as well.

GitHub Enterprise

Customers will need to get the new URL from the GitHub integration
pane in Shortcut and put it into GitHub sometime between September 13 -
November 13.

Note: Linking commits to stories is now via [sc-XXX]. However, we will support [chXXX] forever as well.

 

GitLab

Customers will need to get the new URL from the GitLab integration
pane in Shortcut and put it into GitLab sometime between September 13 -
November 13.

Note: Linking commits to stories is now via [sc-XXX]. However, we will support [chXXX] forever as well.

Google Drive

No customer action needed.

Google Sheets

No customer action needed.

iCal

Customers should grab new ical links from the iCal integration pane in
Shortcut sometime between September 13 - November 13.

Outgoing Webhook

• Starting September 14, 2021 all links in Webhook payloads which were to clubhouse.io domains will be to shortcut.com domains instead.
• The Clubhouse-Signature header is now deprecated. It is now called Payload-Signature.
  For now, we are including both headers (with the same signature value),
  but Clubhouse-Signature will be removed on November 13th, 2021.
  Please update your application to read Payload-Signature instead.
  If you did not configure your webhook with a secret to sign payloads with,
  you are not affected by this change.

Please see our Webhook payload documentation at https://shortcut.com/api/webhook/v1.

Productboard

We believe no customer action will be needed and will communicate if that changes.

Sentry

No customer action needed.

Slack

You will need to re-authorize the Slack integration to allow it to unfurl app.shortcut.com URLs. To do so, visit the Slack integration page in Shortcut, click "Reinstall in Slack", then complete the authorization flow.

Zapier

No customer action needed.

Zendesk

We believe no customer action will be needed, and will communicate if that changes.

Integrations managed By 3rd-parties

The following integrations are managed by the respective companies, so
will need to be updated by them. We have given them the information
they need to update, and they will have until 11/13 to make those
updates. It is unlikely that any of those updates will impact
customers.

• Bugsee
• Bugsnag
• Clockify
• Codestream
• Double loop
• FireHydrant
• Honeybadger
• Instabug
• Lambda
• LinearB
• Marker.io
• Plecto
• PomDoneApp
• Rollbar
• Status Hero
• Testlodge

Our API

• The API Token header is now Shortcut-Token. Clubhouse-Token is deprecated but will keep working until November 13, 2021.
• Starting September 14, 2021 the API URL is https://api.app.shortcut.com.
  https://api.clubhouse.io will be deprecated after that time, but will keep working until November 13, 2021.
• Starting September 14, 2021 all links in REST API responses which were to clubhouse.io domains will be to shortcut.com domains instead.

Please see our API documentation at https://shortcut.com/api/.

 

By the end of Aug, expect emails to come from "Team Shortcut" instead of "Team Clubhouse." We ask that you please whitelist the @shortcut.com domain in your email settings to ensure they’re delivered.

In September, our company name on invoices and credit card receipts will be Shortcut Software Company instead of Clubhouse Software, Inc. Please give your finance team a heads up!

As of Aug 3, our Twitter handle has changed to @useshortcut. If you have been following us on @clubhouseio, there's no action needed - you're automatically following @useshortcut right now.

Any invite links sent from the app.clubhouse.io domain will redirect after Sep 13 5pm PT. Any invites sent after the 13th via app.shortcut.com will, of course, just work.

If you’re logged in when we make the switch you’ll likely need to log back in. Any work you’ve submitted during this time will be saved.

Our native mobile apps are being retired on Aug 31, 2021. Our mobile browser app is already more fully featured than our native apps and we’d prefer to put all of our focus in one place rather than three. Read about this decision.

Though Apple Shortcuts is an app, it still more or less functions as a feature within the larger Apple ecosystem. From our perspective, it is far less likely people will confuse us with a feature within a larger brand than to confuse us with another startup. Had Clubhouse Audio’s growth not been so explosive, it’s possible that no one would have confused our two companies at all.

Lots and lots of companies and features share the same or similar names. The core issue for us is potential brand confusion, which we don’t consider to be very likely in these kinds of cases. Could we ultimately end up wrong about that? Sure. But only time will tell. Read our blog post about the change.