# Custom integrations

*Custom integrations* allow Rewst users to build their own integrations tailored specifically to their organization's needs. Integrate workflows with any service that exposes an API, even if Rewst doesn't currently have a native integration with that vendor.

{% hint style="warning" %}
Currently, there is documentation for both V1 and V2 of Rewst's custom integrations on this site. All new custom integrations should be set up using the method for V2. V1 documentation remains to assist existing customers with their migration from V1 to V2.
{% endhint %}

## Why use custom integrations? 

* Build integrations that are perfectly tailored to your unique automations requirements. 
* Custom integration supports both modern and legacy APIs by accepting Swagger, [OpenAPI specifications](https://www.openapis.org/), or allowing you to build your own integration from scratch. 
* Automatically generate actions from API definitions, which can be used in workflows without manual coding. 
* Manage who in your organization or in sub-organizations can see and use the integrations. 
* Easily manage the lifecycle of your integrations with statuses like draft, published, deprecated, and hidden. 

## How to use custom integrations 

### Enable custom integrations in your Rewst instance

{% hint style="info" %}
Custom integrations can only be enabled by users with the Rewst Admin role. 
{% endhint %}

1. Navigate to **Settings > Feature Preview** in the right side menu of your Rewst platform.
2. Click **Custom Integrations V2.**
3. Click **Enable**. A green confirmation message will appear at the top of your screen.
4. Whenever you wish, you may click **Disable** to turn off the custom integrations functionality for your instance, from this same menu.

<figure><img src="https://1835401289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQQ1EHVcEsGKBPVHmiav%2Fuploads%2FucBCyNuqNyp4MLQvrpRK%2FScreenshot%202026-03-06%20at%2010.12.13%E2%80%AFAM.png?alt=media&#x26;token=d9215642-95bc-4d52-9aee-456bd47cfdd0" alt=""><figcaption></figcaption></figure>

### Supported schemas

{% tabs %}
{% tab title="Supported authorization schemas" %}
{% hint style="info" %}
An *authorization schema* defines the rules, methods, and structures for controlling user access to resources, determining who can do what, after authentication confirms their identity. It's a system that dictates access rights, ensuring users only see or interact with what they're allowed, such as a department report page intended only for admins.&#x20;
{% endhint %}

* None&#x20;
* API key&#x20;
* Basic authorization&#x20;
* OAuth 2.0 with the following grant types&#x20;
* Client Credentials&#x20;
* Authorization code&#x20;
* No grant type&#x20;
  {% endtab %}

{% tab title="Supported pagination schemas" %}
{% hint style="info" %}
A *pagination schema* defines how large datasets are broken into smaller, manageable chunks- usually pages- for display, managing the data structure and communication between front-end and back-end, ensuring efficient loading, better user experience, and improved performance by limiting server strain and response times. It's a convention for requesting, processing, and delivering subsets of data, rather than the whole set at once.&#x20;
{% endhint %}

* None&#x20;
* Index&#x20;
* Page&#x20;
* Link&#x20;
* Pointer &#x20;
  {% endtab %}
  {% endtabs %}

## Edit and manage integrations&#x20;

Once an integration is created, you can edit it by navigating to the integration's detail page. Here, you can:&#x20;

* Change the visibility status of the integration - **Hidden** or **Published**.&#x20;
* Modify existing actions or add new actions or mark them as deprecated.&#x20;
* Delete the integration - note that the integration must be uninstalled from all sub-organizations first.&#x20;

## Use custom integrations in workflows&#x20;

Once your custom integration is set up, you can use it in your workflows and tasks using the `Custom API Request` action. You select which custom integration configuration to use for a workflow using `Integration Overrides`, which is covered in more detail in our documentation on [multi-instance](https://docs.rewst.help/documentation/integrations/multi-instance-integration) integration.

{% columns %}
{% column %}

<figure><img src="https://1835401289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQQ1EHVcEsGKBPVHmiav%2Fuploads%2Fgit-blob-c4b81d026add88b1272cb37cb9a54328f79c19a4%2Fcustom-integrations-action.png?alt=media" alt=""><figcaption></figcaption></figure>

{% endcolumn %}

{% column %}

<figure><img src="https://1835401289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQQ1EHVcEsGKBPVHmiav%2Fuploads%2FTA4YHXw4iexJOtZP8loa%2Fimage.png?alt=media&#x26;token=a86cabc9-4137-4e6f-8693-3bc97dfeba1b" alt=""><figcaption></figcaption></figure>

{% endcolumn %}
{% endcolumns %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.rewst.help/documentation/integrations/custom-integrations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.