> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://knowledge.buildagil.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Process Automation Using Various Tools

* [Benefits of Integration with Automation Platforms](#3-benefits-of-integration-with-automation-platforms)
* [Creating Custom Triggers & Actions](#3-creating-custom-triggers-actions)
* [Terms of Use](#3-terms-of-use)

||| This feature is a preview version. Therefore, it may not behave as expected, or it may change before its general release.

### Benefits of Integration with Automation Platforms
In addition to [Microsoft Power Automate](/en/article/process-automation-with-power-automate-cvud94/), buildagil can be used with various automation platforms such as [N8n](https://n8n.io), [Make](https://www.make.com), [Zapier](https://zapier.com) or [Workato](https://www.workato.com). This enables the automation of workflows within buildagil as well as between buildagil and third-party systems, without requiring any programming knowledge. Flows can react to changes in buildagil in an event-driven manner as soon as they occur. Additionally, actions can be executed within buildagil, such as creating or updating tasks and documents. Typical use cases include automatically moving documents based on their status, automatically categorizing items based on their content, or forwarding information to third-party systems when items are created or modified in buildagil. The available triggers and actions correspond to the capabilities of [Buildagil openCDE API](/en/article/buildagil-opencde-api-odul8z/).

> n8n, Make, Zapier, Workato, automation platform, alternative to Power Automate, workflow automation, iPaaS, no-code integration, event-based triggers, connect third-party systems, connect buildagil with other tools, openCDE API
### Creating Custom Triggers & Actions
To connect an automation platform to buildagil, custom triggers and actions are created based on [Buildagil openCDE API](/en/article/buildagil-opencde-api-odul8z/). This allows workflows to access project data directly in buildagil. The terminology and procedures vary depending on the tool and are described in the documentation provided by the respective vendor.

Authentication is based on the OAuth 2.0 Authorization Code Flow described in [Buildagil openCDE API](/en/article/buildagil-opencde-api-odul8z/).

| To obtain the client ID and client secret, please contact Support. Finally, after creating a custom trigger, you must provide Support with the redirect URL displayed by the tool so that it can be stored.

| We cannot provide support for the setup and use of individual automation platforms.

> custom trigger, custom action, custom connector, OAuth 2.0 authorization code flow, client ID, client secret, token URL, redirect URL, request access credentials from support, support for third-party tools, set up connection
### Terms of Use
The Terms of Use for [Buildagil openCDE API](/en/article/buildagil-opencde-api-odul8z/) apply.