> 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/~/revisions/oox5xThRKRJizwPMPxvl/documentation/configuration/integrations/custom-integrations.md).

# Custom integrations

## Introduction 

*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, enhancing automation and efficiency within your operations. 

{% 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? 

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

## How to use custom integrations 

To understand how to create a custom integration in Rewst, check out the walkthrough on the page for more information.

{% tabs %}
{% tab title="Supported authorization schemas" %}

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

{% tab title="Supported pagination schemas" %}

* None 
* Index 
* Page 
* Link 
* Pointer  
  {% endtab %}
  {% endtabs %}

## Edit and manage integrations 

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

* Change the visibility status of the integration (Hidden or Published). 
* Modify existing actions or add new actions or mark them as deprecated. 
* Delete the integration (Note: The integration must be uninstalled from all sub-organizations first). 

## Use custom integrations in workflows 

After creating and configuring your integration, you can use it in workflows by adding actions from your custom integration to the workflow.  


---

# 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 dynamically by asking a question.

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

```
GET https://docs.rewst.help/~/revisions/oox5xThRKRJizwPMPxvl/documentation/configuration/integrations/custom-integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.