> 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/integration-setup-guides/easit-integration-in-automations/connection-setup.md).

# Connect Easit GO

Create one connection per Easit environment (for example, test and production). The connection stores the Easit address, the API token and optional mail field mapping used by every action and trigger.

### Connection fields

| Field                                      | Kind    | Required | Meaning                                                                                                                          |
| ------------------------------------------ | ------- | -------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Base URL (`base_url`)                      | Setting | Yes      | Easit tenant host or Integration API URL, for example <https://tenant.easit.net/integration-api>                                 |
| Module system name (`module_system_name`)  | Setting | No       | Leave as Request for normal tickets/Ärende. Change it only when your Easit administrator gives you another module's system name. |
| Module ID (advanced) (`module_id`)         | Setting | No       | Leave empty. Only use a numeric override supplied by your Easit administrator if automatic module discovery does not work.       |
| Mail body field (`mail_body_field`)        | Setting | No       | System name supplied by Easit for the outgoing email-body field. Required for Send Easit Email.                                  |
| Mail from field (`mail_from_field`)        | Setting | No       | System name supplied by Easit for the sender-address field                                                                       |
| Mail to field (`mail_to_field`)            | Setting | No       | System name supplied by Easit for the recipient-address field                                                                    |
| Mail Cc field (optional) (`mail_cc_field`) | Setting | No       | Optional system name supplied by Easit for the Cc field                                                                          |
| Mail subject field (`mail_subject_field`)  | Setting | No       | System name supplied by Easit for the email-subject field                                                                        |
| Mail trigger field (`mail_trigger_field`)  | Setting | No       | System name supplied by Easit for the date/time field that activates the customer's mail rule. Written last.                     |
| API Token (`api_token`)                    | Secret  | Yes      | API token supplied by your Easit administrator                                                                                   |

The API token is stored as a secret. Keep it out of prompts, node inputs and shared documentation.

### Create and check the connection

Ask your Easit administrator for the Easit address and an API token. They must enable GraphQL and give the token access to the ticket module and fields the workflow uses.

1. Enter the Easit address under **Base URL**.
2. Enter the token under **API Token**.
3. For normal tickets/Ärende, leave **Module system name** as `Request`.
4. Leave **Module ID (advanced)** empty. The integration discovers it automatically.
5. If you do not send email, leave all **Mail … field** boxes empty.
6. Save the connection.

To check the connection without leaving Automations, create or open a workflow, add **Set Easit Item Field**, select this connection, and open its **Field** list. A populated list confirms that Automations can read the configured Easit module. You can remove the action afterward without publishing the workflow.

### Email automations

Easit sends the email. Ask the Easit administrator to create the outgoing-mail fields and sending rule, then enter the system names they provide in the **Mail … field** boxes. **Send Easit Email** saves the content and updates the trigger field last. Customer replies require Email2GO or another inbound mail import configured in Easit.

### Permissions

Ask the Easit administrator to grant the API token only the capabilities used by the workflow: Integration API and enabled GraphQL access; read access to the configured module, items, fields, and data-source values; write access to target item fields for updates; message read/create access for message actions; access to configured Item Views and Import Handlers for legacy actions; and write access to mapped mail content and trigger fields for Send Easit Email. An administrator configures export rules, outgoing-mail rules, and inbound mail import separately. These are capability requirements, not verified Easit permission names; confirm the exact role and permission names in the customer's environment.

### Request volume

This server does not configure a tenant API quota. Confirm applicable limits with the Easit administrator. Field discovery can issue multiple requests while walking data sources; use List Easit Field Values when the field is already known. Retrying an email action can trigger another email.

Next: install the [Incoming Easit Item](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/incoming-easit-item.md) trigger, or browse the [action reference](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions.md).
