Feedbucket can deeply integrate with Shortcut. That means that your team should be able to manage all feedback inside of Shortcut instead of in the Feedbucket Admin.

Install the Shortcut integration on your Feedbucket project

1. Go to your project and then click the tab Integrations.
2. On the integrations page click the button Connect next to Shortcut logo as show in the image below.

3. If this is the first time you are connecting Feedbucket and Shortcut, you will be prompted to enter your Shortcut API-token. You can create an API token by going to this link. If that doesn't work, you can find detailed information at the Shortcut documentation. Enter your API token into Feedbucket and click Save as in the image below:

4. You will now see a green bar on the Shortcut integration that indicates that the connection is made. The settings should have opened automatically but in case it doesn't, click on the Settings button to start configuring the Shortcut connection for this project.

Configure the Shortcut integration to your needs

Most often, you will create one Feedbucket project per client website you are building. That way you can connect each project to a specific Epic inside of Shortcut as well. It's up to you how you want to configure it.

After you connect you should see the configuration pop-up. If you don't, just click on the Open Settings button.

1. Select the Epic. Each story that Feedbucket creates needs to belong to an Epic.
2. Select the Workflow. Select the Workflow that should be used by Feedbucket.
3. Select the open state. This is the state that the story will have when it initially gets created by Feedbucket in Shortcut.
4. Optionally, you can select labels that the story created by Feedbucket will have.
5. If you want to have a 2-way sync between Feedbucket and Shortcut you will have to create a webhook inside of the Shortcut UI. Please refer to the Shortcut webhooks documentation to see how you can do this. The URL in this field should go into the Payload URL field in Shortcut when you create the webhook.
6. The webhook secret for this project. This field should be inserted into the Secret field in Shortcut when creating the webhook.

How to use the Shortcut integration

Once you have configured everything as you wish, below is how the integration should behave.

When new feedback is created

Whenever a new piece of feedback is created in Feedbucket, a story will be created inside of Shortcut. This story will belong to the Epic selected in #1 and use the workflow selected in #2 and be opened with the state selected in #3. The story will automatically have all of the technical details that Feedbucket collected like the session information of the reporter, the screenshot/recording etc.

If you selected any labels in #4 the story will also automatically have those set.

When a new comment is created on feedback

A piece of feedback can have lots of comments as a thread to communicate and collaborate. When a new comment is created on a piece of feedback that has been created in Shortcut by Feedbucket, that comment will also be created inside of Shortcut under the correct story. That way, all comments that happens in Feedbucket will automatically be pushed to Shortcut as well.

If you have set up webhooks the real power lies in the two-way communication here. If your team needs to ask a follow-up question that can be done without leaving Shortcut. All you have to do is to add a new comment that starts with @feedbucket and it will automatically be pushed over to Feedbucket and notify the client of this new comment from you. Regular comments submitted without the prefix of feedbucket will not sync over so you can continue to keep your internal conversations flowing in Shortcut.

When the feedback is resolved

If the feedback gets resolved from Feedbucket, the story will automatically be set to the first state of type done of the workflow configured in step #2.

There's a 2-way sync here as well if webhooks has been set up. If you change the state of the story to one of type done, it will be resolved in Feedbucket. If you archive the story, the feedback will also be resolved in Feedbucket.

When the feedback is re-opened

If the feedback gets unresolved from Feedbucket, the story's state will change to what you selected as Open state in step #3 when configuring.

There's a 2-way sync here as well if webhooks are set up properly. If you change the state of the story from one with type done to another state, the feedback in Feedbucket will be unresolved.

FAQ

Do I need to create one API token per project?

No, you only need to enter the API token once. When that is saved in Feedbucket, the same token will be used for all your Shortcut connections.

2-way sync does not work. What can I do?

Make sure that you have created the webhook as in step #5 and #6 when configuring Feedbucket. If it still doesn't work. Please reach out to support.

Do I need to create one webhook for each project?

Yes, you do. This is so Feedbucket can keep track of the different webhooks coming from Shortcut.

How to disconnect the Shortcut integration

When the Shortcut integration is active you will see a button for Disconnect. Click this to disconnect your Shortcut integration with this project.

Updated on: 13/01/2026