> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/tutorials/ide-or-workflow-designer.md).

# IDE or Workflow Designer

Building Collibra workflows involves two distinct activities that call for different tools. Knowing which tool to use for each prevents confusion and leads to better, more maintainable workflows.

## Writing Groovy scripts: use an external IDE

Use an external IDE such as IntelliJ IDEA or Eclipse to write and test the Groovy code for your script tasks. Once the code is ready, copy it into the script task in the Workflow Designer.

For setup instructions and a full list of advantages, see [Future-proof your script tasks](/tutorials/future-proof-your-script-tasks.md#use-an-external-ide-for-groovy-script-development).

{% hint style="warning" %}
Do not use the Flowable Eclipse plugin to design workflow processes. Eclipse is a tool for writing Groovy code, not for designing processes — this is a common source of confusion.
{% endhint %}

## Designing processes and forms: use the Workflow Designer

Use the Workflow Designer to build and configure workflow processes and forms. Several capabilities are only available there:

* **External API task**: make calls to external systems.
* **Collibra API task**: make calls to the Collibra REST API without writing Groovy code.
* **Dynamic forms**: create forms whose fields and behavior adapt based on user input or workflow state.


---

# 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://developer.collibra.com/tutorials/ide-or-workflow-designer.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.