Email Thread Management for AI Agents

LobsterMail sets the correct In-Reply-To and References headers automatically. When your agent replies to an email, the reply appears in the same thread in the recipient's inbox. No manual header management.

Yes. The agent sends an initial email, waits for a reply using waitForEmail() with a threadId filter, processes the response, and replies in-thread. This loop can continue for as many turns as needed.

Call scheduleCheck() with a thread ID and a delay. If no new reply arrives in that thread before the timer fires, LobsterMail triggers your follow-up action — send a reminder, escalate, or whatever you define.

LobsterMail stores the full thread history. When a new reply arrives, your agent can read every previous message in the thread to generate a contextually appropriate response.

Yes. Each conversation has its own thread ID. The agent can have dozens of active threads across different inboxes, each tracked independently.

Two options: waitForEmail() with a threadId filter for synchronous polling, or set up a webhook that fires when a new message arrives in a specific thread. Both work.

waitForEmail() accepts a timeout. If no reply arrives, the promise rejects and your agent can decide what to do — send a follow-up, escalate, or close the thread.

Yes. LobsterMail uses standard email threading headers (In-Reply-To, References). Replies show up as threaded conversations in Gmail, Outlook, Apple Mail, and any other standards-compliant client.

Yes. Send a new email with a different subject line and no threadId reference. The recipient gets a new conversation. Useful when the topic shifts and you want a clean thread.

Yes. Threading works on all plans. Free accounts can send up to 50 emails per month, which includes replies in threads.