For the complete documentation index, see llms.txt. This page is also available as Markdown.

Record Easit Ticket Message (No Email)

Record a message on an Easit GO ticket: resolves an approved requester-email field, creates a styled message, and tags it for loop protection. This does NOT send email - Easit has confirmed createMessages cannot deliver mail. Use Send Easit Email for outbound mail; use this for an agent-visible thread entry.

Action identifier: respond_to_ticket.

Inputs

Field
Type
Required/default
Meaning

item_id

integer

Required

Internal Easit item id (the ticket)

from_address

string

Required

Sender email address

subject

string

Required

Reply subject

body_html

string | null

null

HTML reply body (styled)

body_plain

string | null

null

Plain-text reply body

state

string

"DRAFT"

Message state recorded on the item; no state sends email

to

array of strings | null

null

Explicit recipients; if empty, resolved from ticket fields

cc

array of strings | null

null

CC email addresses

recipient_field_keys

array of strings | null

null

Approved item field keys containing requester email

message_setting_identifier

string | null

null

Optional message metadata; does not cause delivery

ai_tag

string

"ai-generated"

Tag added to outgoing message for AI loop-protection

extra_tags

array of strings | null

null

Additional message tags

add_thread_marker

boolean

true

Prepend Easit thread token so replies route back to this ticket

Example input:

{
  "add_thread_marker": true,
  "ai_tag": "ai-generated",
  "body_html": "<p>Hi, here is our answer.</p>",
  "extra_tags": [],
  "from_address": "support@example.com",
  "item_id": 8708,
  "message_setting_identifier": null,
  "recipient_field_keys": [],
  "state": "DRAFT",
  "subject": "Re: your request",
  "to": []
}

Output

Paths are relative to this action's output. Select them from the builder's variable picker rather than typing them. A field that is null or empty was not returned by Easit; it is not proof that the value is empty in Easit.

Path
Type
Meaning

success

boolean

Whether the requested operation completed successfully.

item_id

integer

Internal numeric Easit Item.id used by GraphQL actions.

message_ids

array of integers

Ids of the recorded thread messages; empty on failure.

resolved_to

array of strings

Recipient addresses supplied or resolved from the ticket.

state

string

Requested message state; no state causes email delivery.

error

string | null

Failure details when the operation did not succeed; otherwise null.

Behavior and limits

Records a tagged message on the ticket using GraphQL createMessages. It cannot send email in any Easit environment, regardless of state. Use Send Easit Email for delivery.

Supply internal numeric item_id, from_address, subject, and at least one of body_plain or body_html. Optional to and cc hold address lists. With no to, recipients are read from the ticket; recipient_field_keys overrides the fields searched.

The default state is DRAFT. Optional message_setting_identifier is tenant-specific. ai_tag defaults to ai-generated; extra_tags adds tags. add_thread_marker defaults to true and prepends the ticket's Easit thread marker to the subject when available. These tags do not prevent loops caused by the separate email field-update path.

Returns success, item_id, created message_ids, resolved_to, state, and an optional error. A missing or unreadable ticket returns a structured failure. No message is created if the prerequisite read fails.

See Troubleshooting, or return to the action catalog.

Was this helpful?