MCP

schemas/followup

The Followup object returned by sequence/get_followups_by_id, sequence/post_followups_by_id, followup/get_by_id, and followup/patch_by_id.

A followup is one automated email inside a sequence (see schemas/sequence), sent after its own wait period and carrying its own delivery and engagement counters.

field type constraints description
followupId integer int64 Unique identifier.
sequenceId integer int64 Sequence this followup belongs to.
subject string max 1024 Subject line for this followup.
body string HTML email body. In a list response, a body over 1,500 characters arrives as a plain-text preview unless you pass fullBodies: true — see schemas/pagination.
waitMin integer 1–1000 Wait duration before this followup sends.
waitUnits string one of: Minutes, Hours, Days Unit waitMin is counted in.
useOriginalSubject boolean Use the campaign's subject instead of this followup's own.
sendInSameThread boolean Send as a reply in the same email thread as the initial email.
replyInThread boolean Reply as a thread to the original conversation.
replyInThreadToFollowupId integer int64 Earlier followup this one replies to within the thread.
sentCount integer Times this followup was sent.
openCount integer Times this followup was opened.
clickCount integer Link clicks in this followup.
bounceCount integer Bounces received for this followup.
interestedCount integer Prospects marked Interested from this followup.
replyCount integer Replies received to this followup.

The six counters are cumulative, scoped to this followup alone, and 0 on a newly created one — they are the per-step breakdown of a campaign's totals. To reach the individual messages behind one step, filter message/get by followupId. Single-followup responses (create / get-by-id / update) may omit bounceCount and replyInThread; the list operation returns them.