> 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/rewst-documentation/documentation/integrations/integration-guides/cork-integration.md).

# Cork integration

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

## What does the Cork integration do?

Our Cork integration connects Rewst’s automation engine with Cork’s cyber risk management platform, enabling MSPs to streamline compliance event tracking, billing reconciliation, security remediation, and endpoint hygiene monitoring. By automatically logging, analyzing, and responding to compliance incidents and security gaps, this integration strengthens security posture, enhances operational efficiency, and supports proactive risk management.

## Set up the Cork integration

### Set up steps in Cork

{% hint style="warning" %}
Cork's requirements for their API keys set them to expire every 180 days. We recommend setting up a reminder to create a new key and update it on your Cork integration's configuration page.
{% endhint %}

1. Log in to your Cork Portal.
2. Navigate to **Admin > API Keys**.
3. Click **Add API Key**.
4. Enter Rewst or a similar name that will describe what the API key is for into the **Display Name** field.&#x20;
5. Leave the value in the **Expiry Days** drop-down selector at 180 days.
6. Click **Generate API Key**.
7. Copy the key and store it somewhere secure. Note that you won't be able to return to this key to copy or view it again.

### Set up steps in Rewst

1. Navigate to **Integrations** in the left side menu of your Rewst platform.
2. Search for `Cork` in the integrations page.
3. Click on the integration tile to launch the configuration setup dialog.
4. Choose from either Production or Demo Mode for the setup of your integration:
   1. **Production**: Connect with real credentials for live data
   2. **Demo Mode**: Explore the integration with simulated mock responses
5. Click **Next: Configure and Authenticate**.
6. Select **+ Create New Credential from the Credential** drop-down selector.
7. Enter the **API Key** copied from Cork into the relevant fields.
8. Click **Save Credential**.
9. Click **Next: Confirm**.
10. Click **Install Integration**. The integration will now appear in the top Connected section of your Integrations page.&#x20;
11. Click on the installed integration. Scroll down to the Org Mappings section of the configuration page and complete organization mapping as needed.&#x20;

{% hint style="success" %}
Got an idea for a new Integration? Rewst is constantly adding new integrations to our integrations page. Submit [feedback](https://docs.rewst.help/rewst-documentation/support-and-community/feedback.md) to let us know.&#x20;
{% endhint %}


---

# 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/rewst-documentation/documentation/integrations/integration-guides/cork-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.
