Skip to main content
POST
/
api
/
follow-ups
Create Follow-up
curl --request POST \
  --url https://app.replyify.ai/api/follow-ups \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "due_at": "<string>",
  "contact_id": "<string>",
  "client_id": "<string>",
  "reply_id": "<string>",
  "action": "<string>",
  "notes": "<string>",
  "draft_message": "<string>"
}
'

Documentation Index

Fetch the complete documentation index at: https://docs.replyify.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Body Parameters

​
due_at
string
required
ISO 8601 scheduled send time. Must be in the future (at least 1 minute from now).
​
contact_id
string
required
The contact to send the follow-up to
​
client_id
string
required
The client account (used for AI context and connection routing)
​
reply_id
string
Link to an existing reply thread (optional for manually created follow-ups)
​
action
string
default:"follow_up_message"
Follow-up type: follow_up_message or linkedin_message
​
notes
string
Internal notes to guide AI generation. These are not sent to the contact.
​
draft_message
string
The email content to send. If omitted, AI will generate the message before the scheduled time.

​
Response

Returns the created follow-up object. 
curl -X POST "https://app.replyify.ai/api/follow-ups" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "contact_id": "contact_abc123",
    "client_id": "client_xyz789",
    "due_at": "2025-02-01T10:00:00Z",
    "notes": "Follow up on pricing discussion from last week",
    "action": "follow_up_message"
  }'
The due_at must be in the future. Creating follow-ups with past dates returns a 400 error.
If no draft_message is provided, AI will automatically generate the message before the scheduled send time. This consumes 1 AI credit for generation + 1 for sending = 2 credits total.