Skip to the documentation
TypeScript

openemail.followUps

Every method in this namespace: its signature, its parameters, what it returns and an example.

Methods

Reminders on mail you sent: ask for a thread to come back to the top of the inbox if nobody replies by a time you choose, list the reminders still waiting and the ones that ended, and cancel one.

followUps.list()

List reminders

Scopesthreads:read
Signature
list(options?: FollowUpListOptions): Promise<Array<FollowUpResource>>

Resolves the reminders you set on mail you sent, newest first: the ones still waiting for a reply and the ones that ended. A reminder is waiting until somebody replies (answered), its time comes with no reply (due, and the thread is back at the top of the inbox, unread) or it is cancelled.

An API key lists the reminders of the workspace owner, and an app those of the person who connected it. A key or an app limited to particular addresses lists only reminders on threads delivered to them. They come back as one plain array with no paging, and limit caps how many.

Parameters

options.statusFollowUpStatus

Only reminders in this state: waiting, answered, due or cancelled.

options.threadIdstring

Only the reminders on this thread.

options.limitnumber

How many to return, newest first, from 1 to 200. 100 when left out.

options.signalAbortSignal

Cancels the request.

options.apiKeystring

Overrides the client's API key for this call only.

Returns

Array<FollowUpResource>, each { object: 'follow_up', id, threadId, messageId, emailId, subject, remindAt, status, answeredAt, firedAt, createdAt }. threadId is null until a scheduled message with a reminder goes out, emailId names the email when the reminder was set with followUpAt, answeredAt is null unless answered and firedAt is null unless due.

Example

const waiting = await openemail.followUps.list({ status: 'waiting' }) for (const reminder of waiting) console.log(reminder.subject, reminder.remindAt)

Notes

  • In query, is:waiting finds the same conversations through threads.list: the ones with a reminder nobody has answered yet.

  • Read only, so the SDK retries it after a network failure like any other read.

Also available in

API
GET /follow-ups
Python
follow_ups.list()
Ruby
follow_ups.list
PHP
followUps->list
Go
FollowUps.List
Java
followUps().list
C#
FollowUps.ListAsync
CLI
openemail follow-ups list

followUps.set()

Set a reminder on a thread

Scopesthreads:write
Signature
set(body: FollowUpSet, options?: RequestScope): Promise<FollowUpResource>

Asks to be reminded about a thread if nobody replies by remindAt. If a real reply arrives first, the reminder closes by itself. Otherwise, when the time comes, the thread returns to the top of the inbox, unread, with the built-in FOLLOW_UP label and a push to your phones. Automatic replies, delivery reports and your own sending address do not count as a reply.

A thread holds one waiting reminder per person, so setting another moves the time. remindAt takes a Date or an ISO 8601 string with an offset, and the SDK converts a Date with toISOString(). To set one as you send, pass followUpAt to emails.send instead.

Parameters

body.threadIdstringRequired

The thread to be reminded about, as threads.list returns it.

body.remindAtDate | stringRequired

When the thread comes back if nobody replied: a future instant, at most 365 days out.

options.signalAbortSignal

Cancels the request.

options.apiKeystring

Overrides the client's API key for this call only.

Returns

FollowUpResource, the reminder with status set to waiting: { object: 'follow_up', id, threadId, messageId, emailId, subject, remindAt, status, answeredAt, firedAt, createdAt }.

Example

const remindAt = new Date()remindAt.setUTCDate(remindAt.getUTCDate() + 3) const reminder = await openemail.followUps.set({    threadId: 'CAHk7pQ2x9LmZ4-mail.example.com',    remindAt}) console.log(reminder.id, reminder.status, reminder.remindAt)

Notes

  • A remindAt that is not in the future, or is more than 365 days out, is a 422 invalid_follow_up. A thread that does not exist, or one delivered to no address the key covers, is a 404.

  • An API key sets the reminder for the workspace owner, and an app for the person who connected it. The push goes out unless that person turned phoneFollowUps off in settings.

  • The SDK retries this call after a network failure, which is safe because setting the same time twice leaves one reminder.

Also available in

API
POST /follow-ups
Python
follow_ups.set()
Ruby
follow_ups.set
PHP
followUps->set
Go
FollowUps.Set
Java
followUps().set
C#
FollowUps.SetAsync
CLI
openemail follow-ups set

followUps.cancel()

Cancel a reminder

Scopesthreads:write
Signature
cancel(id: string, options?: RequestScope): Promise<FollowUpResource>

Cancels a waiting reminder, so the thread stays where it is when the time comes. A reminder that already ended is returned as it is, which is why the SDK retries this call. Only your own reminders can be cancelled.

Parameters

idstringRequired

The id of the reminder, fup_ and 24 hex characters, as list returns it.

options.signalAbortSignal

Cancels the request.

options.apiKeystring

Overrides the client's API key for this call only.

Returns

FollowUpResource, the reminder as it is now: cancelled when it was waiting, and unchanged when it had already ended.

Example

const cancelled = await openemail.followUps.cancel('fup_4c1b257a9e3d6f8025b7c1d4') console.log(cancelled.status, cancelled.remindAt)

Notes

  • An unknown id, and a reminder somebody else set, are each a 404. So is one on a thread delivered to no address the key covers.

  • A cancelled reminder is kept, and list returns it with status set to cancelled.

Also available in

API
DELETE /follow-ups/{id}
Python
follow_ups.cancel()
Ruby
follow_ups.cancel
PHP
followUps->cancel
Go
FollowUps.Cancel
Java
followUps().cancel
C#
FollowUps.CancelAsync
CLI
openemail follow-ups cancel