> 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.