NudgeForMe
Home/Blog/Guide
THE NUDGEFORME JOURNAL ✳

Email Follow-Up API: Find Unanswered Threads and Create Drafts

A developer guide to turning an already-sent unanswered email into a reviewable follow-up draft through the NudgeForMe REST API.

An email follow-up API can mean different things. Some services send bulk outreach; others expose data about conversations already in your mailbox. NudgeForMe's developer API is in the second group: it helps you discover existing sent conversations, start monitoring an eligible thread and create a follow-up draft. The API does not send email.

This tutorial uses real documented endpoints. It is intended for an integration developer working on an authorized account, not for scraping other people's inboxes.

Before you begin

Connect Gmail, Microsoft 365 / Outlook or another supported mailbox to NudgeForMe. Keep the mailbox in Draft mode for external draft-creation workflows. In Settings → Developer API, create a scoped key with permissions needed for the operation. Keep that key server-side.

The Global REST base URL is https://app.nudgeforme.com/api/v1; EU accounts use https://europe.nudgeforme.com/api/v1. A developer key is used as Authorization: Bearer YOUR_KEY. The remote MCP interface uses OAuth instead of developer keys.

See the authentication guide and API quickstart.

Step 1: Find the connected mailbox

Call the mailbox endpoint using a key with nudge.mailboxes.read:

curl 'https://app.nudgeforme.com/api/v1/mailboxes' \
  -H 'Authorization: Bearer YOUR_KEY'

Select the mailbox you intend to inspect. If you manage multiple workspaces or clients, enforce workspace boundaries at the key and application layers.

Step 2: Search conversations you previously sent

Once you know mailboxId, search an existing conversation:

curl -G 'https://app.nudgeforme.com/api/v1/conversations' \
  -H 'Authorization: Bearer YOUR_KEY' \
  --data-urlencode 'mailboxId=MAILBOX_ID' \
  --data-urlencode 'search=proposal'

Inspect the results to confirm the recipient, conversation and next step. Do not infer that every unreplied message deserves a follow-up. A sent thread may be resolved off-email, deferred or intentionally left open.

Step 3: Watch the selected thread

When you have an appropriate providerThreadId for an already-sent conversation, add it to monitoring with a stable idempotency identifier:

curl -X POST 'https://app.nudgeforme.com/api/v1/conversations/watch' \
  -H 'Authorization: Bearer YOUR_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: watch-proposal-20261111-001' \
  -d '{"mailboxId":"MAILBOX_ID","providerThreadId":"PROVIDER_THREAD_ID"}'

Important: the Nudge watched threadId returned by this call is not necessarily equal to the email provider's thread ID. Use the returned Nudge ID in subsequent calls.

Step 4: Create a draft, not a sent email

curl -X POST 'https://app.nudgeforme.com/api/v1/drafts' \
  -H 'Authorization: Bearer YOUR_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: draft-proposal-20261111-001' \
  -d '{"threadId":"NUDGE_THREAD_ID","research":false}'

The API creates a follow-up draft for review in the supported workflow; it never sends the message. Set "research":true only where your plan and configured integrations support research-assisted drafting, and review any added context.

Step 5: Verify status and avoid duplicates

curl -G 'https://app.nudgeforme.com/api/v1/followups/status' \
  -H 'Authorization: Bearer YOUR_KEY' \
  --data-urlencode 'threadId=NUDGE_THREAD_ID'

For all write requests, use a unique identifier that meets the documented format. If a request times out, read back the status before retrying rather than generating a new key blindly. See the safe drafting workflow.

Real examples by industry

Agencies: Use a client-scoped key to produce a weekly list of pending approvals and prepare drafts only when a client manager selects a thread.

Sales teams: Find the proposal previously emailed from a rep's mailbox and create a polite reviewable follow-up after verifying the deal hasn't closed in the CRM.

Recruiters: Review unanswered candidate scheduling emails that you sent, excluding candidates who have opted out or already replied through another channel.

Operations: Track an invoice clarification or vendor document request and draft a reminder without changing a live invoice or payment system.

REST API versus MCP

Use the REST API for server scripts, n8n workflows, and internal dashboards. Use MCP if you want ChatGPT or Claude to triage your opportunities in a conversation. Both surfaces respect access controls; neither offers an email-send operation.

Frequently asked questions

Can I send cold email with this API?

No. A conversation must already exist in a connected mailbox and be eligible for monitoring. The API is not a cold outreach service.

Can I edit generated drafts through the API?

Not in this version. The API creates a draft that you review in the supported mailbox or application workflow.

Does NudgeForMe have an OpenAPI specification?

Yes. The REST API reference and developer platform document the supported operations.

If you only need wording for one reply, write a draft without setting up an integration.

GET USEFUL FOLLOW-UP TIPS

A better follow-up habit starts here.

Get practical email follow-up tips and occasional product updates. Just your name and email — no mailbox connection required.

Loading secure subscription form…

Subscribe only if you want these messages. Unsubscribe any time. See our Privacy Policy.

Missed a follow-up?
Scan free