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

# Easit GO Integration in Automations

Connect Easit GO tickets to Ebbot Automations. The **Easit GO Workflow Server** provides the trigger and the actions your workflows use; prompts, conditions and knowledge retrieval are configured in Automations.

Use this guide to connect Easit, start workflows from Easit events, look up the exact input and output fields of each action, and build workflows that read tickets, suggest answers, set field values or send email.

### Start here

1. [Connect Easit GO](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/connection-setup.md): connection fields, API token permissions and a first check.
2. [Incoming Easit Item](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/incoming-easit-item.md): the export rule your Easit administrator sets up, and the trigger's output fields.
3. [Action reference](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions.md): all actions, with required fields, defaults, output paths and behavior.
4. [Workflow patterns](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/workflow-patterns.md): read a ticket, suggest a knowledge article, classify, reply by email.
5. [Troubleshooting](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/troubleshooting.md): no runs, wrong item, empty fields, failed writes and email delivery.

### How an Easit event becomes an action

Example: a workflow that suggests a knowledge article when a new ticket is created.

```mermaid
flowchart TD
    A["1. Easit GO: a ticket is saved"] -->|"Object rule exports the item"| B["2. Workflow Server: Incoming Easit Item receives the export"]
    B -->|"Start the workflow"| C["3. Automations: read the ticket, search knowledge, choose an article"]
    C -->|"Run Set Easit Item Field"| D["4. Workflow Server: write the field over GraphQL"]
    D --> E["5. Easit GO: the field shows the suggested article"]
```

**Easit GO** sends the event and stores the result. **Automations** runs the workflow you build and decides what should happen. The **Easit GO Workflow Server** provides the trigger that receives the export and the actions that read or write Easit data.

Step 3 is configured in your workflow: you choose its conditions, actions and any LLM or knowledge-retrieval nodes. Nothing is created automatically when you connect Easit.

A **connection** stores the Easit address, API token and optional mail field mapping. The **export rule** in Easit decides which events reach the trigger; your Easit administrator sets it up in Design Studio.

### Two ids: internal id and ticket number

Every Easit item has two numbers, and mixing them up is the most common setup error:

|                                  | Where you see it                                                | Use it for                                                                                                                                                                                                                                 |
| -------------------------------- | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Internal id** (`Item.id`)      | Trigger output `item.internal_id`; action output `item.id`      | The **Item Id** of every GraphQL action                                                                                                                                                                                                    |
| **Ticket number** (`sequenceId`) | Shown on the ticket in Easit; trigger output `item.sequence_id` | Messages to people; lookup with [Find Easit Item by Ticket Number](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions/find-item-by-ticket-number.md) |

Passing a ticket number as an Item Id does not fail with "not found" if some other item has that internal id. The action then reads or writes that other item, often a contact.

### Choose the right output

* [Get Easit Item (GraphQL)](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions/get-item-graphql.md) returns `item.subject`, `item.description`, every non-empty field in `item.field_values`, and `item.text`, all fields as lines ready for a prompt.
* Fixed-choice fields such as status, category and priority take the **data-source id**, not the label shown in Easit. The dropdowns in the action form show both; at runtime use [List Easit Field Values](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions/list-field-values.md).
* [Send Easit Email](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions/send-easit-email.md) is the only action that sends email, through a mail rule in the customer's Easit. [Record Easit Ticket Message (No Email)](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions/respond-to-ticket.md) adds a message to the ticket and sends nothing.
* Write actions return `success`. A run can show **Done** even when a write failed, so check `success` with a condition when later steps depend on it.

Select variables from the node output picker instead of typing a path. For classification or picking a value, use the LLM node's [structured output](https://docs.ebbot.ai/ebbot-docs/core-capabilities/automations/workflow-nodes/llm-nodes); see [Workflow patterns](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/workflow-patterns.md).

### For agents helping with a customer solution

Read the relevant action or trigger page before changing a node. Then open the customer's workflow and a real run: compare each node's actual input with what the reference says it expects, starting from the trigger. Field system names, module names, data-source ids and mail fields are specific to each Easit environment; never copy them from another customer.

Before adding writes, check which Easit events your own writes cause, so the export rule does not start the workflow again. Verify the destination ticket after a test, and keep the earlier flow version so a change can be reversed.

### Reference scope

The connection, trigger and action pages are generated from the Easit GO Workflow Server's own manifest, so they list exactly the fields the server exposes. This overview, the workflow patterns and the troubleshooting guide were reviewed against the server on **4 November 2026**. If an action or field is missing in your installed integration, ask Ebbot to confirm the server version before building around it.

General product guidance: [Understanding Workflows](https://docs.ebbot.ai/ebbot-docs/core-capabilities/automations/understanding-workflows), [LLM Nodes](https://docs.ebbot.ai/ebbot-docs/core-capabilities/automations/workflow-nodes/llm-nodes), [Condition Nodes](https://docs.ebbot.ai/ebbot-docs/core-capabilities/automations/workflow-nodes/condition-nodes) and [Dashboard and Monitoring](https://docs.ebbot.ai/ebbot-docs/core-capabilities/automations/dashboard-and-monitoring).
