> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/integrations/integration-guides/crushbank-integration.md).

# CrushBank integration

{% hint style="info" %}
If you’re new to integrations in Rewst, read through our introductory integration documentation [here](https://docs.rewst.help/documentation/integrations).
{% endhint %}

## What does the CrushBank integration do?

Our CrushBank integration enables the automation of ticket categorization and prioritization analysis. Use the CrushBank API within Rewst workflows to automate tasks such as analyzing ticket text for sentiment and prioritization and document enrichment.

## Set up the CrushBank integration

### Set up steps in CrushBank

1. Log in to your [CrushBank account](https://app.crushbank.com/)
2. Navigate to the **Admin** tab.
3. Locate your Client ID and Client Secret in the Company Info section. Copy the values and store them somewhere secure. You'll need this information for further steps in Rewst.

<figure><img src="https://1835401289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQQ1EHVcEsGKBPVHmiav%2Fuploads%2FTT298jQJFffm9BUmafnA%2FScreenshot%202025-06-30%20at%204.11.12%E2%80%AFPM.png?alt=media&amp;token=0a5ad8e5-f5d1-4650-9971-d697083e13fb" alt="A view of the admin menu in the Crushbank portal: a grey screen with white text and fields,. The ones highlited are the Client ID field and the Client Secret field."><figcaption></figcaption></figure>

### Set up steps in Rewst

1. Navigate to **Marketplace > Integrations** in the left side menu of your Rewst platform.
2. Search for `CrushBank` in the integrations page.\
   \
   ![](https://1835401289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQQ1EHVcEsGKBPVHmiav%2Fuploads%2FmOccX3qeH6k8R3ZpDC3N%2FScreenshot%202025-06-30%20at%203.40.49%E2%80%AFPM.png?alt=media\&token=9d31d238-b248-48b3-aab3-d2008c04bb7c)
3. Click on the integration tile to launch the configuration setup page.
4. Under **Parameters**, enter the information copied from Crushbank into the relevant fields.
5. Click **Save Configuration**.

{% hint style="success" %}
Got an idea for a new Integration? Rewst is constantly adding new integrations to our integrations page. Submit your idea or upvote existing ideas here in our [Canny feedback collector](https://rewst.canny.io/integrations).
{% endhint %}

## Actions and endpoints

{% hint style="info" %}
For more on how actions work in Rewst, check out our [introductory actions documentation here](https://docs.rewst.help/documentation/workflows/actions-in-rewst).
{% endhint %}

| Category            | Action                | Description                                                                |
| ------------------- | --------------------- | -------------------------------------------------------------------------- |
| **Analyze**         | Analyze               | Analyze text for categorization and prioritization using CrushBank's AI    |
| **Generic Request** | CrushBank API Request | Generic action for making authenticated requests against the CrushBank API |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rewst.help/documentation/integrations/integration-guides/crushbank-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
