> 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/incoming-easit-item.md).

# Incoming Easit Item

**Trigger identifier:** `incoming_easit_item`.

Triggered when Easit GO sends data via export automation.

### Install the trigger

1. Create an [Easit connection](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/connection-setup.md).
2. Add the **Incoming Easit Item** trigger to a workflow, select the connection and save the workflow.
3. Open the trigger again. Automations now shows the setup steps below with the exact webhook URL for this connection.
4. Give those steps to the Easit administrator, who configures the export in Easit GO Design Studio.

### Setup in Easit GO Design Studio

The steps shown in Automations after saving the trigger:

Use **Export Configuration + Automation Rule (Objektregel)**:

1. Create an **Export configuration** for the target object type (JSON format). Map just two fields — not the ticket's content:

   * an identifying field (e.g. an external id) → property `eid`
   * Objekttyp → property `itemType`

   The internal id and ticket number are already part of Easit's export and need no mapping. The workflow reads subject, description, and everything else afterward over GraphQL using that id, so there is nothing else to add here.
2. Create an **Automation rule** → **Object rule (Objektregel)** that applies *after an object is saved*, on a field that's always set when a ticket is created (so it fires once per new ticket, not on every later edit).
3. Add the **Exportera objekt** function, type `REST/JSON`, and select the export configuration above.
4. Deliver it with `POST` to: `https://<easit-workflow-server>/webhooks/easit/<connection-id>`
5. This external trigger endpoint does not require Ebbot's server token. Do not configure that token on Easit's export sender.
6. Save, activate, and send one test event.

`https://<easit-workflow-server>` and `<connection-id>` stand for the values Automations fills in for your trigger.

### Output

Paths are relative to the trigger's `payload`. Select them from the builder's variable picker.

| Path               | Type            | Meaning                                                                           |
| ------------------ | --------------- | --------------------------------------------------------------------------------- |
| `data`             | object          | Original parsed Easit export body.                                                |
| `payload_format`   | string          | Format of the incoming payload, such as json or xml.                              |
| `item`             | object          | Normalized item identifiers; unavailable identifiers remain null.                 |
| `item.uid`         | string \| null  | Raw exported uid, when available.                                                 |
| `item.internal_id` | integer \| null | Internal numeric Item.id parsed from the export; use for GraphQL actions.         |
| `item.sequence_id` | integer \| null | Visible ticket number (Item.sequenceId), when available; not the GraphQL item id. |
| `item.external_id` | string \| null  | External id from the configured export mapping, when available.                   |
| `item.item_type`   | string \| null  | Exported item type, when available.                                               |

### Behavior and limits

Starts a workflow when Easit GO exports an item as JSON or XML. Save the workflow trigger first: Automations then shows the setup steps for the Easit administrator, including this connection's exact webhook URL.

An Easit administrator creates the export configuration and an Object Rule that delivers events to that URL. Exclude changes made by the workflow itself from the rule, or the workflow's own writes start new runs. Events are delivered only to workflows that use the same connection. Easit posts directly to the URL; it needs no Ebbot token.

The payload contains `data` (the original parsed export), `payload_format`, and normalized `item` identifiers:

* `item.internal_id` is the numeric GraphQL `Item.id`, parsed from an internal id such as `8708:2`. Map this into the **Item Id** of every GraphQL action.
* `item.sequence_id` is the visible ticket number. Do not use it as an Item Id: Easit then reads or writes whichever item happens to have that internal id, often a contact or another ticket. Use it in messages to people, or resolve it with **Find Easit Item by Ticket Number**.

Identifiers remain null when the export does not contain them. The export carries identifiers only; read the subject, description and other fields with **Get Easit Item (GraphQL)**.

Exports larger than 1 MiB are rejected. The webhook does not verify a signature from Easit. Test with one disposable ticket and confirm a single run before enabling broader rules.

See [Troubleshooting](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/troubleshooting.md), or return to the [integration overview](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations.md).
