> For the complete documentation index, see [llms.txt](https://docs.ebbot.ai/ebbot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations.md).
# Automations Integrations
## What are Integrations in Automations?
Integrations are the core of the Automations platform. They provide the "building blocks" (Triggers and Actions) that allow you to connect different services and automate your business processes.
**Crucial First Step**: You cannot build workflows until you have installed and connected at least one integration. These integrations populate your toolbox in the workflow builder.
## Automations Integration Setup Guides
For available integration setup guides, click below.
{% content-ref url="/pages/yZDbNVk5YgCQkRuqeVga" %}
[Integration Setup Guides](/ebbot-docs/integrations/automations-integrations/integration-setup-guides.md)
{% endcontent-ref %}
## What do Integrations add?
Each integration expands the capabilities of the platform by adding:
* **Triggers:** Events that can start a workflow (e.g., "New Zendesk ticket", "Email received").
* **Actions:** Tasks the workflow can perform (e.g., "Post a reply", "Update ticket status", "Send a notification").
The more integrations you connect, the more powerful and flexible your automations become.
## Create a connection in Automations
When you connect an integration (like Zendesk or TOPdesk), the system asks for information such as a **Base URL** and **Authentication** details.
This is necessary because:
1. **Secure access**: The platform acts as an authorized agent on your behalf. To read data or perform actions, it needs valid credentials for your specific system instance.
2. **Environment targeting**: Most systems have multiple environments. The **Base URL** tells our system exactly where your data lives.
3. **Permission control**: You control exactly what the automation is allowed to see and do by managing the permissions of the connected account.
To connect a new system, navigate to the Integrations page in Automations and follow the connection prompts for your chosen service.
## What integrations are available in Automations?
To see what integrations that are available and that you can connect to, visit the Automations platform and navigate to the [Integrations page](https://automations.ebbot.eu/apps).
## Is it possible to build an integration and use it in Automations?
Yes, get started with building so called Workflow servers to connect to your service operations systems and design workflows that automates your processes.
{% content-ref url="/pages/BQBCNWr83nmaDN8Chhiy" %}
[Integrations SDK](/ebbot-docs/developer-resources/ebbot-automations/integrations-sdk.md)
{% endcontent-ref %}
\
---
# 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.ebbot.ai/ebbot-docs/integrations/automations-integrations.md?ask=&goal=
```
`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.