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.
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.
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, 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
Custom integrations can only be enabled by users with the Rewst Admin role.
Navigate to Settings > Feature Preview in the right side menu of your Rewst platform.
Click Custom Integrations V2.
Click Enable. A green confirmation message will appear at the top of your screen.
Whenever you wish, you may click Disable to turn off the custom integrations functionality for your instance, from this same menu.
Supported schemas
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.
None
API key
Basic authorization
OAuth 2.0 with the following grant types
Client Credentials
Authorization code
No grant type
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.
None
Index
Page
Link
Pointer
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 that the integration must be uninstalled from all sub-organizations first.
Use custom integrations in workflows
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 integration.
Last updated
Was this helpful?