CC Gent on an existing thread workflow

Token first

Make sure the agent has these scopes.

Create a new token or update the agent's current token before trying the calls below.

Required token scopes

email:read labels:write tasks:write files:write workflows:write

Outcome

What this gives you.

A copied thread can create labels, tasks, files, reminders, and webhook events while the human conversation stays where it already is.

Use when

The operational shape.

A client, vendor, approver, or internal stakeholder already started the conversation elsewhere.
You want Gent to track work, files, and follow-up without becoming the main sender or recipient.
You need a low-friction way to test an agent inbox on one recurring thread type before moving to a dedicated address.

API path

The calls to make.

01

Receive the copied message

GET/v1/messages/{message_id}/

After the Gent address is added to To or CC, fetch the received copy with sender, recipients, subject, labels, attachments, and thread context.

Client follow-up

Copy the project or client Gent inbox when a client promises a file, answer, or approval later.

To: client@example.com
Cc: project@your-domain.example
Subject: Re: Launch checklist

Vendor intake

Copy the finance or vendor Gent inbox when a vendor sends an invoice, renewal, document, or missing-detail thread.

To: vendor@example.com
Cc: finance@your-domain.example
Subject: Re: July invoice

02

Review the thread workspace

GET/v1/messages/threads/{thread_id}/workspace/

Use the composed thread workspace when the UI or an API client needs participants, labels, attachments, notes, ticket state, and suggested next actions in one read model.

03

Create a label or task rule

POST/v1/workflows/

Match copied mail by recipient, sender, subject, attachment state, or label, then create tracked work.

Default example

Start deterministic: recipient, sender, subject, attachment state, and existing labels are easier to verify than broad semantic matching.

{
  "name": "Track copied client requests",
  "trigger": "email_received",
  "conditions": [
    {"field": "to_or_cc", "op": "contains", "value": "project@your-domain.example"},
    {"field": "subject", "op": "contains", "value": "checklist"}
  ],
  "writes": [
    {"source": {"from": "trigger.email"}, "target": {"type": "email.add_label", "label_id": "lbl_client_request"}},
    {"source": {"from": "trigger.email"}, "target": {"type": "task"}, "contract": {"required": ["summary", "due_at"]}}
  ]
}

Save attachments to Files

Use this when copied threads often contain invoices, forms, screenshots, or documents that should become durable Files records.

{
  "name": "Save copied-thread attachments",
  "trigger": "email_received",
  "conditions": [
    {"field": "has_attachments", "op": "eq", "value": true},
    {"field": "to_or_cc", "op": "contains", "value": "finance@your-domain.example"}
  ],
  "writes": [
    {"source": {"from": "trigger.attachments"}, "target": {"type": "files.save_to_folder", "folder_id": "fld_vendor_intake"}}
  ]
}

Send a webhook

Use this when another system owns the next step but should receive a durable Gent message ID.

{
  "name": "Notify ops on copied request",
  "trigger": "email_received",
  "conditions": [
    {"field": "to_or_cc", "op": "contains", "value": "ops@your-domain.example"}
  ],
  "writes": [
    {"source": {"from": "event.payload"}, "target": {"type": "webhook", "url": "https://example.com/webhooks/copied-thread", "event_type": "workflow.cc_thread_received"}}
  ]
}

04

Review generated work

GET/v1/agenda/

Use Agenda, Labels, Contacts, Tasks, or Files to review the work created from copied threads.

Controls

Review points.

Gent should treat the real sender and recipients as the relationship context; the Gent mailbox is the workflow observer.
Use this pattern for visible participation, not hidden surveillance. The Gent address appears on the thread.
Outbound responses remain drafts or review records until sending is enabled for the inbox.

Messages Workflow rules Labels Tasks

Menu

CC Gent on an existing thread.